Related
After a recent partition to make more internal space available to install Kingdom Shooter,I started getting the error in the title. The error pops up after any action in recovery. The new rom goes on fine and I'm showing over 200MB left after several user apps are installed from the market.
Every now and then though, after a battery change or regular reboot, the rom won't load and requires a complete redo.
Last time I did a fresh rom install my OLD Custom WALLPAPER was put in as default on a fresh setup..so..I've got stuff stuck in internal memory. Is there a way to clean it up in root explorer or other app?
My current setup is not my sig..
it is stock kernel HW004 32 MB swap 1024 ext3 partition
Thanks for any suggestions for clearing up this error.
No1 ever fixed this error?
When I had that happen once I made sure to back up all my stuff to my pc. Then I reformatted the card twice. It kept happening to me when I first partitioned. So a re-format and then partition again did the trick. Either that or your sd is takin is gonna be taking a crap on you soon.
I just had this issue too with my EVO 4G:
E: Can't read MISC: (No space left on device)
I had some 'RA HAUS 2.3' recovery, weird name, I don't know anything about this recovery, was installed when I did my rooting back in March 2011; it seems to be someone's version of Amon RA.
Anyway, I found the real Amon RA:
http://forum.xda-developers.com/showthread.php?t=705026
Downloaded it, put to my USB root folder and went to HBoot, allowed it to recognize the 'real' Amon RA; when finished the update, rebooted normally.
Then went back to recovery and wiped cache, dalvik cache and data; then installed ROM EVOlvedROM r3chargeD Final which I installed on my wife's EVO over the weekend.
Anyway, no more weird message 'E: Can't read MISC: (No space left on device)', I'm done with that and the phone at least for a few hours seems more stable now.
For more details, see post 5 on this link, this is almost identically to what I did:
http://androidforums.com/evo-4g-all-things-root/402522-e-cant-read-misc-no-space-left-device.html
EDIT: some pertinent information, my EVO had plenty of storage both internal and SD card when this 'error' appeared, no reason to get this message!
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.
I know there is a lot of information out here about the nook color not being able to boot but none of it seems to fix this issue. I was trying to upgrade my nook from cyanogenmod 7.2 to cyanogenmod 10.2. I used Rom Manager on the device and downloaded the new ROM. Everything was fine until I told it to install. The nook went to reboot and I was presented with a black screen. I couldn't get it to do anything and I thought it was dead forever. I then installed a bootable ROM on my SD card and was able to get it to boot from the SD card. I have attempted to install several different versions onto the EMMC but none will boot. When I reboot the nook it just goes to a black screen and sits there, even with the SD card in it. This is the only sequence that allows me to get my nook color to boot from an sd card:
1) Hold the "n" and power buttons for 30 seconds (I think this forces it to power down)
2) Push and hold power button for a few seconds.
If I do this with a bootable SD card installed the nook boots the SD card. If I do this without the SD card installed I just get a black screen. I have tried many things from many threads here. I have tried fixing partitions, installing new ROMS and other things but nothing seems to work. I know the nook is not bricked because I can boot it from the SD card. I think the boot partition may be the issue. When I am booted from the SD card I can mount all partitions except "/boot". Should I be able to mount this partition?
I just need to know how to get my nook back to a state where it will boot without the SD card inserted. I know how to create a bootable SD card and install zips.
Very frustrated at this point, guidance that anyone can give would be greatly appreciated...
Thanks.
You said you tried fixing partitions. How did you do that and what were the results? Were you using my partition repair zips from my partition repair thread linked in my signature?
And ROM Manager assumes you have a correct version of CWM installed on internal memory. It is best not to use that tool. It is way outdated. It is best to install ROMs manually with CWM.
Sent from my BN NookHD+ using XDA Premium HD app
deleted post
Partitoning did not seem to help
leapinlar said:
You said you tried fixing partitions. How did you do that and what were the results? Were you using my partition repair zips from my partition repair thread linked in my signature?
And ROM Manager assumes you have a correct version of CWM installed on internal memory. It is best not to use that tool. It is way outdated. It is best to install ROMs manually with CWM.
Sent from my BN NookHD+ using XDA Premium HD app
Click to expand...
Click to collapse
Yes I have done 2 out of the 3 zips you have on your post. 1) NookColor-emmc-repair-partitions-1-4-5-6-7-8.zip and 2)NookColor-emmc-format-partitions-5-6-7-8.zip. I did not do the partition 2 zip as it looked like it may cause more problems. However, I'm not sure it could get much worse.
Today I ran the RecoveryFix.zip from this post --> http://forum.xda-developers.com/showthread.php?t=958748
No Help. Same issue, I reboot and nothing but a black screen. I have to do the 2 steps I described in my original post to get the SD card to boot. Is there a way I can see what is on the nook partitions? These tools allow me to copy zip files but there is nothing that allows me to look around on the nooks internal partitions. What does the nook need to boot without the SD card. It seems there must be something partially working because I can get the SD card to boot...
Thanks I advance for your help.
Need to fix internal hard drive...
Ok, so now I'm pretty sure it's just my internal memory that is screwed up. I installed CM 7.2 on an SD card and now my nook color is running from the SD card. But if I take the SD card out and try to reboot all I get is a black screen(Not even a flash or anything when hitting the power button). So right not the only thing my nook can do is boot from the SD card.
How can I fix the internal memory??
noooker said:
Ok, so now I'm pretty sure it's just my internal memory that is screwed up. I installed CM 7.2 on an SD card and now my nook color is running from the SD card. But if I take the SD card out and try to reboot all I get is a black screen(Not even a flash or anything when hitting the power button). So right not the only thing my nook can do is boot from the SD card.
How can I fix the internal memory??
Click to expand...
Click to collapse
Try flashing the repair partition 2 zip. It has protections built in to prevent further damage.
Then go to my NC tips thread linked in my signature and return to stock via item A15. Be sure to flash the format zip listed there too. Then you should be able to start over.
Sent from my BN NookHD+ using XDA Premium HD app
Repair Partiton 2 failed
leapinlar said:
Try flashing the repair partition 2 zip. It has protections built in to prevent further damage.
Then go to my NC tips thread linked in my signature and return to stock via item A15. Be sure to flash the format zip listed there too. Then you should be able to start over.
Sent from my BN NookHD+ using XDA Premium HD app
Click to expand...
Click to collapse
Ok, I think I may have totally screwed this nook up. I found some other repartition//format zips that I ran trying to fix the problem. Now I can't even run from the SD card. It tries to boot but I get an error and it fails. I tried to run your repairpartition2.zip file but it did not work. This is the output:
E:Can't mount /cache/recovery/last_install
E:failed to open last_instal: no such file or directory
Finding update package...
Opening update package...
Installing update...
Repair /rom partition (P2)
Checking for /factory - if ot found will return error message and repair will be aborted.
assert failed:mount("ext2", "EMMC", "/dev/block/mmcblk0p3", /factory") == "/factory"
E:Error in /sdcard/NookColor-emmc-repair-partition-2.zip
(Status 7)
Installation aborted.
I've also noticed that it cannot mount any of the partitions from the booted SD card any more. I'm seeing
E:Can't mount /cache/recovery/log and other errors
I think one of the other .zips I ran screwed things up even more. Am I now screwed up past the point of no return? I have very good unix knowledge but very little android knowledge. Is there anything I can do with the adb utility to help here.
Thanks for all your suggestions so far. It seems like I need to redo this thing from scratch and need some guidance on how to do it.
More Info: Now when booted from SD card I cannot mount "/boot", "/system", "/data", "/emmc" or "/cache" partitions. I wish I could get a shell and look around on the rom...
noooker said:
Ok, I think I may have totally screwed this nook up. I found some other repartition//format zips that I ran trying to fix the problem. Now I can't even run from the SD card. It tries to boot but I get an error and it fails. I tried to run your repairpartition2.zip file but it did not work. This is the output:
E:Can't mount /cache/recovery/last_install
E:failed to open last_instal: no such file or directory
Finding update package...
Opening update package...
Installing update...
Repair /rom partition (P2)
Checking for /factory - if ot found will return error message and repair will be aborted.
assert failed:mount("ext2", "EMMC", "/dev/block/mmcblk0p3", /factory") == "/factory"
E:Error in /sdcard/NookColor-emmc-repair-partition-2.zip
(Status 7)
Installation aborted.
I've also noticed that it cannot mount any of the partitions from the booted SD card any more. I'm seeing
E:Can't mount /cache/recovery/log and other errors
I think one of the other .zips I ran screwed things up even more. Am I now screwed up past the point of no return? I have very good unix knowledge but very little android knowledge. Is there anything I can do with the adb utility to help here.
Thanks for all your suggestions so far. It seems like I need to redo this thing from scratch and need some guidance on how to do it.
Click to expand...
Click to collapse
That error message says your factory partition is gone and it contained info there that is vital and un-retreivable. You might be able to rebuild your partitions but some ROMs will never run without that backup info from /factory (partition 3). You just got too aggressive with your partition repairs.
Sent from my BN NookHD+ using XDA Premium HD app
I'm running deodexed build from this post: http://forum.xda-developers.com/showpost.php?p=40232503&postcount=43 and CWM bootloader. I'm using link2sd and 16GB external CD card.
Strange things started to happen (I think) after using my phone in the swimming pool. Apps from my external card vanished and I couldn't fix this issue, so finally formatted SD card (minitool didn't work, partition toolkit did). Meanwhile every now and then "no place on disk" error while installing apps popped up. Approx. 400 MB of internal storage was free...
After format things started to look promising, but "no place on disk" error still bugged me, so I thougth about workaround, and tried adb shell pm set-install-location 2. After restart I got bootloop. Tried several options and finally was able to flash firmware with odin 1.85. While I was at it, I flashed bootloader with CWM mod and odin 3.09. (Before flashing I was getting an error after restart and had to reboot manually:
E: failed to verify whole-file signature
E: signature verification failed
Click to expand...
Click to collapse
). Well, that worked, and no data was lost, but my external card is unusable, link2sd warns me about my second partition not being automounted and every time I restart phone I'm in the bootloop again, having to flash firmware to be able to unbrick it.
I tried to fix second partition from within partition toolkit, but no luck, formated it, again, but now link2sd doesn't see it mounted at all (partition toolkit does). I've reverted install location already, set it to 0, and later to 1, but no luck... I mean it works, but doesn't solve the problems.
I'm running out of ideas. I backed up everything with titanium backup and I'm considering factory reset, but not sure if it will help at all...
UPDATE:
I bought 32 GB SD card and replaced the old one. Formatted it and things seemed to work, but in roughly 50% of cases I couldn't install application due to "usufficient space on disk" error.
And another issue: yesterday my phone hung, so I restarted it. Basically it entered bootloop, but starts normally as soon as SD card is removed. Recovery log says "can't partition non mmcblk device" regarding SD card.
It looks as if SD card was mountable only when fresh formatted, any application moved to it (link2sd) and things end up as described.
Tried to boot without SD card and insert it later when system starts, but no luck (card is not discovered at all).
I'm seriously considering selling this phone - without external space for installing apps it's next to unusable, and it seems I am not able to solve the issues with SD card.