Huge Problem With Cyanogen Auto Apps2sd - G1 Q&A, Help & Troubleshooting

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.

Related

[Guide] Partition your Sd Card, Upgrade to Ext3, and Install Apps2SD

WARNING: DO NOT FOLLOW THE APPS2SD AS MOST ROMS ALREADY DO THIS FOR YOU.
If you do, it will break things.
-ivanmmj
Like My Guide(s)? Donate
Here we go!
Things you need:
A Rooted G1 Phone
Cyanogen ROM - Download v4.0.2
Cyanogen Recovery 1.4 - Download
Apps2SD - Download
Clean SD Card
Note: This will remove ALL files on your SD Card so please back it up
------------------------------------------------------------------------------------------------------------------
Install the New Recovery Image
Download the recovery image
Place the cm-recovery-1.3.1.img file in the root of your SD Card (Root = not in any folder)
Go back to your phone (Dont forget to unmount)
Open terminal and type in the following
Code:
su (wait for a screen to popup and press "allow")
flash_image recovery /sdcard/cm-recovery-1.3.1.img
------------------------------------------------------------------------------------------------------------------
Install Apps2SD
Download the Apps2sd apk from above
Place the apps2sd.apk on your sd card
Download a file manager like Linda or Astro from Market (They are both free)
Go to Settings > Applications and check the Unknown Sources button
Open up the file manager you just downloaded and find the apps2sd on your sdcard
Press on the app and install the Package Installer and press on Install
Apps2sd should now be installed
------------------------------------------------------------------------------------------------------------------
Partition Fat32/Ext2 with App2SD
Open up Apps2SD
It will show you a screen telling you that your card is not partition and you will have a sliding bar to choose the amount of space you want for an EXT2 partition
I suggest a max of 600mb for EXT2 space (I use 500mb)
Press Ok
You will get a Force Close screen DONT PRESS FORCE CLOSE PRESS WAIT
You will get a reboot message, Press Reboot
You now have a EXT2 partition
------------------------------------------------------------------------------------------------------------------
Upgrading your EXT2 Partition to EXT3
Note: You do need the Cyanogen Recovery image for this to work!
Reboot into Recovery (Home + Power)
Go to console (Alt+x)
Press Enter
Type the following in the Console:
Code:
upgrade_fs
Wait for it to finish
Congrats! You now have a Fat32/EXT3 partitioned Sd Card!
------------------------------------------------------------------------------------------------------------------
Installing the Cyanogen ROM with Auto Apps2SD
Download the ROM
Rename the file from cm-xxxxxxx.zip to update.zip
Place update.zip at the root of your sd card (Root = Not in any folder)
Reboot into Recovery (Home + Power)
Wipe (alt+w)
and Flash (alt+s)
Wait for it to finish and reboot!
------------------------------------------------------------------------------------------------------------------
Congratulations! You now have a Fat32/EXT3 Partitioned SD Card with auto Apps2SD enabled. You can check if you have both partitions in Settings > Sd Card and Storage. Remember, this is Auto Apps2SD, that means the everytime you reboot it will move all your installed apps to your sd card AUTOMATICALLY!
------------------------------------------------------------------------------------------------------------------
Format your EXT3 Partition (ADB is needed)
Code:
adb remount
adb shell
rm -r /system/sd/*
reboot recovery
then flash the update.
------------------------------------------------------------------------------------------------------------------
Here is another way to partition your sd card!
Note: You will need The latest CM recovery image
This guide will partition your SD card with 32 mb swap, and 512 mb EXT4 partitions!
WARNING! This will erase EVERYTHING on your SD Card!
Note: ADB Is needed for this script to work. If you dont have ADb working please read the ADB Sticky in the Q & A Forum
Step 1:
Download the necessary files HERE
Step 2:
Place the sdparted.sh file in C:\ Note: Do not place it in any folders!
Place adb.exe and AdbWinApi.dll in C:\Windows\system32
Step 3:
Run sdparted.bat
Thats it! All done!
Thank you 51dusty for the sdparted Script!
Batch file made by me!
Great guide...again =] But this way is MUCH MORE stable.
http://forum.xda-developers.com/showthread.php?t=534714
ya i know i saw that guide. I decided to put this one up becuase it uses minimal commands and doesnt involve a lot of terminal usage and stuff. Just another way to partition i guess.
Ok I looked in settings and storage. This is what I have....sd card total 6,501mb available space 5,813mb sdcard secondary 1,048mb available space 829mb but for internal space it's showing 86mb. Did I do this process right? Is my internal space suppose to have much more space? When I download something it takes away the internal memory.
lazee_smurf said:
Ok I looked in settings and storage. This is what I have....sd card total 6,501mb available space 5,813mb sdcard secondary 1,048mb available space 829mb but for internal space it's showing 86mb. Did I do this process right? Is my internal space suppose to have much more space? When I download something it takes away the internal memory.
Click to expand...
Click to collapse
yup! you are all good! 86mb for a cupcake rom is perfect! Congrats!
So what goes into the secondary storage because if I download something the internal space gets used
lazee_smurf said:
So what goes into the secondary storage because if I download something the internal space gets used
Click to expand...
Click to collapse
just reboot and your app will go to your sd card.
nephron said:
just reboot and your app will go to your sd card.
Click to expand...
Click to collapse
Thanks for the help!
Greetings
I knew it all could'nt go as smoothly as the new rom install ^_^
When I try to run apps2sd wether out of astro or from the app panel, it goes to a black screen, and thats it. The phone is not locked, I just hit home (after waiting for minutes for something to happen) and I'm back at my home screen.
I did'nt think I skipped any steps. Idea's ?
Thanks for the Sticky Guide
upgrading filesystem
I have the right recovery if I upgrade from ext2 to ext3 will I lose all my apps?
installed app2sd it asked if I wanted to reboot, I hit reboot and now I'm stuck on the G1 screen
maybeoneday said:
installed app2sd it asked if I wanted to reboot, I hit reboot and now I'm stuck on the G1 screen
Click to expand...
Click to collapse
This is why you don't partition your sdcard using this. It works most of the time but not always. Wipe and reformat your sdcard. Then reflash ROM
pistol4413 said:
I have the right recovery if I upgrade from ext2 to ext3 will I lose all my apps?
Click to expand...
Click to collapse
No you will not.
sweet
alritewhadeva said:
No you will not.
Click to expand...
Click to collapse
Sweet man thanx!
ext3 slowed my g1 down
I jus upgraded my partition using this guide and my fone seems WAY SLOWER. Is there anyway to downgrade safely back to ext2 without wiping the partion clean? Or do u recomed an app I already have an overclock app.
fixed problem!
I fixed the issue. Lol I feel kinda dumb. Just has to many processes running that where eating memory.
I am lost. I have the newer SPL and JF 1.51 adp. Why all of these steps for apps2sd?
Should it not be:?
1. Format card using a partition program and create ext3 / FAT partitions
2. Install newest Cy rom
3. It automatically moves the apps when it sees the ext3 related parameters.
Why all of the steps in this thread? Am I missing more brain than I normally do?
Why would I need the 1.3.1 recovery rom? Are all of these steps if you do not already have a JF rom?
Thanks!
rushless said:
I am lost. I have the newer SPL and JF 1.51 adp. Why all of these steps for apps2sd?
Should it not be:?
1. Format card using a partition program and create ext3 / FAT partitions
2. Install newest Cy rom
3. It automatically moves the apps when it sees the ext3 related parameters.
Why all of the steps in this thread? Am I missing more brain than I normally do?
Why would I need the 1.3.1 recovery rom? Are all of these steps if you do not already have a JF rom?
Thanks!
Click to expand...
Click to collapse
Apps2SD2 detects if your card has been formated with an ext2 partition. If not it will format your sd card for you therefor not needing a computer program. The new reocvery 1.3.1 allows you to run the upgrade_fs command to format the ext2 to ext3 and also has other features such as gparted and fix ext filesystem.
my question is this...I already have cyanogen's rom installed...I have been away from a computer and the internet for about a week so I'm still on 3.6.5...which is fine with me.
In Cyan's thread, he says:
DO NOT RUN ANY OTHER APPS2SD APPLICATIONS ON THIS BUILD. YOU WILL BREAK YOUR SYSTEM. THEY ARE NOT NECESSARY BECAUSE THIS ROM WILL DO A2SD AUTOMATICALLY AND BETTER!
Click to expand...
Click to collapse
however one of the steps to partitioning the sd card in this post is installing apps2sd..
i want to partition the card...but I don't want to break my system...am I missing something? clarification please?

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

Switchrom -s / Re-Parition SD / Switchrom -r

So if I have a few roms that I save with switchrom and then I decide to backup my sd to my computer.....
Then format my sd card in a different way (ie used to be ext2, now I want ext4)
And then I copy the files back onto my sdcard after the repartition....will I be able to restore those switchroms?
Because from what I have tried...it usually doesn't work...(I forget the exact error message) is there some command I am forgetting in between?
I have done this with BART, which is basically switchrom with a few modifications...
Here is what I did just the other day:
Reboot into recovery (Amon-RA)
Drop down into console
Run :
Code:
bart -s myRomName
After completed, type
Code:
reboot recovery
Then choose to Mount the SD card and copy everything over to your PC
Once completed, un-mount the SD card and then move onto partitioning...
I went from 128MB swap to 256MB swap
I went from 640MB ext2 to 1024MB ext2
After that, I upgraded to ext3... I have heard that ext2 is better, but every
time I use that format, my SD card gets corrupted in a matter of days.
(Hence the reason why I sent through this process recently.) I will "three
finger salute" the phone at times due to a hanging app, from the countless
ones that I download to try out, so this might be causing the problem.
After the upgrade, mount the SD card and copy your FAT32 section back.
Drop down into the console and type
Code:
bart -l
You should see the ROM that you just stored...
Type
Code:
bart -r myRomName
Once completed type
Code:
reboot recovery
Then go the Wipe section and Clear the Dalvik cache...
Finally reboot...
I have done this numerous times on both my and my wife's G1... I have also
done the above steps keeping the same sizes of the partitions and moving
from ext2 -> ext3 -> ext4 to give each of them a try...
Using BART will only back up the files on the ext partition, not the filesystem...
It is like a fresh install... At least that has been my experience with it...
Cool well I might use Bart then instead of switchrom since it seems to have worked for you without any hiccups.
Essentially I am doing the same process as above except with switchrom rather than bart (although i have used all 3 forms of backup in Amon Ra's Recovery)
Just wanted to make sure there wasnt some special command in console to fix something outta whack.
I figured my method would work but for some reason it doesn't like the repartitioning of the sdcard in between switchrom -s and switchrom -r
Thinking it might have been a fluke.....
Yep, I had to migrate my switchROM folder when I got my new SD Card and had no issues.

[Q] Switching SD Cards NO Apps2SD

Hi, I have a G1 rooted with the SuperD 1.9.3 Rom, I never partitioned my SD card or anything like that. I want to upgrade my SD Card and partition it to get Apps2SD and keep the same Rom. I am not sure what steps to take...
lmt125 said:
Hi, I have a G1 rooted with the SuperD 1.9.3 Rom, I never partitioned my SD card or anything like that. I want to upgrade my SD Card and partition it to get Apps2SD and keep the same Rom. I am not sure what steps to take...
Click to expand...
Click to collapse
Which recovery do you have? If you don't yet, make sure to upgrade to Amon_Ra latest. Once you have that, reboot into recovery, select partition card and follow directions on screen. This will wipe your card completely so backup anything you want to save. It will not affect your rom in any way. You may have to move your existing apps manually, not sure.
How do i know what recovery i have? Do I partition my current sd card or the new one?
So I do not need to reflash the Super D?
lmt125 said:
How do i know what recovery i have? Do I partition my current sd card or the new one?
So I do not need to reflash the Super D?
Click to expand...
Click to collapse
You would boot into recovery and look to see which one you have, it will say it right on top. You will partition your new card. Absolutely no need to reflash your rom, it will recognize your ext partition and install all future apps in it automatically. As I said, I'm not sure about existing apps, you may need to move them manually.
It says Android Sysem Recovery Utility Build: JFv1.42 There is nothing that says Partition SD or anything like that... Now my rom is on my current sd card if I don't flash it to the new one my phone still knows what rom I have? Sorry about all the questions thanks for your help =)
I was thinking of doing this to install Amon RA's recovery img
I got it from another forum in here....
Copy recovery-RA-dream-v1.7.0.img to the root of your sdcard
Boot into your current custom recovery (boot while holding HOME)
select console from the menu
#mount -a (this can give back an error if you don't have an ext partition, don't worry about it and just proceed)
#flash_image recovery /sdcard/recovery-RA-dream-v1.7.0.img
JF's recovery does not have that option because it's really, really, really old. We did not even have apps to sd back then.
Flash RA's recovery (directions seem right, I assume you got them out of RA's thread), you'll see the difference: many more options, etc
Good luck.
Ok, so I am going to do the following steps....
1. Flash Amon Ra's recovery image
2. Reboot phone
3. Get into recovery again
4. Back up my sd card on the computer, remove sd card from phone
5. Insert new sd card, partition sd card
6. Transfer files from old sd card including update.zip which is the rom
7. Reboot phone
Let me know if I'm missing something thanks for all your help!
I'm going to do this over the weekend...
Ok, so I got the new Amon RA recovery image but haven't done anything else...lol. So can you tell me if those steps are right? And why don't I need to flash the rom again...I currently have it on my sd card...I'm a bit confused
1. Reboot to recovery. Partition your card (I suggest 512mb for ext partition, rest is fat, follow instructions within recovery).
2. Upgrade ext to ext3.
3. Reboot (your phone will move your existing apps onto sd.) It may take a while to fully boot, just give it 10 min or so.
4. In terminal emulator type
Code:
su
fix_permissions
5. Reboot again.
5. Transfer whatever you had on your old sdcard (music, pics, etc) onto your new card.
As far as flashing the rom again.... why? Your OP says you want to keep your existing rom.
To check if your apps were moved:
In terminal:
Code:
su
ls /system/sd/app
ls /system/sd/app-private
ls /system/sd/dalvik-cache
Should give you print-out of what you have on ext partition of your sdcard (or you can use root explorer or whatever other file manager, I'm a bit old shool so I prefer terminal or adb)
5. Reboot again.
5. Transfer whatever you had on your old sdcard (music, pics, etc) onto your new card.
Okay in step 5. Reboot again do I just type in the terminal emulator reboot or reboot recovery?
Also when you say "transfer whatever you had on your old card..." Do I also transfer the file that says update.zip?
Sorry for all the questions, I should be getting my new sd card today and will try it out tonight.
Thank you.
You just type reboot.
It is up to you what you want to transfer onto your new card. I assume that update.zip is your current rom. If so, it's nice to have just in case but it will not make any difference in how the phone works. It's just an install file that you use once (unless, of course something goes terribly wrong and we all have been there ) but it's nice to have all tools needed on your card so you can quickly recover from any problems.)
BTW, with your new shiny recovery (RA1.7), you don't have to rename your files to update.zip. You can name them whatever you want (i.e Super-D1.9.3.zip, Recovery.zip) and, if you decide to reflash something, at least you will know what it is. Your new recovery will let you choose which file to flash so you can have more then one .zip file on your card if you want.
Ok so I still haven't gotten my new card! It should be here next week...Anyways I tried using switchrom to store my current just in case but I get this error Can't mount /dev/block/mmcblk0p1 (or /dev/block/mmcblk0) (No such file or directory)
Any clues why I'm getting this do I need to have my phone connected by USB or something to a computer....?
Thanks hopefully I'll stop asking so many questions...I tried this solution but no luck
Originally Posted by siraf View Post
Guys, I just had this problem too .. at first i was so devastated. I'm glad i solved it.
I don't know if my solution is the ultimate solution or not but you guys can give it a try.
problem :
"E:Can't mount /dev/block/mmcblk0p1 (or /dev/block/mmcblk0) (No such file or directory)"
In the Android System Recovery, select "USB-MS Toggle". It will enabled/disable the feature. Do it one more round and it will solve the problem.
It's telling you that it can't mount SD card.
Back up all of your stuff from SD card, format it and try again, that's the only thing I can think of.
Actually, I just ended up doing a Nandroid Backup just did Nandroid not Nandroid +ext since I don't have this card partitioned...it is backed up!
Ok buddy its easier if you do the whole process through the sdcard
First you should backup everything on your sdcard and do a BART or NAN+EXT then partion your card and restore your BART or NAN+EXT and your good to go
If this does not work press my name and look at my threads because I ask this same quetion a while ago
Post again if this does not work
Sent from my HTC Dream using Droidfreeks's App
DroidFreek said:
Ok buddy its easier if you do the whole process through the sdcard
First you should backup everything on your sdcard and do a BART or NAN+EXT then partion your card and restore your BART or NAN+EXT and your good to go
If this does not work press my name and look at my threads because I ask this same quetion a while ago
Post again if this does not work
Sent from my HTC Dream using Droidfreeks's App
Click to expand...
Click to collapse
Hi, I tried doing a Nan+ext backup but I got this error : Run nandroid-mobile.sh via console I also tried doing a Bart backup and it also said Run Bart via console...
So I just did a regular Nan Backup...I don't have my current sd card partitioned...should I partition it so I can do the Nan+ext I currently have a 2gb card and it doesn't have a class number.... Maybe I should format my card?
Thanks!
Ohh ok I see ur problem it won't let u backup nand+ext if you don't have a ext
since you backed up already go ahead and throw the nandriod and any other files on sd card to your pc the format your sd create the app partion and swap partion make sure u formate it ext3 or ext4 depending on what ur rom uses put the nandroid back on sd after format and restore post if it works or not
If this don't work just reverse the process put nad back on pc format card to what is was before then put nand back on sd and restore
Sent from my HTC Dream using XDA App
OK so I partitioned my current memory card =) and was able to succesfully do a nandroid +ext...so now when I get my new card I just have to go into recovery and do a nandroid restore and transfer all my files right? Thanks
Remember to partion your sdcard before transfer
Sent from my HTC Dream using XDA App
Ok so I tried switching my cards and formatted my new card,paritioned it, transfered the files from my other sd card, and tried to a nandroid restore...that's when I get the same error as before to do it from console.
I tried taking all the files out and repartitioning the sd card doing everything again no luck. Reflashed my rom and turned it on after it boots like normal I get a black screen. So just went back to my old sd card was getting force closes so did nandroid restore it said it did but would boot normal and get force closes.
So I reflashed my rom and reinstalled everything manually...from sd card as my market disappeared got it back after reinstalled it...
Any suggestions as I really want a bigger capacity memory card....=/

[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.

Categories

Resources