Database Develop

Huge Problem With Cyanogen Auto Apps2sd

So I partitioned my sd card so i would be able to automatically have apps to sd like the faqs of the cyanogen mods said, but now that i have done the process and partition my sd card 500mb ext, 34mb linux swap, not only has it not worked and the apps are still taking up memory on my phone, it is not noticing the secondary partition in the settings and when i reboot my phone, after the g1 screen and android screen, my phone just goes blank. does anyone have any input? ive wiped and reflashed the rom, now im just clueless. and if it matters, i used Paragon Partition Manager to partition my sd card.

You could re-partition it by using the console in recovery mode.
http://forum.xda-developers.com/showthread.php?t=533731
Look at the 2nd code box and follow it. This is how I did it my first time.
It is really easy.

yea the only thing is it is either saying not found, or error could not stat device dev/block/mmcblk0 no such file or directory. so im stuck i cant even format my card and get back to 8 gigs its sayin 6.06 gigs. ionno im stuck.

Can't you use your partition manager to delete the partitions you made? Then just make 1 partition: fat32, then use the code on the link.
I use paragon Partition mgr. and that is an option to use.

If you partion your card after flashing your rom, then you must reflash your rom for changes to take effect. You have to do that so the system can change the way it runs

Oops sorry, I just reread your first post and saw that I missed that you did reflash. Try going into your recovery console and type ums_enable to mount your card and than try downloading gparted and try to reformat that way, when you are done type ums_disable to unmount. Have you tried taking your sd out when you try to boot up just to see if you can get past, it is possible that your sd corrupted

its ok thank you both, i used the recovery erase all partitions and im gonna read the second box and partition threw the console instead of on the manager.

I just had the same thing happen to me earlier today. I have the 404 Cyanogen MOD and now my SD card is stuck. I can't figure out how to get rid of that partition. All of the directions are not step by step. And this rookie is stressed out. Please let me know where or which directions you used to format your SD.

surfereddie said:
I just had the same thing happen to me earlier today. I have the 404 Cyanogen MOD and now my SD card is stuck. I can't figure out how to get rid of that partition. All of the directions are not step by step. And this rookie is stressed out. Please let me know where or which directions you used to format your SD.
Click to expand...
Click to collapse
To get it back to just a fat32 partition.... THIS WILL WIPE ALL DATA ON YOUR SDCARD!!!! MAKE A BACKUP OF FAT32 also this will only work with 1.3.1 and up cyanogen recovery image
boot into recovery and go to the recovery console and type
parted /dev/block/mmcblk0
rm 1
rm 2
rm 3 (if you have a linux-swap partition)
print (after the 4th or 5th line there is a number after a line that reads disk size or something and that will be the end value for the next command. Sorry on my g1 now)
mkpartfs primary fat32 0 xxxx(substitue with number above)
quit
reboot recovery
Then reflash your rom. That will clear all partitions of your sdcard and leave you with one whole partition that is fat32.

Can't apply ZIP updates. HELP! Wave invites for help.

