[Q] Creating EXT3 partition on SLCD Desire - Desire Q&A, Help & Troubleshooting

Hi, does anyone have a working method for creating ext3 partition on SD card for app2sd on SLCD Desire? The following methods do not work for one reason or another on mine SLCD Desire with 0.83Hboot and 2.5.0.1. modified Clockwork recovery:
1. Via Rom Manager .. does not work because installing the standard Clockwork recovery is required for this and that one just "turns off" your screen.
2. Via Amon Ra recovery .. because it does not support the SLCD Desire AFAIK
3. Via ADB console .. I get "Not found" message when trying to run parted
I was wondering, if it is really necessary to perform the partitioning with the SDcard in the phone, I would prefer to use a USB reader and some partitioning software, but I am not able to find a normal description of needed partition specifics (if there are any).
If I understand the requirements correctly, I need to create three separate partitions (to be safe with the roms that use also the swap one) .. FAT32 first, ext3 second and linux-swap third.
Does anyone have an idea how to create these and maybe a tip for a suitable software that can to this (most of the freeware partition managers do not support non-windows filesystems )

I did mine via Rom manager no problems and I have an SLCD. I installed what it said didn't change anything.
Sent from my HTC Desire using XDA App

hmm I tried it with the newest ROM manager and it works

Related

[Q] Question about SD ext partitioning and the Desire

Hi all
ive been using A2SD and A2SD+ for a while now.
But the only way Ive ever been able to avoid a boot loop with any custom rom is is i use adb and parted to partition the SD card as per:
http://androidandme.com/2009/08/news/how-to-manually-partition-your-sd-card-for-android-apps2sd/
If I use any other method (including via my custom recovery image - Amon RA) my desire just gets caught in a boot loop.
I get the impression that others dont have this limitation.
Any ideas?
I used Amon_RA 1.7.0.1 R5 from here http://forum.xda-developers.com/showthread.php?t=721792 to partition my SD card and convert the Ext2 to Ext3. Works like a charm with LeeDroid 1.4c.
Did you convert to Ext3?
Hi Stooby,
Thanks for the reply.
Yes, thats the same Recovery image I have installed, and Ive tried all sorts of things:
- leave as ext2
- convert ext2 to ext3
- convert ext3 to ext4
- repair ext partition
Also tried partitioning via clockworkmod / Rom Manager, same results
Regardless of whatever rom I use, the only way I seem to be able to get out of boot loop is partitioning via adb
Mods - I just realised I posted this in development - feel free to move it to a better home if you see fit.
subvertbeats said:
Regardless of whatever rom I use, the only way I seem to be able to get out of boot loop is partitioning via adb
Click to expand...
Click to collapse
That's weird - I've never had any problems creating Ext2/3/4 partitions using that recovery.
FWIW, I was using Amon_RA's recovery roms back when I had my old Dream, and never had your problem with those either!
Hopefully, someone with more knowledge will be along soon to make a constructive suggestion or 2.

2 CyanogenMod questions

I got 2 questions for CM6, I'll be getting my Desire back by Thursday hopefully :
1) CM6 by default doesn't have any of the Google's applications, including the Market App. I know it has a separate package, but it has too many Google's applications. The only ones I want from it are the Market, and the necessary ones required for operation(Google's accounts for authentication, setup wizard etc). Rest I want to download from Market(I see that most are available from it). So can I just delete the apps from the system folder in the package? If so, what are the must ones that must be kept?
2) Is the SD card required to be partitioned in 3 partitions(Fat32 + Ext2/3/4 + Linux Swap) when using CM6?
1. you can open gapps.zip and remove all the apps you don't need in /system...don't know which are "must have"
than you zip it back and flash it ,you can sign it but you don't have to...you can flash unsigned gapps.zip using clockwork recovery
2.no CM doesn't use apps2sd(ext) they use native froyo a2sd
hope this helps
I got another Q, can a Goldcard be used as a normal SD Card? I mean I plan on making one as soon as I get my Desire but I'll preserve it for future needs, I SLCD bricked my last one and realised the importance of having one. So would that be a good idea?
Thanks for your reply, it helps . Also, what are the kind of partitions I need to create for the SD card to be usable in the phone as well as Amon Ra's or ClockworkMod's Recovery? I created a FAT32 one using Windows and GParted(2 different times) but Clockwork's recovery or fastboot couldn't recognize them.
Yes the goldcard can be used as a regular sd-card
And for partitioning you only need a fat32 one as long as you don't run any old a2sd. Using windows should work fine, but you could try partitioning it again with amonra or something similar. And are you sure, you haven't got something wrong. The recovery is usually easily able to read fat32 easily, and how do you see, recovery and fastboot doesn't recognize it?

