I recently flashed Grankin01's kernel and one of the CM7 preview nightlies. Everything seemed to be fine until this morning when I tried to mount my SD Card to flash one of the new nightlies. My Redhat box comes up as
The volume '_PNG ' uses the vfat file system which is not supported by your system.
My Vista box doesn't pick it up at all, even trying to mount the card fails on the phone. HALP? Am I going to have to reformat the card? Is there a way around this without losing all my crap?
Try flashing the stock kernel that comes with cm7. But it sounds like you may have to format the card.
Reflashed with what I have on the card currently, no dice. Super-weak
Gonna try reloading clockworkmod 2.5, dropping back down to a non-gingerbread and see what happens there. If not, guess I'll be formatting away
Couldn't format to save my life. Had to partition the card through recovery to get it to mount
But after trial and error (and error and error and error F'ING MMCBLK1P1) I finally got it to go
Now to rebuild the phone from scratch. Oh well, probably didn't need all that junk I acquired anyway
Related
I tried to update to the 2.33 jachero rom got a bootloop
tried an older version got a bootloop
tried the dudes build got a bootloop
i then used and old sdcard from my sidekick and i got on the dudes build
i tried to use apps2sd on the stock 1gb card which i previously already had and it said i didnt have a partition on it which i did previously so it set it up and rebooted into a bootloop
is this a bad sd card?
any ideas?
Is it trying to move the /data to the sd? If it is, that would be the issue, Least it was for me when I went to 1.51
sorry havent been on here in awhile been on vacation
i tried upgrading to jacshero2.3 at the time and i just got a constant bootloop nothing would happen so i took an old sdcard from my sidekick lx and put back on the dudes build and it worked but i cant reboot the phone from the sd card i tried to install hero on it will bootloop.
also i lost appstosd nothing saves to the sd but if i open partion manager it says i still have ext2.
and if i use appstosd it says i have to partition my sd card and if i try it the phone reboots and bootloops
Yea sounds like you need to redo the sd card.. Id just save the apps and apps-private folder and wipe the rest. Then put the apps and apps-private back on after you wiped the card then relink them.
is it a simple copy and paste
it started up today wit the sd card so ill reformat it
Its not a simple copy and paste.. Usually if you use linux you need to make sure the attributes are saved as well. cp -a
I've been using android on my phone for awhile, and tried a bunch of different builds and never got this error. Yesterday when i was switching back to shubcraft all of the sudden the boot loader gives me
mounting /dev/block/mmcblk0p1 on /sdcard failed: invalid argument
failed
failed to mount sd card. cannot continue.
/bin/sh: cant't access tty; job control turned off
i tried loading just about ever build and get the same thing.
I've changed the startup.txt and i always reformat before i switch builds. i was thinking it might be the sd card itself, but it works fine in winmo.
if anyone can help me it would be much appreciated, im having android withdrawls...
oh and its the stock 16gb class 2
EDIT: It randomly started working again...strange...
This Is What I Do
I was getting either the same thing or something very close to it on about 2 rom to the best of my understanding is when your trying to flash (for lack of better words) a new rom you still have some left over traces either on your storage card or the phone so what you need to do is format your SD card and reflash your phones rom.
I took the origin file put it on my sd card unzipped it there went into the android rom folder cut the plain android folder paste it withe the other folders then reased every folder EXCEPT the PLAIN ANDROID FOLDER now put the sd card in the phone enable the the sound then install android.
To be able to watch the process after you flash your rom go to settings, system, power (battery) and uncheck everything so it doesn't sleep. when you install now you will see the progress and will be able to read the progress if you see 2 things have failed
This is my process and it hasn't failed yet when I didn't do it this way I had fails.
Striving said:
I was getting either the same thing or something very close to it on about 2 rom to the best of my understanding is when your trying to flash (for lack of better words) a new rom you still have some left over traces either on your storage card or the phone so what you need to do is format your SD card and reflash your phones rom.
I took the origin file put it on my sd card unzipped it there went into the android rom folder cut the plain android folder paste it withe the other folders then reased every folder EXCEPT the PLAIN ANDROID FOLDER now put the sd card in the phone enable the the sound then install android.
To be able to watch the process after you flash your rom go to settings, system, power (battery) and uncheck everything so it doesn't sleep. when you install now you will see the progress and will be able to read the progress if you see 2 things have failed
This is my process and it hasn't failed yet when I didn't do it this way I had fails.
Click to expand...
Click to collapse
you can search a tool named SDFORMATER V2.0, it will be worked.
okay this is now happening to me as well!
had been using Android and various different builds without hitch.
but today after trying the Hyperdroid build the sd card fails to mount on startup.
Editing the startup.txt does nothing, have also flash to the latest chuckyrom and formatted the sd card time and time again and tried different builds.
anyone have any other suggestions?
Ta
working again now.
the fix for me was to reupload my backup to the sd, format then upload the required new build.
very odd...
snigs said:
working again now.
the fix for me was to reupload my backup to the sd, format then upload the required new build.
very odd...
Click to expand...
Click to collapse
odd indeed...for me i had to reformat my sd card using my phone, didnt really make any sense to me but it worked
I had been using a 16GB external SD card on my phone and it had been working fine. I decided to swap it out for an 8GB card and now my phone doesn't even see that the card is installed. When I try to mount the card using the storage settings, it tells me that it's preparing the SD card and then it doesn't do anything else.
I've tried reformatting the card, reinstalling CM9, purging both cache and Dalvik. Nothing seems to help. The card works perfectly on my PC. What should I do to get the card to work on my phone?
What happens if you put the 16 back in? Does it mount or does it fall into the same behavior as the 8? So your file explore won't see the emmc or it is just that settings->storage doesn't see it?
Just so we are clear (and I assume you know this b/c you are running nightlies) but I have to ask, you know that External_SD is now the emmc? Sorry.
Thank you for your help. When I put the 16GB back in it acts the same way now. When I browse to the emmc folder with Root Explorer, it shows it as being empty, even though I have the SD Card installed. For some reason, it's just not mounting any of them at all. Very weird.
Did you unmount it before you took it out initially? Maybe try putting it in and rebooting and see if it mounts. Or try rebooting w/o it and them putting it in to see if it remounts. Gotta be something simple cause those are always the hardest to find.
I would suggest a few options then.
1. Post something in the CM9 thread and maybe someone will know a little more about it and possibly some code that you might type in the re-mount it. I have an idea what it would be but I am not running CM9 now, so not sure I can do it ad-hoc.
2. If you can see your internal, then maybe make a nandroid and Odin back to stock 2.1, then reinstall. (but your OP says that you already did that, hmm.)
3. There was a mount fix floating around somewhere on Euphoria or Passion maybe Slim or AOKP. That was mainly for mounting to PC.
See what Faultexception thinks, since he is maintaining the CM9 ROM.
I did unmount it before removing it. I've tried all of the steps you've suggested and even posted on the CM9 thread. Hopefully someone on there has dealt with this before. Thanks for your help. I appreciate it.
I too is having the exact issue, have tried all the above and still nothing.
Haha been having this issue on ics passion for months.. ive just ggotten over it.
My 8gb doesnt work but my exact same model/brand 4gb does.. nothint i can do will fix it.
ive tried secure formatting to every fs imaginable and several other things
Sent from a cell tower to the XDA server to you.
Hi, so I've tried everything I can think of to restore my Nook to the stock 1.4.1 but nothing has worked and I've given up before I break anything else...
This all started when I was trying to install the CM7.2/CM9 dual boot from SD card - I burned the image to the SD card and booted but the device just hanged at a black screen (for a lot longer than it should have) after the CM "loading" startup screen.. I tried removing the SD card after holding the power button to turn it off but it then refused to boot to the EMMC stock OS... Somehow (I've only ever used SD card CM ROM's) an old CWM install (v.3.0.2 or something) was installed on the internal memory that booted when I tried to launch a factory reset (Power + N + vol+).
I then followed an older guide to restore to stock by formatting the /system and /data and installing a .zip from sd card (the nookcolor_1_4_1_signed.zip) but it failed with a (bad) error....
Now I don't know what to do. The device now hangs at "Read Forever" and the internal CWM is gone, as well as everything else I'm assuming... It will boot into CWM if it's installed on an SD card, but without that it will just reboot into Read Forever when I try to turn it off...
An aside, but now that I've checked with external CWM again, it appears there is now a "/system1, /system2, /data1, and /data2" file on the EMMC...
TL;DR: How do I restore Nook Color to stock 1.4.1 from CWM installed on an external SD card without flagging a "(bad)" error with the install?
Thank you for any help and I hope I haven't bricked this device... Hopefully this is just a case of ignorance on my part
EDIT: I've tried re-downloading the 1.4.1 and even a 1.2 signed ROM with out success. I haven't rooted the device, but I do not know how the internal CWM got there, as well as the fact that the external SD dual boot didn't work.. I'm using a new SanDisk Ultra 16GB SDHC Class 10 card if it makes a difference..
Could not having rooted the Nook be the only cause?
I had successfully dual booted the CM7.2 and CM9 for months until my old 16GB card broke... This was the new card I bought last week and it's been nothing but problems, exacerbated by myself, probably :/
I
cekren said:
Hi, so I've tried everything I can think of to restore my Nook to the stock 1.4.1 but nothing has worked and I've given up before I break anything else...
This all started when I was trying to install the CM7.2/CM9 dual boot from SD card - I burned the image to the SD card and booted but the device just hanged at a black screen (for a lot longer than it should have) after the CM "loading" startup screen.. I tried removing the SD card after holding the power button to turn it off but it then refused to boot to the EMMC stock OS... Somehow (I've only ever used SD card CM ROM's) an old CWM install (v.3.0.2 or something) was installed on the internal memory that booted when I tried to launch a factory reset (Power + N + vol+).
I then followed an older guide to restore to stock by formatting the /system and /data and installing a .zip from sd card (the nookcolor_1_4_1_signed.zip) but it failed with a (bad) error....
Now I don't know what to do. The device now hangs at "Read Forever" and the internal CWM is gone, as well as everything else I'm assuming... It will boot into CWM if it's installed on an SD card, but without that it will just reboot into Read Forever when I try to turn it off...
An aside, but now that I've checked with external CWM again, it appears there is now a "/system1, /system2, /data1, and /data2" file on the EMMC...
TL;DR: How do I restore Nook Color to stock 1.4.1 from CWM installed on an external SD card without flagging a "(bad)" error with the install?
Thank you for any help and I hope I haven't bricked this device... Hopefully this is just a case of ignorance on my part
EDIT: I've tried re-downloading the 1.4.1 and even a 1.2 signed ROM with out success. I haven't rooted the device, but I do not know how the internal CWM got there, as well as the fact that the external SD dual boot didn't work.. I'm using a new SanDisk Ultra 16GB SDHC Class 10 card if it makes a difference..
Could not having rooted the Nook be the only cause?
I had successfully dual booted the CM7.2 and CM9 for months until my old 16GB card broke... This was the new card I bought last week and it's been nothing but problems, exacerbated by myself, probably :/
Click to expand...
Click to collapse
Easy solution. Go to my tips thread linked in my signature and make a bootable CWM card per item A10. Then flash my format 567 zip. Then go to item A15 and download my 1.4.3 stock ROM and flash that. Boot up, register and you are golden.
If you want to put a ROM on SD go to my updated SD instruction thread also in my signature.
Sent from my Nook HD+ Running CM10 on SD
leapinlar said:
I
Easy solution. Go to my tips thread linked in my signature and make a bootable CWM card per item A10. Then flash my format 567 zip. Then go to item A15 and download my 1.4.3 stock ROM and flash that. Boot up, register and you are golden.
If you want to put a ROM on SD go to my updated SD instruction thread also in my signature.
Sent from my Nook HD+ Running CM10 on SD
Click to expand...
Click to collapse
Thanks! I'll try that right when I get home..
EDIT - Awesome - It works! The dual boot card also works!
EDIT 2 - so... booting from the SD card still doesn't work... It just hangs at the Cyanogen7 boot video looping over and over (left to go to the store, got back and it was still looping)... holding power button down just resets the device while the SD card is in, doesn't actually shut down for more than 4 seconds or so....
Should I post this as a new thread? I'll try searching for anybody else having this problem in the mean time...
cekren said:
Thanks! I'll try that right when I get home..
EDIT - Awesome - It works! The dual boot card also works!
EDIT 2 - so... booting from the SD card still doesn't work... It just hangs at the Cyanogen7 boot video looping over and over (left to go to the store, got back and it was still looping)... holding power button down just resets the device while the SD card is in, doesn't actually shut down for more than 4 seconds or so....
Should I post this as a new thread? I'll try searching for anybody else having this problem in the mean time...
Click to expand...
Click to collapse
Are you using Racks' dual boot SD? If so, how recent is it? You might want to go to his special CWM and clear dalvik cache and try rebooting again.
Sent from my Nook HD+ Running CM10 on SD
leapinlar said:
Are you using Racks' dual boot SD? If so, how recent is it? You might want to go to his special CWM and clear dalvik cache and try rebooting again.
Sent from my Nook HD+ Running CM10 on SD
Click to expand...
Click to collapse
Yeah, I used the Dual Boot image I downloaded a couple days ago from Techerrata (I used the one at the top of the list that had the most downloads, connection I'm on is blocking Techerrata so I can't get the exact name ATM) with burned with Win32DiskImager, popped in the card and turned on but it just hangs. I'll try clearing the dalvik cache with his CWM image and see if it fixes anything..
EDIT - Ok, I tried clearing the cache, but it gives me the following error:
E:unkown volume path [/data]
I checked the Mounts and Storage Menu, and it looks like I still have "/system1, /system2, /data1, and /data2" directories, did the 567 format.zip not take care of whatever file structure or partition these were kept on in the EMMC?
cekren said:
Yeah, I used the Dual Boot image I downloaded a couple days ago from Techerrata (I used the one at the top of the list that had the most downloads, connection I'm on is blocking Techerrata so I can't get the exact name ATM) with burned with Win32DiskImager, popped in the card and turned on but it just hangs. I'll try clearing the dalvik cache with his CWM image and see if it fixes anything..
EDIT - Ok, I tried clearing the cache, but it gives me the following error:
E:unkown volume path [/data]
I checked the Mounts and Storage Menu, and it looks like I still have "/system1, /system2, /data1, and /data2" directories, did the 567 format.zip not take care of whatever file structure or partition these were kept on in the EMMC?
Click to expand...
Click to collapse
The format 567 zip was for clearing the partitions on internal memory (emmc). Those partitions you are looking at are on the SD card (system1, etc).
You might just try clearing cache with his cwm rather than dalvik cache. You also might get a better response posting your dual boot question on the dual boot thread. I don't know a lot about the dual boot.
leapinlar said:
The format 567 zip was for clearing the partitions on internal memory (emmc). Those partitions you are looking at are on the SD card (system1, etc).
You might just try clearing cache with his cwm rather than dalvik cache. You also might get a better response posting your dual boot question on the dual boot thread. I don't know a lot about the dual boot.
Click to expand...
Click to collapse
Sounds good, I'll try that. Thanks again for all the help, though!
One thing to note... the initial boot does take a while and sits on a black screen while the cache image and formatted. Racks has put that into the dual boots with loop mounting so each bootable system will have its own cache space and avoid overwriting cache data from nother ROM.
DizzyDen said:
One thing to note... the initial boot does take a while and sits on a black screen while the cache image and formatted. Racks has put that into the dual boots with loop mounting so each bootable system will have its own cache space and avoid overwriting cache data from nother ROM.
Click to expand...
Click to collapse
Good to know, but should it really take more than 90 minutes to initially boot? I let it boot up to CM7 on a freshly burned Class 10 card and left for the store, when I got back it was still at the boot video, watched it for another 5 minutes and it still didn't do anything... I don't really know what the problem is, could it be the card?
I have seen it take up to10 minutes, but 90 is definately excessive... I would suspect the card being the issue... class 10 cards are not good for running any operating system from. While they have exceptional sustained read/write speeds... they (generally) have poor random small read/write speeds, and this is the types of files used by an operating system.
DizzyDen said:
I have seen it take up to10 minutes, but 90 is definately excessive... I would suspect the card being the issue... class 10 cards are not good for running any operating system from. While they have exceptional sustained read/write speeds... they (generally) have poor random small read/write speeds, and this is the types of files used by an operating system.
Click to expand...
Click to collapse
Oh.. ok, well good to know! I'll pick up a different card today and see if that will work.
I got the Mirage 7.2 to work, by writing the "generic_sd.img" to the card, the coping the .zip download to the boot partition (renaming it to "update-cm7-mirage.zip" so the generic loader would see it)...
I inserted the card, booted, and Tux showed up and it ran through partitioning the card, expanding the mirage zip, and shutting down. However, when I turned it back on, it showed the Cyanogen mod bootloader, and I selected "SD Normal" but Tux showed up again and it went through trying to partition again (which it said was not needed, so it skipped) and finding an update- / .zip file (which it deleted when it expanded it before), same with the SD recovery boot option... Should I just try a new card?
EDIT - So, I was sick of messing with SD card booting, and realized I really don't care if I have the stock OS on it anymore since my warranty is about to run out anyway, I just rooted it an installed Mirage 7.2 and it works! Thanks for the help with the SD Card problems, though!
I thought i will have no problems now and nothing will suprise me with my HTC, but of course i was wrong =)
As i solved my last problem with Google Play, now once my phone weirdly rebooted by itself, and when i loaded android it looked like it flashed itself cause i had Menu as i flash rom to set language and stuff.
I was like "wut.." but ok, i set my phone again, and then it started to download all apps i had before, but every dll ended up with an instant error
"There is insufficient space on the device."
I also looked at the App settings, selected All and huh, Internal Storage status bar was all grey with no info how much space is left.
I downloaded ROM (tytung's 4.2.2 ..) again through my phone, and tried to flash it again, but it said i have no EXT space, so i had to wipe my SD card in CWM and create 1gb ext partition.
Then it was all good, i downloaded all my apps without any problem and i was happy, but next day it was same thing, it rebooted with Setting Language Screen and afterall i have no storage. Now downloading tytung's ROM again to flash it...
Seem like an endless fun :crying:
Any solutions?
PS. I am on holidays, and i have no connection with PC, only phone + web.
#EDIT
Oh, when i try to flash ROM i get an error:
Code:
Mounting SD-EXT failed!
Please Create an EXT4 partition
(mmcblk0p2) on the SD Card First
Error Messages:
mount: mounting /dev/block/mmcblk0p2 on /NativeSD failed: Invalid Argument"
Making partition will help, but i bet that tomorrow i will have the same situation...
I was going to suggest changing the SD card. Or it could be the same problem with robbie, try to remove the sd card and clean the contacts on the sd, and clean the slot of the phone if possible.
Marvlesz said:
I was going to suggest changing the SD card. Or it could be the same problem with robbie, try to remove the sd card and clean the contacts on the sd, and clean the slot of the phone if possible.
Click to expand...
Click to collapse
Thanks, i just caught myself that last time i partitioned EXT i set swap to 32mb or sth, and it should be 0 ofc, will see if that will or won't help, then i will try with sd card.
#EDIT, yay, it's stuck on green HTC logo now!
#EDIT2: couldnt stand this, deleted everything, gonna hard reset or wait till i get usb to install new rom ... anyway phone useless for now.