Related
hello, i hope my thread didnt post somewhere else.
so, i am using hs2 and i installed android 2.2 yesterday and i installed 8 apps on it. everything is working perfect until i installed google eath. i run it and it says that i dont have enough space and it close.. i also remove many apps and i only have 50mb internal memory only. how do i clean android because i wanna install more apps soon!
also how many mb internal memory hd2 has?
is android installed on internal memory of my hd2 thats why its running low now??
thanks i hope to get what am looking for
USA T-Mobile HD2 - 1024MB ROM
Everywhere else - 512MB ROM
Which NAND build are you using? Perhaps it supports A2SD, A2SD+, data2ext, data2sd, if it does one of those, partitioning your MicroSD card and formatting the partition in ext2/ext3/ext4 will give you more space to install applications.
LiFE1688 said:
USA T-Mobile HD2 - 1024MB ROM
Everywhere else - 512MB ROM
Which NAND build are you using? Perhaps it supports A2SD, A2SD+, data2ext, data2sd, if it does one of those, partitioning your MicroSD card and formatting the partition in ext2/ext3/ext4 will give you more space to install applications.
Click to expand...
Click to collapse
wait wait wait i bought hd2 at 14/1 and i put android at 13/1 so am sooo noob on these what A2SD, A2SD+, data2ext, data2sd are?
how do i partition my sd? how do i format to ext...
i got 512rom btw uk one
thanks
This is the downside of using NAND rom, the internal memory is very low. My phone is showing about 120 MB available and still I permanent have the icon telling me low disk space.
So there is a solution and that is to partition the sd card? Are there any instructions for this available so it becames part of the OS?. I have searched but could not seem to find the proper thread.
BTW I am using the "desire stock rom":
http://forum.xda-developers.com/showthread.php?t=893620
Have a look at this one. Especially the instructions.
Or search the NAND Forum Titles for App2SD, Data2EXT, ext4, data.img or something like that.
lenarass said:
wait wait wait i bought hd2 at 14/1 and i put android at 13/1 so am sooo noob on these what A2SD, A2SD+, data2ext, data2sd are?
how do i partition my sd? how do i format to ext...
i got 512rom btw uk one
thanks
Click to expand...
Click to collapse
"-_- sweat -_-"
I am not going to explain what it is, but instead, I am gonna tell you what to look at. When choosing a ROM.
Example1:
[15 JAN] -=MDJ's CyanogenMod 7 v. 2.4 [A2SD+][GRH78][RMNET][Kernel: MDJ S10.4 OC]
See the wonderful [A2SD+] that means it uses A2SD+
Example2:
[16 JAN][DAF][ZIP] RAFDROID HD 2.2 [DATA2EXT][Kern:MDJ 10.3][RMNET][UPDATED!]
This uses data2ext
Example3:
[30 DEC][DFT]LEO "Stock Desire" NAND Android ROM
This doesn't use anything, so you are screwed... you run out of space, that's it, SCREWED.
I highly recommend that you read this, and understand what it says.
[10 JAN][RECOVERY] ClockworkMod Recovery for HD2 - v1.2
Because Clockwork makes things really easy for noobs, if you want to call yourself that. It is also used in every Android Devices that I know of, including the Real HTC DesireHD, Samsung Galaxy S, Samsung Nexus S, HTC Desire, and many more. HD2 users prefer people to do everything for them and package everything neatly, then complain about having to wipe everything away each update.
** [GUIDE] How to format SD-Card to EXT 3 **
bakskj, so yah, you have 120MB left. So unless you know how to put A2SD, A2SD+ or data2sd or data2ext into the ROM you are using now, pretty much, use that 120MB sparingly, that's all you will have.
LiFE1688 said:
"-_- sweat -_-"
I am not going to explain what it is, but instead, I am gonna tell you what to look at. When choosing a ROM.
Example1:
[15 JAN] -=MDJ's CyanogenMod 7 v. 2.4 [A2SD+][GRH78][RMNET][Kernel: MDJ S10.4 OC]
See the wonderful [A2SD+] that means it uses A2SD+
Example2:
[16 JAN][DAF][ZIP] RAFDROID HD 2.2 [DATA2EXT][Kern:MDJ 10.3][RMNET][UPDATED!]
This uses data2ext
Example3:
[30 DEC][DFT]LEO "Stock Desire" NAND Android ROM
This doesn't use anything, so you are screwed... you run out of space, that's it, SCREWED.
I highly recommend that you read this, and understand what it says.
[10 JAN][RECOVERY] ClockworkMod Recovery for HD2 - v1.2
Because Clockwork makes things really easy for noobs, if you want to call yourself that. It is also used in every Android Devices that I know of, including the Real HTC DesireHD, Samsung Galaxy S, Samsung Nexus S, HTC Desire, and many more. HD2 users prefer people to do everything for them and package everything neatly, then complain about having to wipe everything away each update.
** [GUIDE] How to format SD-Card to EXT 3 **
bakskj, so yah, you have 120MB left. So unless you know how to put A2SD, A2SD+ or data2sd or data2ext into the ROM you are using now, pretty much, use that 120MB sparingly, that's all you will have.
Click to expand...
Click to collapse
amazing post . bit i use LEO "Stock Desire" NAND Android ROM so am SCREWED . do i have to install NEW ROM ? and start downloading apss from the bigging? if yes what rom is the best ?xda-developers - Reply to Topic or RAFDROID HD 2.2 ?
whats the difference between these 3 roms? more available internal space?
thankss
Urm, it's hard to say what is the best. I guess look at the screen shot and choose the one that looks the most pleasing?
But you know what, now that you are starting again,
[10 JAN][RECOVERY] ClockworkMod Recovery for HD2 - v1.2
READ THAT... USE THAT...
Then choose a ROM that says CLOCKWORK
-=DOWNLOAD v. 2.4 A2SD+ NAND Clockwork Mod=-
Like that. This way, if you have a small little fix, you don't have to reflash the whole rom, some nice guy/girl might already post up the fix in a nice zip file that you can use clockwork to install.
LiFE1688 said:
Urm, it's hard to say what is the best. I guess look at the screen shot and choose the one that looks the most pleasing?
But you know what, now that you are starting again,
[10 JAN][RECOVERY] ClockworkMod Recovery for HD2 - v1.2
READ THAT... USE THAT...
Then choose a ROM that says CLOCKWORK
-=DOWNLOAD v. 2.4 A2SD+ NAND Clockwork Mod=-
Like that. This way, if you have a small little fix, you don't have to reflash the whole rom, some nice guy/girl might already post up the fix in a nice zip file that you can use clockwork to install.
Click to expand...
Click to collapse
thx but am too confuzed. i will wait for a better android that does everything without flashing again and again
lenarass said:
thx but am too confuzed. i will wait for a better android that does everything without flashing again and again
Click to expand...
Click to collapse
All of them do everything. Have you at least tried one?
hello00 said:
All of them do everything. Have you at least tried one?
Click to expand...
Click to collapse
flashed on nand the original desire android on my hd2. its 2.2ver and i cant save app on sd card. the other 2 ver are 2.3 android right? the last one?
PLEASE NOTE:
There are down sides to using app2sd and data on sd.... Namely you cannot mount the SD Card via usb.
The single best option for having a stable, low maintenance build is projections Stock desire, which has some squashing to reduce the space. HD builds are all flawed for 512mb users because of the size. You either have no space, or you cannot mount your sd card.
Based on that I would always go for a stock desire/evo based build, which give full functionality, but with ~180mb free space. Everybody is so quick to ask for data on sd.... but the corruption factor that is still there, combined with the inability to mount the drive, makes it a no go for many people who are starting out, and will be back on here in a few days asking why they are getting force closes, or why they cannot access SD card via usb.
Good comments
MattOG said:
PLEASE NOTE:
There are down sides to using app2sd and data on sd.... Namely you cannot mount the SD Card via usb.
The single best option for having a stable, low maintenance build is projections Stock desire, which has some squashing to reduce the space. HD builds are all flawed for 512mb users because of the size. You either have no space, or you cannot mount your sd card.
Based on that I would always go for a stock desire/evo based build, which give full functionality, but with ~180mb free space. Everybody is so quick to ask for data on sd.... but the corruption factor that is still there, combined with the inability to mount the drive, makes it a no go for many people who are starting out, and will be back on here in a few days asking why they are getting force closes, or why they cannot access SD card via usb.
Click to expand...
Click to collapse
First off thanks for the informative replies. I think I'm gonna go for a partitioned one because more space is essential for me.
What i do want to know is. Is there a fix for those eventual crashes and what not? And if they are really to annoying. Because nothing beats stability.
I know I should not be starting a new thread, but I think this is relevant. Many of us here are using some sort of popular method of increasing our data storage, be it either firerats or data2ext. I will submit that they are both very useful, and I personally use data2ext v2, and it works excellent for me with a nominal setup problem. I have also done firerats, which I believe is good for some folks, but just not worth the effort and tweaking for me. Data2ext is easier for me to set up and maintain between ROMS, never had market issues, and my space that I set is constant (I currently work with a half gig, gives me plenty of app room). I would be interested in any discussions which validate firerats as the better choice given a specific situation. The bottom line is I know we all have our preferences, but make an argument why one is better than the other. The newer guys want to ask, but are afraid to. State your case.
FTW.....this thread makes sense because i cant make sense of which one to use. firstly because all attempts have ended in bootloops, secondly whenever i did think i got it going and checked stats nothing changed (obviously my fault) but after several dozen attempts you start to lose faith and don't want to ask questions because you get dragged across the coals for asking hows and why's. I use Amon Ra 1.6 / Asop mod 3/7, S-Off unrevoked method, "ondemand gov / min 267-max 710, JIT enabled, Comp Cache 18%, VM is at 32, CWM 3, Titanium B is my best friend, Radio is 2.42.02.10.29, Class 6 16 GB SD Card, partitioned thru Amon recovery "0" swap/ 1024 on ext4. fix permissions thru CWM after every new ROM update and reboot, every new update i wipe dalvik cache 3 times, only flash Gapps if its updated, i reboot (pull battery/ bootloader reset device/ reboot thru recovery at least 4-6 times before getting nervous, nandroid back up, nandroid back up, nandroid back up, I have SDK etup on my MAC, ADB only works using "./fastboot" commands which are limited on information on the internet, signed many consent forms stating that i hold no-one responsible for my learning curve and that any modifications to my phone might potentially set my phone on fire and unleash lucifer on orphaned blind babies ....obviously i have kept up and read alot of the forum extensively but yes the new guys would like a hand once in a while, the language is difficult and the native are at times are restless., yes i like learning something new and yes i like being taught, yes i want to breathe life into it, yes i want to see incredible benchmarks that make my phone proud, yes i want to see ridiculous battery life to brag, yes iwant to do all i can to see my old dog do new tricks, Yes I love my hero..... <whew> apologies for the rant but had to let it out... i will be reading this post quite a bit if questions can be answered with patience. ;-p
@cortacana
Well I don't think your recovery supports ext4 with 1.6 RA. If you want to use data2ext. Try ext2 and RA1.7 and down grade your ext to ext2. And if your going to use firerats you don't need your sd/card partitioned. If you want to use data2ext ext 4 your ext is correct but I think you need the newer cwm recovery that supports ext4 I think or RA1.7 Well hope this helps. Good luck.
Yea its me Again With the
Modified Hero-
laie1472 said:
@cortacana
Well I don't think your recovery supports ext4 with 1.6 RA. If you want to use data2ext. Try ext2 and RA1.7 and down grade your ext to ext2. And if your going to use firerats you don't need your sd/card partitioned. If you want to use data2ext ext 4 your ext is correct but I think you need the newer cwm recovery that supports ext4 I think or RA1.7 Well hope this helps. Good luck.
Yea its me Again With the
Modified Hero-
Click to expand...
Click to collapse
i will try all that. where do you find RA 1.7 havent spied that anywhere
cortacanya said:
i will try all that. where do you find RA 1.7 havent spied that anywhere
Click to expand...
Click to collapse
found it. i took my thumb out my butt and used this thing called "google"
cortacanya said:
found it. i took my thumb out my butt and used this thing called "google"
Click to expand...
Click to collapse
Lmao. If you need any help and your trying one of the methods just pm me or post here slow night at work so I'll be here for a while. Good luck
Yea its me Again With the
Modified Hero-
i have a slide 3g.....8 gig micro sd card...how can i do the data2ext mod?.....I really need basic step by step instructions..this stuff is confusing me......is there a tutorial somewhere?...please help....lol Im not dumb...but I aint too savvy with phones......now computers are another thing...those I understand well.....but not commands and such...TIA....Dirty
dirtylarry10 said:
i have a slide 3g.....8 gig micro sd card...how can i do the data2ext mod?.....I really need basic step by step instructions..this stuff is confusing me......is there a tutorial somewhere?...please help....lol Im not dumb...but I aint too savvy with phones......now computers are another thing...those I understand well.....but not commands and such...TIA....Dirty
Click to expand...
Click to collapse
This is about the best resource there is: http://romrepo.info/wiki/index.php?title=Enable_data2ext
FWIW...
I tried data2ext set at 512M with aospCMod and CM7 RC2. The phone reported it had 473M. It worked fine for a day or two, then I started getting all kinds of FC, especially with Google Maps, and several apps just started failing to open.
So I switched over to Firerat's with CM7 RC2 and haven't looked back. I've got 340M for apps, but it seems much more stable.
It could very well be that my sd card simply won't support having my /app partition on it (although it did fine with the app2sd function that came with CM6).
Cheers
I had the same problem and have been meaning to do firerats. How simple is it to set up?
Sent from my HTC Hero CDMA using XDA App
cmason1015 said:
FWIW...
I tried data2ext set at 512M with aospCMod and CM7 RC2. The phone reported it had 473M. It worked fine for a day or two, then I started getting all kinds of FC, especially with Google Maps, and several apps just started failing to open.
So I switched over to Firerat's with CM7 RC2 and haven't looked back. I've got 340M for apps, but it seems much more stable.
It could very well be that my sd card simply won't support having my /app partition on it (although it did fine with the app2sd function that came with CM6).
Cheers
Click to expand...
Click to collapse
The instructions state the recommended partition is 1024 and you tried 512 could be your reason for fc's. And did you try ext2 or ext4?? I've been using ext2 with and I have my partitions at
1024 ext2 swap 0 and the rest fat. That gives me 0.94gb of internal mem and I've had not one problem. But a all phone are different.
Yea its me again with the
Modified Hero
laie1472 said:
The instructions state the recommended partition is 1024 and you tried 512 could be your reason for fc's. And did you try ext2 or ext4?? I've been using ext2 with and I have my partitions at
1024 ext2 swap 0 and the rest fat. That gives me 0.94gb of internal mem and I've had not one problem. But a all phone are different.
Yea its me again with the
Modified Hero
Click to expand...
Click to collapse
I used ext4 and got the same issue. I may try ext2 and see how it works.
AjaxBU said:
I used ext4 and got the same issue. I may try ext2 and see how it works.
Click to expand...
Click to collapse
Ext2 is faster especially with the boost.
Yea its me again with the
Modified Hero
laie1472 said:
Ext2 is faster especially with the boost.
Yea its me again with the
Modified Hero
Click to expand...
Click to collapse
Seems a lot easier to set up too
AjaxBU said:
Seems a lot easier to set up too
Click to expand...
Click to collapse
Yup easy and simple. If your going to try it tonight and you run into any problems let me know I'll be online for a while. If I can help I will.
Yea its me again with the
Modified Hero
Thanks, I started to do it then realized that I had CM recovery 2.5.0.7...which doesn't have the option to partition the sdcard.
AjaxBU said:
Thanks, I started to do it then realized that I had CM recovery 2.5.0.7...which doesn't have the option to partition the sdcard.
Click to expand...
Click to collapse
Just flash the newer one or flash Darchs's /RA1.7 if you don't like it you can always just go back.
Yea its me again with the
Modified Hero
Thanks for your help, I just went through with the backups, changed recoveries, and did a full wipe before I updated. Unfortunately I ran into some problems with gapps, and had to do it all over again. Anyway, as of now data2ext2 is working. Hopefully this will work better than the ext4.
AjaxBU said:
Thanks for your help, I just went through with the backups, changed recoveries, and did a full wipe before I updated. Unfortunately I ran into some problems with gapps, and had to do it all over again. Anyway, as of now data2ext2 is working. Hopefully this will work better than the ext4.
Click to expand...
Click to collapse
Nice. Good Modding to get it working. A did you do the boost as well????
Yea its me again with the
Modified Hero
laie1472 said:
Nice. Good Modding to get it working. A did you do the boost as well????
Yea its me again with the
Modified Hero
Click to expand...
Click to collapse
Never heard of the boost what do I need to do? And for what it's worth I didn't see an increase in quadrant scores. Class 4 card. Not that I care, since quadrant scores mean nothing but is that normal?
Hi,
I just bought a nook color. I'm trying to install nightly cm9 on it. i have been reading and i have some questions .. please help i don't wanna turn my new nook into paperweight lol. I understand i need to make a bootable sd card with CWR on it. i understand there are newer version CWR out there now but I am only able to find 4gb version of 3.0.2.8. Will that cause a problem ? Do i have to use 4gb version CWR? I can find 1gb CWM 3.2.0.1 ( i have a 4g micro sd card ). About wiping, i know with android phones you always wipe before you flash roms but i have been reading, posts suggest to wipe cach and dalvik AFTER flashing cm and gapps. Is that the correct order to wipe? [GUIDE] Install CM7 or CM9(!) + Clockworkmod to EMMC - ALL NOOKS! (Updated:1/16/12) - xda-developers This post don't even mention wiping dalvik. So what exactly should i wipe and in what order? Also in that post it says after you flash, without rebooting you are to remove sd card and format it on a computer... since its a bootable CRW, the nook color doesnt even have the recovery on it , will removing the sd just cause it to crush ? Please help ~ Thank you.
Best advice is to go to the "development forum" and read the CM9/ICS nightly thread.Everything you need is in the first post.I would suggest you test your SD card with CrystalDiskMark 3.0(free program,google it up)first to see if it is suitable for a ROM install.
See the SD card strange thread in this forum first.
Don't worry too much about bricking your Nook Color. It is pretty much impossible to get it in a state which you can't recover from as it has priority on booting from the SD card.
That's not say you shouldn't try to get it right to avoid any hassle.
For an internal install use the Eyeballer SD clockwork recovery method as detailed in the development forum. When you image this to an SD then you always end up with a 1GB partition on the card irrespective of the real SD size. Don't worry about that as this is just a staging post and you just need space to put on the zips you want to install.
For CM9 use the "unofficial" nightly builds and put the main ROM, Gapps, and the telephony permissions fix on.
When you boot from this card you will be in Clockwork recovery. First time you want to format system, data, and cache then install ROM, Gapps and telephony fix in that order.
After that you want to put in a cleanly formatted single partition SD card, either by reformatting partitioning the installation one or a different one if you wanted to keep the original. It won't crash but some apps expect the Sd card to be present.
Once rebooted then you should be in CM9. You can install clockwork recovery to the internal memory as well by using the ROM Manager app. This means that if you reboot with the N key held down you get into a boot menu and can choose to go into recovery. That is very convenient for subsequent updates as you can just copy zips onto the SD card via USB or Wifi without having to remove the card (ES File Explorr app helps a lot here).
For small updates you can normally just format system and cache then reapply the set of zips. This will leave your set up and installed apps alone. You don't need to do Dalvik separately as it is in the cache partition.
Thanks and what is the "telephony permission fix" ?
bobtidey said:
Don't worry too much about bricking your Nook Color. It is pretty much impossible to get it in a state which you can't recover from as it has priority on booting from the SD card.
That's not say you shouldn't try to get it right to avoid any hassle.
For an internal install use the Eyeballer SD clockwork recovery method as detailed in the development forum. When you image this to an SD then you always end up with a 1GB partition on the card irrespective of the real SD size. Don't worry about that as this is just a staging post and you just need space to put on the zips you want to install.
For CM9 use the "unofficial" nightly builds and put the main ROM, Gapps, and the telephony permissions fix on.
When you boot from this card you will be in Clockwork recovery. First time you want to format system, data, and cache then install ROM, Gapps and telephony fix in that order.
After that you want to put in a cleanly formatted single partition SD card, either by reformatting partitioning the installation one or a different one if you wanted to keep the original. It won't crash but some apps expect the Sd card to be present.
Once rebooted then you should be in CM9. You can install clockwork recovery to the internal memory as well by using the ROM Manager app. This means that if you reboot with the N key held down you get into a boot menu and can choose to go into recovery. That is very convenient for subsequent updates as you can just copy zips onto the SD card via USB or Wifi without having to remove the card (ES File Explorr app helps a lot here).
For small updates you can normally just format system and cache then reapply the set of zips. This will leave your set up and installed apps alone. You don't need to do Dalvik separately as it is in the cache partition.
Click to expand...
Click to collapse
Found the telephony fix thanks
A bit of unsolicited advice: if you are having these kinds of problems, then I suggest CM9 is not baked enough for you, and you may be much better off with a far more stable and better-documented CM7.x install. I am not being condescending... I myself am quite capable of extreme hacking and tolerant of an array of stability issues, being a Linux software engineer, but I just don't have the time or energy to put into making CM9 work right now, given the quantity of issues. For the hardcore Android hobbyist, CM9 is the way to go right now. For a NC user wanting a functional Android tablet, I say wait a little bit.
You might consider simply using the SD card boot ROM's, and leaving the internal Nook alone for the present. That would allow you to try out the various Rom's available and find one that works best for you. I'm currently running CM7.2 Kang on my emmc partition, but booting on SD card from the CM9 nightly builds. The CM7.2 Kang is quite stable, but not as much fun as the alpha ICS CM9 stuff. Best of both worlds.
I already have cm7 on my phone , hopefully its not gonna be the same thing lol . i was hoping to put cm9 on there so it will entertain me for a while but if its really that buggy mb i will consider just running on cm7.
mr72 said:
A bit of unsolicited advice: if you are having these kinds of problems, then I suggest CM9 is not baked enough for you, and you may be much better off with a far more stable and better-documented CM7.x install. I am not being condescending... I myself am quite capable of extreme hacking and tolerant of an array of stability issues, being a Linux software engineer, but I just don't have the time or energy to put into making CM9 work right now, given the quantity of issues. For the hardcore Android hobbyist, CM9 is the way to go right now. For a NC user wanting a functional Android tablet, I say wait a little bit.
Click to expand...
Click to collapse
Thanks. I already have bobzhome 7.2 on my phone. The reason why i wanna cm* on my nook is because i don't read(i read enough for school XD ) haha so the nook factory rom will be kinda pointless for me. Also just booting from sd and flashing roms seem really straight forward to me so that's why i want to flash cm* on internal memory. As im not that knowledgeble about nook colors, running on a bootable rom still seem complicated for me but i sure will think about it .
brentb636 said:
You might consider simply using the SD card boot ROM's, and leaving the internal Nook alone for the present. That would allow you to try out the various Rom's available and find one that works best for you. I'm currently running CM7.2 Kang on my emmc partition, but booting on SD card from the CM9 nightly builds. The CM7.2 Kang is quite stable, but not as much fun as the alpha ICS CM9 stuff. Best of both worlds.
Click to expand...
Click to collapse
when i was downloading cm7 roms , my anti virus kept saying there were viruses in the roms ... is that normal ?
optimusv45 said:
when i was downloading cm7 roms , my anti virus kept saying there were viruses in the roms ... is that normal ?
Click to expand...
Click to collapse
How many places you going to ask this?
It is a false positive.
Normal? No. Crappy antivirus? Yes.
As long as you are downloading from links from the developers here you're safe.
Sent from my NookColor using XDA App
just making sure since im not very knowledge about nook colors. i rather ask more than do something stupid on my device and cause myself problems.
Benzoman said:
How many places you going to ask this?
It is a false positive.
Normal? No. Crappy antivirus? Yes.
As long as you are downloading from links from the developers here you're safe.
Sent from my NookColor using XDA App
Click to expand...
Click to collapse
No problem. Just noticed it was in a separate thread already.
Please post what A/V you are talking about so others having the same issue will take note.
I'll also give a +1 to the people who suggested that you work off an SD card until you are really comfortable with the process. You can always recover your Nook, but why go through that hassle when the SD card is so easy.
Just my $.02
Dual booting SD
I agree with try the Dual boot off the SD card to see what you like. Check out http://forum.xda-developers.com/showthread.php?t=1000957Verygreens process was simple to follow and I am newer at rooting also. Cheers.
I posted what a/v already. its kaspersky internet security. i guess i never look into running off SD. I don't read much so i just don't need nook color stock ROM, i guess that's also part of why i wanna run on internal memory. oh and i bought a refurbished nook color from BNs website and it came defective. part of the screen didn't work. To those who wanna buy it from them i suggest to buy from a retail store so u don't have to pay shipping and waste time I think all they did was a factory restore on a return and sell it again for 149.
TL2000 said:
Please post what A/V you are talking about so others having the same issue will take note.
I'll also give a +1 to the people who suggested that you work off an SD card until you are really comfortable with the process. You can always recover your Nook, but why go through that hassle when the SD card is so easy.
Just my $.02
Click to expand...
Click to collapse
Im gonna buy a new nook color and i read that newer ones have different hardware. newer hardware aren't supported by CM7. I guess I'll have to try a nightly CM9 build.
The1Power said:
I agree with try the Dual boot off the SD card to see what you like. Check out http://forum.xda-developers.com/showthread.php?t=1000957Verygreens process was simple to follow and I am newer at rooting also. Cheers.
Click to expand...
Click to collapse
will CM7 work on a new nook color? i have read that it doesn't have some needed drivers.
mr72 said:
A bit of unsolicited advice: if you are having these kinds of problems, then I suggest CM9 is not baked enough for you, and you may be much better off with a far more stable and better-documented CM7.x install. I am not being condescending... I myself am quite capable of extreme hacking and tolerant of an array of stability issues, being a Linux software engineer, but I just don't have the time or energy to put into making CM9 work right now, given the quantity of issues. For the hardcore Android hobbyist, CM9 is the way to go right now. For a NC user wanting a functional Android tablet, I say wait a little bit.
Click to expand...
Click to collapse
optimusv45 said:
will CM7 work on a new nook color? i have read that it doesn't have some needed drivers.
Click to expand...
Click to collapse
I just bought my nook color Dec. 30th, 2011 and I have ran cm7 as well as cm9. Like the others are saying, set up cm7 off of a SD card until you learn what you are doing then consider moving to the emmc.
optimusv45 said:
will CM7 work on a new nook color? i have read that it doesn't have some needed drivers.
Click to expand...
Click to collapse
I believe that is CM9, not 7 that was having issues with the new nook color touch screen drivers.
Here's a post about it:http://forum.xda-developers.com/showthread.php?p=21333209&highlight=touchscreen#post21333209
Looks like it may already be fixed: http://forum.xda-developers.com/showthread.php?p=21353661&highlight=touchscreen#post21353661
Hey guys, I;m appealing for a little help here.
I have an HTC HD2 which has been great for about a year but all of a sudden it has problems.
I;ve been using this rom pretty much since it came out....
http://forum.xda-developers.com/showthread.php?t=905060
I;ve never had any problems with it untill now. I started to get the "insufficient storeage space available" message on it so I assumed a restore/reflash would solve the problem.
I used HD2 toolkit to resize my MAGLDR partition to 450MB & reflashed - the phone wouldnt boot. Stuck on the HTC logo.
Repartitioned to 400 - still no boot!
Repartitioned to 350 - still no boot!
Repartitioned to 300MB - phone now boots however now, I;ve installed no apps & when I try to install spotify, its telling me insufficient storeage available, again! With nothing on the phone except the ROM!
I'm a bit of a n00b with all this stuff, but had my HD2 running fine for ages & its frustrating me that now it wont work properly!
Anyone care to help? THanks, Cardz.
Edit: im using MAGLDR 1.13 & the latest Clockwork mod to flash the ROM. I'm wiping cache & data partitions every time...... :/
Install it with as lower as possible space for system partition. In your case it shoud be 135MB of system partition and 2MB cache but I recommend to put some more of space for system partition as I had some problems with low system partition so you can put 150MB for system partition.
The simple explanation of why you dont have enough of space for apps is that you gave too much of space for system partition and simply this ROM does not require that much of space for system partition. And other space left in your phone memory will be used for apps etc.
EDIT: And also try to install MAGLDR and CWM manually if you can and when you install CWM edit flash.cfg in WordPad or other text editing tool before you flash CWM and edit system partition size to 150MB and Cache size to 2MB
jan.selep said:
EDIT: And also try to install MAGLDR and CWM manually if you can and when you install CWM edit flash.cfg in WordPad or other text editing tool before you flash CWM and edit system partition size to 150MB and Cache size to 2MB
Click to expand...
Click to collapse
Thanks a lot for the reply, i understand now about the 150MB/2MB cache, but what is the point of this other bit? Could you explain more the purpose of this?>
cardyology said:
Thanks a lot for the reply, i understand now about the 150MB/2MB cache, but what is the point of this other bit? Could you explain more the purpose of this?>
Click to expand...
Click to collapse
Well to simply explain you why i wrote you to use manual installation of CLOCKWORKMOD RECOVERY was that I wanted to explain you how is it working with partitioning your nand memory using cwr or magldr. I just added some helpfull info for you from my experience with HD2 and android flashing. So in the future you will know what to do and you will be able to uderstand more from technical point of view about flashing etc. I just wanted.to share some of my experience with you
But it is up to you if you want to use hd2 toolkit or manual configuration.
Sent from my HTC HD2 using xda premium
You can also use 4ext recovery instead of clockwork...
Sent from my HTC HD2 using xda premium
Afaik it's better to post in a similar topic than create a new one, so here I go.
I have recently switched to an ICS NAND rom and since then I keep having constant storage problems. I understand that in order to solve that I have to partition my SD card but it seems, since I don't really understand the whole android storage management process too deeply, I am not doing things properly cause I keep getting "Low on space" notifications. I attach some screenshots below in order to give you more info about my sd card partitions and rom specs. Please let me know what I did wrong and how I can solve it. I understand I will probably need to repartition and reflash the devide again?
Edit: The screenshots I have attached don't have 2nd part mounted, going to upload proper screens in a minute. Done.
Edit 2: Will this fix my problems?
(cant post proper links yet)
wwwDOTjayceooiDOTcom/2011/12/26/how-to-create-custom-clockworkmod-recovery-partition-size-for-htc-hd2/
You are mixing different things. In the first post of this thread the issue was the partitioning of the internal Flash-ROM in the Phone.
You wrote about the SD card partitioning and these things are totally different.
I think, you have a problem with your internal memory and you have to try the same things like cardyology has done after the hint from jan.selep.
Partitioning for Ubuntu's users
I don't find the way to modify partitioning of the internal Flash-ROM when you are an Ubuntu user on PC (no Windows boot anywhere..)
Monolecte said:
I don't find the way to modify partitioning of the internal Flash-ROM when you are an Ubuntu user on PC (no Windows boot anywhere..)
Click to expand...
Click to collapse
If you use cLK instead of magldr you can repartition from the cLK bootloader, , no PC necessary.
Before you say 'I cant install cLK without a PC', there is a version of cLK you can flash from sd card.
It will mean you have to resinstall your rom, though.
I believe more simple to find a Windows PC...
dont see why it should take any more than 25 minutes to accomplish, properly prepared.
samsamuel said:
dont see why it should take any more than 25 minutes to accomplish, properly prepared.
Click to expand...
Click to collapse
Hummmm because the Murphy's law? :crying:
I found a Windows PC, I downloaded the HD2 Toolkit... but not the good one, because the last version don't works with 32 bits PC. So, I found the good one, I saved all my stuff, I tried to repartition and... I miss a dll and other bull****... 2 hours later, I thought is too long to be good and I sought a lighter ROM (I understood Hyperdroid CM7 has a 150 Mo system partition : it's very short!), but, I found nothing with ICS or JB, only GB... pfff.
So, I took a week to flash ROM, I read miles of thread, hours to understand how my device working and each time I found a solution, each time I have at less a new issue to solve. It pissed me of.
Monolecte said:
Hummmm because the Murphy's law?
Click to expand...
Click to collapse
Haven't you heard? Murphy was an optimist!
---
If you have a 50% chance of being right, you will be wrong 90% of the time...
NYLimited said:
Haven't you heard? Murphy was an optimist!
---
If you have a 50% chance of being right, you will be wrong 90% of the time...
Click to expand...
Click to collapse
You're right : I did it!!!
Miles of threads here was usefull indeed!
I won against the machine!
Youpi!
Monolecte said:
You're right : I did it!!!
Miles of threads here was usefull indeed!
I won against the machine!
Youpi!
Click to expand...
Click to collapse
CONGRATULATIONS! I love a happy ending!
And, if you read only 10% of the posts some of us read your would find it rather refreshing too!
---
If you have a 50% chance of being right, you will be wrong 90% of the time...
Hey Guys,
I asked @kokotas to help me figure out a way to make a Patch to extend the Internal Memory as for me, due to the size of the high-end Applications and Games, is too limited 16GB, 11,70GB available only, on our Z1.
So my first Idea was to sacrifice 16Gb Internal Memory and use 64GB External SD Memory formatted in EXT4 where all the Data will be stored.
To do so we have to understand few thing and how is the structure of the Z1 Kernel is made and try to extract "ramdisk.cpio" where we can edit "init.rc" and change the line "/data mount"
As for the kernel "Autopsy" we used @krabappel2548 kernel build, I hope he is fine with that.
From what we know, the recovery is injected in the boot.img and this makes things more complicated.
Are all kernels built in this way? Even the stock ones?
Also, is there a specific rule in the way of naming the included ramdisks?
I attached a picture to make things more clear.
Any help will be appreciate.
eclyptos said:
Hey Guys,
I asked @kokotas to help me figure out a way to make a Patch to extend the Internal Memory as for me, due to the size of the high-end Applications and Games, is too limited 16GB, 11,70GB available only, on our Z1.
So my first Idea was to sacrifice 16Gb Internal Memory and use 64GB External SD Memory formatted in EXT4 where all the Data will be stored.
To do so we have to understand few thing and how is the structure of the Z1 Kernel is made and try to extract "ramdisk.cpio" where we can edit "init.rc" and change the line "/data mount"
As for the kernel "Autopsy" we used @krabappel2548 kernel build, I hope he is fine with that.
From what we know, the recovery is injected in the boot.img and this makes things more complicated.
Are all kernels built in this way? Even the stock ones?
Also, is there a specific rule in the way of naming the included ramdisks?
I attached a picture to make things more clear.
Any help will be appreciate.
Click to expand...
Click to collapse
1. Sony doesn't have a recovery partition in their phones hence developers add the recovery in the ramdisk. Also stock sony kernels doesn't have a recovery included by default only bootloader/flashmode.
2. You can't adjust the 16gb internal partition without diving deeply into the bootloader. The NAND partition profiles are hardcoded in the bootloader so modifying even just a little bit of info in the partition of the NAND would brick your device. The only way I could possibly suggest to try is hijacking the fstab and ramdisk to unmount the internal storage and mount the external storage on init. But if your issue is only about disk space I suggest you leave the internal storage and just symlink the obb folder instead of hijacking the whole internal storage. And BTW the disk IO of the internal storage is worlds apart compared to your microsd card no matter what class it is so it would be very unefficient if you use your microSD card as internal. IMHO reading the dalvik-cache 1 by 1 on startup would be pretty slow! Same goes for reading the byte code of an app once you open it.
Riyal said:
1. Sony doesn't have a recovery partition in their phones hence developers add the recovery in the ramdisk. Also stock sony kernels doesn't have a recovery included by default only bootloader/flashmode.
Click to expand...
Click to collapse
We know that. If there will be a Partition for recovery it will be much more easy and safe. That why we also used a Kernel with recovery implemented.
Riyal said:
2. You can't adjust the 16gb internal partition without diving deeply into the bootloader. The NAND partition profiles are hardcoded in the bootloader so modifying even just a little bit of info in the partition of the NAND would brick your device.
Click to expand...
Click to collapse
We trying and this is the risk of everybody who flashing a Custom Kernel.
Riyal said:
The only way I could possibly suggest to try is hijacking the fstab and ramdisk to unmount the internal storage and mount the external storage on init. But if your issue is only about disk space I suggest you leave the internal storage and just symlink the obb folder instead of hijacking the whole internal storage.
Click to expand...
Click to collapse
Maybe not the whole internal storage but implement the external SD with the internal?
Riyal said:
And BTW the disk IO of the internal storage is worlds apart compared to your microsd card no matter what class it is so it would be very unefficient if you use your microSD card as internal. IMHO reading the dalvik-cache 1 by 1 on startup would be pretty slow! Same goes for reading the byte code of an app once you open it.
Click to expand...
Click to collapse
I know the difference between Internal and External Storage. Yes the internal bandwidth is higher but like I said is worth the sacrifice, or try. Best solution will be System and Apk on Internal and link the SD to use there all Data. This is more efficient that a third Apps like Link2sd or kind of. BTW, I don't think it will be so slow but we have to try. The idea have to be made to improve what next.
So we need more Ideas, do you have any?
We know that. If there will be a Partition for recovery it will be much more easy and safe. That why we also used a Kernel with recovery implemented.
We trying and this is the risk of everybody who flashing a Custom Kernel.
A: This isn't about risk this is a fact. Once you successfully manage to alter the partition table of the built in NAND you're sure to get a hard brick from doing this.
Maybe not the whole internal storage but implement the external SD with the internal?
A: Implementing internal storage with external to support it is possible but limited. Like I said you could symlink the obb and Android folder to the external storage. That way you can allocate some of the storage space to data, dalvik etc. and the data files to the external SD which uses the most resources.
Hmm, changing the partition table has been successfully done on the xperia T
http://forum.xda-developers.com/showthread.php?t=2147997
I am not an expert here, but is this what you are talking about,
What benefit would this give a user?
Sent from my C6903 using xda app-developers app
gregbradley said:
I am not an expert here,
Click to expand...
Click to collapse
Me either, @kokotas is the Master here and all thanks should go to him for help me with this, actually the picture is of his work.
gregbradley said:
Hmm, changing the partition table has been successfully done on the xperia T
http://forum.xda-developers.com/showthread.php?t=2147997
Click to expand...
Click to collapse
We do not try to repartitioning the Sony Z1 internal memory to get a recovery bootable from different partition, which still a very good idea to develop for Z1. We try to mount the External SD instead of the Internal to expand the storage for the Z1, and here we need a patch. If kind of patch like that will really work, with some help, anyone just will format the SD in EXT4 and use what like he like, 32/64GB.
So we will be glad even to involve more "Programmers" to help us make it true.
So any way to let this work?
Jay794 said:
What benefit would this give a user?
Click to expand...
Click to collapse
Expand storage. You will be able to format a 64GB, micro SD in 2 Partitions and use 32GB by the System and 32GB like a normal SD, for example, and it will be managed by the system and not by Apps. So instead of 11,70GB you will have 30GB in System.
Surely this will just make accessing the SD card data really slow? Even with a class 10 running games off the SD card would be laggy as hell
Sent from my C6903 using xda app-developers app
Jay794 said:
Surely this will just make accessing the SD card data really slow? Even with a class 10 running games off the SD card would be laggy as hell
Click to expand...
Click to collapse
Thank you for your Opinion. Is not your problem.
Expert Request Please..
Can someone who know more than me just have a look on the attachment and answer few question, unanswered form post 1.
..for Z1
1) Are all kernels built in this way? Even the stock ones?
2) Also, is there a specific rule in the way of naming the included ramdisks?
3) Do all kernels use the sbin folder?
4) Is ramdisk.cpio the default name used in all kernels
Hey, I support the idea, I just don't see how useful it will be
Sent from my C6903 using xda app-developers app
gregbradley said:
Hmm, changing the partition table has been successfully done on the xperia T
http://forum.xda-developers.com/showthread.php?t=2147997
I am not an expert here, but is this what you are talking about,
Click to expand...
Click to collapse
Yes it is possible but not easy... I'm pretty sure the dev that made that had a hard time before he successfully got it. Also I'm pretty sure he has a JTAG box so in case his phone got hard bricked he can easily fix it again. Also IMHO that was already patched by sony on the latest s1boot so I'm sure it's alot harder than before.
Riyal said:
Yes it is possible but not easy... I'm pretty sure the dev that made that had a hard time before he successfully got it. Also I'm pretty sure he has a JTAG box so in case his phone got hard bricked he can easily fix it again. Also IMHO that was already patched by sony on the latest s1boot so I'm sure it's alot harder than before.
Click to expand...
Click to collapse
Yes, he did brick his Xperia T a few times, and the LK kernel was never really taken up because of the risks.
But it does show that it was possible to change the partition table.
As for on the xperia Z1, I don't know
gregbradley said:
Yes, he did brick his Xperia T a few times
Click to expand...
Click to collapse
I can do that.
Only problem with having the SD used all the time for system files is the risk of corruption and or a failed card.
Saying that I had it on the S3 and it worked brilliantly, was a relatively simple script which required init'd support from a custom kernel.
In all fairness, after using folder mount the worries i've had with my internal memory have gone, i'm always over 10GB of space with several really big games installed which would easily take over the whole internal memory.
dladz said:
Only problem with having the SD used all the time for system files is the risk of corruption and or a failed card.
Click to expand...
Click to collapse
Here you sound like Google.
dladz said:
Saying that I had it on the S3 and it worked brilliantly, was a relatively simple script which required init'd support from a custom kernel.
Click to expand...
Click to collapse
I had it on HD2 as well and never had any issues and I had full control of my device, this is what also we looking at, no restrictions and no storage limit on a high-end device. I will be glad to see 64GB recognized as my System Storage instead using Apps on Apps like the Mount Folder.
I play Most Wanted, of curse a bit slow, on mine HD2 so if we get this work we will have 40mb/s in writing and reading, instead of 70mb/s in internal, due to the limitation of the slot. I think even with a kind of transfare like that you will never see any slow down of the performance on your device.
Some Smart One will say now to me "Why then you don't go back to HTC". That's the point! Imagine have Z1 with such a Development and full control of you device.
At last it's a choice of the user if he want apply that patch or not, but I think if this will be possible many will be happy, but like I can see, we don't have much support due to the risk and any Developer will not take this in consideration, or maybe will, but apparently not now.
eclyptos said:
Here you sound like Google.
I had it on HD2 as well and never had any issues and I had full control of my device, this is what also we looking at, no restrictions and no storage limit on a high-end device. I will be glad to see 64GB recognized as my System Storage instead using Apps on Apps like the Mount Folder.
I play Most Wanted, of curse a bit slow, on mine HD2 so if we get this work we will have 40mb/s in writing and reading, instead of 70mb/s in internal, due to the limitation of the slot. I think even with a kind of transfare like that you will never see any slow down of the performance on your device.
Some Smart One will say now to me "Why then you don't go back to HTC". That's the point! Imagine have Z1 with such a Development and full control of you device.
At last it's a choice of the user if he want apply that patch or not, but I think if this will be possible many will be happy, but like I can see, we don't have much support due to the risk and any Developer will not take this in consideration, or maybe will, but apparently not now.
Click to expand...
Click to collapse
I actually probably will be going back to HTC after this phone. Doubt it'll be the M8, although i do like it, the camera is sup par though and i've come accustomed to a decent picture.
dladz said:
I actually probably will be going back to HTC after this phone. Doubt it'll be the M8, although i do like it, the camera is sup par though and i've come accustomed to a decent picture.
Click to expand...
Click to collapse
I know, I try to don't give up on it too but to much to deal with. The camera is good but I was disappointed anyway. So I was thinking about 64GB HTC One, or wait for the next release and I will finally be fine. For the moment I try to deal with Z1, I hope somewhere we will have 64GB system storage , this maybe will change my mind, everything is possible.
eclyptos said:
I know, I try to don't give up on it too but to much to deal with. The camera is good but I was disappointed anyway. So I was thinking about 64GB HTC One, or wait for the next release and I will finally be fine. For the moment I try to deal with Z1, I hope somewhere we will have 64GB system storage , this maybe will change my mind, everything is possible.
Click to expand...
Click to collapse
Have you used folder mount before? It really is a great app and i've not needed the larger internal storage since using it.