I'm bored because the UOT Kitchen is down so since I flashed CM7 only a couple of days ago, and pretty much like it, I thought I'd also now take the plunge and flash the CM7 r2 HBOOT but I have a couple of questions first:
1) I've read the instructions on Alpharev site but still confused by the partition table. Do I somehow have to change the various system/data/cache size before flashing the HBOOT, or am I right in thinking that when I flash the HBOOT this will automatically resize them as part of the flash process?
2) What's the benefit of flashing this particular HBOOT? Is it because it'll increase system partition due to the number of apps? (noticed much less available space since swapping from LeeDroid)
and (yes I know I said only "a couple" of questions but...)
3) % chance of bricking my phone???
1. It will automatically resize the partition tables.
2. More space on data partition for apps.
3. None if you do it properly and check the MD5 of the image file you've downloaded.
Sent from my HTC Desire using XDA App
I'm confused by the two methods shown on Alpharev. Method 1 says to donwload the image file and Fastboot flash the file and Method 2 says to add the renamed PB99IMG.zip to SD card and flash. With method 1 do I do I have to do any of the process on PC or all on the phone? With method 2 do I just boot into recovery and flash the .zip like I would flash a new ROM (i.e. "Install zip from SD Card">"Choose zip from SD Card") or do I have to go into Fastboot the same as in Method 1?
As you can tell, I'm confused, but this is something I want to get right, for obvious reasons. The instructions on the Alpharev are basic but need to be a bit better explained for noobs like me, I think.
Which of the 2 methods are the easiest/safest and could some one be kind enough to give a more precise walkthrough please?
xybadog said:
I'm confused by the two methods shown on Alpharev. Method 1 says to donwload the image file and Fastboot flash the file and Method 2 says to add the renamed PB99IMG.zip to SD card and flash. With method 1 do I do I have to do any of the process on PC or all on the phone? With method 2 do I just boot into recovery and flash the .zip like I would flash a new ROM (i.e. "Install zip from SD Card">"Choose zip from SD Card") or do I have to go into Fastboot the same as in Method 1?
As you can tell, I'm confused, but this is something I want to get right, for obvious reasons. The instructions on the Alpharev are basic but need to be a bit better explained for noobs like me, I think.
Which of the 2 methods are the easiest/safest and could some one be kind enough to give a more precise walkthrough please?
Click to expand...
Click to collapse
I think fastboot is the best way to do it.... Not one of your choices - Edit - sorry it is i'm just blind!!! you have more control because you run the commands
As the previous dude said CHECK MD5SUMS!! if they match you should be fine
You flash the hboot depending on your needs.... I use reflex s CM7 with CM7 r2 hboot and I have a huge internal memory
The fastboot method says I have to rename the image file for the HBOOT I downloaded. The file I downloaded was bravo_spl_cm7r2.img so what do I have to rename it to?
Jeez I'm confused @!*$!&
EDIT: Ignore me, I just figured it out
xybadog said:
The fastboot method says I have to rename the image file for the HBOOT I downloaded. The file I downloaded was bravo_spl_cm7r2.img so what do I have to rename it to?
Jeez I'm confused @!*$!&
EDIT: Ignore me, I just figured it out
Click to expand...
Click to collapse
For others, please write your solution here.
Swyped from Oxygen with Transparent XDA App
@matdroid - No solution, just me misreading the instructions on Alpharev :/
I'm in the fastboot.exe cmd screen (made sure that the HBOOT .img file is in the same folder as fastboot.exe) and when I enter "fastboot flash hboot bravo_alphaspl-cm7r2.img" I get the error "cannot load bravo_alphaspl-cm7r2.img". When I enter Fastboot on the phone do I then have to select "BootLoader"? before I can flash the HBOOT?
Any ideas?
EDIT: Done it I used the info here.
Do I just "Power Down" now that flashing the HBOOT is complete or "Reboot Bootloader" or what? (Hope I get an answer quick coz don't want to leave the phone attached to the laptop in fastboot mode all night lol.
OK, so just installed the CM7 HBOOT but while my internal memory is excellent (currently 154MB free) the system storage size repartitioned to 145MB as expected but is showing only 15MB free. Is this worryingly low? What could be hogging this space?
xybadog said:
OK, so just installed the CM7 HBOOT but while my internal memory is excellent (currently 154MB free) the system storage size repartitioned to 145MB as expected but is showing only 15MB free. Is this worryingly low? What could be hogging this space?
Click to expand...
Click to collapse
The less space on /system/ partition the better, apps will use only /data/.
Actually i have like 400kb free space on /system.
double post sorry
///delete please
xybadog said:
OK, so just installed the CM7 HBOOT but while my internal memory is excellent (currently 154MB free) the system storage size repartitioned to 145MB as expected but is showing only 15MB free. Is this worryingly low? What could be hogging this space?
Click to expand...
Click to collapse
Unless you've got a lot of apps installed it shouldn't be that low (did you do a fresh instal after flashing the hboot? if not then..) .. do a nand backup of your rom, then do a full wipe (/mounts & storage/ format boot, system, data, cache; /advanced/ wipe dalvic cache) and install CM7 again.. you should have the full 145mb.. and if you don't (for some reason) you can always restore your backup ^_^
If you install MIUI-XJ it actually see's your sd-ext as internal memory.. so I have 2GB recognised as internal memory
I have quite a few user apps installed (about 60).Did full wipes after flashing the hboot then restored my nandroid backup.
xybadog said:
I have quite a few user apps installed (about 60).Did full wipes after flashing the hboot then restored my nandroid backup.
Click to expand...
Click to collapse
Yeah then the 15mb free space sounds about right lol.. you could try A2SD if you need more space, for that you need an EXT parition on your SD.. just read this, I can't explain what it is and how to use it better than that lol
neoKushan said:
Ok, so here's the deal, in a very longwinded way that should hopefully explain everything and answer ALL questions.
You have an SD card in your phone and, a bit like normal PC Hard Drives, you can "partition" them (split them into two or more sections of different filesystems). Normally, your SD card is just one big FAT32 partition, which is fine for storing your pics, messages, emails, etc.
Now, other then your Phone's SD card, your phone will have its own internal flash memory (or "NAND") storage. Tradditionally with Android, you could only install applications to this NAND storage, you cannot install them onto your SD card. So if you have an empty 32GB SD card, but only 5Mb of internal phone storage, you still wont be able to install many apps, if any at all.
This was done to protect the apps from things like piracy - it's not easy to access the location where apps are installed on your phone's internal storage (normally impossible without root), so you can't for example buy an app, copy it, refund it, then install it again.
Still, this is no good for those of us who like to install lots and lots of apps, legitimately, as we run out of internal storage very quickly.
So Google came up with a way to install apps to the SD card. A folder is created called something like .android_secure and this stores (I believe) encrypted versions of applications, but there's a few catches:
1) Apps aren't automatically stored here, you have to manually "move" them
2) Not all apps are capable of being moved, in fact most apps aren't, the developer needs to update their app and allow it. Some apps aren't and wont be updated and some developers may not want to allow it for whatever reason.
3) Not all app data is moved, most of it is but some data is left on your phone so many people still run out of internal storage quickly.
4) You can force ALL apps to be moved to this area by default, but it breaks incompatible ones - such as Widgets, which are unable to load due to the SD card not being "prepared".
So that's Froyo's version. Before Froyo existed, some very clever people came up with a thing called "Apps2SD". Remember I said that your SD card normally is one big FAT32 partition? Well, Apps2SD works by having your SD card patitioned into TWO filesystems. A normal FAT32 partition for your usual stuff and a secondary "EXT" partition. EXT is just a filesystem, like FAT32 or NTFS, but it's the filesystem used by Android internally. The SD card is normally FAT32 because it's a "universal" filesystem, that just about any machine will be able to read, whereas EXT filesystems are generally Linux only, but I digress.
EXT has several different versions. The most common one you'll see is ext3. The main difference between ext2 and ext3 is "journaling", which is just a fancy way of saying that should an operation (such as copying, writing or reading) be interrupted unexpectedly (say, by you turning your phone off), then no data should be lost or corrupted. You know how when you turn your phone on, it says "preparing SD card"? It takes a few minutes, but what it's actually doing is checking that the FAT32 partition hasn't been damaged, because FAT does NOT have journaling. If you used a computer back in the Windows 98 days, you may remember that lovely blue "Scandisk" screen that had to run every time you didn't shut your computer down correctly - that's the same thing. But then Windows 2000/XP came along with NTFS, which also has journaling, meaning you had less chance of loosing data. But I digress once more.
So you have your SD card partitioned into EXT and FAT32. Generally it doesn't matter if it's ext3 or ext4, but you don't get any real advantage with ext4 over ext3 in this instance. Apps2SD then runs a special script on your phone which "symbolically links" the folder from your phone's internal storage where your apps are normally stored, to the ext partition on your SD card. A symbolic link is a bit like a shortcut for folders, except it's transparent to the OS: In other words, Android doesn't know that when it's installing it's apps to the internal phone storage, it's actually being stored on the SD card. This effectively boosts your internal phone memory from the previous 5mb that you had in my example above, up to whatever size you made the ext partition on your SD card (often 512Mb or 1Gb, but it depends on how many apps you install).
Plus, because it's "journaled", it doesn't need to be "prepared", meaning it's ready to go as soon as the phone starts - so your widgets and apps work immediately (unlike "forced" Froyo Apps2SD, where widgets disappear).
The catch with Apps2SD is that whatever space the ext partition takes up is taken away from the SD card. So if you have a 4Gb card (with something like 3.5Gb of actual storage) and you make a 512Mb ext partition, your SD card will "shrink" to 3Gb. The space isn't actually lost, it's just being used by the ext partition. If you reformat your card, you'll get it back.
Finally, there's a difference between "Apps2SD" and "Apps2SD+". Remember I said that your apps are stored on a special folder inside your Phone's NAND storage? Well, that was a bit of a lie. It's actually stored in TWO places. There's a second area which is called the Davlik Cache. You don't really need to worry about what this is for (Hint: IT's to do with the Java runetime your phone uses to run apps), all you need to know is that apps use it to store data, which also eats up internal phone memory. Apps2SD+ moves davlik cache to the ext partition on your SD card as well, freeing up even more space. Some people believe that this may come at the cost of performance, as the internal NAND memory should be faster than your SD card (Which is why you also get people arguing over which "class" SD card is better for Apps2SD - the logic being that a faster SD card means less impact from this move), but the truth of the matter is that your applications will be running from your Phone's RAM anyway, so performance isn't really impacted at all. Since most apps are only a few hundred Kb's in size, or a couple of MB at the most, it's a non-issue.
Finally, any recent version of Apps2SD/Apps2SD+ should work with an SD card that is or isn't formatted with an ext partition. It'll check for this partition when your phone first boots and if it's not there, just use internal phone storage.
Having an ext partition WITHOUT Apps2SD+ shouldn't cause any issues, either, so you can format your SD card whenever you're ready.
So in summary:
Apps2SD "fakes" your phone's internal memory and puts it all on a hidden section of your SD card.
Apps2SD+ pushes even more content to the SD card, freeing up even more space on the phone itself.
"Froyo" Apps2SD has various limitations that "old" apps2SD does not, but is much easier to handle as it doesn't involve any kind of "partitioning".
Click to expand...
Click to collapse
Already got A2SD with Ext3 partition. I've noticed though that the A2SD partition doesn't show up on Titanium Backup or System info like it does with other ROMs.
xybadog said:
Already got A2SD with Ext3 partition. I've noticed though that the A2SD partition doesn't show up on Titanium Backup or System info like it does with other ROMs.
Click to expand...
Click to collapse
Partition your sd card again (make sure to save all important data on it before) with recovery or gparted again and take care, you set correct sizes. When you use gparted:
1st create fat32 (primary) and then ext partition (also primary).
MatDrOiD said:
Partition your sd card again (make sure to save all important data on it before) with recovery or gparted again and take care, you set correct sizes. When you use gparted:
1st create fat32 (primary) and then ext partition (also primary).
Click to expand...
Click to collapse
Got a new SD card on order so I'll wait till I get that and partition from new and see if that works.
I'm having trouble getting link2sd to work
As soon as I got my phone & found out how little internal storage there is for games, I read about link2sd. I didn't know that I was supposed to make an extra partition on my SD card. Whoops.
I moved a bunch of apps to the SD card (main FAT partition) and they all still ran, though I was still really short on space on the /Data partition of my internal storage. I guess there's still data & cache being stored in there.
Recently I found out that I was supposed to have made an extra partition, so I added an ext3 partition and a swap partition (both Primary) after my main FAT32 partition. CWM is able to mount the ext3 partition, but FreeSpace does not see it, and S2E doesn't appear to see it either. Link2SD sees it, though, so I figured it was fixed (maybe?).
I was thinking that if I moved some apps from SD back to internal, and to SD again, maybe ALL the associated files would be moved and I'd have more free space. No luck. It takes FOREVER to move an app from SD to internal storage now, and I don't wind up with any extra space when I move them back to the SD again.
Could somebody please help me troubleshoot & correct this mess?
Phone is an AT&T Xperia Play R800at, Android version 2.3.3 if it matters. It's rooted, but no custom ROM.
Hello development community
I'm currently running an CM 9 on an unlocked, rooted Wildfire S. A while ago I created a 4 GB partition in my SD card (Ext 2 format I believe) and set link2sd to install all new apps to this partition (this is the tutorial I followed http://forum.xda-developers.com/showthread.php?p=31544540 )
Anyway lately I've been having trouble installing new apps and larger updates (Facebook and DoubleTwist, namely) and my phone keeps telling me that I don't have enough memory. I tried wiping all my cache data and generally cleaning up, still no luck.
So I checked my storage usage in my settings, that's when things got interesting. My phone is telling me that I have 150 MB total of internal storage (which is how much there is without the partition), but somehow I have 229 MB used with 21.63 MB free. Doesn't take a mathematician to figure out that i can't be using 250 MB when there's only 150 MB to be had, however this 250 MB it's telling me I have is a lot less than the 4 GB of space I formatted and am linking everything too.
Does anyone know a way to get the phone to recognize the partition as internal space so it stops telling me I'm running out? I should be able to install any apps to my phone via my computer since they won't install directly from Google Play. Or is there a way I can set everything to just automatically install to the partition? That would solve my app installing problems but I might run into storage problems later on depending on how full my caches get. The more steps your give me the better, I'm still pretty new to this stuff :silly:
Thanks for any help!
PS. I checked some other threads but nothing I saw was helpful; so sorry if this is answered somewhere else, but I didn't find it.
After flashing rom did u flash the latest cronmod script
Sent from my Wildfire S A510e using xda premium
schalm1029 said:
Hello development community
I'm currently running an CM 9 on an unlocked, rooted Wildfire S. A while ago I created a 4 GB partition in my SD card (Ext 2 format I believe) and set link2sd to install all new apps to this partition (this is the tutorial I followed http://forum.xda-developers.com/showthread.php?p=31544540 )
Anyway lately I've been having trouble installing new apps and larger updates (Facebook and DoubleTwist, namely) and my phone keeps telling me that I don't have enough memory. I tried wiping all my cache data and generally cleaning up, still no luck.
So I checked my storage usage in my settings, that's when things got interesting. My phone is telling me that I have 150 MB total of internal storage (which is how much there is without the partition), but somehow I have 229 MB used with 21.63 MB free. Doesn't take a mathematician to figure out that i can't be using 250 MB when there's only 150 MB to be had, however this 250 MB it's telling me I have is a lot less than the 4 GB of space I formatted and am linking everything too.
Does anyone know a way to get the phone to recognize the partition as internal space so it stops telling me I'm running out? I should be able to install any apps to my phone via my computer since they won't install directly from Google Play. Or is there a way I can set everything to just automatically install to the partition? That would solve my app installing problems but I might run into storage problems later on depending on how full my caches get. The more steps your give me the better, I'm still pretty new to this stuff :silly:
Thanks for any help!
PS. I checked some other threads but nothing I saw was helpful; so sorry if this is answered somewhere else, but I didn't find it.
Click to expand...
Click to collapse
First of all, you can never use 4GB of your card as a partition Since there are some restrictions-- 100mb internal is needed for every 500mb sd-ext. We are getting around 100+ internal only for most of the ROMs , right? So you can use only around 600-700MB of the SD card as a partition.
Use min-partition tool and format your card and better make use of that card to the max. Format with ext4 (your choice) for around 700-800MB (Since 1/2/3/4GB is totally useless considering the above restriction) . After that, download and place this on SD card .
Before we go any further make sure that there are no scripts already loaded in that ROM you are using. (Apps2SD, Link2SD, etc). You need to have init.d support to make this work. This , you can verify by opening the ROM zip package and follow the path - system/etc . If you see a "init.d" folder there, then you have this support. All CM9 ROMs have this (I believe). So, now you make sure that the ROM whichever you are trying doesn't have any link2sd or apps2sd pre-loaded in it.
Then do the following.
* Put both the ROM and INT2EXT file on the SD card.
1- Goto Recovery.
2- Wipe Dalvik Cache, Battery Stats (Twice - Just to make sure )
3- Factory reset , Wipe Cache partition (Twice)
4- 'Choose zip from SD card' and select your ROM. Wait until it has finished installation.
5- Once Finished, again 'Choose zip from SD card' and flash/install the INT2EXT file that you have already placed on SD card.
6- Once done, reboot the phone. Goto settings->Apps and check if you have 'added' memory now
7- Go to recovery again and Flash GAPPS.
You are all set to Rock and Roll
Check this if you need more information
Hey, this will give you better space manipulation than the Link2SD, but still this is also limited to use, You can't fill all the internal memory. That will considerably lag your phone. Use the internal memory wisely
I guess this helps. And don't forget to thank "croniccorey" for his work
Thank you so much!!!
rishr4 said:
First of all, you can never use 4GB of your card as a partition Since there are some restrictions-- 100mb internal is needed for every 500mb sd-ext. We are getting around 100+ internal only for most of the ROMs , right? So you can use only around 600-700MB of the SD card as a partition.
Use min-partition tool and format your card and better make use of that card to the max. Format with ext4 (your choice) for around 700-800MB (Since 1/2/3/4GB is totally useless considering the above restriction) . After that, download and place this on SD card .
Before we go any further make sure that there are no scripts already loaded in that ROM you are using. (Apps2SD, Link2SD, etc). You need to have init.d support to make this work. This , you can verify by opening the ROM zip package and follow the path - system/etc . If you see a "init.d" folder there, then you have this support. All CM9 ROMs have this (I believe). So, now you make sure that the ROM whichever you are trying doesn't have any link2sd or apps2sd pre-loaded in it.
Then do the following.
* Put both the ROM and INT2EXT file on the SD card.
1- Goto Recovery.
2- Wipe Dalvik Cache, Battery Stats (Twice - Just to make sure )
3- Factory reset , Wipe Cache partition (Twice)
4- 'Choose zip from SD card' and select your ROM. Wait until it has finished installation.
5- Once Finished, again 'Choose zip from SD card' and flash/install the INT2EXT file that you have already placed on SD card.
6- Once done, reboot the phone. Goto settings->Apps and check if you have 'added' memory now
7- Go to recovery again and Flash GAPPS.
You are all set to Rock and Roll
Check this if you need more information
Hey, this will give you better space manipulation than the Link2SD, but still this is also limited to use, You can't fill all the internal memory. That will considerably lag your phone. Use the internal memory wisely
I guess this helps. And don't forget to thank "croniccorey" for his work
Click to expand...
Click to collapse
Thank you so much for the post! I know it's been a while since the OP, but this worked perfectly! My phone now tells me that I have 705MB of internal storage. I believe all my problems have now been solved. I literally can't say "Thank you" enough!
Hi all! I need help.
As we know, Motorola Droid X has 8Gb of internal memory, but unfortunately, it can be used only for installing apps.
So, the biggest partition of int memory, as you can see on the screenshot, is a data.
Yes, you can say that we can mount a folder in data partition to a folder onto sdcard, and at this moment I use this method.
But, unfortunately, there are many pitfalls and it's starting to annoy me. So, I decided somehow to cut the data onto two partitions (2Gb data and the memory remaining to new partition). And then, using hijack init, mount that partition as internal sdcard, and the real sdcard as external.
What are your suggestions?
Code:
mmcparts=mmcblk1:
p1(mbmloader),
p2(mbm),
p3(mbmbackup),
p4(ebr),
p5(bploader),
p6(cdt.bin),
p7(pds),
p8(lbl),
p9(lbl_backup),
p10(logo.bin),
p11(sp),
p12(devtree),
p13(devtree_backup),
p14(bpsw),
p15(boot),
p16(recovery),
p17(cdrom),
p18(misc),
p19(cid),
p20(kpanic),
p21(system),
p22(cache),
p23(preinstall),
p24(userdata)
Any ideas?
I am sad