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
Related
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.
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.
I have been searching the forums for 2 hours trying to figure this out and I cannot find out how. I tried following the tutorials on the forums here on how to partition the SD card but none of the settings that were listed are not on my recovery. But I still tried it anyways. Here is the list of options on my recovery
Reboot system now
Nandroid v2.2 backup
Nandroid v2.2 restore
Apply sdcard:update.zip
Apply sdcard:choose zip
Wipe data/factory reset
Wipe SD:ext partition
Wipe SD:dalvik-cache
Part SD:fat32+ext2+swap
Part SDnly fat32
Repair ext filesystem
Convert ext2 to ext3
Fix apk uid mismatches
Fix rotate
USB Mass storage on
USB Mass storage off
The bottom says "Build : RA-heroc-v1.2.3".
Upon reading the tutorials, I decided to try something different. So I wiped ext partion, parted sd fat32 ext2 and swap, then converted ext2 to ext3. Applied PureHero 2.1 and I enabled Apps2SD, move apps to sd, move dalvik cache to sd, enable JIT, and changed dalvik heap to 24mb. It rebooted and none of the applications I downloaded and installed were transferred to the SD.
Before this I applied a rom before wiping and parting and changed the same settings and it wasn't working then either.
I tried using the cmd and located to my android-sdk-windows and tried finding what version of apps2sd I had but it kept aborting. I tried repairing and it kept aborting, I even tried installing and it kept aborting.
I am at a loss here and I am trying to get all of this working.
It is a 2gb card and it is only showing 1.34gb available so I have no idea how to give me the full 2gb like it was before I tried partitioning.
Before I posted this, I applied the program at http://forum.xda-developers.com/showthread.php?t=715116 and that didn't work as well.
Please help.
I'm not sure if it makes a difference, but I would try to upgrade to RA-heroc-v1.6.x, it might be your recovery not partitioning correctly or something. Once you have upgraded, go ahead and wipe everything (data, dalvik, and ext). Flash your ROM. Before you move your dalvik to the sd card you want to make sure you have at least a class 4 sd card. Once your phone is booted up check your internal memory and you should have 90+M out of 159 or so. If you have that then I am pretty sure your ap2sd is working. You can also check to make sure it is working through adb. I don't use the option in recovery to move the apps to sd. Hope this helps, and I hope my information is correct, lol. I still consider myself a noob.
Ok ill do some research on how to update and see what I find. If that don't work then ill come back and keep you updated.
Thanks
EDIT: I have tried updating my Recovery using FlashRec and it isn't backing up my recovery or finding the recovery at all. I am on ubuntu so maybe that might be the problem, idk. Is there any other way I can update my recovery? I have 1.6.2 downloaded and just need to apply it.
puppetmstr said:
Is there any other way I can update my recovery? I have 1.6.2 downloaded and just need to apply it.
Click to expand...
Click to collapse
The instructions are here http://forum.xda-developers.com/showthread.php?t=581521#1
I used the adb method last night no problem.
Note: the first thing it tells you to type is "mount -a"
After which your phone might spit out some sort of error message. Don't worry about it, it doesn't affect anything. That's what people said, and it didn't affect me.
c00ller said:
The instructions are here http://forum.xda-developers.com/showthread.php?t=581521#1
I used the adb method last night no problem.
Note: the first thing it tells you to type is "mount -a"
After which your phone might spit out some sort of error message. Don't worry about it, it doesn't affect anything. That's what people said, and it didn't affect me.
Click to expand...
Click to collapse
Well this is confusing lol. I went into recovery, went into USB mode getting ready to update my recovery option and a screen popped up in ubuntu with the folders app, app-private, dalvik-cache, and lost+found. Apparently I had apps2sd working the entire time... But I nandroid last night back to ZenEXP. Idk if it still works in Pure Hero.
But now that I have apps2sd working, I can flash a new rom and still have my applications right?
EDIT: In Windows 7, it doesn't show the partition anymore for the apps2sd. So im just gonna go ahead and update recovery then repartition everything.
Please update with whether or not your apps still work after flashing a new ROM, I want to know if it works like that.
c00ller said:
Please update with whether or not your apps still work after flashing a new ROM, I want to know if it works like that.
Click to expand...
Click to collapse
I cant update the recovery at all. I have tried both ways and it fails.
I tried adb and as soon as i try to use the command "mount -a" it says "no such device". I tried using "mount /sdcard" and it says "Device or resource is busy".
On the Fastboot + adb I can load into fastboot. But when i type "fastboot boot recovery-RA-heroc-v1.6.2-blue.img" it says "cannot load fastboot boot 'recovery-RA-heroc-v1.6.2-blue.img'".
I tried pressing the trackball on fastboot usb and the screen goes black for a second, then i hear a connect noise in the speakers then it shows fastboot for a split second then fastboot usb again.
Also in Fastbot +adb when I use the command "adb shell mount /sdcard" it says "device not found".
EDIT: im also starting to think my adb shell is broken or something lol.
Ok nevermind I got it working. I typed mount /sdcard and it said it was busy but then i used the command "flash_image recovery /sdcard/recovery-RA-heroc-v1.6.2-blue.img" then Rebooted into recovery and it says 1.6.2 and its blue. I just hope I did it the right way and didnt **** anything up...
EDIT: Ok well I partitioned it with 64mb swap, 1024mb ext2, converted to ext3, and loaded up PureHero 2.1. How do I know if it is working? I have my DConfig options set to move dalvik and apps to sd, with JIT enabled. Do I just install an app and see if the internal memory lowers or stays the same? How do I access the apps folder through USB mode?
This is how to tell if you have A2SD working
http://forum.xda-developers.com/showpost.php?p=6848245&postcount=80
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.
(Please let me know if this is the correct forum!)
I have a Motorola Milestone 1 (A853) with Open Recovery 1.46 on a 16GB card. I've been using this to try new roms for over 2 years now. Everything was fine until I tried to create an ext 2 partition using MiniTool Partition Wizard, but things went sideways. Needless to say I wiped the card, created a new 10GB Primary Partition on it and a 4 GB ext2 for further usage. Then, I restored backup items on the card (pictures etc.) plus a fresh new version of Open Recovery. Now, every time I am at the Recovery menu and try to apply sdcard:update.zip I get this message:
E:Can't open cache/recovery/command (<-- this is nothing new - seen it many times before but still able to boot into open recovery)
-- Install from sdcard...
Finding update package...
E:Can't mount /dev/block/mmcblk0p1 (or /dev/block/mmcblk0)
(Invalid argument)
E:Can't mount SDCARD:update.zip
Installation aborted
.. any ideas what to do?
It seems like your phone dont mount the sdcard properly.
Try out a 2ndboot OR. (there is one from kabaldan and one from FuFu)
get a proper sdcard, and unzip to the root OpenRecovery from this url: http://forum.xda-developers.com/showthread.php?t=1897048
And voila! :good:
Thanks for the assistance guys.
The card is fine, It is seen in Windows perfectly with the 2 new partitions, but the phone is not seeing it. I was following MrTapa's guide here before the trouble started: http://forum.xda-developers.com/showthread.php?t=1750888 . When the card worked before, it was formatted using NTFS and both Windows and the phone could see it. Now, the 10 GB partition is NTFS and it has the additional 4 GB ext2 partition. Windows sees it, the phone does not.
Does Skrilax_CZ's note have anything to do with it? "If file "/system/etc/install-recovery.sh" exists on your Milestone, delete it (prior to flashing the SBF)" <-- from http://modmymobile.com/forums/563-m.../531599-open-recovery-v1-46-11-21-2010-a.html
lezztor said:
Thanks for the assistance guys.
The card is fine, It is seen in Windows perfectly with the 2 new partitions, but the phone is not seeing it. I was following MrTapa's guide here before the trouble started: http://forum.xda-developers.com/showthread.php?t=1750888 . When the card worked before, it was formatted using NTFS and both Windows and the phone could see it. Now, the 10 GB partition is NTFS and it has the additional 4 GB ext2 partition. Windows sees it, the phone does not.
Does Skrilax_CZ's note have anything to do with it? "If file "/system/etc/install-recovery.sh" exists on your Milestone, delete it (prior to flashing the SBF)" <-- from http://modmymobile.com/forums/563-m.../531599-open-recovery-v1-46-11-21-2010-a.html
Click to expand...
Click to collapse
NTFS?
Replace it with FAT32. Then it should work.
In the link you provided check step 9 (though FAT32 should work fine even with 2GB cards)
Ok - so reformatted 10GB partition to Fat32 and loaded OpenRecovery again to root of sd card - same error. I might also mention that I tried Fat32 on another smaller (2GB) card with an ext2 partition and it gave the same error. I'm beginning to believe that this phone has a problem with multi-partition sd cards?
Just tried the original way - one partition using NTFS ... same error. Frustrating .. over 3 days on this now ...
NTFS and Android can not work.
Unless someone included ntfs-3g into the kernel - but that would be a madman's work...
Delete every partition off your sd card, boot up Android, it will prompt you to format it, do it.
Copy recovery (OpenRecovery directory + update.zip) to sd card, try booting to recovery.
If it works resize FAT partition created by android to make space for an ext partition, boot Android again to see if it's ok with the changes.
Solved - if anyone is trying create an additional ext2 partition remember that BOTH the FAT32 and EXT2 must be created as PRIMARY. The app I was using defaulted to logical ...