Database Develop

Removed SD Card

Sorry if this has been adressed before, but i did use the search and i cannot quite figure out what to do next. I might have dropped my phone the other day, and since then none of my apps run from the SD becase it thinks that it was ejected. So, i wiped and installed a clean JackXrom again, and it was fine for about 20 min, then phone locked up, and when i restarted, i get the same problem. Should i format the partitions on the card perhaps? I was trying to avoid that, so any work around would be helpfull.
Latest radio, spl. Class 6 8 gig SD card.
Thanks.

te5ter said:
Sorry if this has been adressed before, but i did use the search and i cannot quite figure out what to do next. I might have dropped my phone the other day, and since then none of my apps run from the SD becase it thinks that it was ejected. So, i wiped and installed a clean JackXrom again, and it was fine for about 20 min, then phone locked up, and when i restarted, i get the same problem. Should i format the partitions on the card perhaps? I was trying to avoid that, so any work around would be helpfull.
Latest radio, spl. Class 6 8 gig SD card.
Thanks.
Click to expand...
Click to collapse
sounds like a corrupted partition try repair ext file systems if that dosent work youve got to format partition and reinstall all apps.
btw does youre fat32 partition work?

te5ter said:
Sorry if this has been adressed before, but i did use the search and i cannot quite figure out what to do next. I might have dropped my phone the other day, and since then none of my apps run from the SD becase it thinks that it was ejected. So, i wiped and installed a clean JackXrom again, and it was fine for about 20 min, then phone locked up, and when i restarted, i get the same problem. Should i format the partitions on the card perhaps? I was trying to avoid that, so any work around would be helpfull.
Latest radio, spl. Class 6 8 gig SD card.
Thanks.
Click to expand...
Click to collapse
If it only happened once it shouldn't be an issue, but if it does it wouldn't hurt to format your ext.
In recovery
mount -o rw /dev/block/mmcblk0p2 /system/sd
rm -r /system/sd/*

I tried repairing my ext, no luck.
Whenever i try to mount in recovery console i get error : No such file or directory

te5ter said:
I tried repairing my ext, no luck.
Whenever i try to mount in recovery console i get error : No such file or directory
Click to expand...
Click to collapse
Sounds like you need to delete the partition and make a new one, as it can't be read. If you're going to use parted from you're phone then you'll probably have to start over and recreate fat (and linux-swap if you had one) too. If you're using paragon or Gparted you should be able to recreate just your ext.

I cant recall which tutorial i fallowed, but it was all done through the terminal or recovery. Could you possibly point me to the right thread?

AdrianK said:
Sounds like you need to delete the partition and make a new one, as it can't be read. If you're going to use parted from you're phone then you'll probably have to start over and recreate fat (and linux-swap if you had one) too. If you're using paragon or Gparted you should be able to recreate just your ext.
Click to expand...
Click to collapse
if you can remember the start and end of youre ext partition i think you can do this in parted by typing print then note down the start and end then type mkpartfs primary ext2 start - end

te5ter said:
I cant recall which tutorial i fallowed, but it was all done through the terminal or recovery. Could you possibly point me to the right thread?
Click to expand...
Click to collapse
Here you go, follow the second section.
http://android-simplicity.blogspot.com/2009/08/how-to-6-how-to-partition-your-sdcard.html

Everytime i try to mount in recovery i get "mount: mounting /dev/block/mmcblk0p1 on /sdcard failed: device or resource busy"
I'm lost.

pull your battery our for 30 seconds or so. remove your sd card then reinsert it and then try again. if that doesnt work then do what the others guys have said and try to reformat your sd card and start from scratch.

AdrianK said:
Sounds like you need to delete the partition and make a new one, as it can't be read. If you're going to use parted from you're phone then you'll probably have to start over and recreate fat (and linux-swap if you had one) too. If you're using paragon or Gparted you should be able to recreate just your ext.
Click to expand...
Click to collapse
Actually, with Parted you can just rm and mkpartfs any partition you want without affecting the other partitions.

I bit the bullet and just formated all the partitions.
Thanks anyways guys.

My advice for next time or any body else reading would be to download a live CD for ubuntu or fedora or similar and boot your PC off that - it's graphical and v. easy.
Or just dump windows altogether and go for linux ;-)
Smiffy.

Lordsmiff said:
My advice for next time or any body else reading would be to download a live CD for ubuntu or fedora or similar and boot your PC off that - it's graphical and v. easy.
Or just dump windows altogether and go for linux ;-)
Smiffy.
Click to expand...
Click to collapse
Yeah Gparted is amazing problem is then you have to walk the person through downloading, burning the image...which can be painful.

This is still happening, fresh format on sd card partitios and a wipe and clean install of Jacxrom.
Bad sd card? Or the phone?

JACxROM [v1.3]
I am attempting to flash to this ROM. Everything seems to go as describen in other posts, but when I power up the phone, I never make it past the splash screen. Any thoughts??

sorry
Sorry I posted this in the wrong place, I will move it.
rberger13 said:
I am attempting to flash to this ROM. Everything seems to go as describen in other posts, but when I power up the phone, I never make it past the splash screen. Any thoughts??
Click to expand...
Click to collapse

Bump, dead SD card?

partition corrupted anyway to recover?
I need help please!
I was running cyanogen 4.0.3.1 just installed today morning then changed theme to enoch 1.12 the newest one that worked fine. Updated the browser to loccys Then installed the HTC music and when finally rebooted the phone it was working fine until I noticed I had none of my apps on the sdcard.
All I have is syste/app folder which runs internally I think everything else does not work. It's like my sdcard is not in.
I shutdown rebooted and waited. Then removed sdcard rebooted and inserted the card one fully powered on and it is saying it wants to format it.
I get home turn my ubuntu system on and it detects it as a ext3 partition yet nothing inside. and now no fat32 partition or linux-swap.
anyways to recover or am I SOL?

HELP SD card not recognized

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.

[solved] Card "Preparing SD card; Checking for errors"

Hi all,
I have a problem with my G1, running on latest Cyanogen mod. After restarting the card cannot be read and it is seems to be checking the sd card, if it really happens I dunno. What is weird is that I can access the card from recovery mode (shell), and it is not damaged (at least the windows doesn't detect damage while it is in the card reader. So that implies that the problem might be in the Android system.. anybody has a clue how to solve this? Thanks a lot.
Edit: solved it, deleted fsck_msdos from bin and it works flawlessly again

Can always wipe and reflash. Or if you have another sd card laying around and put that in to see if it recognizes it.

I'm having the same problem How did you delete the fsck_msdos from the bin?

theinstagator said:
I'm having the same problem How did you delete the fsck_msdos from the bin?
Click to expand...
Click to collapse
your phone should rooted
then download and install root explorer
in the root explorer go to
system /bin
and delete fsck_msdos
now reboot your phone

I was having this same issue..it would typically take up to 5 minutes or more to "check for errors" after a boot.
To fix this I backed up my sdcard, reformatted, copied everything back, then reflashed. Everything was fine after that.

i have somewhat the same problem but in my case it sometimes say blank sdcard or damged sd card it read fine when plugged into an sd card reader any help

Thanks. It worked by simply deleting fsck-msdos but it keeps giving SwiftKey3 error " unable to load language packs". Keyboard still OK. I have xperia x10 mini rooted running android 2.1 E10i.

hmaxos said:
Thanks. It worked by simply deleting fsck-msdos but it keeps giving SwiftKey3 error " unable to load language packs". Keyboard still OK. I have xperia x10 mini rooted running android 2.1 E10i.
Click to expand...
Click to collapse
Well, after getting other errors such as "no enough space" from Platinum Backup (there was a space on SD Card), I had to go to Format the SD after copying everything. Then I copied back the important folder the SD. I also had to reinstall SwiftKey. Now everything is fine and no data loss.

SD card Checking for errors
sajjji said:
your phone should rooted
then download and install root explorer
in the root explorer go to
system /bin
and delete fsck_msdos
now reboot your phone
Click to expand...
Click to collapse
Well I will try to backup and format it.... If it works then good if not then I will have to root my LG P880 .

My Problem is "preparing external sd card checking for errors" now that error is not showing while following above steps but now when i click my memory card that is not opening and after opened my memory card my internal device memory also not opening .

baka.yarou said:
Hi all,
I have a problem with my G1, running on latest Cyanogen mod. After restarting the card cannot be read and it is seems to be checking the sd card, if it really happens I dunno. What is weird is that I can access the card from recovery mode (shell), and it is not damaged (at least the windows doesn't detect damage while it is in the card reader. So that implies that the problem might be in the Android system.. anybody has a clue how to solve this? Thanks a lot.
Edit: solved it, deleted fsck_msdos from bin and it works flawlessly again
Click to expand...
Click to collapse
Simple fix, Difficult decision. Remove SD Card from slot then Factory reset phone. Once it comes too just go through all steps to setting up device then reinsert the SD Card into the slot. BOOM!

thank you very very much it worked for me
baka.yarou said:
Hi all,
I have a problem with my G1, running on latest Cyanogen mod. After restarting the card cannot be read and it is seems to be checking the sd card, if it really happens I dunno. What is weird is that I can access the card from recovery mode (shell), and it is not damaged (at least the windows doesn't detect damage while it is in the card reader. So that implies that the problem might be in the Android system.. anybody has a clue how to solve this? Thanks a lot.
Edit: solved it, deleted fsck_msdos from bin and it works flawlessly again
Click to expand...
Click to collapse
thank you so much but it is read only please help

yeah...
supremeteam256 said:
Can always wipe and reflash. Or if you have another sd card laying around and put that in to see if it recognizes it.
Click to expand...
Click to collapse
i am having same issue i always changes roms please can you halp me..

still not working mine is lenovo K3 Note And my Phone is rooted. It is showing Preparing SD card checking for errors

Didn't work for me.
Hard reset don't work.
Delete the fsck.msdos but don't work.
The fsck.msdos file comes on every wipe back.
I think this is a cm issue.
On stock no problems with my external sd card on my HTC One M8.
I'm going crazy...

No need to go to bin.. just put ur SD card in other mobile.. it will show fcsk files when u open the SD card.. just delete those files. Then remove the SD card and put it back in Ur mobile.. Then restart it mobile.. problem solved..,,,

Anitha Sivakumar said:
No need to go to bin.. just put ur SD card in other mobile.. it will show fcsk files when u open the SD card.. just delete those files. Then remove the SD card and put it back in Ur mobile.. Then restart it mobile.. problem solved..,,,
Click to expand...
Click to collapse
ive deleted the fcsk file on bin
the notif "preparing sd card" was gone but another problem occured, i cant even open my storage, ext sd card and even internal card ive tried your solution, ive put my sd card on another device, i cant find any fcsk files that you mention i cant even delete any file from my card using another mobile :crying::crying::crying:

It worked.... Thanks bro..
:good:
sajjji said:
your phone should rooted
then download and install root explorer
in the root explorer go to
system /bin
and delete fsck_msdos
now reboot your phone
Click to expand...
Click to collapse

sajjji said:
your phone should rooted
then download and install root explorer
in the root explorer go to
system /bin
and delete fsck_msdos
now reboot your phone
Click to expand...
Click to collapse
Bloody Brilliant. I have no idea why I could not find this solution two years ago. I have spent several hours searching for this solution, several times. In my case, I needed to remove the fsck.exfat file in the /system/bin folder.
My attention span is extremely short. I have been living with a 3 to 4-minute card scan for a 256GB microSD in my Samsung Note 3 for two and a half years. For all of the reboots I have done (which must be near a thousand, if that's not severely underestimated) I have had to deal with waiting to use my phone. I can't tell you how discouraging it has been to have such a powerful, useful device crippled by such a stupid flaw: that of checking the SD card that you rarely remove, for errors, every single time the phone is rebooted, even after graceful reboots called by the "proper" methods.
I can't tell you how many times I have rebooted my phone, only to forget the reason I rebooted it, because my phone took 4 minutes to reboot.
Productivity to the cubed-root.​Pisses me off.
Someone who has more voice than me please get the Android People to change this. As of Nougat, this is still the default behavior. How can an organization be so stupid...? I have no doubt that just this flaw has sent many people to the Apple camps. Who the cuff in their right mind would want to deal with such a hassle?? Are they seriously unaware of the trend for people to actually believe that their devices, machines and technology ought to be doing things faster than previous generations?
(Please just take the following cynicism with a grain of salt. I just learned the above fix, something I really should have figured out a long time ago/kicking myself!!) :crying:
For the anally-inverted who might bring up the obvious argument that your phone will no longer be able to detect or fix corruption, all that needs to be done is the following:
1) move the fsck.exfat (or whatever the formatting) file to a different folder. In my case I moved it to the /data folder
2) use some delay scripting program that will symlink the fsck.exfat file to a tmpfs location say, 30 seconds after boot; or longer if needed. This intermediary step is necessary in order to create a temporary symlink, which will be nonexistent upon reboot.. If we didn't create a temporary symlink, the fsck.exfat command would be immediately available after each reboot (which we don't want) because symlinks are normally permanent. Therefore, this step will need to be run after every reboot (but again, time-delayed).
3) the last command is to create another symlink, linking the tmpfs fsck.exfat symlink created in the last step back to the /system/bin folder (or wherever it originally resided). So this is a symlink of another symlink. This step actually should only need to be done once, since this symlink should remain after reboot, even though it is initially broken upon reboot until the previous command recreates the intermediary symlink. It should become effective again when the previous step is run by the time-delayed scripting program.
Now your phone has the ability to check the card upon you calling the fsck.exfat routine through normal means, one of which can just be a simple unmount -> mount request from the Android system settings . Your card won't be needlessly fsck-checked to death every bloody time you reboot your phone.
(If you found this tutorial helpful and desire to quote or improve upon it, please cite/credit me for the inspiration! It came through much effort and learning!)

app2sd workin on telus milestone

wow i got app2sd working on my telus milestone make sure that busybox is not installed on the system i mean when u use adb to install not busybox itself (from titanium etc) if the method does not work unroot then root the try it will work.
i did not create this i have just copied and pasted it i know alot of people need this so here
. App2SD Version 2 (http://www.mediafire.com/?emhyw4tmkmh)
This revised version of App2SD is more refine. It moves cache as well as apps to MicroSD.
Steps to prepare for installation:
1. Unzip the downloaded file and you should see a folder "APP2SD Package".
2. Rename "APP2SD Package" folder to "app2sd" and move this folder to MicroSD. (place it in the root: MicroSD card/)
Next, simply connect the Milestone to your computer.
Ensure it is "Charge Only" for USB connection and USB Debugging mode for USB is turned on under Settings > Applications > Development.
Once you have the above checked, go ahead to launch a command prompt and perform the following:
Type: cd/ (to get to the root of your C: drive)
Type: cd /android/tools (to get to the folder of the Android SDK which i mentioned earlier)
Type: adb devices (you should see your Milestone serial number showing up. If you do not see serial number, it means there is no connection to your Milestone)
Type: adb shell
Type: su (make sure you do not see a prompt window on your Milestone. If you do, grant permission for it to access)
Type: cd /sdcard/app2sd
Type: sh install_use_busybox.sh (trigger installation of App2SD)
Type: y (to confirm that you want to install)
wait for the prompt to show you that App2SD is complete and a reboot is needed for it to take effect.
Type: y (to confirm reboot. You might notice that Milestone do not reboot by self which is normal)
Type: reboot (if you find Milestone do not reboot after you enter y as above mentioned)
Enjoy after the reboot... this works yes

u can type ls -l /data to see if it works

hey I'm just about to do the apps2sd for my milestone and was wondering which partitions if any did you make for the SD card? thanks
I'm assuming it needs at least ext2 and I'm about to set mine up with ext3, just want to make sure so I don't screw anything up
also just wanted to say if you haven't overclocked your milestone, definitely do it, just did mine yesterday, running at 1ghz and it is so amazing, downloads are insane, browser is quick and menus and everything are perfect, eat that X10

kittcoldfire said:
hey I'm just about to do the apps2sd for my milestone and was wondering which partitions if any did you make for the SD card? thanks
I'm assuming it needs at least ext2 and I'm about to set mine up with ext3, just want to make sure so I don't screw anything up
also just wanted to say if you haven't overclocked your milestone, definitely do it, just did mine yesterday, running at 1ghz and it is so amazing, downloads are insane, browser is quick and menus and everything are perfect, eat that X10
Click to expand...
Click to collapse
haha ya i overclocked it but I do not go over 800mhz to risky plus gets pretty hot.
I made a ext 2 partion using unbuntu,.......partionmanager said it was partioned but would not work,app2sd did not see it. u can try it though but i recommend unbuntu let me know what happens

gemini002 said:
haha ya i overclocked it but I do not go over 800mhz to risky plus gets pretty hot.
I made a ext 2 partion using unbuntu,.......partionmanager said it was partioned but would not work,app2sd did not see it. u can try it though but i recommend unbuntu let me know what happens
Click to expand...
Click to collapse
so I got it all running, partitioned with ext3, it seems to be working but it didn't push any of my existing apps over to the SD card, do you know if there's a script to do this? Or do I have to uninstall each and reinstall them? (tested that way and they seem to go to the SD card then)

kittcoldfire said:
so I got it all running, partitioned with ext3, it seems to be working but it didn't push any of my existing apps over to the SD card, do you know if there's a script to do this? Or do I have to uninstall each and reinstall them? (tested that way and they seem to go to the SD card then)
Click to expand...
Click to collapse
ya uninstall reinstall had to do that too but hey it works

gemini002 said:
ya uninstall reinstall had to do that too but hey it works
Click to expand...
Click to collapse
I had to reinstall everything and i rooted and did everything exactly the same way as i did before, but now for some reason it won't let me install the apps to sd... here's the errors I get
warnning/system/bin/busybox'exists,use -f to overwrite
warnning'/system/lib/modules/ext2.ko'exists,use -f to overwrite insmod: can't insert '/system/lib/modulesext2/ko':File exists
mkdir failed for /system/sd, File exists
mount: mounting /dev/block/mmcblk0p2 on /system/sd failed: device or resource busy
sorry, mount sd ext2 fail!!!!!
what the heck does this mean? how can i fix this?
I partitioned the sd card as... (16gb) 14.something gb fat32, 1gb ext3, 32mb linux swap

kittcoldfire said:
I had to reinstall everything and i rooted and did everything exactly the same way as i did before, but now for some reason it won't let me install the apps to sd... here's the errors I get
warnning/system/bin/busybox'exists,use -f to overwrite
warnning'/system/lib/modules/ext2.ko'exists,use -f to overwrite insmod: can't insert '/system/lib/modulesext2/ko':File exists
mkdir failed for /system/sd, File exists
mount: mounting /dev/block/mmcblk0p2 on /system/sd failed: device or resource busy
sorry, mount sd ext2 fail!!!!!
what the heck does this mean? how can i fix this?
I partitioned the sd card as... (16gb) 14.something gb fat32, 1gb ext3, 32mb linux swap
Click to expand...
Click to collapse
busy box cannot be installed i had this error at first too .well u dont need linux swap so get rid of it what did u use to partion sd card i use unbuntu all other partioned card but it would not work only worked when i used unbuntu .unroot download open recovery 1.05(google it)root with open recovery and try again

gemini002 said:
busy box cannot be installed i had this error at first too .well u dont need linux swap so get rid of it what did u use to partion sd card i use unbuntu all other partioned card but it would not work only worked when i used unbuntu .unroot download open recovery 1.05(google it)root with open recovery and try again
Click to expand...
Click to collapse
yeah it's okay, this morning I sat down with it and put on my programming hat and went through the script and modified it enough to make it fix all the errors I was getting, so I've got it all done, nice 144mb of free space on the phone, and back to overclocked, and everything is running nice and smooth!!

glad u got it working ...im I right about busybox causing the errors?

did u hear the bootloader has been cracked

nevermind - got it working, just had to ensure the partition is made the correct way in Ubuntu!

Hi apps2sd v1 is kinda old news and was much more complicated then that , are you sure your guide is complete for someone who hasnt done all that was needed to be done in previous version ?
Also I never applied this mod because I was wondering why there was a need for it .. with the 'davlik mem cache hack' I have tons of applications & widget installed , much more then I need in fact so yea you guys notice if the phone is faster or anything else after usin apps2sd ?
gemini002 said:
did u hear the bootloader has been cracked
Click to expand...
Click to collapse
it s not , or I guess it all depends on what you call cracked , whatever has been done to it is useless for us practically speaking , truth is we are in fact very close ( talking of a few weeks maximum a the speed its currently going )to running 'roms' on our stone !!!

DAGr8 said:
Hi apps2sd v1 is kinda old news and was much more complicated then that , are you sure your guide is complete for someone who hasnt done all that was needed to be done in previous version ?
Also I never applied this mod because I was wondering why there was a need for it .. with the 'davlik mem cache hack' I have tons of applications & widget installed , much more then I need in fact so yea you guys notice if the phone is faster or anything else after usin apps2sd ?
it s not , or I guess it all depends on what you call cracked , whatever has been done to it is useless for us practically speaking , truth is we are in fact very close ( talking of a few weeks maximum a the speed its currently going )to running 'roms' on our stone !!!
Click to expand...
Click to collapse
it's faster with overclock module 4 sure plus i have tons of apps
the guide is straight forward just make sure u use unbuntu to partition
true but now no siginature is needed so custom roms on the way froyo was ported on sat to droid so we should get it in a few week heck maybe this week it is something worth doing now that we don't need no bootloader

DAGr8 said:
Hi apps2sd v1 is kinda old news and was much more complicated then that , are you sure your guide is complete for someone who hasn't done all that was needed to be done in previous version ?
Click to expand...
Click to collapse
it is complete and works well, from what I can gather its just a script of the previous apps2sd so makes life a lot easier (with some obvious tweaks)
One part about it I do not like and am looking into how to change it is it goes and installs a heap of Telus libs/files in the OS as well as the UMTS/GSM files - nice to be able to do both Milestones at once, but a bit sloppy....time to tweak....
Just make sure the card is partitioned in a card reader and not via the phone in Ubuntu (its NOT unbuntu!!..lol) and there is no need for a swap partition.
And if you are not using gparted but the included 'disk utility' in Lucid, make sure you untick the 'Take Ownership' check box otherwise it will partition it for super user access only!
Took me 3 goes to get it done right but that was the only method of partitioning that would work for me with no errors
The only speed increase has been thanks to the Overclock module, just nice to see 140mb still free on the phone after installing many many apps - better than the 10mb I used to have free

gemini002 said:
true but now no siginature is needed so custom roms on the way froyo was ported on sat to droid so we should get it in a few week heck maybe this week it is something worth doing now that we don't need no bootloader
Click to expand...
Click to collapse
Sorry dont get your hopes up but you are Wrong ... plain wrong
its not cracked
signature still needed
and Kexec aint workin yet either ..
Our best hope for custom roms is Kexec and it will most likely be up and runnin within a month ( fingers crossed )
This Forum is a great (1 of the best ) forum so unless you are able to boot something without signature by yourself please dont spread false information as others might think because it has been posted here its true .

ya i know the bad news

So App2SD will not be listed under Settings->Applications?
When i do ls -l /data, what should i expect to see if it works? If it didnt work?

mischief4l said:
So App2SD will not be listed under Settings->Applications?
When i do ls -l /data, what should i expect to see if it works? If it didnt work?
Click to expand...
Click to collapse
I'm going to guess you will get a list of apps that would be in the /data part of your sd card. Assuming that you have correctly installed for the lack of a better word App2SD...
~PsyCl0ne

uhm....help? lol
kittcoldfire said:
yeah it's okay, this morning I sat down with it and put on my programming hat and went through the script and modified it enough to make it fix all the errors I was getting, so I've got it all done, nice 144mb of free space on the phone, and back to overclocked, and everything is running nice and smooth!!
Click to expand...
Click to collapse
I had the same error as you did earlier about the 'sorry, mount sd ext2 fail!!!!!' issue. I'm not a programmer, but can you please detail how'd you get around this problem? I use Windows 7, and have the milestone plugged in on 'charge only'. Am I missing a step here?
Please advise what the heck I'm doing wrong here and thanks. :]
Az

[Q]Supersu issue, re-rooting and other questions

Hey, I got a Virgin Mobile HTC Desire 510. Y'know, the blue one....
I fudged up severely the other evening and installed another rom which bricked my phone. I did manage however restore a stock back-up I managed to find online, however the phone was still rooted, tampered and TWMP(did I get the abbreviation correct?) is still on it. So I go and install Supersu and Busybox in an attempt to go back to where I left off as I've been attempting to get the phone to do the internal to SD card bit but no success thus far, especially not right now. In anycase, after reinstalling Supersu, I load it up and get the message of "There is no SU binary installed and SuperSU cannot install it. This is a problem! If you just upraded to Android 4.3, you need to manually re-root. consult the relevant forums for your device.". I attempted to reinstall threw recovery and it seems to be working till I get the actual phone's Google ROM running and click on the SuperSU program only to get that message.
Any suggestions or advice on how to do this and get SuperSU back up? How do I exactly re-root or can I somehow install the binary via PC or flash?
Can the HTC Desire 510(Virgin Mobile version) even have the the script/rom/trick setting to have the SD Card used as Internal memory or is this quest just wasted time?
Thanks
EDIT- Device version is 0PCV1

Okkvltist said:
Hey, I got a Virgin Mobile HTC Desire 510. Y'know, the blue one....
I fudged up severely the other evening and installed another rom which bricked my phone. I did manage however restore a stock back-up I managed to find online, however the phone was still rooted, tampered and TWMP(did I get the abbreviation correct?) is still on it. So I go and install Supersu and Busybox in an attempt to go back to where I left off as I've been attempting to get the phone to do the internal to SD card bit but no success thus far, especially not right now. In anycase, after reinstalling Supersu, I load it up and get the message of "There is no SU binary installed and SuperSU cannot install it. This is a problem! If you just upraded to Android 4.3, you need to manually re-root. consult the relevant forums for your device.". I attempted to reinstall threw recovery and it seems to be working till I get the actual phone's Google ROM running and click on the SuperSU program only to get that message.
Any suggestions or advice on how to do this and get SuperSU back up? How do I exactly re-root or can I somehow install the binary via PC or flash?
Can the HTC Desire 510(Virgin Mobile version) even have the the script/rom/trick setting to have the SD Card used as Internal memory or is this quest just wasted time?
Thanks
EDIT- Device version is 0PCV1
Click to expand...
Click to collapse
Hello and welcome to xda,
Where exactly did you get the back-up from that you used to restore?
You were close it is TWRP or Team Win Recovery Project.
I believe the reason you can't install SuperSU is because you don't have a write protect removed kernel installed. You can find one here. Check out their related forums and see which one you like best. They are pretty much all great. Some aren't being supported anymore as a heads up. To flash a kernel, in case you didn't know how:
Go into Settings-About-Software information-More-Kernel version and write down the name of the Kernel
1. Power the phone down
2. Hold "Down" button then hold "Power" key while still holding "Down" button, until you get into the bootloader
3. Release "Down" and "Power" button
4. Tap "Power" key once and it will change from "HBOOT" in white letters with blue background to "FASTBOOT" in white letters with red background on your phone
5. Connect your USB cable and it will say "FASTBOOT USB" on your phone
6. Navigate to the folder you have your fastboot.exe from Android Studio or wherever you obtained it from (Mine is in C:\Users\myusername\Android\sdk\platform-tools)
7. Hold the "Shift" key then right click in any empty space in that folder
8. Select "Open command window here"
9. Type
Code:
fastboot devices
in the command window, then press Enter just to make sure it is picking up your phone
10. You should see something like:
Code:
HT42PXU89475 fastboot
if you don't make sure your USB cable is inserted all the way and you are in "FASTBOOT USB"
11. Make sure your recovery.img or whatever the name of the recovery is, is in the folder you are currently in
11. Type
Code:
fastboot flash boot boot.img
in the command window
You should see something like:
Code:
C:\Users\yourusername\Android\sdk\platform-tools>fastboot flash boot boot.img
sending 'boot' (12932 KB)...
OKAY [ 1.350s]
writing 'boot'...
OKAY [ 1.030s]
finished. total time: 2.385s
Your phone will still be in FASTBOOT USB mode
To test it out to see it was correctly flashed, reboot the phone
Go into Settings-About-Software information-More-Kernel version and see that the version changed
You can follow my little guide to use SD as Internal memory. Let me know if you need any help.

I won't be able to get to this til tomorrow but another issue is I can't d/l apps off Google play. It comes up with some server issue and some weird code that starts with an R. Sorry I can't give full details as I'm at work :/.

Okkvltist said:
I won't be able to get to this til tomorrow but another issue is I can't d/l apps off Google play. It comes up with some server issue and some weird code that starts with an R. Sorry I can't give full details as I'm at work :/.
Click to expand...
Click to collapse
Is your phone completely stock or do you have any custom ROMs? I have seen errors like that.

blaqueknight said:
Is your phone completely stock or do you have any custom ROMs? I have seen errors like that.
Click to expand...
Click to collapse
I'm fairly certain I reinstalled Busybox when I was installing(or trying to) Supersu. I'm giving the kernel bit a shot.
Oh the stock back-up is this(No, I didn't back up my phone since I didn't see a reason, I had everything I needed on the computer/sd) file:
http//qc-.androidfilehost-com/dl/PObYV5uN55P2PGDNrX1pLQ/1430391523/95832962473396445/2014-12-02--16-24-34+KOT49H+Stock.not.rooted.rar
(can't post links since i'm a newb)
Had to make a backup of my empty phone and put the files into the empty back up to restore it.
UPDATE- Flashed over Modded Kernel V2.6.1 since that looked like a safe bet. Installed correctly. Tried to reinstall Supersu. Got "Android is upgrading". Supersu Installed. Next is the SD Card bit.

Okkvltist said:
I'm fairly certain I reinstalled Busybox when I was installing(or trying to) Supersu. I'm giving the kernel bit a shot.
Oh the stock back-up is this(No, I didn't back up my phone since I didn't see a reason, I had everything I needed on the computer/sd) file:
http//qc-.androidfilehost-com/dl/PObYV5uN55P2PGDNrX1pLQ/1430391523/95832962473396445/2014-12-02--16-24-34+KOT49H+Stock.not.rooted.rar
(can't post links since i'm a newb)
Had to make a backup of my empty phone and put the files into the empty back up to restore it.
Click to expand...
Click to collapse
I'm sorry, please disregard that last comment. I was posting like your only problem was the Play Store. lol Sorry. But yea, check out those things I mentioned to you and you should be able to get SuperSU back up, if not I'll help you with anything else.

Okkvltist said:
I'm fairly certain I reinstalled Busybox when I was installing(or trying to) Supersu. I'm giving the kernel bit a shot.
Oh the stock back-up is this(No, I didn't back up my phone since I didn't see a reason, I had everything I needed on the computer/sd) file:
http//qc-.androidfilehost-com/dl/PObYV5uN55P2PGDNrX1pLQ/1430391523/95832962473396445/2014-12-02--16-24-34+KOT49H+Stock.not.rooted.rar
(can't post links since i'm a newb)
Had to make a backup of my empty phone and put the files into the empty back up to restore it.
UPDATE- Flashed over Modded Kernel V2.6.1 since that looked like a safe bet. Installed correctly. Tried to reinstall Supersu. Got "Android is upgrading". Supersu Installed. Next is the SD Card bit.
Click to expand...
Click to collapse
UPDATE 2- When partioning the sd card, it continues to come up as ext2. When I go into Link2SD and I go to select I get the message on whatever I select- "Mount script cannot be created. mount: invalid argument"

Okkvltist said:
UPDATE 2- When partioning the sd card, it continues to come up as ext2. When I go into Link2SD and I go to select I get the message on whatever I select- "Mount script cannot be created. mount: invalid argument"
Click to expand...
Click to collapse
Are you using Aparted? What was the method you used to partition? You should partition as ext4.

Yeah, I downloaded Aparted, went in to partition the SD card("8" gigs) and selected ext4 but it comes out ext2. Do I need S-OFF and/or 4EXT Recovery?

Okkvltist said:
Yeah, I downloaded Aparted, went in to partition the SD card("8" gigs) and selected ext4 but it comes out ext2. Do I need S-OFF and/or 4EXT Recovery?
Click to expand...
Click to collapse
Did you select Create then Format? If it still comes out ext2 after that, I don't know what the problem is. Format will take a while because it is creating journals.

blaqueknight said:
Did you select Create then Format? If it still comes out ext2 after that, I don't know what the problem is. Format will take a while because it is creating journals.
Click to expand...
Click to collapse
It's saying the partition doesn't exist when I go to format after creating the partition. Even when creating the proper ext from the create screen, it still doesn't come up as ext4.
other info
device- /dev/block/mmcblk1.
when I opened up link2sd its asking me for mmcblk1p2 but there is no mmcblk1p2

Okkvltist said:
It's saying the partition doesn't exist when I go to format after creating the partition. Even when creating the proper ext from the create screen, it still doesn't come up as ext4.
other info
device- /dev/block/mmcblk1.
when I opened up link2sd its asking me for mmcblk1p2 but there is no mmcblk1p2
Click to expand...
Click to collapse
Are you trying to partition the whole SDcard as ext4? To properly partition the card to be used with Link2SD you have to:
1. Delete the sdcard
2. Create a FAT32 partition of any size of your choosing
3. Format the FAT32 partition
4. Create an ext4 partition of any size of your choosing
5. Format the ext4 partition (this will take a long time, as it will create journals that are used to recover from an error such as removing the device while files are being copied)
After following those steps, Link2SD should properly create the script/mount and you should be able to link to your sdcard
If you are doing those steps perfectly and you still have an error, we have to find out another solution

Ok, I still can't get it to make Ext4......
However, weirdness- I made a Fat32 Partition and went into Link2SD. Link2SD was able to use/read the Fat32 partition. Tried to create/change the Fat32 and it didn't work. Tried to make a third partition under ext4 and it comes up ext2. Openned Link2SD and it doesn't read/use the ext2. Uses the additional Fat32 no sweat. I don't know how much of it is working(tried downloading Brave Frontier and had to delete loads of stuff in general) usual memory bull**** ensures and I see theres a lock for the full copy of Link2SD....
another thing; I can't get into/mount the open part of my SD card. Should I go back to square one or should I blow the meager 3 bucks for the full copy and see if I can do it from there?
PS- Does the class of the sd decide on if I can partition an ext3-4? Cause if so, mine is only a class 4 SD card.

Okkvltist said:
Ok, I still can't get it to make Ext4......
However, weirdness- I made a Fat32 Partition and went into Link2SD. Link2SD was able to use/read the Fat32 partition. Tried to create/change the Fat32 and it didn't work. Tried to make a third partition under ext4 and it comes up ext2. Openned Link2SD and it doesn't read/use the ext2. Uses the additional Fat32 no sweat. I don't know how much of it is working(tried downloading Brave Frontier and had to delete loads of stuff in general) usual memory bull**** ensures and I see theres a lock for the full copy of Link2SD....
another thing; I can't get into/mount the open part of my SD card. Should I go back to square one or should I blow the meager 3 bucks for the full copy and see if I can do it from there?
PS- Does the class of the sd decide on if I can partition an ext3-4? Cause if so, mine is only a class 4 SD card.
Click to expand...
Click to collapse
I just made a couple of very simple tutorials to use Aparted and Link2SD and they are both working for me. Check them out: Aparted tutorial, Link2SD tutorial. I believe the ext2 that you are talking about is around the 10 second mark in the Link2SD video. Do you mean the /data/sdext2? That is just the name of the second sdcard partition.
If you can, you should buy the full copy of Link2SD to link external data and whatever other options become available.
The class of sdcard shouldn't have anything to do with the partition. That's just a classification of the speed of the card.
If needed, I'll make more videos to show exactly how everything is done. I think sometimes it is better to show than simply explain how something is done.
Hope this helps.

Wow.......I mean seriously, holy zen, it worked.
I had to start over from scratch since my f'ling screwed so much crap up but after everything was reinstalled and flashed and what not, It made the ext4. I don't know why the programming is so touchy you have to create it threw such weird steps but I believe it worked. Upgraded the link2sd. Next question and I'm pretty sure on the answer- Are you able to remove the SD card or is it perma-bound to the phone(IE- if I change SD cards around, will everything crash?)? Thank you so much

Okkvltist said:
Wow.......I mean seriously, holy zen, it worked.
I had to start over from scratch since my f'ling screwed so much crap up but after everything was reinstalled and flashed and what not, It made the ext4. I don't know why the programming is so touchy you have to create it threw such weird steps but I believe it worked. Upgraded the link2sd. Next question and I'm pretty sure on the answer- Are you able to remove the SD card or is it perma-bound to the phone(IE- if I change SD cards around, will everything crash?)? Thank you so much
Click to expand...
Click to collapse
I'm happy it worked out good for you.
Yes, you are able to remove your sdcard. Be aware that your apps are on your sdcard so if you remove it, you remove them. They are placed on your sdcard and symlinked so Android thinks they are still on your phone in the place they would normally be. Nothing should crash, they just shouldn't show up. There is some great info about Link2SD here.

@blaqueknight..
nice videos man.