[Q] CDMA; attempting to replace the recovery

Please bare with me, as there's a lot to explain. I am in dire need for your help.
Starting off, my specs are as follows:
HTC Desire CDMA from U.S. Cellular
Rooted via Unrevoked (with unrevoked forever)
Current Recovery: ClockworkMod 2.5.0.9
Current ROM: CyanogenMod 6.1.0
Current SD: 8GB
The phone is barely over a week old. I rooted it last week, flashed Cyanogen, and customized everything. Well one thing I wished I had done before was partition a part of my SD to allow for more internal phone space. Even with
Cyanogen's FroYo (2.2.1) capability to move apps to the SD, I kept running a thin line on low memory. This is because, as most of you know, not the entire app is moved. I was faced with the decision of removing apps that I frequently used, or look for other storage solutions.
I found out that there was a way to make the phone think it has extra memory by partitioning a part of your MicroSD card to an Ext3. I researched how to do this with the tools I already had available (this being ROM Manager & ClockworkMod). I first tried ClockworkMod's recovery, which give me the option to partition the SD. I selected 512MB for the size (it's more than enough for me) and a swap size of 0. It completes, and I reboot the phone. I checked the internal storage space, and it's still low (< 15MB). Upon more research, I found that it may have only been an Ext2, and not Ext3. Upon plugging my phone back into the USB/Computer, I noticed the overall size for my MicroSD went from 7.5x GB to 6.9x GB. If the partition didn't work like I wanted, I wanted my space back.
So for hours I scour the forums with nothing helpful in return. I tried Partition Magic to try and merge the partition back to my original card, but it couldn't see it. It only saw a SD card that was 6.9x GB. So further research showed me that ClockworkMod was pretty bad at partitioning the SD card to Ext3, and everyone suggested AmonRa. I found a version of AmonRa that was designed for the HTC Desire. I placed the .img file on the root of my SD card and opened up ROM Manager. The option to "Flash Alternate Recovery" was greyed out, despite the fact that the image was on my SD Card (which was mounted; USB Storage for the PC was turned OFF). So further reading said I needed the premium version of Rom manager. I bought it, installed it, and re-fired it up. The option is still greyed out.
Frustrated, I look for alternate methods. I found one that recommended Terminal and the flash_image script.
I tried doing this with the AmonRa recovery image (which I renamed to recovery.img on my SD card). I rebooted into recovery, but instead of ClockworkMod or AmonRa appearing, I just got the HTC logo with the white
background where it would ultimately freeze. I performed a hard reset and tried again. Same thing. I reboot, went into ROM Manager and tried flashing ClockworkMod 2.5.0.9. It said it installed, so I reboot into recovery. Same HTC Logo freeze.
Freaking out, I tried other solutions, involving one where I placed a script on my SDcard. From there, I would go into Terminal and type the following:
su
sh /sdcard/FR-flashRec-v03.txt
And after the 2nd or 3rd time trying this, I reboot my phone, and instead of going into recovery, it dumps me back into Fastboot. Every time I tried selecting Recovery from bootloader, it would take me to Fastboot. I'm freaking out about now. So I fired up Unrevoked, the tool I used to originally root my phone. After the 2nd attempt, it successfully flashed ClockworkMod back to my phone.
Relieved but still unsolved, I continue to look for a reason why I'm not able to flash a different recovery image. Then I found a thread which dates back to June 2010 and applied to the CyanogenMod 5.0.x Eclair build. There was a disclaimer that read:
DO NOT USE ROM MANAGER TO FLASH YOUR RECOVERY.
DO NOT USE flash_image SCRIPT TO FLASH YOUR RECOVERY IN THE LIVE SYSTEM.
So I figured the problem was with my current ROM. Sure, that referred to CyM 5.0.x, and I'm running 6.1, but there was no documentation saying that the issue had been fixed, and there weren't any other threads regarding my issue.
Not wanting to take a risk losing my current recovery, I restored a backup from my stock ROM I received from U.S. Cellular. I installed ROM Manager and tried to flash the recovery image via the "Flash Alternate Recovery". The option was once again greyed out. I bought premium again and still, the option is still greyed out.
Running out of ideas, I restored my CyanogenMod state I made before I did any changes. And this is where I am.
I'm running out of internal phone space rapidly.
[*]I don't know how to restore the partition I made to get my SD storage space back (in fact, since I made that partition, it's been slower).
[*]I don't know how I can flash AmonRa, or if it's even possible with CyanogenMod.
[*]I don't know how to use ADB shell.
I found a site that has a collection of AmonRa images, and for the Desire, they have the following: recovery-RA-desire-v2.0.0-AW.img, recovery-RA-desire-v2.0.0-CM.img, and finally recovery-RA-desire-v2.0.0.img. I don't know which one I need to install for my HTC Desire CDMA.
If you've made it through this entire thread. Thank you. I really need some answers, and I don't know where else to look or to even ask. Can you please help me?
First of all making a ext partition won't magically provide more space, there is more behind it. See the second post in this thread under 'Still low storage for apps'.
And the partition made with rom manager should be fine however if you want something else use Gparted (can run of a linux live cd so no need to install anything)
For the restoring of the partition also use Gparted.
Not 100% sure but i believe that with unrevoked you can flash a alternative recovery image even if you are already rooted, but if you use Gparted there is no real reason for doing so.
For adb there are enough tutorials.
Hmm, many of these AmonRa releases are designed for HTC Desire GSM. Will these releases also work for CDMA devices?
Also, GParted will not work under Windows 7, and I don't use linux. All these other partitioning programs cannot detect the missing 1GB from my 8GB MicroSD. I have no idea how to restore it.

