Related
Ok this is extremely annoying. I got the g1 and rooted with 1 click rooting cyanogen 4.0.4 rom. It was so simple and worked BTW. Later I used the hardspl so that I could do apps to sd. I have had the phone for 7 months and have used custom roms since I’ve gotten it.
Following this tutorial http://forum.xda-developers.com/showthread.php?t=535232 I tried to partition my 8g sandisk micro sd card. Now I probably destroyed my sd card (Nothing to big). And I am stuck at the g1 screen (pretty big). When ever I try to flash a different rom with a different or even the same rom I get an error acout the sd card “E:Can't mount /dev/block/mmcblk0p1 (or /dev/block/mmcblk0) (No such file or directory) E: Can't mount SDCARD:"
With around 8 hours of digging around on forums I have decided that I might have to get a replacement unless someone could help me revert with access that I have to the recovery to allow my sd cards to be recognized.
Note: I didn’t install the Cyanogen ROM - Download v4.0.2 or Cyanogen Recovery 1.4 - Download as I had a better one. Hince my problem, and did use the apps2sd.apk. Things didn’t go wrong until I typed in “upgrade_fs” . After doing so my phone would not boot up after I restarted it.
Something tells me that I changed something in the phone to allow apps to sd partition 2 and I need to be changed back to the default, as I can’t even flash another rom to fix this problem. Any help would be greatly appreciated .
willl your phone boot when you remove the sdcard
My phone will not boot after removing the sd card.
One thing that I forgot to mention above is. While using the phone after my uncessful attemp to partition my sdcard, the top notification bar was displaying "The SD card is blank or using an unsupported file system." After messing with it a bit i decided to reboot but it froze. Being impatient I pulled the battery from the back of the phone.
Looks as if files are missing from the Cyanogen 4.0.4 rom. As when I type “mount sdcard” is displays “mount: mouting /dev/block/mmcblkop1 on /sdcard failed: No such file or directory” Sounds like I am missing mmcblkop1 from my phone now? Apps2sd.apk doesn’t change this file does it? I'm also wondering if you change a file to look somewhere else for the partition part of the sd card? And if so how would you tell it to look for the default?
Tried this "flash_image recovery /sdcard/update-cm-4.0.4-signed.zip" and it displayed this "usage: flash_image [-d] partition file.img" does this delete the partition of the sd card or what is this referring to?
I think you 'bricked' your sd card.
Try format it with SD Formatter.
Worked for me.
Because you did use App2SD, you have erased app data, so setting up your G1 from scratch is your best option.
Ok first of all using that guide to install apps2sd on cyanogen's rom is what messed up your phone. Cyanogen has clear warnings about this in his thread. Now that the damage is done lets fix it. Can you boot into recovery by holding home and pressing power? Is there an option to flash any zip file?
After rereading your post i see that you don't have recovery 1.4.
You need to do step 4 HERE when you're done do step 5 to install cm-recovery-1.4
After trying different things with the console as I posted above the phone allowed me to install the Cyanogen 4.0.4 from the 2gb sd card. For some reason the phone would not allow me to do this before. As it wouldn't recognize the sd card, or that it had 1 for that matter. What would cause this problem? Maybe a faulty sd card? But I swapped to the 2 gb sd card that came with the phone and tried this numerous times before. Glitch? Why work now? I'm so lost.
I'm so glad that this worked this time though..... another save for this g1. Its taken a licking and it keeps ticking. I have dropped it 14 feet from the top of a railcar. I have crippled it 3 times now as it wouldn't allow me to get past the g1 screen. A simple flash from the sd card allowed me fix that problem. I have also dropped it in water. It was submerged for around 6 seconds in a leather carrying case that clips on your belt. Fast thinking allowed me to remove it from the water, pull the back off, and pull out the battery. I allowed it to dry in the car for around 4 hours and then put it in a bag full of those "do not eat" packets that come in most shoes for 24 hrs. Thanks to Walmart for the donation. Probably the best phone that I have ever gotten.
Well looking over the history of the phone I understand now why it may have done this to me. However it shows that by being persistent you can figure out most things. I appreciate all who have made these guides that make my g1 ownership so much fun.
Now go to get that apps2sd working. Another method probably.
I did have recovery 1.4 installed at the time the g1 quit working. I never downgraded and was able to access the recovery the entire time. But I kept getting the error “E:Can't mount /dev/block/mmcblk0p1 (or /dev/block/mmcblk0) (No such file or directory) E: Can't mount SDCARD:"
I did change the sd card at this point but had the same results.
As you may have noticed i didn't read Cyanogen thread discussing this.
I found the guide for apps 2 sd here: http://forum.xda-developers.com/showthread.php?t=535232 and read through it. Sounded easy enough and well tried. With failure of course.
I was under the inpression that apps2sd already is included in cyanogen 4.0.4 all i needed is to partition my sd card.
Jnewell05 said:
I did have recovery 1.4 installed at the time the g1 quit working. I never downgraded and was able to access the recovery the entire time. But I kept getting the error “E:Can't mount /dev/block/mmcblk0p1 (or /dev/block/mmcblk0) (No such file or directory) E: Can't mount SDCARD:"
I did change the sd card at this point but had the same results.
As you may have noticed i didn't read Cyanogen thread discussing this.
I found the guide for apps 2 sd here: http://forum.xda-developers.com/showthread.php?t=535232 and read through it. Sounded easy enough and well tried. With failure of course.
I was under the inpression that apps2sd already is included in cyanogen 4.0.4 all i needed is to partition my sd card.
Click to expand...
Click to collapse
Unfortunately that guide is still a sticky and someone uses it at least once a week and we end up with your problem every week. ivanmmj added a warning to the guide a few mins ago. I'm glad you are working now. You are correct about apps2sd being included in cyanogen roms. In post 3 HERE I've made a script that will partition your sdcard for you.
I was dicking around with the Rom Explorer (can't remember the exact name) app that comes with CM7 and I installed CMR onto my Nook. Problem is, it installed the 3.0.0.5 version over the previously installed 3.0.0.6, which I didn't know until I rebooted. When I did, it booted straight into Recovery version 3.0.0.5 and threw up the following errors:
E:Can't mount /cache/recovery/command
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
Fine, no problem. I'll just flash 3.0.0.6 on and... ADB won't work.
Okay, new tactic. I'll just wipe /system, /data, /cache, and reinstall CM7, which might fix recovery. Only...
E:Can't mount /sdcard
Ah.
Well, no problem, B&N wisely made the NC basically unbrickible to stop returns from idiots like me. I'll just boot 3.0.0.6 from my sdcard and flash CM7 again. Yay, it works! Only... it doesn't quite. It refuses to show up in ADB, and the root that I have is buggy. Titanium backup offers to install a newer version of su, but I already have the latest. I double check by trying to rename a file in /system with Root Explorer. No dice.
Well wonderful. Time to start from scratch. So I try all the return-to-stock methods in this thread, but none of them work.
At this point, I'm not really sure what I messed up... obviously flashing the older recovery image is a big part of it, but I'm completely flabbergasted as to why I apparently can't overwrite it with ANYTHING.
Does anyone have any ideas how I can fix this?
Sigh. I know this is the wrong section, but I don't have enough posts to post in the development subforum... certainly someone must have an idea of what I can do? Or am I completely SOL?
Finally got back to stock using brian21's stock 1.1 image! Now to start all over again.
lelandjs said:
Finally got back to stock using brian21's stock 1.1 image! Now to start all over again.
Click to expand...
Click to collapse
Glad you got it working again.
Isn't the Nook a wonderful device. It makes your world shine when you first root it. And then comes CM7. And even a HC preview. And then of course it throws a wrench in everything when we aren't paying attention to details and our happiness is turned into frustration.. and from the frustration brings us some actual knowledge.
I find the best part about my Nook is all the great things that I have learned along the way. From never touching an android platform to actually starting to learn some linux along the way.
Just my 2 cents.
racks11479 said:
Glad you got it working again.
Isn't the Nook a wonderful device. It makes your world shine when you first root it. And then comes CM7. And even a HC preview. And then of course it throws a wrench in everything when we aren't paying attention to details and our happiness is turned into frustration.. and from the frustration brings us some actual knowledge.
I find the best part about my Nook is all the great things that I have learned along the way. From never touching an android platform to actually starting to learn some linux along the way.
Just my 2 cents.
Click to expand...
Click to collapse
Not gonna lie, I was... underwhelmed by the rooted default Nook firmware. It just ended up being too slow. But CM7?
The NC actually marks my return to Android; I was slinging roms on my G1 back in the day (hence my vague knowledge of rom flashing).
Can't wait for a Honeycomb build, though I'm happy enough with CM7 for the moment. This really is a great tablet; the perfect size for taking with you to work and reading some comics on the subway. I liked the iPad but it (and other 10" tablets) was just too large for practical use.
i have the same problem,
E:Can't mount /cache/recovery/command
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
is this due to the CWR version, I have 3.0.0.5. I have CWR installed on the internal as well as booting it from sd.
were you able to format system and data under mount and settings because i get an error when doing so. Seems like this is a crucial step. This stops me from completing the steps necessary to flashing the file. If I try flashing the zip without formatting, my install aborts and gives me an error.
Sam is actually helping me sort out when he can but we still haven't been able to get it going. My emmc is corrupt is all i know and needs reformatting but abd won't even allow.
I am having the same problem as the post above me. I am a noob any help would be greatly appreciated.
lelandjs said:
Can't wait for a Honeycomb build, though I'm happy enough with CM7 for the moment.
Click to expand...
Click to collapse
Until now and you are still waiting for HC? Seriously?
wendellc said:
My emmc is corrupt is all i know and needs reformatting but abd won't even allow.
Click to expand...
Click to collapse
I had a very good double-boot configuration from NC stock 1.0.1-cm7 on a 32Gb SanDisk card. At that point, I could easily sideload media into the NC and the SDCard. I thought that I had successfully upgraded to the NC to 1.4 and then installed the triple-boot configuration stock/cm7/cm9 from the SDCard. The NookColor showed up in XP Pro Device Manager > Hardware. However, I began to run into problems at this point, I can't recall specifically (that was several weeks ago) what these problems were, other than that, after reading the forums here, I suspected that it might have had to do with upgrading the NC stock from 1.0.1 to 1.4. So, I managed to restore the NC 1.4 back to 1.2 (I read that NC stock 1.3 auto-updated if it were the boot). Then I burned the triple-boot back onto to the SDCard. I could access NC 1.2 stock/cm7/cm9 but I could no longer sideload media into the NC. When I take out the SDCard and plug the NC into XP, only two partitions appear as separate drives. The only partition that appears in XP Pro Windows explorer is the "boot" (115MB), with the list of files for the NookColor, it looks like.
I thought that, maybe, this was an acceptable price to pay, this loss of access to the internal 5Gb of the NC but access to the rest of the storage on the 32Gb SDCard. But, I need the NC ebook reader's access to its internal 5Gb storage and the 32Gb storage. When I recently booted into cm9, I got the message "Unfortunately, Trebuchet has stopped" so I tried to use adb to load an .apk into the appropriate place in order to attempt to repair/correct this. This is when I discovered that it seems like my NC emmc has, somehow, been corrupted because it doesn't appear in adb > adb devices. And when I've closed the 5037 connection in TCPView, adb still will not connect.
So, besides no longer being able to access the NC 5Gb storage from inside NC nor being able to sideload into NC, I can't repair the cm9 installation. If the NC emmc has been corrupted, would a simple upgrade to 1.3 repair this? If so, do I put the 1.3 update into the root NC by copying it to the "boot" 115MB drive and then inserting the SDCard into the NC and booting into NC?
Is there a way to repair or restore the NC so that I can sideload files into it?
I've plugged the NC into two other Windows XP machines with similar results, so it's a problem with the NC.
Thank You!
Sorry i didn't read all the details, but you really shouldn't be using such old CWM recoveries.
http://forum.xda-developers.com/showthread.php?t=1469732
boldred said:
I had a very good double-boot configuration from NC stock 1.0.1-cm7 on a 32Gb SanDisk card. At that point, I could easily sideload media into the NC and the SDCard. I thought that I had successfully upgraded to the NC to 1.4 and then installed the triple-boot configuration stock/cm7/cm9 from the SDCard. The NookColor showed up in XP Pro Device Manager > Hardware. However, I began to run into problems at this point, I can't recall specifically (that was several weeks ago) what these problems were, other than that, after reading the forums here, I suspected that it might have had to do with upgrading the NC stock from 1.0.1 to 1.4. So, I managed to restore the NC 1.4 back to 1.2 (I read that NC stock 1.3 auto-updated if it were the boot). Then I burned the triple-boot back onto to the SDCard. I could access NC 1.2 stock/cm7/cm9 but I could no longer sideload media into the NC. When I take out the SDCard and plug the NC into XP, only two partitions appear as separate drives. The only partition that appears in XP Pro Windows explorer is the "boot" (115MB), with the list of files for the NookColor, it looks like.
I thought that, maybe, this was an acceptable price to pay, this loss of access to the internal 5Gb of the NC but access to the rest of the storage on the 32Gb SDCard. But, I need the NC ebook reader's access to its internal 5Gb storage and the 32Gb storage. When I recently booted into cm9, I got the message "Unfortunately, Trebuchet has stopped" so I tried to use adb to load an .apk into the appropriate place in order to attempt to repair/correct this. This is when I discovered that it seems like my NC emmc has, somehow, been corrupted because it doesn't appear in adb > adb devices. And when I've closed the 5037 connection in TCPView, adb still will not connect.
So, besides no longer being able to access the NC 5Gb storage from inside NC nor being able to sideload into NC, I can't repair the cm9 installation. If the NC emmc has been corrupted, would a simple upgrade to 1.3 repair this? If so, do I put the 1.3 update into the root NC by copying it to the "boot" 115MB drive and then inserting the SDCard into the NC and booting into NC?
Is there a way to repair or restore the NC so that I can sideload files into it?
I've plugged the NC into two other Windows XP machines with similar results, so it's a problem with the NC.
Thank You!
Click to expand...
Click to collapse
First, your adb problem with CM9 is because CM9 uses different device ids for the windows usb adb driver than stock or CM7. If you want to know how to fix that, I can quote one of my posts for you.
I think you should take your SD and make a new single CM7 SD. You are getting too complex with triple booting while trying to debug. Then you can see if your emmc media partition is corrupt or not as I said in my other post about mounting drives in windows. Then once you are sure everything is ok with emmc, you can go back to triple booting.
The reason you are seeing 'boot' show up in windows when you plug the NC into windows running stock is the stock looks at partition 1 of an SD for 'sdcard'. On your triple boot SD partition 1 is the boot partition.
If it turns out that your emmc media partition is corrupt, I can help you fix that.
To learn more about fixing your stock if you need to again, read eyeballers thread (the epilogue of the first post).
http://forum.xda-developers.com/showthread.php?p=12797652
By doing the repartitioning he talks about in Dean Gibson's thread you can follow it but instead of going from 1GB media to 5GB media, back up, repartition to 5GB again and you will have a new reformated 5GB media. Then restore your data partition.
votinh said:
Until now and you are still waiting for HC? Seriously?
Click to expand...
Click to collapse
eyeballer said:
Sorry i didn't read all the details, but you really shouldn't be using such old CWM recoveries.
Click to expand...
Click to collapse
Folks, if you look at the dates of these earlier posts you will see they are from February of 2011 not 2012. That's why they were talking about Honeycomb and CWR 3.0.0.5.
leapinlar said:
Folks, if you look at the dates of these earlier posts you will see they are from February of 2011 not 2012. That's why they were talking about Honeycomb and CWR 3.0.0.5.
Click to expand...
Click to collapse
Ahh, my bad, getting old, I guess.
Apologize to OP, beer on me
Okay I'm a newbie wanting to root and uinstall CWR but have been confused after reading several How to's. My S7 came with v2.2 and I received and installed v3.2 on the first day.
I read a post mentioning this link: http://www.androidcentral.com/dell-streak-7-getting-bugfix-update. I "thought" that I followed the simple instructions but maybe not! I downloaded the file, renamed it "update.pkg" and while connected to my PC copied it to the root of my S7.
I put the S7 into recovery mode, selected install update.pkg from sdcard. Now this is where some of the confusion starts. While connected to my PC, nothing is refered to as a sdcard and I don't have one installed.
Okay back to the install. The S7 errors with four lines of text. It's looking for either "update.pkg" or "update.zip" with a file path: /mnt/sdcard/sdcard2/. I forget the exact wording but it's something like Failed or Can't Mount followed by the file path.
This left my S7 only booting to the Dell Logo and unable to connect to my PC beacause it wouldn't boot up. I had to do a factory reset which surprised me going back to v3.2 and not v2.2.
The file path mentioned above appears to show that it was looking for either file in the sdcard2 folder which is inside the sdcard folder. I had and since reinstalled the File Expert app which shows /mnt/sdcard/ and /mnt/sdacrd2/ or sdcard2 as a seperate folder not nested within the sdcard folder. Here again, the term/name "sdcard" is used and I don't have one. Is "sdcard" used to refer to the 16GB of internal memory? I assume so.
I'm not sure now if I would have used File Expert to copy "update.pkg" to the sdcard2 folder that I may have worked or not? On the linked page above, you see that I posted a comment about the problem and there is also another person has a screwed up S7 now too!
EDIT:
Nope, sdcard2 is indeed the optional sdcard slot which is empty and File Expert just errors.
When you boot into recovery and you are at the main menu with all the different options, choose the option to update from "internal" sdcard. The key is "internal" sdcard.
Sorry to not be more specific but I don't have my DS7 handy.
Good luck.
nagahtom said:
When you boot into recovery and you are at the main menu with all the different options, choose the option to update from "internal" sdcard. The key is "internal" sdcard.
Sorry to not be more specific but I don't have my DS7 handy.
Good luck.
Click to expand...
Click to collapse
I believe that there was only one option to install the update.pkg from but the point or question is, where is it looking for the file at? It appears that it's looking on the sdcard2 which isn't there!
This makes me wonder now, when a procedure states to put a file on your sdcard, just actually what are they refering to? The internal memory sdcard or an optional plugged in sdcard?
They are referring to the removable sdcard. If you don't have one, I'd suggest picking one up. It doesn't have to be a 32GB or even a 16GB. Then, put the update.pkg file on the root of that SDcard.
The filesystems can be very confusing on the DS7. Try it with a removable SD card and you should have better luck.
nagahtom said:
They are referring to the removable sdcard. If you don't have one, I'd suggest picking one up. It doesn't have to be a 32GB or even a 16GB. Then, put the update.pkg file on the root of that SDcard.
The filesystems can be very confusing on the DS7. Try it with a removable SD card and you should have better luck.
Click to expand...
Click to collapse
Yeah, why refer to the internal memory as sdcard?? The procedure for installing this update doesn't mention that an optional sdcard must be used either.
There's another thread where they appeared to have done that and it still failed! I may just wait till Dell puts it out OTA.
Hello!
I can not believe this: My brand new Xperia Z with 4.2.2 has no option to put apps to sd card!!!
Where did this button go?
The only thing I can move are photos, music and videos! This is CRAP!
What did happen?
My phone is rooted but not on unlocked bootloader.
How can I get this option back?
I tried "Foldermount", but despite this app will cost money it is sending my phone into bootloops!
Could please tell me someone how I can get this crucial option back??
WHY DID THEY DO THIS?
Looking at this thread, I feel we should just stop with the arguing and actually try to answer the question.
OP asked why?
So, to answer your question, as of 4.2, external storage is emulated in order to support the multi-user feature.
Read here & here.
4.2 has changed the way storage is treated by the Android OS.
This is why it is no longer possible to move applications to the external SD Card.
Further, as to how you can try to build up some extra space, it would be nice to copy your Android folder (This is usually where the big games store their files) from the root of your internal sdcard to your external storage.
Then create a soft link like this:
Code:
ln -s /storage/sdcard0/Android /storage/sdcard1/Android
Similarly, you can manually create softlinks for other large folders and move them to external storage. (Should be no problem for a power user!)
I choose to stay above the arguments in the thread & stick to the topic. If you do reply to me, please try and stay on topic if you want me to respond.
Rants, discussions and arguments can be taken over to the general section. Everyone is entitled to an opinion, just find the right place for it, that's all.
c1ph4 said:
@kgs1992; This is so far the best response I got. Thank you very much, Sir!
Unfortunately your links are worthless, because it is all related to TWRP. The only "hack" I did so far with this phone is rooting it. I am really not interested in using TWRP/CWM or ROMs the next weeks and/or months. I am really looking for an option to solve this irritating problem.
You tell me to symlink this Android folder and you "guess" that there are games. What about other files? I will read this up as I think this is the only solution I can think of right now.
Click to expand...
Click to collapse
The links were meant to be informative, just to give you some info & provide a reference on which my answer is based.
Symbolic links is (currently) the only possible solution unless you plan to swap the internal and external sdcard mount points.
I don't recommend the latter though, nor can I help you with it because I haven't tried it myself.
c1ph4 said:
@thalada: Yeah, you are definitley VERY helpful. Better stick with your Real Slim Shady, maybe you will marry him one day.
---
Click to expand...
Click to collapse
Glad i could be of help :silly:
@kingvortex: I really appreciate your efforts! But after I saw this strange "Folder Mount" app I don't think this is the right solution for me. It also needs to be unlocked for money. If my efforts with symlinking fail, I will come back for more. But your advice could be useful for users with very very much spare time. And there is no guarantee that it will work...
@kgs1992: The links are informative, no doubt about that. But I realize that even the hackers from TWRP have problems with this new behavior. This should make us think.
The ExtSD2IntSD switch thing is no option for me either. I totally agree with you!
Just give me time to read this symlink option up. I also need to know where other files than games files are stored. But I also see a problem here that different manufacturers of games store their files in different places. Some ask where they should put the data to, which is good, others (like EA) just use your internal memory without asking.
So, you see: What I need to do know is reading, reading, reading and trying, trying, trying. And maybe one day I will find a solution. But this problem was not there in 4.1.2. Time is a precious ressource nowadays. We should save it and not waste it.
All the best
c1ph4 said:
@kingvortex: I really appreciate your efforts! But after I saw this strange "Folder Mount" app I don't think this is the right solution for me. It also needs to be unlocked for money. If my efforts with symlinking fail, I will come back for more. But your advice could be useful for users with very very much spare time. And there is no guarantee that it will work...
Click to expand...
Click to collapse
@kingvortex is absolutely right.
I gave you the method, i.e. symlinking.
But he, it seems, gave you an app that does the symlinking for you without you having to do much of the work.
I would say his solution is far better than mine, although both effectively do the exact same thing.
Try use GL to SD app from play store. Is worked for me.
shinpeng said:
Try use GL to SD app from play store. Is worked for me.
Click to expand...
Click to collapse
Does the same as "Folder Mount": Phone reboots when I try to link with the symbol.
But thanks anyway, was worth a try.
Has anyone tried if link2sd does the trick like it did on my previous phone (neo)
[email protected]
indycar said:
Has anyone tried if link2sd does the trick like it did on my previous phone (neo)
[email protected]
Click to expand...
Click to collapse
You mean the app, right? No, that is the point, it does not work.
All these apps either say:
a) your device is not supported (sic!)
b) your external SD card is emulated (sic!)
These kinds of apps are obsolete now. Thanks to, well, you know already.
Symlinking does not work.
After moving a game directory to external SD card and symlinking it via "Terminal Emulator" I get the following message:
Code:
link failed: function not implemented
I also heard that symlinking is _not_ possible with FAT32 which drives my SD card.
And now?? Great.
P.S.: I have three different places to search for files before moving, btw: storage, sdcard0 and sdcard1. Veeery intelligent.
c1ph4 said:
Symlinking does not work.
After moving a game directory to external SD card and symlinking it via "Terminal Emulator" I get the following message:
Code:
link failed: function not implemented
I also heard that symlinking is _not_ possible with FAT32 which drives my SD card.
And now?? Great.
P.S.: I have three different places to search for files before moving, btw: storage, sdcard0 and sdcard1. Veeery intelligent.
Click to expand...
Click to collapse
Make an ext3 partition on your external sdcard.
kgs1992 said:
Make an ext3 partition on your external sdcard.
Click to expand...
Click to collapse
Did convert the file system from FAT32 to ext3. All my files are still there.
However, now Android says "SD card empty".
Perfect.
I give up. It is not possible anymore.
What I did:
1) made one partition FAT32, so that this poor little Droid can have his supreme SD card primary deluxe file system
2) made another one, ext3
I ended up with two partitions on the same SD card.
3) downloaded "Link2SD" and started it
4) first it lets you choose which file system is present on your second partition (in my case ext3). Then
5) "Link2SD" said: "Could not create mount script. Mount: invalid argument."
Finish! Nothing worked. I'm out of this. Good luck.
Hi,
This is my first android device, so am pretty much a newbie for android.
Have created this mod to mount external SD card partition as internal partition.
I took pointers from a lot of threads on xda forums to get this working, so I feel bound to share it.
Note: Have only tested it with Android 4.1.
(I'm not responsible for any Damage to your phone. Use at your own risk.)
Note: This will likely result in data loss. Backup!
Required :
1. Root Access
2. init.d support click here
3. Root Browser click here
4. SManager click here
5. An sd card (duh!) (with class 10 SD cards preferable)
6. Some way to partition your SD Card (like MiniTool Partition Manager)
Install instructions:
1. Create two ‘fat32’ partitions on SD card(EDIT: PS: both partitions should be Primary). Your first partition will be mounted as normal extSd card, and your second partition will be mounted as internal SD Card for your apps. (I partitioned my 64GB(10^9 bytes) sd card with ~16 GB 1st partition and ~42 GB 2nd partition)
2. Copy and paste “mountSd” to etc/init.d folder. (If you don’t have such a folder, means you lack init.d support. click here and follow instructions to enable it) This script creates another mount point called ‘sdcard2’ and mounts current internal sd card there. It also tries to mount second partition to ‘sdcard0’ location, but seems to fail some times (as fat32 is not natively supported linux partition it seems, but could be wrong), so step 3 is required.
3. Copy ‘mountSdFailSafe.txt’ to your phone’s ‘/data’ folder. Now with ‘SManager’, register this file as script with ‘su’ and ‘boot’ selected. (click and hold script -> in context menu click ‘Open As..’ -> ‘Script/Executable’ -> Is Script = true, select ‘su’ and ‘boot’ buttons)
4. Restart.
This should do it. Once restarted, second partition will be shown as internal memory.
Note:
You will lose all app data and other app related customizations. You may be able to restore it by simply copy pasting ‘Android’ folder from ‘/storage/sdcard2’ to ‘/storage/sdcard0’. This has not been tested by me but should work theoretically (as I started with a blank phone, and so did not need to back up my app data). Or you could use Titanium Backup.
Some Issues that occur due to this mod:
I have been using this mod since the past 2 weeks, and the phone is quite stable with this mod.
The only issue I have faced is that when connected to PC (Windows 8) through USB, ‘My Computer’ keeps crashing unless and until you disconnect the phone. Otherwise it seems to be working fine. To circumvent this issue I have been using Samba to share files between PC and my phone.
Please share how it works out for you guys.
Other Notes:
I tried to get this working with ext4 partition, which has a +ves that it will not require step ‘3’ of install instructions and supports file sizes >4GB, but there are loads of permission issues happening, which I could not solve.
(Thought of setting “set GID” bit and then finding and adding all users to root group but failed. Also tried to set owner group ‘sdcard_rw’ without much success. May be someone who knows linux better may know how to solve this, Could not find much help on the forums as it seems others are facing a similar problem see more)
Thanks to:
For basic idea (PS: do not use the given method exactly as you will end up in a boot loop. For some reason, ‘sdcard1’ mount point has to be mounted by system only and can’t be mounted any other way, it seems.)
http://forum.xda-developers.com/showthread.php?t=2180733
Edit:
Simplified installation if you do not care for easy accessibility to your orig internal memory:
Use this video tutorial by ashwin123:
The only exceptions are that, you need to partition your card,
and you have to use the file 'mountSdFailSafe.txt' instead of the file in the package mentioned by him.
Nice
Waiting for someone to test it n confirm it successfully works
Still here
N!geR -> E!ch0
NisJ said:
Hi,
This is my first android device, so am pretty much a newbie for android.
Have created this mod to mount external SD card partition as internal partition.
I took pointers from a lot of threads on xda forums to get this working, so I feel bound to share it.
Note: Have only tested it with Android 4.1.
(I'm not responsible for any Damage to your phone. Use at your own risk.)
Note: This will likely result in data loss. Backup!
Required :
1. Root Access
2. init.d support click here
3. Root Browser click here
4. SManager click here
5. An sd card (duh!) (with class 10 SD cards preferable)
6. Some way to partition your SD Card (like MiniTool Partition Manager)
Install instructions:
1. Create two ‘fat32’ partitions on SD card. Your first partition will be mounted as normal extSd card, and your second partition will be mounted as internal SD Card for your apps. (I partitioned my 64GB(10^9 bytes) sd card with ~16 GB 1st partition and ~42 GB 2nd partition)
2. Copy and paste “mountSd” to etc/init.d folder. (If you don’t have such a folder, means you lack init.d support. click here and follow instructions to enable it) This script creates another mount point called ‘sdcard2’ and mounts current internal sd card there. It also tries to mount second partition to ‘sdcard0’ location, but seems to fail some times (as fat32 is not natively supported linux partition it seems, but could be wrong), so step 3 is required.
3. Copy ‘mountSdFailSafe.txt’ to your phone’s ‘/data’ folder. Now with ‘SManager’, register this file as script with ‘su’ and ‘boot’ selected. (click and hold script -> in context menu click ‘Open As..’ -> ‘Script/Executable’ -> Is Script = true, select ‘su’ and ‘boot’ buttons)
4. Restart.
This should do it. Once restarted, second partition will be shown as internal memory.
Note:
You will lose all app data and other app related customizations. You may be able to restore it by simply copy pasting ‘Android’ folder from ‘/storage/sdcard2’ to ‘/storage/sdcard0’. This has not been tested by me but should work theoretically (as I started with a blank phone, and so did not need to back up my app data). Or you could use Titanium Backup.
Some Issues that occur due to this mod:
I have been using this mod since the past 2 weeks, and the phone is quite stable with this mod.
The only issue I have faced is that when connected to PC (Windows 8) through USB, ‘My Computer’ keeps crashing unless and until you disconnect the phone. Otherwise it seems to be working fine. To circumvent this issue I have been using Samba to share files between PC and my phone.
Please share how it works out for you guys.
Other Notes:
I tried to get this working with ext4 partition, which has a +ves that it will not require step ‘3’ of install instructions and supports file sizes >4GB, but there are loads of permission issues happening, which I could not solve.
(Thought of setting “set GID” bit and then finding and adding all users to root group but failed. Also tried to set owner group ‘sdcard_rw’ without much success. May be someone who knows linux better may know how to solve this, Could not find much help on the forums as it seems others are facing a similar problem see more)
Thanks to:
For basic idea (PS: do not use the given method exactly as you will end up in a boot loop. For some reason, ‘sdcard1’ mount point has to be mounted by system only and can’t be mounted any other way, it seems.)
http://forum.xda-developers.com/showthread.php?t=2180733
Click to expand...
Click to collapse
Am interested to try this but before I do, just wanted to check when you say data is lost, is it due to the lost of the original /data partition? Or just due to the sd card's partition?
What's the outcome when this is done, I mean do we have two data partitions one from the original phone's memory and another with the sdcard? And in the settings menu, will we get to choose to send apps over to sd? Thanks
grim_ripper said:
Am interested to try this but before I do, just wanted to check when you say data is lost, is it due to the lost of the original /data partition? Or just due to the sd card's partition?
What's the outcome when this is done, I mean do we have two data partitions one from the original phone's memory and another with the sdcard? And in the settings menu, will we get to choose to send apps over to sd? Thanks
Click to expand...
Click to collapse
Your application data will be lost in a way, as orig internal sd card will be mounted to 'sdcard2' mount point(newly created). All your app data will be installed to your memory card's second partition, which is now the new internal sdcard. To access your orig data, you will have to go to it through a file manager, and apps or media scanner will not be able to access this memory any more.
The scripts provided will not format your internal memory.
Still apk files, dalvik cache etc, will still take up your original internal memory's space.
Partitioning your sd card will probably format it as well unless you take special precaution (ie. through shrink volume).
Hope it makes sense...?
NisJ said:
Your application data will be lost in a way, as orig internal sd card will be mounted to 'sdcard2' mount point(newly created). All your app data will be installed to your memory card's second partition, which is now the new internal sdcard. To access your orig data, you will have to go to it through a file manager, and apps or media scanner will not be able to access this memory any more.
The scripts provided will not format your internal memory.
Still apk files, dalvik cache etc, will still take up your original internal memory's space.
Partitioning your sd card will probably format it as well unless you take special precaution (ie. through shrink volume).
Hope it makes sense...?
Click to expand...
Click to collapse
It makes sense, just am confused on how the system will still recognize the original storage when the sd card's storage is supposingly replacing it. Could you post a screen shot of your storage from settings?
grim_ripper said:
It makes sense, just am confused on how the system will still recognize the original storage when the sd card's storage is supposingly replacing it. Could you post a screen shot of your storage from settings?
Click to expand...
Click to collapse
Here you go....
PS: third image shows that internal storage is still accessible, just not to apps. Only apk files, and other android files go there go there. sdcard2 in 4th image is newly created mount point for your orig internal storage, but is ignored by most of the apps...
NisJ said:
Here you go....
PS: third image shows that internal storage is still accessible, just not to apps. Only apk files, and other android files go there go there. sdcard2 in 4th image is newly created mount point for your orig internal storage, but is ignored by most of the apps...
Click to expand...
Click to collapse
Can u do a tutorial video how to install this script bro?
Cuz the installation steps r bit complicated
Still here
N!geR -> E!ch0
NisJ said:
Here you go....
PS: third image shows that internal storage is still accessible, just not to apps. Only apk files, and other android files go there go there. sdcard2 in 4th image is newly created mount point for your orig internal storage, but is ignored by most of the apps...
Click to expand...
Click to collapse
Phone keeps rebooting now, couldn't copy it to /etc/init.d
I think it has something to do with having data running in the background, now I don't know what to do with my phone
EDIT: Ok, manage to recover from the reboot state, had to deny root access to my file explorer. I think the reboot was caused when I set permission to write for /system. Anyway, everytime I keep trying to copy to /etc/init.d, I get a permission denied so am not sure what I should do now.
grim_ripper said:
Phone keeps rebooting now, couldn't copy it to /etc/init.d
I think it has something to do with having data running in the background, now I don't know what to do with my phone
EDIT: Ok, manage to recover from the reboot state, had to deny root access to my file explorer. I think the reboot was caused when I set permission to write for /system. Anyway, everytime I keep trying to copy to /etc/init.d, I get a permission denied so am not sure what I should do now.
Click to expand...
Click to collapse
When ever you copy something to init.d it will reboot, or does it go into boot loop?
To check if it worked correctly, see if new mount point storage/sdcard2 was created..
EDIT: If it worked correctly, then you could move to next step.
else you could also skip it, and goto the next step of SManager, but in that case you will lose access to your original internal storage as it wont be mounted to sdcard2.
E!ch0 said:
Can u do a tutorial video how to install this script bro?
Cuz the installation steps r bit complicated
Still here
N!geR -> E!ch0
Click to expand...
Click to collapse
Creating a video will take time at least til sat... prob more.
Will see if I can create a simplified install instructions once i reach home.
NisJ said:
When ever you copy something to init.d it will reboot, or does it go into boot loop?
To check if it worked correctly, see if new mount point storage/sdcard2 was created..
EDIT: If it worked correctly, then you could move to next step.
else you could also skip it, and goto the next step of SManager, but in that case you will lose access to your original internal storage as it wont be mounted to sdcard2.
Click to expand...
Click to collapse
What happens is that everytime I try to mount /system as writable, it reboots and hence I can't copy either files to their designated location
EDIT: Also, now everytime I reboot, there's a popup that says USB connectivity has stopped, and if I go under settings->storage, settings fc. I'm thinking this has something to do with two partitions on the sd card so I hope it all goes away when this works or I revert back to as it was.
EDIT 2: So I managed to get all the files to the appropriate place using terminal and managed to get the script to run at boot. Alas, the phone doesn't detect my sdcard at all now and still throws the USB connectivity error at boot. Once I removed the sdcard, everything works alright. Also, I figured the solution to the reboot (haven't tested it yet as I wanted to resolve my sdcard first):
http://forum.xda-developers.com/showthread.php?t=2317432
EDIT 3: Got the reboot solve, but the sdcard can't be read and I tried plugging it into my other phone, the first partition is only read. I can't get minitool to even find the 2nd partition. I am thinking I need to get a card reader to plug it into my laptop. Anyway, I went through your script and open the log file it used, says that there's an invalid argument for mount. Any idea?
Final Edit: Got it working! I had to re-partition my sdcard and made both partitions primary so maybe you might want to add that in OP as MiniTool by default selected the 2nd partition as logical
grim_ripper said:
What happens is that everytime I try to mount /system as writable, it reboots and hence I can't copy either files to their designated location
EDIT: Also, now everytime I reboot, there's a popup that says USB connectivity has stopped, and if I go under settings->storage, settings fc. I'm thinking this has something to do with two partitions on the sd card so I hope it all goes away when this works or I revert back to as it was.
EDIT 2: So I managed to get all the files to the appropriate place using terminal and managed to get the script to run at boot. Alas, the phone doesn't detect my sdcard at all now and still throws the USB connectivity error at boot. Once I removed the sdcard, everything works alright. Also, I figured the solution to the reboot (haven't tested it yet as I wanted to resolve my sdcard first):
http://forum.xda-developers.com/showthread.php?t=2317432
EDIT 3: Got the reboot solve, but the sdcard can't be read and I tried plugging it into my other phone, the first partition is only read. I can't get minitool to even find the 2nd partition. I am thinking I need to get a card reader to plug it into my laptop. Anyway, I went through your script and open the log file it used, says that there's an invalid argument for mount. Any idea?
Click to expand...
Click to collapse
Why are you trying to mount /system as rw?
for getting init.d support you just have to download the apk from mentioned thread and install it, and then fallow instruction in app.
you can mount root as rw with the foll command if you want, and that is exactly what is done in he scripts as well if you will check:
Code:
mount -o remount,rw /
also to check if partition is created on sd card, type the command:
Code:
blkid
and see if
Code:
/dev/block/vold/179:34
is listed
if not post the output and i'll see what i can do.
grim_ripper said:
Final Edit: Got it working! I had to re-partition my sdcard and made both partitions primary so maybe you might want to add that in OP as MiniTool by default selected the 2nd partition as logical
Click to expand...
Click to collapse
EDIT: Correct, you need both the partitions to be primary. got out of my mind when posting the tutorial.
NisJ said:
Why are you trying to mount /system as rw?
for getting init.d support you just have to download the apk from mentioned thread and install it, and then fallow instruction in app.
you can mount root as rw with the foll command if you want, and that is exactly what is done in he scripts as well if you will check:
Code:
mount -o remount,rw /
also to check if partition is created on sd card, type the command:
Code:
blkid
and see if
Code:
/dev/block/vold/179:34
is listed
if not post the output and i'll see what i can do.
EDIT: Correct, you need both the partitions to be primary. got out of my mind when posting the tutorial.
Click to expand...
Click to collapse
For whatever reason, my /etc folder is actually a link from /system/etc
Could you post a way to revert back? I think my apps are acting all funny now and just want to revert back to before. Thanks!
grim_ripper said:
Could you post a way to revert back? I think my apps are acting all funny now and just want to revert back to before. Thanks!
Click to expand...
Click to collapse
The apps are behaving funny because you have lost their data as I had warned in the original post.
To fix do either of the foll:
1. reinstall app, and start fresh.
or
2. restore from Titanium backup if you had created...
or
3. copy paste 'Android' folder from sdcard2 if it is created to 'sdcard0'
To remove and revert, just delete the files from int.d, and stop scheduling it in SManger.
Note: to un schedule it from smanager, you first have to remove memory card, un schedule and then put in your memory card (this is coz when phone boots up, it is in standard way, with 8gb internal but, after script is executed SManager looses its data too.
How complicated will it be to make this compatible with 4.2.2?
grim_ripper said:
How complicated will it be to make this compatible with 4.2.2?
Click to expand...
Click to collapse
Ideally should be possible, unless something has changed majorly, but I haven't tried it, as am waiting for OTA update. If it is not forth coming in 2-3 weeks, may be tempted to flash nordic rom and try.
NisJ said:
Ideally should be possible, unless something has changed majorly, but I haven't tried it, as am waiting for OTA update. If it is not forth coming in 2-3 weeks, may be tempted to flash nordic rom and try.
Click to expand...
Click to collapse
I did try but nothing happened, am guessing it has permission issues or something on those lines
grim_ripper said:
I did try but nothing happened, am guessing it has permission issues or something on those lines
Click to expand...
Click to collapse
Could you be more specific? Like system restarts etc...
Else in terminal try out what I Gave in post no 12 and give me what the output is for both the commands in the terminal.
Note: execute them with super user credentials.
Thanks
NisJ said:
Could you be more specific? Like system restarts etc...
Else in terminal try out what I Gave in post no 12 and give me what the output is for both the commands in the terminal.
Note: execute them with super user credentials.
Thanks
Click to expand...
Click to collapse
on the 4.2.2 update, it doesnt recognize the second partition even if it is formatted to primary and set to active. there r definitely some updates done in that field and plus i cant get the init.d rights on the phone as the test.log file is absent in the data folder..no matter what i do i just cant get it straight with the present procedure. please try it on 4.2 and there r more frequent updates on the nordiac then the local version. so i decided to flash it rather than waiting for ota update