I apologize if this has come up before and I'm just not finding the answer, but I've seen others describe this problem with no solutions offered.
I'm running Paranoid Android off my Nook color, CWM 5.5.0.4 Racks recovery, no alternate, all on the emmc. I used leapinlar's partition fixes prior to flashing PA 3.6 originally, then used it again when I clean wiped to install PA 3.69. I originally ran CM7 off an SD card and for some reason it did take awhile to get CWM to work off the emmc, but once I finally got it flashed, it worked beautifully.
The problem I'm having is with the write access to the emmc and sd cards. It cropped up when I first installed PA 3.6 to the emmc and at first I chalked it up to a flash problem running CWM from the SD rather than emmc. However, when I fixed CWM to flash off the emmc and clean installed PA 3.69, the same problem was there: both the emmc and SD card (when inserted) is marked as read only and problems come up when, say, trying to download files through the browser, from dropbox, box. or goo manager.
Under goo manager, I could see the default download folders were simply wrong though even when the pointer is fixed, it will only download when the external SD card is inserted. While under dropbox I only get the "storage is full or unavailable" or "error exporting..." messages, under box I get the message that I don't have permission to download to storage. I saw under one thread this type of problem was chalked up to a hardware issue, however, not only can I download under goo to the proper folder on the emmc when I have an SD card inserted (browser will download to the SD when inserted), but all my write access is normal under CWM (I can nandroid to the internal storage, no SD card present, without any issues). In addition, there are no issues with the caches and how the system runs in general, nor do I have any problems downloading and installing programs from the play store. So I'm wondering if this could be a user permission issue rather than a hardware issue? "Fix permissions" under CWM is the only reference I know to this possibility but does nothing to fix this problem. I also notice most apps are defaulting to /storage/sdcard which may be a big part of this issue, though it still doesn't explain why all storage is marked as read only in Settings -> Storage, or even if the two events are related!
Whatever it is, I'm about at the end of my skills here and any help would be appreciated!
It is very normal for apps to default to /storage/sdcard.
And fix permissions in CWM only fixes permissions in /data, not the media partitions where you are having the issue.
When the media partitions are mounted at startup they are set up to turn read only if they encounter read/write errors during operations. It sounds like this is what is happening to you. I know in CM10 that the operating system was much quicker to trigger that read only option than in earlier CM versions. It may be true in PA too. The usual solution is to get a better quality SD (SanDisk class 4), but you say it is happening to emmc media too.
Why are you running my partition repair zips when changing systems? That seems unnecessary. It may be somehow related to your issues.
Sent from my Nook HD+ running CM10.1 on emmc.
leapinlar said:
It is very normal for apps to default to /storage/sdcard.
And fix permissions in CWM only fixes permissions in /data, not the media partitions where you are having the issue.
When the media partitions are mounted at startup they are set up to turn read only if they encounter read/write errors during operations. It sounds like this is what is happening to you. I know in CM10 that the operating system was much quicker to trigger that read only option than in earlier CM versions. It may be true in PA too. The usual solution is to get a better quality SD (SanDisk class 4), but you say it is happening to emmc media too.
Why are you running my partition repair zips when changing systems? That seems unnecessary. It may be somehow related to your issues.
Sent from my Nook HD+ running CM10.1 on emmc.
Click to expand...
Click to collapse
The flash of the partition fix files was predominantly to see if there was an issue from the original flash created when I installed PA 3.6. My install of 3.6 would never boot normally and required an SD with a recovery in order to boot at all. My thinking was that, since I never got a recovery installed correctly on emmc that something may have been screwed up when I flashed the partition fixes and/or PA originally causing the write errors that I was getting. Once I had the recovery installed correctly on the emmc, I used that to reflash the partition fixes then updated to PA 3.69 since I had wiped everything in the process. However, the write issues remained in the new install though CWM works wonderfully off of emmc now.
Are there any logs I can check to see if encountering read/write errors could be the problem? I can try going back and installing CM7 to see if I get any of the same issues, but I believe on other systems the partition structure is changed between upgrading from CM9 to CM10. Do I need to watch for any of those issues on the nook color as well?
Thank you very much for your help!
jaxxes said:
The flash of the partition fix files was predominantly to see if there was an issue from the original flash created when I installed PA 3.6. My install of 3.6 would never boot normally and required an SD with a recovery in order to boot at all. My thinking was that, since I never got a recovery installed correctly on emmc that something may have been screwed up when I flashed the partition fixes and/or PA originally causing the write errors that I was getting. Once I had the recovery installed correctly on the emmc, I used that to reflash the partition fixes then updated to PA 3.69 since I had wiped everything in the process. However, the write issues remained in the new install though CWM works wonderfully off of emmc now.
Are there any logs I can check to see if encountering read/write errors could be the problem? I can try going back and installing CM7 to see if I get any of the same issues, but I believe on other systems the partition structure is changed between upgrading from CM9 to CM10. Do I need to watch for any of those issues on the nook color as well?
Thank you very much for your help!
Click to expand...
Click to collapse
There are no partition changes for any version of CM on the NC. And CM7 may give you better write performance.
For logs, go to Terminal Emulator and type dmesg. You must enter superuser mode first by typing su. It will give you a long log you can scroll through.
Sent from my Nook HD+ running CM10.1 on emmc.
Related
Ok, first off, I'm new to this, I've only had my android for about 1 1/2 months. I've read a million threads and posts to absorb information so I don't have to ask stupid questions like this. However, I've searched and tried several different methods, and none have worked. I apologize in advance because I'm sure the information is already somewhere in this forum, but I can't seem to find the specific information for my phone, Mt3G.
The problem I'm having is that last week I decided to partition my my sdcard so I could see how apps2sd worked. After some trial and error, I got it to work.
1. 64 mb swap
2. 512 mb ext
3 remainder on FAT32
After a couple of days, I started notices lags and also issues such as not being able to upload images to facebook, trouble downloading apps from the market, not being able to receive MMS messages or sending them, etc. Overall, it seems like partitions are causing my phone to lag, run slow and other small glitches, so I would like to remove all the partitions, format the sdcard, and just have one single FAT32 partition, as if it were stock. I no longer want apps2sd.
I've tried 'droid explorer', I've followed the cyanogen tutorial on how to uninstall apps2sd via terminal emulator, I've tried wiping, formatting, everything, nothing works. Every time I reboot my phone, the secondary partition still remains, although it says total space unavailable now, but its still there, and according to droid explorer, the apps are still there. I just want to get rid of everything because as of right now, most of my downloaded app icons don't appear, but when I go to download the apps at the market, they say they are already installed. I dont know, I'm about to just throw my phone at the wall.
Any help would be greatly appreciated. By the way, here is my current setup.
Phone: MT3G
ROM: Cyanogen 4.2.11.1 + Cyanogen recovery 1.4
Instead of Cyanogen's recovery, install Amon_RA's 1.5.2G
It will let you format your SD back to Fat32, or you can repartition it the the three, with just the click of a trackball.
In doing so, you will more than likely have to reflash the rom due to you losing all your apps and whatnot that's also on the ext partition, since you will be deleting it.
Backup all your stuff onto your computer first, as you will lose it all when it wipes the slate clean.
@tazz, hey, thanks for your reply. So let me elaborate, when I originally partitioned my card I had amon_ra on my phone. When I started noticing problems, I went back into recovery to see if there was any way to delete or repartition back to a single FAT32, but I couldn't find anything. I stated to back track and flashed CM recovery back on my phone, wiped, reflashed ROM, etc. Nothing...in fact, it caused even more force closes and still, my apps didn't appear in the app drawer, although according to market place and android explorer, they were installed.
Anyway, I took your advice, reflashed amon_ra recovery back on my phone, but I still do not see an option to partition with a single FAT32. All I'm seeing is the option to repartion the SD card, then it gives me the option to pick swap size, ext size, then the remainder on the fat32. Do I just set the swap and ext to 0? Also, do I wipe at all in this process?
yeah just put it to zero. i was thinking about his 1.2.3.
if you put them to zero, it should work out the same either way.
Hmmm....I must be doing something wrong. Went into recovery, selected 'partition sd', set swap to '0', set ext to '0', remainder to FAT32, flashed ROM, system reboot. Secondary partition still appears when I go into the sd storage under settings. Also, android explorer still showing apps in data folder, and marketplace still shows apps such as astro file manager still installed. I'm lost.
Update: Tazz, I followed your instructions, reflashed ROM, rebooted. Secondary partion still appeared. However, I noticed that the option for 'unmounting sdcard' was available. So, I unmounted and physically removed my sdcard to see if this was causing the problem or if it was something internal. After removing sdcard, I still had my applications showing that they were installed, but not showing in app drawer. I decided to try flashing an older CM ROM, just to see what happens. It worked! After flashing older ROM verision, I reflashed newer version and all my problems were solves.
Anyway, just wanted to say thanks for helping me get rid of my partitions.
Hey Guys,Me again,with more question on hand.Thanks in advance for all answers given.
Before the questions,Here's what my WF is currently running : Wildpuzzle(the latest Froyo one),Overclock Kernel from the old wildpuzzle thread.
1)I'm thinking of changing my ROM to CyanogenMod 7,so can someone tell me exactly what are nightly builds and the differences between the nightlies and RC2?
2)Which version of CyanogenMod 7 is most stable? (With the least bugs and with most original functions like FM Radio and WIFI tethering included)
3)Will it be faster and more responsive than my current Wildpuzzle that uses LauncherPro?
4)When I installed Wildpuzzle like a month ago,I partitioned the SD card once.(although it doesn't seem to make much of a space differences with the Stock ROM when all the apps are installed back again)So can anyone explain how partition really works,how some people can have dozens of apps installed and still have 100+MB left and do I have to re-partition when installing CyanogenMod?
Thanks again in advance for your patience.
1) Nightlies are automated builds made by build bots. They contain minor (sometimes major) code changes, and, are experimental releases. RC's are release candidates, and, normally, stable enough for release.
2) Stick with RC2 for now. Nightly #22 should be the better one if the 3G bug is fixed, but, #22 is not released yet. Also, if, you get a bootloop with RC2, flash Jacob's kernel v4.1. Again, this bug will be removed in #22.
3) It should be. Can't really say for sure though, since, this is a subjective thing. For me, moving from Wildpuzzle to CM7 did seem to speed up everything. (After I switched from the default ADW to LP, it was more smooth). Besides, just for the level of options and customization you get, I would say it is worth it.
4) You need to flash DTApps2SD as well after partitioning. Simply partitioning will not make the apps move to the SD Card. Also, if you have a fast SD card, you can consider moving the Dalvik cache to your SD card as well, implying that no phone memory will be used at all when you install apps. You need not repartition again if you already have one.
Thanks for the reply
2)I've read somewhere on the forum that nightly 17 is better and more stable than RC2,is this true? and what are the major bugs in RC2 and what is missing in it(things that can currently be done on Wildpuzzle but not on RC2) and where can I find Jacob's 4.1 Kernel?
4)How do I know if I have a fast SD card? and where can I find DTApps2SD?
1) Don't know really. Since I have not tried #17 myself. Anyway, it looks like #22 is out. I'll be trying that, since it uses a newer kernel compared to Jacob's kernel and should fix the 3G bug. Anyway, just FYI, Jacob's kernel can be found here: (Repeat: Do not flash this if you are using a new nightly over and including #21)
http://forum.xda-developers.com/showthread.php?t=798471
2) You will have to remove the card and check it. Apart from the card vendor's name and capacity, there will be a number surrounded by an almost full circle. This number will be 2,4,6 or 10. For moving everything including the dalvik cache to SD card, it is recommended to have atleast a Class 4 SD Card, else it may potentially cause slowdowns.
DTApps2SD can be found here:
http://forum.xda-developers.com/showthread.php?t=925982
You can check the "Commands" Page (Link given in the thread given above) for instructions on how to use it.
EDIT: 3G Fix didnt happen in #22, but, you can still use it and flash this fix immediately after flashing the CM ROM:
http://forum.xda-developers.com/showpost.php?p=12157846&postcount=3531
1)I just flashed CM7 RC2 earlier today along with Jacob's 4.2 kernel,so what do I do now if I want to install nightly 22?
2)ok,I've checked and it's a class 4...How do I transfer Apps to Sd using Darktremor's A2SD? Through the standard method or with Titanium Backup?
FrydaeXIII said:
1)I just flashed CM7 RC2 earlier today along with Jacob's 4.2 kernel,so what do I do now if I want to install nightly 22?
2)ok,I've checked and it's a class 4...How do I transfer Apps to Sd using Darktremor's A2SD? Through the standard method or with Titanium Backup?
Click to expand...
Click to collapse
If you have already setup as per your liking, then, simply wipe cache and wipe dalvik cache under advanced partition. However, because this has a new kernel, I think it would be better to wipe data and do a factory reset as well.
Just flash the dtapps2sd ZIP file as you flash a ROM. If you want to move the dalvik cache to the SD as well, open terminal emulator, type the following:
su
a2sd
a2sd cachesd
Thanks and I've decides to stick with RC2 for now,so i've re flashed RC2,Google Apps,the 4.2 Kernel and DTa2sd...So how exactly does DTa2sd work?Like when I use Titanium Backup to restore all my apps does it go to sd automatically or there is some process to transfering it
Not aware of the Titanium Backup Process, since, I dont use it. But, what I do know is that when you flash the ZIP, the apps are moved then. But, if you have already flashed Dtapps2sd, and then restore from Ti Backup, it should go to the SD.
Anyway, you can check the thread for its functioning. Its explained much better than I can.
Em,How do I know if my SD is partitioned correctly,cos I did the a2sd check command and all I get are lots of codes ending with permission denied
FrydaeXIII said:
Em,How do I know if my SD is partitioned correctly,cos I did the a2sd check command and all I get are lots of codes ending with permission denied
Click to expand...
Click to collapse
Make sure you type su in your terminal emulator app before running that. This requires Superuser privileges.
Also, another noob way (lol) to check if it is partitioned properly is to go to check the size of your SD card. If it shows the full capacity, it is not partitioned. If it shows the capacity excluding the size of the EXT (eg: Default 2GB + 256 MB EXT will show SD card capacity as 1.60 GB), then, it is correctly partitioned.
Ok,I've checked everything and all seems to be running well,Thanks for all your help
Dammit,New problem...After installing CM7 everything runs fine and after I keep rebooting for everytime I flash something new(GApps,Kernel,DTA2SD),it reboots fine but after restoring my apps and rebooting it,It's stuck at the cyanogenmod bootscreen with the blue arrow(it's called Bootlooping right?) How do I fix this? I really like CM7 and don't want to go back to Wildpuzzle
OK, so I got a new Nook Color, and threw the CWR on a flash drive and Formatted System, Formatted Data, Cleared Dalvik, grabbed Mirage Kang 7.2, and installed it.
Data seems to be having some access issues (won't format), and I don't think the install took right, because nothing but FCs on boot and all the apps (i.e. SuperUser) are missing.
Seems like on my last Nook (2 years ago) I had the same problem and IOM/Cubed gave me a hand fixing the mess I made
I feel like I missed a step here... Any thoughts? Is there a specific root install I'm supposed to do prior to installing Kang?
Update...
I figured this one out.
The problem was that once you install CWR to the EMMC, you have to pull the SD Card, run CWR FROM THERE (post reboot, of course), and format data. For whatever reason, the SD Card CWR image doesn't have access to data (or tries to delete data from the SD Card instead?).
After formatting data (and it actually working), bob's your uncle.
majorpay said:
I figured this one out.
The problem was that once you install CWR to the EMMC, you have to pull the SD Card, run CWR FROM THERE (post reboot, of course), and format data. For whatever reason, the SD Card CWR image doesn't have access to data (or tries to delete data from the SD Card instead?).
After formatting data (and it actually working), bob's your uncle.
Click to expand...
Click to collapse
'Cuz you probably have the old version of it.
votinh said:
'Cuz you probably have the old version of it.
Click to expand...
Click to collapse
Probably true... We need to get some stickies updated with links to actual modern methods for modding the device. After testing out the latest Kang 7.2, I'd say this device hasn't seen it's day yet.
Hi everyone!
I just got CM7 (latest stable release) installed on on external sdhc card. I have wifi issues with CM7 (and looking around the forums tells me that CM7 can be finicky with certain routers) so I would love to be able to use Nook's stock ROM (4.1.4) when I am having issues.
But, when I am on NC ROM, I don't see anything except the small boot partition on the SD and when I am on CM7, I don't get access to this boot partition. I am wondering if there is a way to either create another partition or make the currently existing partitions accessible on both ROMS so that I can share data between them.
I am a n00b without any Android experience so thanks in advance for your patient responses.
Please use the Q&A Forum for questions &
Read the Forum Rules Ref Posting
Thanks ✟
Moving to Q&A
andrandom said:
Hi everyone!
I just got CM7 (latest stable release) installed on on external sdhc card. I have wifi issues with CM7 (and looking around the forums tells me that CM7 can be finicky with certain routers) so I would love to be able to use Nook's stock ROM (4.1.4) when I am having issues.
But, when I am on NC ROM, I don't see anything except the small boot partition on the SD and when I am on CM7, I don't get access to this boot partition. I am wondering if there is a way to either create another partition or make the currently existing partitions accessible on both ROMS so that I can share data between them.
I am a n00b without any Android experience so thanks in advance for your patient responses.
Click to expand...
Click to collapse
Look in my signature for a link to my tips thread. I explain there how to make the SD media partition available to both ROMs (item B3).
leapinlar said:
Look in my signature for a link to my tips thread. I explain there how to make the SD media partition available to both ROMs (item B3).
Click to expand...
Click to collapse
*That's* the one I wanted to point them to.
leapinlar said:
Look in my signature for a link to my tips thread. I explain there how to make the SD media partition available to both ROMs (item B3).
Click to expand...
Click to collapse
Thanks.
Do you mean step #3 in Section B? I could edit it without running your script too, can't I?
andrandom said:
Thanks.
Do you mean step #3 in Section B? I could edit it without running your script too, can't I?
Click to expand...
Click to collapse
If whatever you have on emmc is rooted, you can manually edit it. If you have unrooted stock, then you need to flash the zip since without root you cannot edit those files manually. And I did mean item B3. Each item is a different topic, they are not steps. One topic does not depend on another. Just do B3 and no others if you want.
Yes, item B3. My mistake...
I should be able to do flash the zip from my current CM7 SD card's boot partition, shouldn't I?
So I put the update-stockemmc-vold-fstab-modified-for-partition4.zip file in the boot partition of the SD card, rebooted to Recovery mode and then booted to NC's stock ROM. NC is still using the tiny boot partition on the SD card as my external storage instead of the much larger CM7 partition. This was the same partition that was under 'My Files / Memory card' before I flashed so nothing has changed. I did this twice to double-check.
Am I doing this wrong?
andrandom said:
Yes, item B3. My mistake...
I should be able to do flash the zip from my current CM7 SD card's boot partition, shouldn't I?
So I put the update-stockemmc-vold-fstab-modified-for-partition4.zip file in the boot partition of the SD card, rebooted to Recovery mode and then booted to NC's stock ROM. NC is still using the tiny boot partition on the SD card as my external storage instead of the much larger CM7 partition. This was the same partition that was under 'My Files / Memory card' before I flashed so nothing has changed. I did this twice to double-check.
Am I doing this wrong?
Click to expand...
Click to collapse
Yes you are doing it wrong. You need to flash that file with a CWM card, not put in the boot partition of your SD. And since you did that, you need to re-flash your latest ROM on SD to correct your mistake. (I will edit my instructions to make it a little clearer that you use CWM to flash that file.)
I got NC stock ROM to see my SD card partition by following item A10. That is most excellent and thanks again!
Unfortunately, I no longer see the boot partition when I attach NC to my computer whether NC is running off stock ROM or CM7. My guess is that this is due to my failed attempt to flash from my CM7 SD card yesterday. Am I right?
I thought I could reverse that by copying the update-stockemmc-vold-fstab-return-to-stock.zip file to CM7's boot (and then booting to the recovery mode) but that seemed to have nothing.
If I understand your previous message correctly, I should re-do my entire SD card but... I have already spent a few hours downloading and customizing the Android apps. Is there a way to preserve all that before Win32diskimager destroys the contents of the SD card?
Is there a way to manually mount the /etc folder from a unix prompt and alter the file?
Does it even matter if I don't see boot while I attach NC to a computer? Are there any caveats to 'let it be'?
Questions, questions and more questions...
That leads me to the obvious question, is there a book that explains Android to someone who is not interested in programming it but wants to understand the architecture and design of the OS (and custom ROMs)?
Thanks for being patient with all these n00b questions.
andrandom said:
I got NC stock ROM to see my SD card partition by following item A10. That is most excellent and thanks again!
Unfortunately, I no longer see the boot partition when I attach NC to my computer whether NC is running off stock ROM or CM7. My guess is that this is due to my failed attempt to flash from my CM7 SD card yesterday. Am I right?
I thought I could reverse that by copying the update-stockemmc-vold-fstab-return-to-stock.zip file to CM7's boot (and then booting to the recovery mode) but that seemed to have nothing.
If I understand your previous message correctly, I should re-do my entire SD card but... I have already spent a few hours downloading and customizing the Android apps. Is there a way to preserve all that before Win32diskimager destroys the contents of the SD card?
Is there a way to manually mount the /etc folder from a unix prompt and alter the file?
Does it even matter if I don't see boot while I attach NC to a computer? Are there any caveats to 'let it be'?
Questions, questions and more questions...
That leads me to the obvious question, is there a book that explains Android to someone who is not interested in programming it but wants to understand the architecture and design of the OS (and custom ROMs)?
Thanks for being patient with all these n00b questions.
Click to expand...
Click to collapse
You do not need or want to re-set up the whole SD installation. Just put the same CM7 zip file back in the boot partition and boot to SD recovery. It will put the correct vold.fstab back on the SD. You will not lose any settings or apps you have already set up. (And putting the return to stock zip there was also the wrong thing to do. The vold.fstab for stock and CM7 are different. But don't worry, it will fix that too.)
You are not supposed to see the boot partition on the PC when you plug the nook in with the cable. You are only supposed to see 'emmc' and 'sdcard'. Under the original setup, your stock system thought the boot partition was 'sdcard' and that was why you saw it on your PC. Since you modified stock to see partition 4 as 'sdcard', partition 4 is what the PC sees, not the boot partition.
Most people have to physically take the card out of the nook and put it in the PC to see the boot partition on the PC. If you don't want to do that, use my script in item B4. But since you are on CM7, you will not be adding many things to the boot partition to install with SD recovery in the future. So it is probably best to leave things be.
And I don't know of any books to help you.
Sent from my Nook Color running ICS and Tapatalk
That is excellent news!
A bit of playing around with Astro tells me that I was wrong about seeing the 'CM7 SDCARD' partition when I was on CM7 ROM. I am only seeing the boot. Anyway, I am going to flash the CM7 ROM again and I am hoping it would fix everything.
Also, yes, I can see the boot partition when I put the SD card directly on my computer but I was also able to see it when I hooked up the NC to my computer via USB before I did my unintended tweaks but... I'll survive.
I'll be back after I flash. (Famous last words??)
Mission accomplished!
Thanks again for all your help.
For future reference after you alter stock's fstab... all you have to do is:
mkdir /sdcard/boot (only have to do this one time)
mount /dev/block/mmcblk1p1 /sdcard/boot (do this every time you want to put something on the boot partition)
put anything you want on boot partition in /sdcard/boot
DizzyDen said:
For future reference after you alter stock's fstab... all you have to do is:
mkdir /sdcard/boot (only have to do this one time)
mount /dev/block/mmcblk1p1 /sdcard/boot (do this every time you want to put something on the boot partition)
put anything you want on boot partition in /sdcard/boot
Click to expand...
Click to collapse
Yes, there is one big advantage to using that method. I think it allows the boot partition to be seen not only on the nook, but also on the PC when you plug in the usb.
leapinlar said:
Yes, there is one big advantage to using that method. I think it allows the boot partition to be seen not only on the nook, but also on the PC when you plug in the usb.
Click to expand...
Click to collapse
We could probably come up with a symlink to /dev/block/mmcblk1p1 to /sdcard/boot and avoid having to mount it everytime as well.
DizzyDen said:
We could probably come up with a symlink to /dev/block/mmcblk1p1 to /sdcard/boot and avoid having to mount it everytime as well.
Click to expand...
Click to collapse
Thank you Dizz, your suggestion got me to thinking and I was able to come up with an init.d bash script that does the trick. I just temporarily mounted sdcard and created the sdcard/boot directory and the mounted the boot partition to it, then unmounted sdcard so it could be mounted again by the system later in the boot sequence.
The only problem is now sdcard will not mount on the PC using UMS mass storage. Must be because of having a second mount within the mount. But it does mount with MTP. But that may be acceptable. I will test some more, including using Goo Manager tomorrow.
EDIT (6-21): Goo Manager works. But I think I have figured out why sdcard is not mounting in UMS. Once it is mounted in my script and the boot partition mounted under it, it cannot be unmounted. And since it cannot be unmounted, it cannot be mounted later by the system as vold. If it cannot be mounted as vold, it does not show in UMS. For now I think I will leave it as I have it in Rev 2 of my script (symlinking to the root directory with full r/w permissions). If people want to see the boot partition on the PC, just use my modified for CM9 NookColorUMS available in my tips thread.
Sent from my Nook Color running ICS and Tapatalk
Help!
When CM7 is running, my computer is no longer mounting any of the partitions when I connect NC to my computer via the USB cable.
If the NC stock ROM is running, my computer mounts all three partitions (MyNook..., boot and CM7SDcard) but calibre is not recognizing the external partitions for transfers.
Further, when I boot to my NC stock ROM, I am no longer seeing my SD card's contents in the NC's library.
This may have something to do with the fact that NC stock ROM seemed to have updated itself to 4.1.3.
Should I re-run the scripts again or am I missing something else?
When it was updated to 1.4.3, you lost the emmc mods. Just re-flash my zip with the CWM SD. You may have lost CWM on emmc too.
On CM7, you have to select the turn on storage button after you plug it in. It is not automatic like stock. Pull up the notification area and touch the turn on button.
Darn, I forgot about that 'USB' option under notifications. Enabling it allows me to find the partitions. I will run your scripts again when I find a spare mUSB card.
Thanks again for your help!
Hi,
I have a nook that I rooted and put a custom rom on back about a year and a half ago. I flashed the ROM to the internal EMMC and CWM 3.2.0.1 was flashed as recovery. If it makes any difference it was a CM9 ROM
Now here's where I'm at. I can run ROMs off the sd-card but they are not stable at all. I get a whole bunch of force closes and such.
When I try and flash a new ROM to the internal EMMC it says it completes, but nothing changes. It is still the previous ROM. When I try and format the /data and /system partitions with the EMMC recovery, it doesn't complete. It says there is an error. When I format with TWRP off an sd card, it says it completes but once again, the rom is not wiped.
I've tried the 8 reboot error method, and it never gets to the stock recovery screen. It keeps booting to the EMMC ROM.
I've tried repartioning the EMMC with leapinlar's zip files. It says it successfully completes, but once again nothing changes.
Ideally I'd like to get the emmc back to stock and try and run a rom off the sdcard.
I've read the threads that I thought were applicable to my issues, but nothing seemed to work. I'm completely out of ideas. Anyone have similar issues or can provide some guidance?
Thanks.
The problem you are having running a ROM from SD is the brand and speed of SD you are using. It needs to be SanDisk class 4.
The reason the 8 failed boot does not work is you replaced the stock recovery with CWM. It needs the stock recovery to be able to complete. See my NC tips thread linked in my signature and read item A12. Assuming you can get it to flash, I have a stock recovery zip there.
I don't understand why the ROMs are not flashing. You say it gives errors when you try to wipe with CWM. What do the errors say? You used the internal CWM and TWRP on SD, but none worked. Try my bootable CWM SD to see if that helps.
I don't understand why my partition zips did not work. I know the newest TWRP will not flash them without giving an error 2 message. Try my bootable CWM SD.
Sent from my Nook HD+ running CM10.1 on Hybrid SD
Thanks for the advice...
I've been using a Patriot class 10 micro sd to run the roms/attempt to flash new roms. Its worked fine before, but I'll try and pickup another one from someplace.
When I try and format /system and /data from the emmc CWM it says "Error formatting /system" or "error formatting /data" after working away for about 5 minutes
Here's what i did:
Created CWM 6.0.1.2 Bootable SD
- Flashed NookColor-emmc-stockrecovery.zip
- Message said successfull.
- tried to restart and old CWM recovery 3.2.0.1 was still installed
Booted into CWM 6.0.1.2 Bootable SD Recovery
- mounted /system and /data
- attempted to format
- Message "Done." for both
- attempted to flash stock 1.4.3 that you have modified for CWM
- install from sdcard complete
- reboot
- Old CynanogenMod bootscreen and old rom still installed.
Using same CWM 6.0.1.2 Bootable Sd Recovery
-flashed NookColor-emmc-repair-partitions-1-4-5-6-7-8.zip and NookColor-emmc-format-partitions-5-6-7.zip
-said success
-attempted to flash stock 1.4.3
- nothing changed. Old rom still installed
One more thing I noticed:
Everytime I login to the currently flashed rom, any changes I make are never saved. For example, if i install an apk or uninstall an app, the next time i can successfully boot into the emmc ROM, those changes are reversed to the previous version. Could it be that the current rom is being stored somewhere and being reflashed when it tries to bootup?
I hate to say this, but it sounds like your internal embedded card has become read only. I have had this happen to SDs but not to emmc. The apps act like they are writing and if you leave the folder and come back, they are not there. It is like they are writing to a ramdisk instead of your SD. You might try booting to a ROM on SD and see if you can write to any of the internal partitions like /cache or /rom and see if they stick. If not, you may only be able to run off SD and maybe not even then. You might have to change your dalvik cache setting on SD so it uses /data instead of /cache.
Sent from my Galaxy Tab running Tapatalk
I tried copying a file to the emmc partition from twrp and it didn't persist after reboot... so it looks like the emmc is set to read only. I don't supposed I can change that using adb and/or software solutions right? It's a hardware issue?
Any guidance on how to change davlik cache to use /data instead of /cache? I'll be happy to get any sort of stable rom running off any SD card.
I was hoping to repurpose the nook as in in car tablet to tether a data connection to my phone and play music and such.
Thanks for your help. I appreciate you taking the time.
canjoe said:
I tried copying a file to the emmc partition from twrp and it didn't persist after reboot... so it looks like the emmc is set to read only. I don't supposed I can change that using adb and/or software solutions right? It's a hardware issue?
Any guidance on how to change davlik cache to use /data instead of /cache? I'll be happy to get any sort of stable rom running off any SD card.
I was hoping to repurpose the nook as in in car tablet to tether a data connection to my phone and play music and such.
Thanks for your help. I appreciate you taking the time.
Click to expand...
Click to collapse
I don't know of anything that can revive it. I never could revive my SD that that happened to.
To make your ROM on SD use /data for all of the dalvik cache, create a file in /data named local.prop. In that file put this line:
dalvik.vm.dexopt-data-only=1
Next time it boots the system file portion of dalvik cache will be on /data along with the installed app portion.
Sent from my stock Nook HD+ using XDA Premium
I now have a stable version of CM 7.2 running off the SD card. I put the davlik cache on the data partition and everything seems to be running pretty smooth.
I'll keep messing around seeing if there is anything to revive the internal emmc, but at least I can use the nook off the SD card again.
Thanks for helping me troubleshoot and figure this out. Cheers.