[Q] Couldn't see sd-ext from Ubuntu (Gparted)

I try to partition my sd-card using ClockworkMod Recovery 5.8.0.0.
It went ok, and I can see my partition using adb shell
Code:
# mount
...
/dev/block/mmcblk0p2 on /sd-ext type ext3 (rw,nodev,noatime,nodiratime,barrier=1,nodelalloc,data=ordered)
/dev/block/mmcblk0p1 on /sdcard type vfat (rw,nodev,noatime,nodiratime,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro)
I want to convert ext3 to ext4 so I plug my phone in the USB and mount it in the recovery.
However Gparted can't find any partition in my sdcard. When I try to view it using disk utilities It only shows the FAT32 partition.
I don't understand why gparted can't detect any partition ( it shows unallocated ). Something wrong with the partition table of the sd-card formatted by CWM ? Anyone have solved this before ?
Delete all partitions on your SD card and then partition again.
MatDrOiD said:
Delete all partitions on your SD card and then partition again.
Click to expand...
Click to collapse
How to delete them if I can't see them ? I try to re-partition using CWM but still the same.
Delete partitions with cwm, and then create 1 big fat 32 partition. Alternately use Linux fdisk, which will "see" it.
After one partition is created, use parted, or 4ext.
fdisk or parted both can't find any partition...
But anyway.. after installing MIUI which convert my partition to ext4 automatically the problem is gone, every partition can be seen... So it must be some problem with CWM partition script
It ought to detect the partitions if you use a micro sd card reader. I assume you connected it via the Desire, in recovery?
Droidzone said:
It ought to detect the partitions if you use a micro sd card reader. I assume you connected it via the Desire, in recovery?
Click to expand...
Click to collapse
Yes, maybe that's the problem. I connected it via the Desire in recovery.
What could be wrong ? Because now (after flashing MIUI_xj xpart), I can see all partitions though connected via the Desire.
UPDATE : I still can't see the sd-ext if I mount USB storage in the recover...
ikidntu said:
Yes, maybe that's the problem. I connected it via the Desire in recovery.
What could be wrong ? Because now (after flashing MIUI_xj xpart), I can see all partitions though connected via the Desire.
Click to expand...
Click to collapse
First, erase that crappy recovery from your phone. Then install 4ext. Should fix it.
Droidzone said:
First, erase that crappy recovery from your phone. Then install 4ext. Should fix it.
Click to expand...
Click to collapse
... exactly what I thought atm
when you mount ur desire with usb mass storage option under recovery, it mount ONLY the FAT partition...
put the microsd in a microsd adapter on ur laptop..u will see both...
@droidzone come on, don't call CWM crappy ..every recovery is based on that..koush did a great work in order to write it for about every device (a tons of device support it now)..i agree it's a basic recovery (and maybe there are some limitations)..but it's thanks to that base recovery that now devs can easily mod it and improve it...it's like you and ur rom..ur rom its probably the best htc sense based rom for the desire, but you will never be able to do that without the crappy htc rom, and htc was never be able to do that without the crappy aosp rom made by google..i hope you got what i mean lol...modify is easy than create something from new
@andQlimax, my bone of contention is not with Koush's CWMR. It is with that half baked product called "Clockwork mod touch for Desire" that was recently released here without proper testing (the OP was using this, and his problems are directly caused by the faulty recovery). The very least the "developer" should test is to do a full backup and restore on his own phone after compilation. He has no right to treat poor hapless newbies as guinepigs. I wonder if that person even owns a Desire. If he did and he missed the fact that the recovery he released does not have the capacity to make sd-ext backups, I really feel for him.
People trust developers who release Recovery. If they cant trust their recovery to make proper backup, what's the point of calling it a Recovery software?
I have the utmost respect for Koush, Paul O'Brien and others for their development work. I dont intend to mean any sort of disrespect for those masters and pioneers of Android development. I also respect them for keeping CWMR; and Cyanogen for keeping CM open source despite all circunstances.
anyway i think the touch recovery posted in the dev section come directly from the koush build, he released it and it's on its site http://www.clockworkmod.com/rommanager for some devices
koush usually ask some people to test the recovery for him before he release it, probably someone didn't noticed that bug
Thank you. I wasnt aware of that. But I see that the subversion has increased to 5.8.0.2 while yorzua has still attached the faulty 5.8.0.0.