OK.
So for the last week or two I've been trying to get myself fixed in this thread:
629469
You can read that for some background info. Seeing as this a new problem, I've posted a new thread.
I've pushed SuperD, signed-spl (danger) and ota-radio 2_22_19_26i to the phone.
But now I cant apply these updates. I choose "apply sdcard:choose zip"
and it says:
e:can't mount /dev/block/mmcblk0p1 (or /dev/block/mmcblk0)
(Invalid Argument)
E:Can't mount SDCARD:
HELP.
Wave invites for help (I'll try that one again)

I've run into the same problem but I got there a slightly different way.
I recently switched ROMs from kingklick's aosp 2.1 v1.5 to openeclair 1.5, and I wanted to switch back. I went to do the usual partition, wipe everything, apply update.zip and I got almost exactly the same error message that you got:
E: can't mount /dev/block/mmcblk0p1 (or /dev/block/mmcblk0)
(File not found)
E: can't mount SDCARD:
With my limited knowledge of Unix, I decided to jump into the console and dig around in the dev folder, I didn't see anything in /dev/block that was called mmcblk0, there were several files called "loopX", and also "mtdblkX".
It seems like my phone is acting as though I do not have an SD card at all. I've been testing out different things, I started the process over again by trying to partition the SD card and noticed it finished almost instantly. And now when I connect it to the computer and turn on the USB connection, my computer does not recognize it as a storage device. I then popped out the SD card and put it into the computer itself, it seems fine but there were some extra dm files that I did not expect to see. Not sure what those files are or how they got there.
I have the Death SPL, and the last ROM I used was KingKlick's AOSP 2.1 v1.5
Does anyone out there have any idea why this happened or how I can fix it?

Both of you, it sounds like your sd card is formatted wrong or corrupt. From amon-ra recovery you should try to wipe again, including the SD, and repair SD EXT. If that doen't work go back and use the "format SD" option.
One more thing, please take a few minutes and put together a signature on the forum with all your info, phone, spl, rom, sd setup, what you like for breakfast, all that stuff. Much easier to tell where to start.
Edit...if this should happen to accidentally work, please don't send any wave invites. I will probably never get rid of my 25.

Wipe data - worked (supposedly)
Wipe dalvik - Error : Run 'wipe dalvik' via console!
Wipe SD:ext partition - Error : Run 'wipe ext' via console!
Repair SD:ext - Error : Run 'fs repair' via console!
I don't see an option for "Format SD" in Amon Ra's recovery v1.5.2, so I attempted to Partition SD and give 0 space to swap and ext2. That SAID it completed successfully, but it finished suspiciously fast, and upon inserting the SD into my computer, I can see that it was not re-partitioned nor wiped.
I went into the console and tried the commands mentioned in the error messages and got "No ext partition found!" from each command. I then went back to recovery to "partition" the SD with Swap - 192MB, Ext2 - 1024MB, Fat32 - remainder (approx 2.75GB). I then tried wiping and repairing again, and got the same error messages, then went back to console to try wiping from there, and again was told "No ext partition found!"
I noticed that my SD is class 4, but class 6 is recommended, I'm considering going to buy a new class 6 SD, do you think that will help?
Filled in my sig, did I miss any info?

dracoaffectus said:
Wipe data - worked (supposedly)
Wipe dalvik - Error : Run 'wipe dalvik' via console!
Wipe SD:ext partition - Error : Run 'wipe ext' via console!
Repair SD:ext - Error : Run 'fs repair' via console!
I don't see an option for "Format SD" in Amon Ra's recovery v1.5.2, so I attempted to Partition SD and give 0 space to swap and ext2. That SAID it completed successfully, but it finished suspiciously fast, and upon inserting the SD into my computer, I can see that it was not re-partitioned nor wiped.
I went into the console and tried the commands mentioned in the error messages and got "No ext partition found!" from each command. I then went back to recovery to "partition" the SD with Swap - 192MB, Ext2 - 1024MB, Fat32 - remainder (approx 2.75GB). I then tried wiping and repairing again, and got the same error messages, then went back to console to try wiping from there, and again was told "No ext partition found!"
I noticed that my SD is class 4, but class 6 is recommended, I'm considering going to buy a new class 6 SD, do you think that will help?
Filled in my sig, did I miss any info?
Click to expand...
Click to collapse
to format it, just go to partition, then select 0 for the first two and rest for fat 32. You don't need a new card unless you're running a hero rom, and a class 4 is actually pretty fast. If formatting it doesn't work its done. This happened to me on a brand new class 6 transcend. Sent it back and got a sandisk. Good luck

I have the same problem wiht my G1 and am sending back my phone to HTC for this.
I have made a post here:
http://forum.xda-developers.com/showthread.php?p=5594269
All our phones have activated a memory debugging mode from from hboot. Modifying anything while booted to recovery or system doesn't affect anything because the trigger is happening from hboot.
You can still use fastboot while stuck in this mode. But your phone has no sd card access at the moment because it is locked by the hboot for writing debug logs.
I found that I was not able to flash in fastboot, as my hboot showed S-ON. However it was still possible to use fastboot boot.
Run cat /proc/cmdline
You will see that it says something like the following:
board_trout.disable_uart3=1 board_trout.usb_h2w_sw=1 board_trout.disable_sdcard=1 smisize=64 androidboot.baseband=3.22.26.17 androidboot.cid=ROGER001 androidboot.carrier=Rogers androidboot.keycaps=qwerty androidboot.mode=normal androidboot.serialno=HT********** androidboot.bootloader=1.33.2005 no_console_suspend=1 con
sole=null
You could mount the cache partition to your sdcard directory for flashing files:
adb shell mount -t yaffs2 /dev/block/mtdblock4 /sdcard
I've had this problem for more than a week. I have tried changing SPL, unrooting, recompiling my boot.img, and appending kernel commands.
You can also force your recovery/system to mount the sdcard, but your phone will error out because both the hboot and system will try to write to the sdcard. There is a high chance of corrupting the sd card (correctable by reformatting) this way, but you can generate a gold card:
fastboot -c "board_trout.disable_uart3=0 board_trout.usb_h2w_sw=0 board_trout.disable_sdcard=0" boot recovery.img
The -c switch appends to the kernel cmdline at the end.
There is a working solution if you have SPL 1.76.x in your HBOOT. The command to disable memory debug logs is simply
fastboot oem enableqxdm 0
However I have never seen this SPL for the dream. 32B magic users who flashed this SPL with the accompanying radio ended with semi-bricks, with their SPLs showing 32A board. Attempts to downgrade back to 1.33.x have not worked. Here's the thread:
http://forum.xda-developers.com/showthread.php?t=625604
I did theorize that we might have been able to upgrade our spl and radio to 1.76.x, run the enableqxdm command, and then downgrade back to 1.33.2010 using the test ruu. The 1.33.2010 works for the 32A magic, the 32B magic and the dream. This is one of the variants of the so called danger spl. If you have 1.33.2005 you already have a spl from the magic.

hiddengopher said:
to format it, just go to partition, then select 0 for the first two and rest for fat 32. You don't need a new card unless you're running a hero rom, and a class 4 is actually pretty fast. If formatting it doesn't work its done. This happened to me on a brand new class 6 transcend. Sent it back and got a sandisk. Good luck
Click to expand...
Click to collapse
Ok, I tried that already and it didn't work. So you're saying the SD card is useless now and I just need to get a new one?
and Xaueious, I read your post and I have one question. What do you recommend I do?

dracoaffectus said:
Ok, I tried that already and it didn't work. So you're saying the SD card is useless now and I just need to get a new one?
and Xaueious, I read your post and I have one question. What do you recommend I do?
Click to expand...
Click to collapse
Try this first.
Enter recovery then console
1. type parted /dev/block/mmcblk0
2. type rm 2 to remove ext
3. type rm 3 to remove swap
to resize fat32:
4. type print to get start value and sdcard size
5. type resize 1 <start> <sdcard size> (if i were doing this for my card it would be resize 1 512B 8169M)
Then put the card in computer and format fat32. (just to be sure)
Put it back in the phone and recovery and partition.
If no other way works, the card may be corrupt.
You could use GPARTED in linux for this. Even a GPARTED live cd would be good. In fact that may be your best option.

billquinn1 said:
Try this first.
Enter recovery then console
1. type parted /dev/block/mmcblk0
2. type rm 2 to remove ext
3. type rm 3 to remove swap
to resize fat32:
4. type print to get start value and sdcard size
5. type resize 1 <start> <sdcard size> (if i were doing this for my card it would be resize 1 512B 8169M)
Then put the card in computer and format fat32. (just to be sure)
Put it back in the phone and recovery and partition.
If no other way works, the card may be corrupt.
You could use GPARTED in linux for this. Even a GPARTED live cd would be good. In fact that may be your best option.
Click to expand...
Click to collapse
also, you're going to want to go to "go to console" in recovery to do this

billquinn1 said:
Try this first.
Enter recovery then console
1. type parted /dev/block/mmcblk0
2. type rm 2 to remove ext
3. type rm 3 to remove swap
to resize fat32:
4. type print to get start value and sdcard size
5. type resize 1 <start> <sdcard size> (if i were doing this for my card it would be resize 1 512B 8169M)
Then put the card in computer and format fat32. (just to be sure)
Put it back in the phone and recovery and partition.
If no other way works, the card may be corrupt.
You could use GPARTED in linux for this. Even a GPARTED live cd would be good. In fact that may be your best option.
Click to expand...
Click to collapse
I went to console and typed "parted /dev/block/mmcblk0" and it said "Error: Could not stat device /dev/block/mmcblk0 - No such file or directory"
I tried "parted /dev/block/mtdblock0" instead and got into parted, but when I tried any command such as "print", I got "Error: /dev/block/mtdblock0: unrecognised disk label"

dracoaffectus said:
I went to console and typed "parted /dev/block/mmcblk0" and it said "Error: Could not stat device /dev/block/mmcblk0 - No such file or directory"
I tried "parted /dev/block/mtdblock0" instead and got into parted, but when I tried any command such as "print", I got "Error: /dev/block/mtdblock0: unrecognised disk label"
Click to expand...
Click to collapse
I would say the sd card is dead. Try someone else's or a spare.

Picked up a 2GB microSD at the store for like $10 and got the same results right from the beginning.
So this means it's something wrong with my phone, and not the SD card.
Any suggestions?
....can I unroot?
I don't know if this matters, but I noticed some dm files on my sdcards after trying to startup my phone.
EDIT: I managed to UNroot my phone back to RC29 following the instructions on theunlockr.com. Now I have to contemplate if I'm ready to jump straight back into hacking again.
EDIT2: Ok, so now I'm back on the latest OpenEclair. The key to "fixing" it was to get a totally clean start by UNrooting my phone (http://bit.ly/5qbzIU thanks Unlockr.com). I wasn't able to do step 1 cause I was getting the same errors as before, so I skipped straight to loading the DreaIMG.nbh file, then continued to update to cupcake, load the latest radio, danger SPL, and openEclair, now my phone is working again. (p.s. already on Wave, so no need to send that invite Lachy95 )

Thanks
Its all fixed.
Used a different sd card, im stupid.
Thanks you thank you thank you
ill always remember

Keep losing sd ext

I created an sdext with rom mgr and usaully take it from 2 to 3 with amon ra. Confirm ext 3 with partition tool.
Lately I have lost ext three times. Not sure why.
I have used DT and went to a rom that has auto a2sd and maybe that did it. Don't know if DT has been reinstalled off of one the roms I flash between. Next time I opened the Jave app to see a blank sdcard. Deleted that app. This time I opened Quick boot and and went into CWMod recovery and did a basic bu. Bu completed but could not boot, hung on X. Saw that sdext wont mount.
Restore seems to go ok, but at bottom of recovery screen it says:
E: Can't mount /dev/block/mmcblk0p2
(File exists)
Error mounting /sd-ext/!
Skipping format...
E: Can't mount /dev/block/mmcblk0p2
(File exists)
Can't mount /sd-ext/!
Third time now and wondering what might be causing it.
I have sdformatter and can make another ext 3 partition and copy sd backup from pc to phone. Did that last time. Maybe rom mgr has been having issues. I don't do anything with rm I always boot into recovery. May need to go to amon_ra 1.9a full time.
Maybe stop using sdext and try ModInstallLocation, but heard that was no longer in Market.
Under MyPhone with MIUI .5 it shows sdext, but empty
MIUI .5 did load, don't know why it did and MicroMod 2.10 didin't, maybe too much mem used in the desire rom.
Under Quick System it shows ext as 458 and 323 free. Makes no sense. Maybe just the last reading it had. Internal free 69mb.
Maybe I just need to mount thru adb: mount /dev/block/mmcblk0p2. Not sure exactly how to type the syntaxes on sdk stuff.
I am not at home so can't see if I can mount sd thru pc or recovery or open sdformatter and see what it says.
Frustrated!
Ken

Can run DT which is not supported on MicroMod, I believe. I thought when you wipe and flash the ext is formatted and restored so DT would be removed if there.
I ran DT zipalign and it was ok. That was the only option to do other than Dalvik to sd. So do I have an ext or not?
I am cconfused on DT with different roms. I like MM 2.10 and would like to use it.
BTW: TB does not show an sd-ext either

Well, I restored an MIUI .5 bu and it works. Did a bu and showed ext backed up. But TB and Root Explorer show no ext info, mem size.

[Q] Help getting any rom to run off internal

Ok, backstory, picked up this Nook Color on craigslist, came with Honeycomb v4 on microSD, booted fine into that, but without uSD would boot to 'n' screen and freeze/stall. Got another uSD formatted with CWM Recovery and the clean original nook image to try and load that from scratch. While following the instructions to restore the original image I would get errors while trying to format system and data (something to the effect of Error cannot format system/!). So I tried to install both CWM to the internal and CM7 to the internal and both would say install complete from microSD, but when booting without the uSD, it would still try to boot into the original nook software and hand on the 'n'.
I tried this to see if my partitions were messed up, but I had the same partition structure and size as it should be (according to the post):
http://forum.xda-developers.com/showthread.php?p=13003431#post13003431
Possibly because I ran this "repartition-boot-with-stock" from this post:
http://forum.xda-developers.com/showthread.php?t=914690
Please help, would prefer to run this off the internal!
Got CM7 running off yet another microSD with this thread:
http://forum.xda-developers.com/showthread.php?t=1000957

Assuming the partition table is in tact then try formatting /system /data /cache in Clockworkmod.
If that doesn't work if might be time to entertain the possibility that you were sold a Nook with a bad emmc.
Sent from my NookColor using XDA App

When I try to format /system /data /cache in CWM, I get an error message. What is the function of the emmc?

mattdogg02 said:
When I try to format /system /data /cache in CWM, I get an error message. What is the function of the emmc?
Click to expand...
Click to collapse
Putting it in PC terms, the emmc functions as the ROM for the bios, and as the solid state drive for whatever you're running on internal memory.
(What is the term for the tablet/smartphone equivalent of the "bios"?)

akaCat said:
(What is the term for the tablet/smartphone equivalent of the "bios"?)
Click to expand...
Click to collapse
Bootloader.
As to the OP - It's still possible your internal flash is bad but the fact that you can list your partition table gives me hope that isn't the case.
I read through JoJa15's post you linked in "Dummies Guide to Fixing 'My Nook Won't Boot'" - It sounds like you listed your partition table per his post and found that it matched what he posted but didn't modify anything right?
The fact that your partition table appears to be in tact is good but the contents of those partitions could be complete gibberish which may explain why CWM errors out when trying to format them. What is the exact error CWM is giving?
I think the next "safe" step is to have a look at DeanGibson's post here: http://forum.xda-developers.com/showthread.php?t=1094371
Dean's CWM scripts will essentially blow away partitions 6-8 (/data / cache and /emmc) and re-create them. If your problem happens to be in one of those partitions then his tool may be a quick fix without having to play with fdisk. That said, I doubt it will work since you can't format /system (partition 5) and his tool doesn't touch the /system partition.
At that point you are pretty much left playing with fdisk, unless you can sweet talk DeanGibson into putting together a CWM flash that will re-do partitions 4 and 5 (extended partition and /system partition) which he may do.
From there it boils down to how comfortable you are with the Linux commands dd and fdisk...?
Good Luck,
Martian21

Ok, followed Dean's instructions with the packages from his post, but still no go.
The error I'm getting when going to Mounts and Storage Menu and running the format /system /data /cache options are:
ClockworkMod Recovery v3.0.2.8
Formatting /system...
Error formatting /system!
Formatting /data...
Error formatting /data!
Formatting /cache...
Error formatting /cache!
Really want to try and get this resolved as I want to install stuff onto the internal!

No one with any other advice on this?

mattdogg02 said:
No one with any other advice on this?
Click to expand...
Click to collapse
Your previous post showed that you were using clockworkmod recovery v3.0.2.8, that version does not have support for the “blue dot” NC. Not knowing for sure if your NC is really a “blue dot” or an original one, I would follow these steps.
1. Create a bootable CWM v3.2.0.1 SD card using the image located HERE. The instructions for it are located HERE. I know the post says v3.0.2.1, but it is miss-marked.
2. Once the card is made, download the repartitioning files located HERE, and the stock 1.2 image file “update-nc-stock-1.2-signed.zip” located HERE.
3. Put all those zip files onto the SD Card
4. Shut down the NC
5. Insert and start the bootable SD card
6. Follow the directions to flash the repartitioning files
7. Once that completes, flash the stock 1.2 image
8. When that is done, remove the SD card, and reboot the device
Hopefully at this point, you will be booting into a stock 1.2.0 system. You can now do whatever you want with the device.

stock rom and link2sd: can't mount ext4 partition

i have my ace running with a stock rom again since my wife is using it.
I have rooted the phone and flashed px recovery. After that, I wanted link2sd to mount the ext4 partition but whatever I try: nothing works.
when I try to mount ext 3 or ext 4 in link2sd I get this message: can't mount: no such device
when I try to mount ext2 I get this message: invalid argument
I have repartitioned and formatted both partitions already a dozen times. why can't link2sd mount this ext 4 partition?
i created the partitions using minitool partition wizard. After I placed the sd card back into my phone, I rebooted into px recovery, mount the sd-ext and formatted sd-ext, and after that, link2sd still gave the same errors.
How can I get Link2SD working?

DutchArjo said:
i have my ace running with a stock rom again since my wife is using it.
I have rooted the phone and flashed px recovery. After that, I wanted link2sd to mount the ext4 partition but whatever I try: nothing works.
when I try to mount ext 3 or ext 4 in link2sd I get this message: can't mount: no such device
when I try to mount ext2 I get this message: invalid argument
I have repartitioned and formatted both partitions already a dozen times. why can't link2sd mount this ext 4 partition?
i created the partitions using minitool partition wizard. After I placed the sd card back into my phone, I rebooted into px recovery, mount the sd-ext and formatted sd-ext, and after that, link2sd still gave the same errors.
How can I get Link2SD working?
Click to expand...
Click to collapse
I forgot that stock rom can't work with ext 4. Changing file system to ext2 worked for me and solved the problem (for now).

DutchArjo said:
I forgot that stock rom can't work with ext 4. Changing file system to ext2 worked for me and solved the problem (for now).
Click to expand...
Click to collapse
Are you sure Link2SD works well on stock rom? Because last time I checked it doesn't work well on roms without init.d support. I myself couldn't get it to work on stock rom. It crashed most of the time. Do post the result.