Related
Hi everyone,
I was interested in upgrading to the stable 7.1 release. I am currently using the 7.1 RC on my nook color. I read this on the cyanogen mod website:
"Upgrading from any previous CM-7 release or nightly build should be smooth and no wipe should be required."
Does this mean I can flash the rom over top of the current RC without having to wipe any of my data or apps? This would be great as I have customized my nook quite a bit since getting it. I don't mind if I lose settings or things of that nature, but it would be great if I could keep my home screen and such. Anyways, just wondering. Thanks.
Your assumption is correct, all you need to do (well advised) is wipe your cache, and yes, it will take a while to boot the 1st time... Just did it tonight myself
You just need to wipe dalvik cache when updating.
---------------------------------
Sent from my LG Optimus V using Tapatalk
If this post helped you don't forget to say thanks!
Updated from nightly 200 and just wiped cache. Alls well so far.
About to Update to 7.1 and a question...
I use CM7.03 off of the microSD - does anyone know if the installer from this post: [ROM][CM7] [v1.3] Size-agnostic SD Card image and CM7 installer for SD Cards <http://forum.xda-developers.com/showthread.php?t=1000957> will also work to install 7.1
There have been many changes (for the much better
docfreed said:
I use CM7.03 off of the microSD - does anyone know if the installer from this post: [ROM][CM7] [v1.3] Size-agnostic SD Card image and CM7 installer for SD Cards <http://forum.xda-developers.com/showthread.php?t=1000957> will also work to install 7.1
There have been many changes (for the much better
Click to expand...
Click to collapse
Yes, it upgrades fine with this method.
Thank you for your help everyone I will try it tonight.
docfreed said:
I use CM7.03 off of the microSD - does anyone know if the installer from this post: [ROM][CM7] [v1.3] Size-agnostic SD Card image and CM7 installer for SD Cards <http://forum.xda-developers.com/showthread.php?t=1000957> will also work to install 7.1
There have been many changes (for the much better
Click to expand...
Click to collapse
Just drop the new ROM .zip onto the root of the card and boot up.
Hi,
I'm also running off the SD card. Is there a way to copy the .zip into the boot partition of the SD card from the Nook itself, or do I need to remove it and do it from a computer? I'm using File Expert and don't see a /boot folder.
Thanks!
c0rndog said:
Hi,
I'm also running off the SD card. Is there a way to copy the .zip into the boot partition of the SD card from the Nook itself, or do I need to remove it and do it from a computer? I'm using File Expert and don't see a /boot folder.
Thanks!
Click to expand...
Click to collapse
Use your PC and a card reader.....
I know I can use a card reader, but I was just curious if it is possible to do it without removing the card or connecting the Nook to a computer.
I downloaded the .zip onto my nook, I just don't see where to copy the file.
c0rndog said:
Hi,
I'm also running off the SD card. Is there a way to copy the .zip into the boot partition of the SD card from the Nook itself, or do I need to remove it and do it from a computer? I'm using File Expert and don't see a /boot folder.
Thanks!
Click to expand...
Click to collapse
you can use adb (adb wireless works very well)
on a windows machine you can use windows explorer to get to the folder with your zip file in it...
open a command window (start/run cmd)
if adb wireless... adb connect IP address
adb shell busybox mkdir /sdcard/boot
adb shell busybox mount /dev/block/mmcblk1p1 /sdcar/boot
adb push (zip file... can drag from windows explorer) /sdcard/boot
you will then have the zip file on the boot partition of the sdcard and can boot to uSD recovery for updating.
DizzyDen said:
you can use adb (adb wireless works very well)
on a windows machine you can use windows explorer to get to the folder with your zip file in it...
open a command window (start/run cmd)
if adb wireless... adb connect IP address
adb shell busybox mkdir /sdcard/boot
adb shell busybox mount /dev/block/mmcblk1p1 /sdcar/boot
adb push (zip file... can drag from windows explorer) /sdcard/boot
you will then have the zip file on the boot partition of the sdcard and can boot to uSD recovery for updating.
Click to expand...
Click to collapse
And that my friend is why I said use a card reader. Do you really want to do all that?
Clearly using a card reader is easier than that
Maybe I'm missing something here (forgive me if this is a noobquestion), but why can't I access the /boot partition of the SD card directly from the NC using a file manager?
Upgraded to CM7.1.0 stable from CM7.1.0RC on uSD card
I upgraded to CM7.1.0 stable from CM7.1.0RC using ROM Manager on uSD card. One issue I noticed is the stable version run slower. The RC version had Quadrant scores between 2500 to 3060. Now the Quadrant scores are between 1800 and 2600. I only wiped Davlik cache. All app data and settings remained the same. I activated the emmc as SD for extra storage and OS swapped 5.9gb to internal emmc. I am using a Kinston 8 gb class 10 with Speed Booster cache set to 2048 (original setting on sd was 1024). Anyone else experiencing a slower OS after updating to CM7.1.0 stable?
Sorry if too simple, but how is the best way to "wipe davlik cache?"
yeroc40 said:
Sorry if too simple, but how is the best way to "wipe davlik cache?"
Click to expand...
Click to collapse
I suggest, next time, you should open a new thread, providing a basic system info along with question.
For now, "wipe dalvik cache" simply by entering CwM Recovery (ClockworkMode Recovery) then go to Advanced, you'll see Dalvik there, select it, perform wipe.
Note: this only for running CM7 from eMMC, not booting from uSD.
c0rndog said:
Clearly using a card reader is easier than that
Maybe I'm missing something here (forgive me if this is a noobquestion), but why can't I access the /boot partition of the SD card directly from the NC using a file manager?
Click to expand...
Click to collapse
It's a little like trying to write the boot sector on a Windows system after you've booted. Too much potential damage can result from accessing the boot partition while you're running the system.
Hi the question is in the title.
I got it working on quarx's cm7 RC 1.0(only with directory method), but on WIUI 2.2.3 i get errors.
On startup i get this error:
Internal tests failed!
-Kernel config is not known becouse /proc/config.gz file is not found. /this was present on cm7 too/
Here i click override.
Directory method:
And when i click "Install in chroot directory" it says "Error: Partition is mounted with nodev: Can't remount with nodev!"
Loop method:
Creating and formating the loop finishes fine.
When i click mount loop it says: "Can't mount BLOCK Part: Did you forget to format? I think this ext version is not supported!"
however i'm using the ext2 file format, which is included in the application. In the log i found this line: "MountLoop > Error:mount mounting /dev/block/loop1 on /data/local/mnt/Linux failed: No such device"
I think this is the source of the error. Beside that i didn't found any strange entries in the log.
I managed to get it working.
All i had to do is remount /data with dev option. After that the directory method is working on internal memory. I've also tried to install linux on sdcard, but that fails, because when i try to change the "Chroot point" in the setup i get "Directory is nodev!, not saved", even after remounting /mnt/sdcard with dev option.
Anybody have an idea to fix this?
for me it worked!
..unfortunetly only for debian squeeze :/ would like to get at least ubuntu 10.4.
i had to manually umount my sdcard.
i'm not shure if this was necessary, but i also remounted all devices that where mounted as nodev.
my mountpoint was /data/local/linux
EDIT: *sigh sorry i forgot to say, i'm on atrix,not on defy.. but the point is, that i also get those errors whenever i try to install any ubuntu while debian squeeze works fine.
I have the same problem
Hi!
I have the same problem,I tried all the 3 roms (Wiui,CM,Miui)+the stock with root,but on these roms,the linux installer sends the same message: "Kernel features is not know because the /proc/config.gz file is not found"
I tried to install Ubuntu too with the ubuntu installer app from market ,it didn't work too.
Is there anybody,who use any linux on his/her Defy?
I' sorry for my English.
On CM10 the application named "Complete Linux Installer" is working fine. Unfortunately i'm still not able to use loop method on CM7. If you really need this on your phone you should try CM10.
By the way i would happy to hear about anybody who have a working loop device setup on CM7.
jumika said:
Directory method:
And when i click "Install in chroot directory" it says "Error: Partition is mounted with nodev: Can't remount with nodev!"
Click to expand...
Click to collapse
I may have partially solved this if you haven't already. Here's what I did to install using BLOCK method:
First, used an old HTC Dream that had an Amon RA recovery on it to format the SD card. The recovery has an automated option to make an ext2, 3, or 4 partition + swap on the sdcard. I first made an ext2, then coverted it into ext3, then into ext4. I then put the sdcard back into my main phone. My main phone did not support the Amon RA recovery and that's why I needed to use another phone.
Then I used another app called "Linux Deploy" to see what the ext4's /dev/block was. The app has a menu option called "sysinfo". I think you can also just use that command in Terminal Emulator. Look at the partition sizes carefully. Remember the filesize you used to create your EXT (the swap partition is right under your EXT as well). Use that block device in the Linux Installer setup menu. You shouldn't see the "nodev" anymore.
What happens is that the sdcard itself is usually formatted as FAT32 (vfat) and will always be "nodev". Partition some or all of the space as EXT + SWAP and it will be fine. I've successfully installed to sdcard using this way. Let me know how this works for you or if I need to clarify some things.
I spent more than eight hours to set up HD2 mount /data to sd-ext; but I found that LogCat keeps saying that the error EROFS(Read-only file system) has occurred. After that I went to CWM Recovery, ran e2fsck -yfv /dev/block/mmcblk0p2 and rebooted. It started working again from then; so maybe putting e2fsck command on boot-time script might be useful for failproofing the SD card.
I am using Windows; and I somehow the message cannot find java keeps occurring and I can't use the kitchen. So anybody can help?
you must use e2fsck in order to check the EXT partition before mounting, esp if you are using it for DATA.
also, if you try to mount a bad partition it won't mount as r/w, instead it will mount as r/o (read only). that's why you were having the read-only issue.
regarding java, you need to install JDK. if you have a x64 system, you need both x86 and x64 variants.
hope this helps
blastsound said:
I spent more than eight hours to set up HD2 mount /data to sd-ext; but I found that LogCat keeps saying that the error EROFS(Read-only file system) has occurred. After that I went to CWM Recovery, ran e2fsck -yfv /dev/block/mmcblk0p2 and rebooted. It started working again from then; so maybe putting e2fsck command on boot-time script might be useful for failproofing the SD card.
I am using Windows; and I somehow the message cannot find java keeps occurring and I can't use the kitchen. So anybody can help?
Click to expand...
Click to collapse
How are you mounting /data to EXT? If you are using my method, I have included a accept that scans at boot and then mounts if the partition is clean. Mounted partitions can't be scanned, they have to be unmounted before scanning.
Swyped from my HTC HD2 using XDA Premium
I have been using OmniROM KitKat on my Galaxy S2 for a while with no problems. I've recently had a GPS issue (still don't know the cause but that's another issue for another day) so decided to update my ROM to the latest nightly. The update went well, but then I found that I could not access any of my apps that had been copied using Link2SD.
I had created an EXT3 partition on my SD card and linked all files onto there using Link2SD. It had been working perfectly before but the update had obviously changed something in my system. When I run Link2SD, I get the following message:
mount: Device or resource busy
Googling this it looks like the partition is already mounted (a2sd?) or some scripts are missing. (Link2SD still has root permissions) I've had a look in init.d but can't see anything remiss, though I'm moving out of my comfort zone here.
Can anyone tell me what I should do next? Do I need to delete and recreate the EXT3 partition, copying the data back on to it? Would uninstalling and reinstalling Link2SD help, or would that cause even more trouble?
Finally, if I do another ROM update, what should I do to stop this happening again?
Thanks for your help.
I've had some success with this. I reformatted the partition to be FAT32 and Link2SD accepted this and created the necessary mount links. I then copied the files (apk etc) back onto the partition and everything is working again.
Now is FAT32 a good option for this partition or is it best to use EXT?
Ta
Edit: Title should read "SD Card" (how to edit that?)
I have root and I am trying to get Link2SD to work. I have created the FAT32 (primary) and EXT4 (primary) partitions but I keep getting a mount script error ("unable to mount") (Also tried EXT2)
I am doing the same thing as I have done on several other devices and it is not working on the samsung.
Also, I am having issues with getting Titanium Backup to wrtie to the SD card too. I tried the Kitkit SD card patch but it failed.
I know the SD card works so I am thinking it is a wonky Samsung thing?
Thoughts or advice
Edit: Pulling SD card, re-inserting and rebooting and then Link2SD reports that the 2nd partition is not accessible during boot (and suggests quick boot to fix which it does not). Samsung says the FAT32 is fine but the EXT is "corrupt" but I have confirmed on two other devices it is fine.
So this seems to be some sort of access thing. Maybe related to the removal of encryption patch as part of the TWRP install?
Edit2: cat /sys/block/mmcblk2/device/type gives back "no such file or directory"; (whereas mmcblk1 gives SD)
Total commander shows sd-card (which is internal /storage/emulated/0), sd-card(2) "/data/sdext2"), and USB (SD FAT32 as /storage/BDB2-8960)
Got TB fixed anyway. Backup one file (on device internal location), move the directory to external SD card, then TB decided it is was OK to include that location under settings so select new location.
Now need Link2SD. Could this be a mount script write issue? Encryption issue (I removed it from internal via a scripted)?
Runings Mounts2SD, installed scripts, reboot but it says External is "not mounted". Link2SD still fails with those scripts installed.
chemie99 said:
Got TB fixed anyway. Backup one file (on device internal location), move the directory to external SD card, then TB decided it is was OK to include that location under settings so select new location.
Now need Link2SD. Could this be a mount script write issue? Encryption issue (I removed it from internal via a scripted)?
Runings Mounts2SD, installed scripts, reboot but it says External is "not mounted". Link2SD still fails with those scripts installed.
Click to expand...
Click to collapse
Link2SD never worked for me either no matter what I did. Apps2SD works flawlessly. Links data, apk, obb files and everything without any issues on ext4 format.
moxalis said:
Link2SD never worked for me either no matter what I did. Apps2SD works flawlessly. Links data, apk, obb files and everything without any issues on ext4 format.
Click to expand...
Click to collapse
I tried installed Apps2SD but it never asked for root and decided half the apps could not be moved. I figured it was just offering the usual stock "move apps" which moves marginal amount.
Samsung says that the EXT partition is corrupt but Aparted says it is fine. EXT2, and EXT4 created in either Minitool or Aparted are simply not read.
Mount2SD adds scripts to mount but the partition remains unmounted after reboots.
What format does Samsung want?
chemie99 said:
I tried installed Apps2SD but it never asked for root and decided half the apps could not be moved. I figured it was just offering the usual stock "move apps" which moves marginal amount.
Samsung says that the EXT partition is corrupt but Aparted says it is fine. EXT2, and EXT4 created in either Minitool or Aparted are simply not read.
Mount2SD adds scripts to mount but the partition remains unmounted after reboots.
What format does Samsung want?
Click to expand...
Click to collapse
Samsung reads the partition as corrupt but Apps2SD is using it just fine. You should delete any mount scripts and re-create them through the Apps2SD application.
moxalis said:
Samsung reads the partition as corrupt but Apps2SD is using it just fine. You should delete any mount scripts and re-create them through the Apps2SD application.
Click to expand...
Click to collapse
How do I manually delete the mount scripts?
chemie99 said:
How do I manually delete the mount scripts?
Click to expand...
Click to collapse
There is the option "Delete mount scripts" in the Apps2SD app. Check their FAQ page for any questions, it's pretty helpful.
Hello! I was having just the exact same problem with my T580.
I just loged in to say how I fixed it:
Open SuperSU app -> Settings.
Check "Enable su during boot"
Uncheck "Mount namespace separation".
After a reboot, Link2SD detected the 2nd partition!
EDIT: Now I fin another issue. If I try to link Obb, it says my device is using "sdcardfs". It offers to install fuse insted to fix it, but after rebooting I still getting the same message.
What could I do?
otamaglimmer said:
Hello! I was having just the exact same problem with my T580.
I just loged in to say how I fixed it:
Open SuperSU app -> Settings.
Check "Enable su during boot"
Uncheck "Mount namespace separation".
After a reboot, Link2SD detected the 2nd partition!
EDIT: Now I fin another issue. If I try to link Obb, it says my device is using "sdcardfs". It offers to install fuse insted to fix it, but after rebooting I still getting the same message.
What could I do?
Click to expand...
Click to collapse
Seems Link2SD does not like Marshmallow so I switched to Apps2SD (which also suggests what you did). It would not create the partition itself but took windows EXT4 and after a bunch of config, worked. The issue I now have is that Samsung still thinks the card is corrupt (which it isnt); any EXT partition and it says that. So on any reboot it greets me with a system notification of a corrupt card (which I want to get rid of but so far can't)..
I did try adoptable using a scripts from this site (didn't work) and the Apps2SD option. Seem to work on device but windows only saw the device memory so would not copy anything when it reported full.
took another kick at the cat today; installed Apps2SD, created mount scripts, but now, for reasons unknown, it no longer reports the SD as corrupt on boot (although it does say that partition is corrupt from the storage setting menu. Weird. No idea why it is no longer doing this. I will say the reinstall was funny. I had to delete and recreate the mount scripts several times (all said it worked) to actually get apps to move without disappearing. perhpas I ended up with a different mount script method in all the trying