[Q] My SD partition is not picked up by A2SD+

Hey,
Recently I've partitioned an 8GB SD-card through RA Recovery v2.0.1 to have a 1024MB EXT4 partition without swap (later I tried EXT2, EXT3 and an aligned EXT4 as well).
After installing a ROM said to be compatible with A2SD, the latest Supernova 2.4.0.1, it did not show the additional storage room that should be available from the SD partition.
Also when using a terminal emulator app, after granting it Superuser permission, I could not get any evidence on my phone being able to see the SD partition. "a2sd" and "app2sd" commands are not recognized and the "busybox df -h" and some other command did not return any evidence on an SD partition being present.
Other ROMs I've tried installing were the latest Cool3D RunnyMede and the Runnymede&Bliss.Mix ROMs. Both froze at their boot screens (due to not being able to access SD partition?).
Some (additional) information on my HTC Desire:
- GSM
- Stock HBOOT
- Stock radio
- RA Recovery v2.0.1
So yeah, I was wondering if you guys could help me on getting my SD partition to function Thanks in advance!
I've got the _exact_ same problem. I hope someone at XDA can help, because I'm eager to try Chrome Beta on my Desire with ICS.
Sent from my G100W using XDA
Try redo it with gparted or flash 4ext recovery if s-off
Sent from my HTC Sensation XE with Beats Audio using XDA Premium App
Thanks for the reply!
But sadly I won't be able to confirm whether that would've fixed my problem. I switched to MildWild's CM 3.8 ROM and that alone had my SD partition working for me.
Although it initially didn't appear to have the extra storage room (it displayed around 120MB in the Applications and Storage menus), I soon noticed that after installing a new app, that amount would first drop but then rise back to ~120MB again.
Typing the "busybox df -h" command in the Terminal Emulator confirmed that there was indeed a 1GB partition present from something called "sd-ext"...which would be the partition I made!
But could it be that I have to install A2SD+ separately for certain ROMs and is included in others?
Some like CM need this setup - mostly run AOSP roms myself but boot loops point to issue with the SD-ext partition. As was said earlier Gparted is the way to go to partition, and will align perfectly as well - if it were me I'd nandroid including sd-ext if separate in AmonRa (I use 4EXT Touch Recovery myself), copy sd contents to PC as back up, and re-do partitioning in Gparted.

Categories

Resources