Samsung Galaxy S Boot Loop / Dead Internal SD - Solution - Galaxy S I9000 General

Fully working Samsung Galaxy S - Using 16GB External Micro SD to run OS and function as External SD!!
Ok so to set the scene I will quickly explain the issue I had with my Samasung Galaxy S.
One day it worked....
Next day it didn't...from then on it would only boot to first screen then continually repeat this step.....
After day two of having no luck at fixing the issue I got an S3...great phone!
BUT DONT GIVE UP JUST YET! It can be fixed!!!
Overall I think I would have spent somewhere in the ballpark of about 40 hours trying to fix the Galaxy S...stubborn? Yes....and my Galaxy S was such a good phone I hated the idea of binning it.
I wont waste your time listing the hundreds of methods I tried or posts I read, but in the end all things pointed to a dead internal SD.
I should be able to run the OS off an external SD... shouldn't I? The answer is Yes!
Many hours were spent on this stage and for about a week I had a working pone with OS running on External SD, but no access to the camera or anything which required an external SD.
I now have a perfectly working phone, using a 16gb External SD to run the OS and remaining space on it recognised as the external SD.
I can't promise this will work for everyone but here is the last of WAY TO MANY methods I used which completely solved this problem for me.
Let me know if this works for you & GOOD LUCK!
Step 1:
Your phone must be rooted!
The best, easiest and only way I was able to do it is with the following guide, big thank you to the person who put it up. As my Internal SD was dead! my external SD was to be my new internal SD...so the standard add to zip method for rooting on external SD... would obviously not work for me! yes I worded that perfectly!
BIG IMPORTANT NOTE IN CAPITAL LETTERS! - Make sure you have your external SD inserted during the below process!
http://forum.xda-developers.com/showthread.php?t=1852546
NOW! You should have your phone booting as it used to back in the good old days! However.....some of you wont...if this is the case please follow Step 1B.
Step 1B:
If the above did not work for you then you need a way to connect your Micro SD to your PC (I did this using a USB adaptor).
1. Download and install EaseUS partition master
2. Insert Micro SD in PC
3. EaseUS partition master
4. Wipe all partitions/data.
5. Create EXT4 partition approx 2gb
6. Create FAT32 partition with remaining space.
7. Remove battery from phone
8. Insert SD, Battery back in.
9. Turn on, you should have your phone booting as it used to back in the good old days!
IF NOT THEN.....Start with Step 1B then do Step1 then if all looking as it should move to step 2. If not...sorry...I have failed you!
Step 2:
You phone should now have booted like the good old days....but if you go into SD/Storage on android OS, you will notice it does not recognise the remaining space on the External SD as an external SD...it must be very confusing for the green robot!
So next steps as follows!
1. Install script manager app and mount r/w app from Google Play (market)
2. Use mount r/w to Mount the system partition in r/w mode.
3. Browse using script manager app as root (change setting in config).
4. Go to /system/etc folder and change file permission for vold.fstab to rwxrwxrwx (This means tick all the 9 boxes on the left not the 3 on the right.....such a technical explanation)
5. Then edit the vold.fstab file as text and change the following
Change:
dev_mount sdcard /mnt/sdcard auto /devices/platform/s3c-sdhci.0/mmc_host/mmc0
to
dev_mount sdcard /mnt/sdcard auto /devices/platform/s3c-sdhci.2/mmc_host/mmc2
Change:
s3c-sdhci.0
to
s3c-sdhci.2
Change:
mmc0
to
mmc2
Save the file and reboot the phone!
If all has gone well then your sdcard partition will be mounted and old faithful is ready to ride once again!
I hope this worked for you, if it didn't...gutted and I guess you have moved onto the next post...good hunting!
Please note this solution was created from a pile of posts I trawled through to get a solution. The above vold.fstab solution was taken from the following post. Unfortunately this posts overall solution didn't work for me, but I would not have been able to mount remaining External SD Space as well...you know THE EXTERNAL SD! without his post, which is the best part!
http://forum.xda-developers.com/showthread.php?t=1193010

Nice work... Lesson to be learned...
Never give up!! lol
Above post should be stickied or kept somewhere, seen quite a few people with the same problem. I'll be bookmarking it in case it ever happens to me... Thanks...
Sent from my GT-I9000 using Tapatalk 2

Cheers
knuckles1978 said:
Nice work... Lesson to be learned...
Never give up!! lol
Above post should be stickied or kept somewhere, seen quite a few people with the same problem. I'll be bookmarking it in case it ever happens to me... Thanks...
Sent from my GT-I9000 using Tapatalk 2
Click to expand...
Click to collapse
Thanks Wasn't sure If should really have posted it as......how to run your Samsung Galaxy S from your external SD lol.

Hi There
Thank you for the comprehensive post.
What should I do if scriptmanager app and mount r/w app can't install? In fact, no apps can install.
Also, should the second line in vold.fstab that used to point to external sd stay the same or be modded as well?
My SGS just will not accept any apps installed or anything copied to it. I have repartitioned the external sd but everything still only picks up the internal SD and nothing from external.
Does the external SD need to be partition as a primary or logical partition for the EXT4 part?

The link to the guide is dead, why have xda removed it? does anybody have a link to the guide that works? thanks

Link works fine here.....
Sent from my GT-I9000 using Tapatalk 2

boot loop
reganstott said:
Fully working Samsung Galaxy S - Using 16GB External Micro SD to run OS and function as External SD!!
Ok so to set the scene I will quickly explain the issue I had with my Samasung Galaxy S.
One day it worked....
Next day it didn't...from then on it would only boot to first screen then continually repeat this step.....
[/url]
Click to expand...
Click to collapse
Tried the above but no joy, my problem below could be slightly different
Bought this from Ebay dead, managed to get it going but it would not recognise internal or external storage, tried to update rom, then disaster, now goes into permanent bootloop Have tried to resurrect the phone with….http://forum.xda-developers.com/showthread.php?t=1647890
and with ezbase, EZRom for Galaxy S.
No go, when use Odin3 1.82 to put rom on it says passed, then goes into recovery and tells me that
1) e: format_volume:rfs format failed on /dev/block/mmcblk0p2
2) Deleting Meta data ….data wipe failed
3) Press reboot says failed to Mount Data File
On Reboot goes to permanent boot loop on Samsung S GT-i9000 screen
Searched and found ref to using a riff box to clear this problem, nobody near me has one
Any ideas to get out of this gratefully received

knuckles1978 said:
Link works fine here.....
Sent from my GT-I9000 using Tapatalk 2
Click to expand...
Click to collapse
so I assume you have to have a booting phone for this to work?
---------- Post added at 03:28 PM ---------- Previous post was at 03:20 PM ----------
bryfly said:
Tried the above but no joy, my problem below could be slightly different
Bought this from Ebay dead, managed to get it going but it would not recognise internal or external storage, tried to update rom, then disaster, now goes into permanent bootloop Have tried to resurrect the phone with….http://forum.xda-developers.com/showthread.php?t=1647890
and with ezbase, EZRom for Galaxy S.
No go, when use Odin3 1.82 to put rom on it says passed, then goes into recovery and tells me that
1) e: format_volume:rfs format failed on /dev/block/mmcblk0p2
2) Deleting Meta data ….data wipe failed
3) Press reboot says failed to Mount Data File
On Reboot goes to permanent boot loop on Samsung S GT-i9000 screen
Searched and found ref to using a riff box to clear this problem, nobody near me has one
Any ideas to get out of this gratefully received
Click to expand...
Click to collapse
Ok I think im getting the picture but the guide is not clear, i think 1 partiotion should be ext4 the other fat 32 both primary, if you cannot boot because of the loop do you need a modified kernel ? will the phone then auto mount the external sd and use that instead?

swukjay said:
so I assume you have to have a booting phone for this to work?
---------- Post added at 03:28 PM ---------- Previous post was at 03:20 PM ----------
Ok I think im getting the picture but the guide is not clear, i think 1 partiotion should be ext4 the other fat 32 both primary, if you cannot boot because of the loop do you need a modified kernel ? will the phone then auto mount the external sd and use that instead?
Click to expand...
Click to collapse
Thanks for the reply, have advanced since my post, managed to get into CWM and deleted / formatted everything I could see, then went back to install GB through odin3 and it accepted and is now running with that..........Still left with my original problem that stops me install JB or ICS, in settings, then "SD card an phone storage" SD Card= total space and available space, unavailable and usb storage = total space and available space, unavailable, if I hit format usb storage I get sd card has been removed ........Any suggestions what to try??

bryfly said:
Thanks for the reply, have advanced since my post, managed to get into CWM and deleted / formatted everything I could see, then went back to install GB through odin3 and it accepted and is now running with that..........Still left with my original problem that stops me install JB or ICS, in settings, then "SD card an phone storage" SD Card= total space and available space, unavailable and usb storage = total space and available space, unavailable, if I hit format usb storage I get sd card has been removed ........Any suggestions what to try??
Click to expand...
Click to collapse
I think this
http://forum.xda-developers.com/showthread.php?t=1193010 may help you , apparently you have to change some script with root explorer, my problem is exactly the same as your but still have boot loop, what procedure did you use to get your to boot? did you partition memory card?

swukjay said:
I think this
http://forum.xda-developers.com/showthread.php?t=1193010 may help you , apparently you have to change some script with root explorer, my problem is exactly the sane as your but kust have boot loop, what procedure did you use to get your to boot?
Click to expand...
Click to collapse
managed to install cwm, then wiped everything I could, then installed a stock GB rom through odin3 and it went fine, so guessing I had something corrupted and then cwm formats deleted it, maybe I was lucky , but that is all I did, thanks for the link re sd cards.....

use external sd card with CM10
Hey there,
I have had exactly the same issue and it took my days to figure out that my internal sd card must be broken.
Thanks for the great idea of switching the sd cards, my SGS I9000 works again.
Using my gained enthusiasm I tried to flash the newest 10.1 CM firmware. The installer stops within CWM before rebooting and tells me that the package is defect. I tried it several times, even using sideload. What do I have to do to install it?
Best regards
marco

gt i9000
reganstott said:
Fully working Samsung Galaxy S - Using 16GB External Micro SD to run OS and function as External SD!!
Ok so to set the scene I will quickly explain the issue I had with my Samasung Galaxy S.
One day it worked....
Next day it didn't...from then on it would only boot to first screen then continually repeat this step.....
After day two of having no luck at fixing the issue I got an S3...great phone!
BUT DONT GIVE UP JUST YET! It can be fixed!!!
Overall I think I would have spent somewhere in the ballpark of about 40 hours trying to fix the Galaxy S...stubborn? Yes....and my Galaxy S was such a good phone I hated the idea of binning it.
I wont waste your time listing the hundreds of methods I tried or posts I read, but in the end all things pointed to a dead internal SD.
I should be able to run the OS off an external SD... shouldn't I? The answer is Yes!
Many hours were spent on this stage and for about a week I had a working pone with OS running on External SD, but no access to the camera or anything which required an external SD.
I now have a perfectly working phone, using a 16gb External SD to run the OS and remaining space on it recognised as the external SD.
I can't promise this will work for everyone but here is the last of WAY TO MANY methods I used which completely solved this problem for me.
Let me know if this works for you & GOOD LUCK!
Step 1:
Your phone must be rooted!
The best, easiest and only way I was able to do it is with the following guide, big thank you to the person who put it up. As my Internal SD was dead! my external SD was to be my new internal SD...so the standard add to zip method for rooting on external SD... would obviously not work for me! yes I worded that perfectly!
BIG IMPORTANT NOTE IN CAPITAL LETTERS! - Make sure you have your external SD inserted during the below process!
http://forum.xda-developers.com/showthread.php?t=1852546
NOW! You should have your phone booting as it used to back in the good old days! However.....some of you wont...if this is the case please follow Step 1B.
Step 1B:
If the above did not work for you then you need a way to connect your Micro SD to your PC (I did this using a USB adaptor).
1. Download and install EaseUS partition master
2. Insert Micro SD in PC
3. EaseUS partition master
4. Wipe all partitions/data.
5. Create EXT4 partition approx 2gb
6. Create FAT32 partition with remaining space.
7. Remove battery from phone
8. Insert SD, Battery back in.
9. Turn on, you should have your phone booting as it used to back in the good old days!
IF NOT THEN.....Start with Step 1B then do Step1 then if all looking as it should move to step 2. If not...sorry...I have failed you!
Step 2:
You phone should now have booted like the good old days....but if you go into SD/Storage on android OS, you will notice it does not recognise the remaining space on the External SD as an external SD...it must be very confusing for the green robot!
So next steps as follows!
1. Install script manager app and mount r/w app from Google Play (market)
2. Use mount r/w to Mount the system partition in r/w mode.
3. Browse using script manager app as root (change setting in config).
4. Go to /system/etc folder and change file permission for vold.fstab to rwxrwxrwx (This means tick all the 9 boxes on the left not the 3 on the right.....such a technical explanation)
5. Then edit the vold.fstab file as text and change the following
Change:
dev_mount sdcard /mnt/sdcard auto /devices/platform/s3c-sdhci.0/mmc_host/mmc0
to
dev_mount sdcard /mnt/sdcard auto /devices/platform/s3c-sdhci.2/mmc_host/mmc2
Change:
s3c-sdhci.0
to
s3c-sdhci.2
Change:
mmc0
to
mmc2
Save the file and reboot the phone!
If all has gone well then your sdcard partition will be mounted and old faithful is ready to ride once again!
I hope this worked for you, if it didn't...gutted and I guess you have moved onto the next post...good hunting!
Please note this solution was created from a pile of posts I trawled through to get a solution. The above vold.fstab solution was taken from the following post. Unfortunately this posts overall solution didn't work for me, but I would not have been able to mount remaining External SD Space as well...you know THE EXTERNAL SD! without his post, which is the best part!
http://forum.xda-developers.com/showthread.php?t=1193010
Click to expand...
Click to collapse
im having a little trouble with step 2,
1. Install script manager app and mount r/w app from Google Play (market)------------- done
2. Use mount r/w to Mount the system partition in r/w mode. --------done, then clicked back arrow to do next step
3. Browse using script manager app as root (change setting in config). --------done
4. Go to /system/etc folder and change file permission for vold.fstab to rwxrwxrwx (This means tick all the 9 boxes on the left not the 3 on the right.....such a technical explanation)--------not sure about this step, i think I have done it, but then I cant find the next step
5. Then edit the vold.fstab file as text and change the following
any help would be much appreciated
Regards Mick

E:failed to mount ?sdcard (file exists)
I have figured out the vold.fstab file, but it wont save the changes, what have I done wrong

Please help me
reganstott said:
Fully working Samsung Galaxy S - Using 16GB External Micro SD to run OS and function as External SD!!
Ok so to set the scene I will quickly explain the issue I had with my Samasung Galaxy S.
One day it worked....
Next day it didn't...from then on it would only boot to first screen then continually repeat this step.....
After day two of having no luck at fixing the issue I got an S3...great phone!
BUT DONT GIVE UP JUST YET! It can be fixed!!!
Overall I think I would have spent somewhere in the ballpark of about 40 hours trying to fix the Galaxy S...stubborn? Yes....and my Galaxy S was such a good phone I hated the idea of binning it.
I wont waste your time listing the hundreds of methods I tried or posts I read, but in the end all things pointed to a dead internal SD.
....
Click to expand...
Click to collapse
Hi reganstott i have similar problem but a little different. my galaxy i9000 stuck in boot loop too but the difference is that my phone do not enter into recovery mode and has boot loop even in download mod. therefore i can install no rom's. Do you know what is the exact problem of my phone? i try your solution but step 1A can't be done because my phone continue boot loop even in download mode. please help me

bewildered
I have flashed the phone back to stock, but it wont do anything, still cant get to the internal sd/card, please help, i desperately need to extract the photos off the internal sd/card

more thzs

Bump on
I tested the procedure 3 times, worked all the time, but when I checked on the 'SD card and phone storage' on the 'Settings', still SD card is not recognized, but I got now USB Storage, so I could use the camera now.
Although the real problem of corrupt internal SD card is not yet solved, it is a solution.
Thank you very much, your persisteness.
:good::good::good:

thanks a lot !!
thanks a lot only thing is I am able to mount SD card so camera and no extra memory

wow
very god

Related

[HOWTO] WORKAROUND for BELL i9000m Internal SD Card Failure!!!!!

Hello Everyone,
I like most people upgraded my Bell i9000m from Kies to Froyo, only to have it bricked with the "can't mount /dev/block/mmcblk0" error at the recovery screen during boot-up. I upgraded it last week, where it took the firmware from JL8 to I believe JK3 or JL8 (not sure at this point).
Unfortunately I bought my phone from some guy on Kijiji using it on Rogers, so I doubt Bell is going to handle the return or give me any love
Anyways, I spent many days long days trying to get it back working, and I found a work-around that requires using an external SD card. and going back to Android 2.1 ECLAIR
Steps (This is what I did):
1. Install JK3 stock ROM via Odin (with re-partition at the pit on samfirmware.com, didn't update boot loader)
2. Install K13c speedmod kernel via Odin
3. Insert 16GB External SD card
3. Boot phone to Froyo
4. Reboot to recovery console and wipe data/everything
5. Install JL8 stock ROM via Odin (no re-partition, didn't update boot loader)
6. Phone will boot-up into recovery mode and automatically do wipe data
7. Phone will boot into ECLAIR
8. You will see internal storage of 1.85GB free.
9. Install Market apps - I installed twitter
10. If you remove external SD card, twitter will crash.
11. If you reboot phone without external SD card, you will get rebooting logo
12. If you put external SD card back it, phone boots!
This wasn't a fluke - I was able to reproduce if I flashed other ROMS (XXJPY or similar) instead of JK3.
Background:
Even though the phone can't boot with stock ROM, if I install JK3 ROM + speedmod K13b speedmod kernel, I can get the phone to boot to Froyo, but there is no internal storage (it shows up as 0 bytes available). So you can't install Market apps, and therefore is useless. I can't even mount the external SD card under the Settings app!
So I tried to log in the Froyo device using adb shell, and what I found is that internal SD card is no longer showing up under linux, and the OS thinks that the external SD card is the internal one. This is probably why the external SD card can no longer be mounted.
I figured out that the external SD card shows up as /dev/block/mmcblk0!!! WHich is the same block device as the internal SD card...so I'm thinking if I reboot into recovery and format SD card, how come it's not working? I even tried to partition the external SD card with android partitions, but still nothing!
I think Froyo is 'smarter' in that it knows the external SD card is not internal (whether it's grepping the device-info for manufacture data, don't know).
But if I go to JL8 Eclair, the Android 2.1 is 'dumb' enough that is doesn't see the difference between internal and external, so formats the external to look like internal.
Once I boot to ECLAIR, the external SD card is greyed out under Settings app, but I get 1.85GB internal storage!! OK I can't access the whole 16GB of the card, but at least my phone is not toast.
I can go ahead an install apps, which will install to the external SD card. But if you remove the external SD card, the phone will no longer boot. If I remove the card and apps are running, apps will crash (case in point: I tried twitter).
It will be nice if others can re-produce my findings. But for now my Samsung Galaxy S has been saved!
Kashif Shaikh
this sounds promising, can some more people confirm this solution to use External SD to imitate internal SD?
It worked for me as well! I have i9000M version, with internal SD failure. I'm also using 8GB external microSD card. I tried several 2.2 Android firmwares - specifically I9000XXJPY, I9000XXJPU. With update to speedmod-kernel I'm able to load device, but it doesn't see neither internal nor external SD card. So I couldn't install any applications, upload data or even shot with camera.
Based on this thread, on top of XXJPY with speedmod kernel I uploaded I9000XWJM8 firmware (Android 2.1) with Odin 1.7, no repartitioning. It worked right away - device loaded and I can see ~2GB of program storage (assume they storage is located on my external card). Both internal and external cards are shown as "Not available" in settings. I can install applications now, which made "brick" a bit better then it was before. Unfortunately, I still can't upload any data, i.e. a book for FB2Reader. And can't make a photo with my camera. And it's now Android 2.1, which looks slower.
First of all - thanks for the advice! It would be good to have this topic "sticked" and distributed - there might be other guys with no chance to repair phone under warranty.
Secondly - if someone can do a "hack" for Android 2.2 firmware so it can use external SD card for program storage specifically for I9000M device? And it would be terrific, if the remaining part of SD card (or at least some fixed size, like 4 GB) can be mounted as storage, so the data like music or photo or books can be uploaded.
I'm able to connect to the phone using adb tool, but I can't find a folder on the device where I can upload (push) a file to. I'd like to upload a book to the device so I can finally use it as a reader. I tried all "root" folders (adb shell -> ls) and all don't work. It says "No such file or directory" or "Permission denied".
Is there a folder on the device which I can push file to using adb tool? Maybe somewhere where applications are installed to, i.e. Program Storage location. Please help!
Anyone else following this thread with I9000M with internal card dead?
This isn't much of a fix. This will only work with phones with slightly corrupted (and not fully corrupt) sdcards; eventually your phone will probably stop booting with this "fix" as well. You're going to eventually loose some of the other partitions such as stl10 to corruption, and then you're screwed.
The OP's phone is corrupt in a specific way that allows this - and there are various procedures that will get your phone to a semi-bootable state if you only have a partially dead sdcard. Like the OP said - just installing speedmod kernel with an external SD in will allow your phone to boot, for example (I got my dead sd i9000m to boot froyo with the speedmod kernel, and others had reported the same as well). Then if you're technical enough you can switch around your mount configs and get it to work without the internal mmc device.
It doesn't matter if you bought your phone off kijiji or craigslist 2nd hand; send it back to samsung (or go thru futuretel or a similar provider). No receipt is going to be required (if they ask... just say you can't find it). Products like this will always be repaired under warranty based on manufacture date code.
Send your phone back; don't try to fix it - it's a hardware problem with the mmc connection.
Unfortunately, I'm 10 thousand miles away from Canada with no chance getting there. If I had option to send it back for repair I would do it right away. So I'm searhing an option to use this semi-brick as much as possible.
My i9000M phone has totally corrupted internal SD card - it failed two months ago and I tried all options for it reformatting / remounting / whatever. With speedmod kernel it loads even without external sd card. It just allows loading without internal storage - not use external card to mimic internal. Unfortunately, it doesn't see any storage then - no internal, no program, no external card. So it just loads.
With Android 2.1 and external card it loads _and_ see 2GB of program storage (on external card). It doesn't see any other storage - so I can't upload any file. But at least I can install applications.
I'll try this solution after buy a Microsd card. My i9000M internal sdcard dead in two days ago after fixlag use ext2 partitions.
hi all. i didn't find JL8 stock ROM for sumfireware.com.where can find it ?
i flash my phone step by step as top post.
but after flash 2.1 rom with insert SD card , my Phone still cannot boot into ECLAIR .
who can help me? thanks. my phone can boot to 2.2 system without internal card.
SHINE.YANG said:
hi all. i didn't find JL8 stock ROM for sumfireware.com.where can find it ?
i flash my phone step by step as top post.
but after flash 2.1 rom with insert SD card , my Phone still cannot boot into ECLAIR .
who can help me? thanks. my phone can boot to 2.2 system without internal card.
Click to expand...
Click to collapse
Samsung or bell can help you. Send your phone in for repair....
for same reason .i cannot send my phone to bell. so i very want to know find JL8 rom to let me phone canbe use . please help.
HI guys . thanks for your help.
actually ,every I9000 2.1 rom CAN use this solution. just need your external SD same as your phone internal SD size. if you are 8G internal SD , you must use 8G external SD card with 2.1 ROM . you can get 1.85G system space.
I've just tried XWJVB firmware - stock Android 2.3.3 - and it also works! Phone loads without flashing custom kernel.
I wonder, if there is a way to upload any file to the phone - so I can put there a book and read it.
does this mean this workaround still can't recover the files that were originally in my internal sd?
Nope. the internal sd is gone, probably forever.
workaround allows running the phone and having 2GB out of microsd card available for programs storage. it allows downloading and installing application from app market. still, you don't have other storage - can't upload a file or even make a photo with camera.
very wierd. if anyone would suggest a workaround to upload file to the device - even using any hacked way, like from abd or whatever
I flashed custom Kernel (CF-Root-XW_XEE_JVB-v3.1-CWM3RFS) over latest JVB. The device is now rooted.
Using adb tool I was able to push fb2 file to device - specifically to dev folder. (adb push file.fb2 /dev). Using Moon Reader I can open and read it! That's terrific after long time of finding a way of doing this.
Unfortunately, Moon reader is the only app that works. FBReader tries to open the book but fails with writing cache to sd card (which is broken).
This is a most useful post, thank you. I get the phone working on 2.2 which is great but I am unable to find the JL8 stock ROM, I locked for it everywhere but could not find it, would someone please indicate where to find it...
raullugo said:
This is a most useful post, thank you. I get the phone working on 2.2 which is great but I am unable to find the JL8 stock ROM, I locked for it everywhere but could not find it, would someone please indicate where to find it...
Click to expand...
Click to collapse
Why would you need old stock ROM?
Just flashed XXJVP stock ROM to my I9000M. This is Android 2.3.4. Taken from http://forum.xda-developers.com/showthread.php?t=1011901
Flashed CF-Root-XX_OXA_JVP-v3.7-CWM3RFS on top of it for rooting
Phone works
It needed some tricks this time to upload a file to deivce. For some reason all folders appear to be read only, including dev. So I used abd shell command to change folder permissons
adb shell
$ su
# chmod 777 /data
then exit and
adb push file.fb2 /data
File is stored and is not lost on reboot, like it was for dev folder
stuck on step 6..
first of all, this is a great post for those who still stuck with a dead i9000m and no help from Sammy!
Steps (this is how i followed)
1. fine
2. fine
3. fine (i inserted a 16gb Sandisk class 2 in FAT32 format)
3a. i couldn't 'boot to froyo' i'm not sure if you mean fully boot into the OS or not, but it was in a bootloop
4. i was able to get to step 4 somehow to the recovery (3e) and wipe data (there was still the cant mount error when wiping data but no error when wiping cache partition - is that normal?)
5. i cant find JL8 but others here suggested any other 2.1 ROM works so i tried JM8 (no repart/no update bootloader)
6. the phone did do something other than boot loop! (first time wow!) it was trying to copy something but it didn't go all the way through.. there was an error saying 'efs format failed /dev/block/mmcblk0p2' after/during 'coping media files'.
- could it be the wrong format going in (should it be something other than FAT32?)
- could it be that class 2 was not the right class (no fast enough??)
- the copying process stopped after it finished copying media files.. (the micro sd card did have some media files
- there was 2 folders Samsung folder (with media files) and svox (i think that was the name of the folder)
can anyone shed some light on where i did wrong, thanks everyone, love this forum btw.
pavbul said:
Why would you need old stock ROM?
Just flashed XXJVP stock ROM to my I9000M. This is Android 2.3.4. Taken from http://forum.xda-developers.com/showthread.php?t=1011901
Flashed CF-Root-XX_OXA_JVP-v3.7-CWM3RFS on top of it for rooting
Phone works
It needed some tricks this time to upload a file to deivce. For some reason all folders appear to be read only, including dev. So I used abd shell command to change folder permissons
adb shell
$ su
# chmod 777 /data
then exit and
adb push file.fb2 /data
File is stored and is not lost on reboot, like it was for dev folder
Click to expand...
Click to collapse
Thank you for the instructions, tha only reason to look for the jl8 rom is to follow the instructions to the letter. I trying your method right now, thank you for taking the time to give me another shot at my SGS, I will let you know how it goes

[Q] Help with partitioning SD Card

Hello first I want to say a big THANK YOU to everyone that has put time and effort into making the Nookie what it is today....but I have a noob question.
I recently got a 16gb micro SD and can successfully get the 0.6.8 Nookie to run on my nook color, my problems start when I try to "recover" my other 13gb's. Before I get burned and tossed aside I have checked
http://forum.xda-developers.com/showthread.php?t=922324&page=92
http://forum.xda-developers.com/showthread.php?t=883175&highlight=partition&page=103
and about 5 other pages and they all say the same thing..use EASEUS, grab the slide bar and voila. It appears to work but when I install it in the NC it either becomes very unstable or just boots to the NC as if the SD card was not there.
Anyone have any ideas?
Jeep_Lover said:
Hello first I want to say a big THANK YOU to everyone that has put time and effort into making the Nookie what it is today....but I have a noob question.
I recently got a 16gb micro SD and can successfully get the 0.6.8 Nookie to run on my nook color, my problems start when I try to "recover" my other 13gb's. Before I get burned and tossed aside I have checked
http://forum.xda-developers.com/showthread.php?t=922324&page=92
http://forum.xda-developers.com/showthread.php?t=883175&highlight=partition&page=103
and about 5 other pages and they all say the same thing..use EASEUS, grab the slide bar and voila. It appears to work but when I install it in the NC it either becomes very unstable or just boots to the NC as if the SD card was not there.
Anyone have any ideas?
Click to expand...
Click to collapse
I use Lexar Bootit ....a free utility...to format and flip the bit that says its a removeable drive, then your windows pc drive management can see and format it as full capacity fat32.
Hey thanks for the tip, unfortunately it won't work. I forgot to mention that I followed this tutorial ..... and updated my driver (saved my original Windows just in case) to a hitachi driver and now I can switch my SD memory card forth "removable" to "logical" and back when needed. Once I get it as a logical drive I was EASEUS to increase the size of partition 4 (SD Card)..but again no dice!!!
Seeing that I am a noob I can't post the link to the tutorial but I'll say it worked like a charm and when I want to go back to the original I just need to "roll back" the driver.
Well, a couple of things:
Are you using a Sandisk card? Sandisk class 2 and 4 cards have been found much more stable than most others for running a ROM from SD, and problems with SD installs often go back to the card.
Any particular reason you went with Nookie Froyo? It has pretty much fallen out of use since the NC's stock OS was updated to Froyo in May. If you want an SD install, there's a simpler, size-agnostic method for CM7, which is also a more robust and capable OS and a more advanced version of Android (Gingerbread 2.3.4 rather than Froyo 2.2). I would recommend CM7.1 RC1, or if you're adventurous, Nightly 136.
Taosaur said:
Well, a couple of things:
Are you using a Sandisk card? Sandisk class 2 and 4 cards have been found much more stable than most others for running a ROM from SD, and problems with SD installs often go back to the card.
Any particular reason you went with Nookie Froyo? It has pretty much fallen out of use since the NC's stock OS was updated to Froyo in May. If you want an SD install, there's a simpler, size-agnostic method for CM7, which is also a more robust and capable OS and a more advanced version of Android (Gingerbread 2.3.4 rather than Froyo 2.2). I would recommend CM7.1 RC1, or if you're adventurous, Nightly 136.
Click to expand...
Click to collapse
Thanks for the info unfortunately I am using a 16gb PNY, class 4 and at $15 I couldn't pass it up...looks like I should have done some more reading first. Really I have no clue why I am using the Nookie, my wife said said that was the one she wanted. I think she just likes saying "Nookie", but I'll give the CM7 a go and see what trouble I can get into.
thanks again...
Taosaur...I was able to get the CM7 mod up and running in no time flat. Now the wife wants me to see if I can get bluetooth working.
You said "I was able to get the CM7 mod up and running ...." so I assume you got your problem fixed. That's good.
About bluetooth.
1. Turn off Wifi
2. Power off NC
3. Power on NC
4. Turn on bluetooth
5. Turn on wifi
votinh said:
You said "I was able to get the CM7 mod up and running ...." so I assume you got your problem fixed. That's good.
About bluetooth.
1. Turn off Wifi
2. Power off NC
3. Power on NC
4. Turn on bluetooth
5. Turn on wifi
Click to expand...
Click to collapse
Yep, I had to do the above the first time I turned on bluetooth, but haven't had any trouble toggling it on and off since then. Just open notifications (that broken-circle-and-arrow button on the status bar) and you have toggles there for Wifi, bluetooth, and a couple other things.
@ Taosaur,
I've seen your signature indicate you are running nb136, any change or improvement (both slightly and/or significant) over the previous ones?
Jeep_Lover said:
Thanks for the info unfortunately I am using a 16gb PNY, class 4 and at $15 I couldn't pass it up...looks like I should have done some more reading first. Really I have no clue why I am using the Nookie, my wife said said that was the one she wanted. I think she just likes saying "Nookie", but I'll give the CM7 a go and see what trouble I can get into.
thanks again...
Click to expand...
Click to collapse
Damn! My wife never says "nookie".
votinh said:
@ Taosaur,
I've seen your signature indicate you are running nb136, any change or improvement (both slightly and/or significant) over the previous ones?
Click to expand...
Click to collapse
I haven't done much but read and browse a little since I flashed it, but I haven't noticed any difference from 7.1 RC1, which wasn't really any different from Nightly 102 I had before that. I mostly just flashed this time for the integrated OC/Tweaks kernel, without the video/lag problems that were reported in 132-134.
Thanks for an update, m8
maybe someone can help me, i'm about to loose my mind here trying to figure this out. i'm using a Sandisk class 4 16gb card running CM7 with the OC kernal.Did all of this using the size agnostic install method. everything is working fine but i can't for the life of me figure out how to access the rest of the space on my SD, when i insert the sd card into my PC it just shows up as the 115mb partition. i've tried using EASeus, the lexar bootit, and some other partition tool with no luck. with Easeus i select the 13gb FAT32 partition and make it active and thats it right? does it need to be logical? and which partition am i resizing?
Dr. Light said:
maybe someone can help me, i'm about to loose my mind here trying to figure this out. i'm using a Sandisk class 4 16gb card running CM7 with the OC kernal.Did all of this using the size agnostic install method. everything is working fine but i can't for the life of me figure out how to access the rest of the space on my SD, when i insert the sd card into my PC it just shows up as the 115mb partition. i've tried using EASeus, the lexar bootit, and some other partition tool with no luck. with Easeus i select the 13gb FAT32 partition and make it active and thats it right? does it need to be logical? and which partition am i resizing?
Click to expand...
Click to collapse
None of the above. Windows will only recognize the first partition on a SD card, and when you make a SD bootable, that first partition will be the boot partition. To access the larger storage partition, connect your NC with CM7 running to the PC over USB. Open notifications on the NC, tap through "USB connected" to the USB screen, and "Turn on USB storage." Windows will now detect two storage drives, NookColor (the system partition, where apps install) and SDcard (the large storage partition).
The only time you'll want to remove the card from the NC and plug it into your PC is when you want to put on a new cm...zip update file to flash a new ROM.
I used the size agnostic install method with a 16gb PNY calss 4 SD and after all the steps were completed I was showing 13.8gb free for my SD card when I looked at in on the NC. Not believing my eyes I pulled it out and looked at it with EASUS and it showed partition 4 as 13.8gb (utilizing all the cards remaining space). I then downloaded a few things and added a few books for my wife and the space shrank to 13.4gb. As stated above your computer wont show it.
In short have you looked on the NC under "Storage" (I think that is were I found it) and verified you don't have the full capacity already?
Also there is another method I needed to use when I was messing with an earlier version (Nookie) that allowed me to see an SD card as a "Local Device" so windows would let me see all partitions on the hard drive. I can't post a link until I have more posts but email me and I can send you the link if interested.
Taosaur said:
None of the above. Windows will only recognize the first partition on a SD card, and when you make a SD bootable, that first partition will be the boot partition. To access the larger storage partition, connect your NC with CM7 running to the PC over USB. Open notifications on the NC, tap through "USB connected" to the USB screen, and "Turn on USB storage." Windows will now detect two storage drives, NookColor (the system partition, where apps install) and SDcard (the large storage partition).
The only time you'll want to remove the card from the NC and plug it into your PC is when you want to put on a new cm...zip update file to flash a new ROM.
Click to expand...
Click to collapse
thanks, well that got me some where. i connected nook to PC, turn on storage mode and it shows E/F drive. click either one and it says "Please insert disk into removable disk E/F" so then i turn off debugging and the nook color internal memory pops up as drive F, while clicking on drive E gives me the same error as above. any ideas? btw i'm on Windows 7 64bit, do i need any kind of special drivers or anything?
It is because windows will only allow you to manipulate the first partition on an SD card...even if it "sees" the other partition as another card it will not do anything with it. EASEUS will show you all the partitions on the SD.
The only way I got Windows to see all the partitions and do anything with them was to change my driver via the "Hitachi fix" If you google Hitachi driver SD card you will find it. I used this site and even though it is long it did exactly as advertised and now I install this driver when I need to format just the partition of an SD card and then "roll back" the driver when I'm done. It tricks windows into thinking it is a local device instead of removable. www/1src/com\forums\showthread.php?t=133718
change / to .
\ = /
I can't post a link as I'm still a noob...
Jeep_Lover said:
It is because windows will only allow you to manipulate the first partition on an SD card...even if it "sees" the other partition as another card it will not do anything with it. EASEUS will show you all the partitions on the SD.
Click to expand...
Click to collapse
S/he really doesn't need Windows to do anything with those other partitions--I suspect messing with them was where s/he went wrong in the first place.
Dr. Light said:
thanks, well that got me some where. i connected nook to PC, turn on storage mode and it shows E/F drive. click either one and it says "Please insert disk into removable disk E/F" so then i turn off debugging and the nook color internal memory pops up as drive F, while clicking on drive E gives me the same error as above. any ideas? btw i'm on Windows 7 64bit, do i need any kind of special drivers or anything?
Click to expand...
Click to collapse
I suggest you start over, because you probably damaged your install when you were messing with the partitions earlier. I'm also using Win7x64, and no, I didn't need any special drivers. Delete all partitions except "SDcard" in EASEUS, expand that partition to the whole card, then write verygreen's image to the card again and re-install. At that point, you should be able to access storage over USB from CM7 without turning off debugging or taking any other special steps other than "Turn on USB storage."
Taosaur said:
S/he really doesn't need Windows to do anything with those other partitions--I suspect messing with them was where s/he went wrong in the first place.
I suggest you start over, because you probably damaged your install when you were messing with the partitions earlier. I'm also using Win7x64, and no, I didn't need any special drivers. Delete all partitions except "SDcard" in EASEUS, expand that partition to the whole card, then write verygreen's image to the card again and re-install. At that point, you should be able to access storage over USB from CM7 without turning off debugging or taking any other special steps other than "Turn on USB storage."
Click to expand...
Click to collapse
alright i'll give it a shot when i get home from work. is the verygreen image the same one found in the CM7 size agnostic SD thread?
"http://crimea.edu/~green/nook/generic-sdcard-v1.3.img.gz"
and when i delete all partitions except for "SDCARD" do i need to make that partition logical or active or anything?
again thanks for your help.
Dr. Light said:
alright i'll give it a shot when i get home from work. is the verygreen image the same one found in the CM7 size agnostic SD thread?
"http://crimea.edu/~green/nook/generic-sdcard-v1.3.img.gz"
Click to expand...
Click to collapse
Yep, verygreen is the author of that thread and image.
Dr. Light said:
and when i delete all partitions except for "SDCARD" do i need to make that partition logical or active or anything?
Click to expand...
Click to collapse
No, in fact you might be able to write the image without messing around in EASEUS at all--I'm just not sure if WinImage (or whatever) would write to the whole card or just one partition. I know if you tried to format it, Windows would only format the boot partition.

[GUIDE] How to setup A2SD WITHOUT flashing a fresh ROM

After an hour or two of frustrating googling and thread sifting I managed to successfully setup A2SD to increase internal phone memory without affecting my current ROM and installed apps/data/settings. I thought I'd put together a clear and simple guide to save anybody else the pain and because I feel I owe the community for all the awesome ROMs and hacks my HD2 has been subjected to over the past couple of years!
Update: If you want to upgrade your ICS ROM rather than fresh install and maintain this A2SD script then see here
How to setup A2SD on the HD2 without flashing a new ROM and maintaining all apps, settings and data
1.) Copy the contents of your SD card to a PC so it can be restored later. Before doing anything like this I always make a backup of my current ROM using CWM recovery and you should too! Please search XDA if you are unsure on how to do this. There are other ways to back up your SD card and apps and tools that will do this for you but this is the easiest and most foolproof method.
2.) Reboot your phone into recovery. If you have MAGLDR then when your phone is off, hold power button until you see the MAGLDR menu and select option 8 for recovery using the volume buttons to scroll and call button to select
3.) Still using the volume and call/back buttons to navigate the menu, select ADVANCED and then PARTITION SD CARD. Select your ext partition size. 1024 seems a healthy size big enough for most people. I have read many warnings about using 2048 and above so I recommend only going as big as you need to. Select 0M swap and continue to partition. Please be aware that your SD card will be formatted so make sure you paid attention to step 1!
4.) Now you need to flash the script that will make this partition wizardry happen. Download 40ad2sdx-a2Recovery.zip and save to your PC. From the CWM recovery main menu, select MOUNTS AND STORAGE then MOUNT USB STORAGE with your phone plugged into the PC. Windows will recognize your phone as a USB mass storage device so you can copy the script (40ad2sdx-a2Recovery.zip) directly onto the SD card. Once copied, press the call button on the phone to unmount USB storage. Now, back to the main menu and select INSTALL ZIP FROM SD CARD then CHOOSE ZIP FROM SD CARD. 40ad2sdx-a2Recovery.zip will be the only thing in the list so select and install it
5.) To complete the setup of the script you need to fix permissions. Once again, CWM recovery does all the hard work for us so from the main menu simply select ADVANCED and then FIX PERMISSIONS
6.) Ok. The A2SD virtual internal phone storage is now setup but before you reboot the phone, you need to restore the contents of the SD card so that Android doesn't try and set up the SD card from scratch and inevitably cause issues with your apps. As in step 4 connect your phone to the PC as a USB mass storage device and copy the SD card backup you made in step 1 back on to your SD card. This may take a while depending on how much data you have. 4GB took just over an hour for me. Once complete select UNMOUNT on the phone
7.) Now for the moment of truth... Keep your fingers crossed and select REBOOT from the recovery main menu. If all went to plan everything should look exactly as it did when you left it. Go into SETTINGS/MANAGE APPS to see your shiny new internal storage size and no more complaints from Android about your internal memory being low.
8.) We're almost there. Although everything should now work perfectly and your internal memory has increased you will most likely find you have the low sound issue where media played from the SD card is very quiet. To solve this you simply need to fix permissions one last time. Boot into recovery as in step 2 and select ADVANCED and then FIX PERMISSIONS just as you did in step 5. Now reboot and enjoy!
WARNING
- This guide assumes you have recovery etc. installed (see my signature for the specs that worked for me)
- I have only tried this with tytung's NexusHD2-ICS-CM9 V1.2 so I cannot promise it will work with other ROMs although I don't see why not. Be aware that some ROMs are already DATA2SD enabled and will not require an additional script - do your research!
- I have written this guide with the intent of helping a few lost HD2 users and it's merely based on my experience. I hold no responsibility for you bricking your phone or any other damage caused
- I am not a DEV but a ROM dabbler; I did not write this script and can only thank the guys responsible for it
Update...
uzi2 said:
You can,save a lot of time by creating the EXT4 partition with minitools partition wizard as it won't delete the data already on the FAT32 partition.
Sent from my Xoom
Click to expand...
Click to collapse
This will make the above procedure a hell of a lot faster!
Here is a link to the Minitool Partition Wizard download
Additionally to using MTPW, format your SD with SD Formatter (to have it really nice and clean) and do all your operations with a SD card reader on your pc to make things even more faster
Plus, I think CWR only formats in ext3, not ext4 (which seems to be better)...
More info plus some other scripts in the Tytung Nexus CM9 wiki quoted in my sig.
geenyous said:
Additionally to using MTPW, format your SD with SD Formatter (to have it really nice and clean) and do all your operations with a SD card reader on your pc to make things even more faster
Plus, I think CWR only formats in ext3, not ext4 (which seems to be better)...
More info plus some other scripts in the Tytung Nexus CM9 wiki quoted in my sig.
Click to expand...
Click to collapse
Thanks for the tips, SD Formatter looks like a good idea.
I really need to find my mini-SD to SD adapter!
I have had no issues with ext3 so far, does anybody know the benefits of ext4?
The whole procedure is much more simple that it seems like in the guide (very good guide also).
I did use the same script and it works perfect.
You should add another step that includes rebooting into recovery and fixing permissions a second time to fix the low volume issue. Aside from that thats the best guide on this subject I've read so far. Lets hope this will be a help to people switching to ICS roms without included Whatever2SD.
vasil.domuschiev said:
The whole procedure is much more simple that it seems like in the guide (very good guide also).
I did use the same script and it works perfect.
Click to expand...
Click to collapse
Thank you, your right about it being easier than it looks. My aim was to make sure inexperienced users don't get stuck
Dam4rusxp said:
You should add another step that includes rebooting into recovery and fixing permissions a second time to fix the low volume issue. Aside from that thats the best guide on this subject I've read so far. Lets hope this will be a help to people switching to ICS roms without included Whatever2SD.
Click to expand...
Click to collapse
Thanks, you're right about adding a step to cure the low volume issue. I will do that as soon as I get back on a PC.
All the guides I found before this were unnecessarily complicated and misleading. I hope this helps a few people
Thanks, worked for me!
As said, worked OK for me, but had low sound bug after that. Fixed permissions as you told and it was OK until next reboot. After reboot low sound was back.
Solution for me was to fix permissions twice.
1. Power off
2. CWM recovery and Advanced -> Fix permissions
3. Power off
4. CWM recovery and Advanced -> Fix permissions
5. Power off and boot
Now even after reboot low sound is not coming back.
ponn said:
As said, worked OK for me, but had low sound bug after that. Fixed permissions as you told and it was OK until next reboot. After reboot low sound was back.
Solution for me was to fix permissions twice.
1. Power off
2. CWM recovery and Advanced -> Fix permissions
3. Power off
4. CWM recovery and Advanced -> Fix permissions
5. Power off and boot
Now even after reboot low sound is not coming back.
Click to expand...
Click to collapse
Coincidentally I updated the above guide explaining that you will need to fix permissions twice to avoid the low sound issue about 15 mins ago. See the final 'step 8'
Please can I ask you to have a quick look and confirm these steps make sense?
Thanks
Yes, I think that doing it second time right after the first boot might do the trick also.
ponn said:
Yes, I think that doing it second time right after the first boot might do the trick also.
Click to expand...
Click to collapse
Thanks, just wanted to double check we were on the same page!
Thanks, worked for me. great work.
How to upgrade your ICS ROM.... properly!
I had some trouble upgrading from 1.2 to 1.3 because I was trying to use WinRAR to insert the script into the zipped ROM and CWM kept erroring.
7-zip seems to do the job perfectly so once again, feel free to learn from my mistakes...
How to upgrade your ICS ROM and maintain amarullz script
1.) Back up current ROM and apps however you want. I recommend a backup of the ROM with CWM and a backup of the apps with Titanium Backup. You can also copy the entire contents of the SD card to a PC for a fool proof backup. This is only as a precaution in case all hell breaks loose!
2.) On your PC unzip the script 40ad2sdx from 40ad2sdx-a2Recovery.zip or download the attached file from this post and unzip
3.) Open NexusHD2-ICS-CM9_V1.3.zip with 7-zip (Google and download for free) and go to folder system/etc/init.d/ then drag and drop the unzipped file 40ad2sdx to the opened 7-zip window then close 7-zip
4.) Copy the modified NexusHD2-ICS-CM9_V1.3.zip to the phones SD card
5.) Boot into CWM and install the ROM. There is no need to wipe cache or dalvik cache
6.) Reboot and relax
I am a newbie I don't know where to click on the "Thanks" button. so again, this thread did help me and work very well.
thanx
thnx buddy.... but i tried it on coredroid v3.7 for hd2.... it got stuck....... had to reinstall rom.......... any ideas
Is this script working on urdroid sensational xl stock 3.5? Please advise....
Sent from my mighty HTC HD2
shezi2243 said:
thnx buddy.... but i tried it on coredroid v3.7 for hd2.... it got stuck....... had to reinstall rom.......... any ideas
Click to expand...
Click to collapse
Sorry to hear you're having trouble but as stated I have only tried this on ICS ROMS CM9 by tytung V1-4.
I have not tried installing this script on a Gingerbread ROM such as coredroid v3.7. In fact, I never found the need for more internal memory when I was using Gingerbread ROMS.
On the coredroid thread it says:
"Can we use A2SD?
All CoreDroid builds use EXT partition to use as DATA USER and use some parts of SYSTEM. This was chosen this way cause it makes the build faster. You can always use APPS2SD from MARKET to save a little more space on Phone storage if its not enough for you"
This suggests to me that all you need to do is create the EXT partition using CWM and you're good to go but please do some XDA searching first
Good luck
taufan36 said:
Is this script working on urdroid sensational xl stock 3.5? Please advise....
Sent from my mighty HTC HD2
Click to expand...
Click to collapse
If you are referring to this ROM here:
http://forum.xda-developers.com/showthread.php?t=1275119
Then you do not need the script from my thread. It looks like ext partition support is included and mandatory from version 3.2 onwards. Please see threads specific to your ROM but as in my previous reply it looks like all you need to do is create an ext partition and you're done.
Please search XDA to confirm this as I have not used that ROM
Good luck

Install apps on SD Card on Note 8.0 *root

Hi Guys
I noticed another thread here on how to use your external SD card for apps only me being a noob it was far too complicated. I managed to find this video tho and tried it on my device and it works perfectly. You need a rooted device with Busybox and Script Manager to do this and then you will need to download this script and use Script manager to run this script at startup which basically swaps the internal and SD memory around so your device thinks your SD card is SDcard0. Video explains everything quite nicely.
There are other options out there that work too such as an app called Directory Bind, but this is way easier and much more reliable. With directory bind i was having huge problems trying to access the SD card or internal memory when plugged into my PC. Hope this helps.
script: http://downloadandroidrom.com/file/GalaxyNote2/app2sdNote2
http://www.youtube.com/watch?v=p8PyqCOpERA
hello , thx it really works. but can i bother with how if i want to swap the memory again ?
do you the revert script again ?
dark_knight828 said:
hello , thx it really works. but can i bother with how if i want to swap the memory again ?
do you the revert script again ?
Click to expand...
Click to collapse
No. Just remove the script & reboot, or pull the SD Card & reboot.
GSLEON3 said:
No. Just remove the script & reboot, or pull the SD Card & reboot.
Click to expand...
Click to collapse
how install this!as shown in video?what to do with the enclosed file?
---------- Post added at 09:44 PM ---------- Previous post was at 09:02 PM ----------
it's a go!tnx
Works great!
Followed these steps from original post and now have 64GB as internal storage!
Install script manager from play store
Open script manager, click on browse as root then ok
Choose the downoaded file and choose Script/Executable
Now tap on Su, Boot and Save
Reboot your phone and enjoy!
kable said:
Works great!
Followed these steps from original post and now have 64GB as internal storage!
Install script manager from play store
Open script manager, click on browse as root then ok
Choose the downoaded file and choose Script/Executable
Now tap on Su, Boot and Save
Reboot your phone and enjoy!
Click to expand...
Click to collapse
thanks! i tried this and works perfectly!
Question. What size SD card are you guys using?
Can I add a 64gb SD card, on top of the 16gb internal?
so then I would have like 80 gigs total?
1username4thisforum said:
Question. What size SD card are you guys using?
Can I add a 64gb SD card, on top of the 16gb internal?
so then I would have like 80 gigs total?
Click to expand...
Click to collapse
I used a 64 GB micro sd card. That became my internal storage (Sdcard0) while the original internal storage now shows up as (extSdcard) ( Which is approx 10GB ) so you can use it all but it will be 2 separate storage areas.
Just look at the OP's post, he has a pic of how your storage will be showing up.
I'm using FolderMount from Google Play to move specific folders to the SD card, seems to be working well.
The internal SD is probably much faster than the external, so I'd rather not do a full swap.
1username4thisforum said:
Question. What size SD card are you guys using?
Can I add a 64gb SD card, on top of the 16gb internal?
so then I would have like 80 gigs total?
Click to expand...
Click to collapse
64gb SanDisk Ultra. Yes u can.
Sent from my GT-N5100 using xda app-developers app
Hi guys.
I haven't watched the video yet... I just want to ask a few questions (and state my case) first:
I've just bought a 64gb SanDisk Ultra... I would like to use it as my internal memory as is described here... I have no intention of ever taking it out of the device.
Now my concerns:
1) I've never rooted a device before. I can get my way around windows and build a pc... that's about it. So I'm very nervous about doing this.
2) In all likelyhood I'll be staying on stock, so I want to be able to receive updates in the future.
3) I've already installed some apps to the internal memory... what's going to happen to those after I do this swap?
So what do I need to know?
Who's going to hold my hand in this?
FaeMinx said:
So what do I need to know?
Who's going to hold my hand in this?
Click to expand...
Click to collapse
hey man, I was in the same boat as you, never rooted anything before. you can root the note 8 by using framaroot. Its really easy and you can Install from the Link below and once rooted you Wont be able to do updates but you will be able to unroot when you would like to do an OTA update. I had to use the Samsung desktop application (Kies) for windows to apply the original firmware to do the updates. Not sure if you will need Factory reset but i did and I was able to update again. This is a software root and if anything goes wrong a factory reset will fix anything, that or just restoring your firmware, this also shouldn t void your warranty
the apps you have installed already will still work you just need to copy all the data on the internal across to your 64GB card (select all, copy and paste)
1 Install framaroot
http://forum.xda-developers.com/attachment.php?attachmentid=1952450&d=1368232060
2. Open frama root and select SupesSu. Select the Aragorn method.
3. Reboot your device
4. Install busy box and open the app. Grant Su permissions and do the smart install
https://play.google.com/store/apps/details?id=stericson.busybox&hl=en
5. Now you are rooted and ready to follow the steps of this thread.
6. Use ur device to format the SD card
7. Download script and save to SD card
http://downloadandroidrom.com/file/GalaxyNote2/app2sdNote2
8. Install script manager from play store
9. Open script manager, click on browse as root then ok
10.Choose the downoaded file and choose Script/Executable
11. Now tap on Su, Boot and Save
12. Reboot your phone
Watch this video too.
http://www.youtube.com/watch?v=p8PyqCOpERA
Hope this helps.
Sent from my GT-N5100 using xda app-developers app
Great, Thanks!
This step by step was just what I was looking for.
:highfive: :good:
Had the script running for a while prior to a reboot last night....now smanager shows " sh: /storage/sdcard0/Download/app2sdNote2.bin: can't execute: Permission denied"...Don't know what happened??Tried deleting and reinstalling with no luck?? tried saving the download to the sdcard and the internal memory..neither worked??
This is great info and all but what happens if the sd card gets corrupt. Its a very real possibility as I have seen on AC it happens quite frequently. If the sd gets corrupted and that is where your android os file are now stored does your phone/tablet become a brick?
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2
I wrote the hard to understand version of what's very much this process.
The gui is helpful, but you do need to know what the script is doing and what the script is to troubleshoot problems. It's not actually swapping all of your Android system onto the sdcard, to start with.
Your OS stays internal, and installer files for most of your apps stay on the internal memory. Applications write their data to the sdcard.
Gotchas with this approach include:
-your script needs to be executable by the process which runs it. When I first set this up there were issues around who owned the script and who could run it. If that's broken, you'll get the 'this script could not run' error.
- if you use one of the alternate roms, you will need a different script. Civato's kernel, for example, requires a different version of this script.
- I have heard rumors that 4.2 and above break this approach. Unknown by me.
roustabout said:
I wrote the hard to understand version of what's very much this process.
The gui is helpful, but you do need to know what the script is doing and what the script is to troubleshoot problems. It's not actually swapping all of your Android system onto the sdcard, to start with.
Your OS stays internal, and installer files for most of your apps stay on the internal memory. Applications write their data to the sdcard.
Gotchas with this approach include:
-your script needs to be executable by the process which runs it. When I first set this up there were issues around who owned the script and who could run it. If that's broken, you'll get the 'this script could not run' error.
- if you use one of the alternate roms, you will need a different script. Civato's kernel, for example, requires a different version of this script.
- I have heard rumors that 4.2 and above break this approach. Unknown by me.
Click to expand...
Click to collapse
This is the only part of the script in red when I view the log inSuperSU:
stdout redirected to /dev/null
Don't know if that clears things up a little?
you might try enabling adb and running the script from an adb prompt;
adb shell
cd /etc/init.d
find the script (probably called XYmount where X and Y are numbers) and
type
sh XYmount
That should give you fuller output of the error.
small ricurr
roustabout said:
you might try enabling adb and running the script from an adb prompt;
adb shell
cd /etc/init.d
find the script (probably called XYmount where X and Y are numbers) and
type
sh XYmount
That should give you fuller output of the error.
Click to expand...
Click to collapse
Since this is not a full swap to the sd card I think I am just going to leave it alone....don't want to mess around and risk bricking the unit. If I do decide to try the adb route I will let you know what I find. THANKS!
melvill said:
hey man, I was in the same boat as you, never rooted anything before. you can root the note 8 by using framaroot. Its really easy and you can Install from the Link below and once rooted you Wont be able to do updates but you will be able to unroot when you would like to do an OTA update. I had to use the Samsung desktop application (Kies) for windows to apply the original firmware to do the updates. Not sure if you will need Factory reset but i did and I was able to update again. This is a software root and if anything goes wrong a factory reset will fix anything, that or just restoring your firmware, this also shouldn t void your warranty
the apps you have installed already will still work you just need to copy all the data on the internal across to your 64GB card (select all, copy and paste)
1 Install framaroot
http://forum.xda-developers.com/attachment.php?attachmentid=1952450&d=1368232060
2. Open frama root and select SupesSu. Select the Aragorn method.
3. Reboot your device
4. Install busy box and open the app. Grant Su permissions and do the smart install
https://play.google.com/store/apps/details?id=stericson.busybox&hl=en
5. Now you are rooted and ready to follow the steps of this thread.
6. Use ur device to format the SD card
7. Download script and save to SD card
http://downloadandroidrom.com/file/GalaxyNote2/app2sdNote2
8. Install script manager from play store
9. Open script manager, click on browse as root then ok
10.Choose the downoaded file and choose Script/Executable
11. Now tap on Su, Boot and Save
12. Reboot your phone
Watch this video too.
http://www.youtube.com/watch?v=p8PyqCOpERA
Hope this helps.
Sent from my GT-N5100 using xda app-developers app
Click to expand...
Click to collapse
Thank you for the step by step instructions . I do have a couple questions before I dig into this method.
1 - You mean to copy all the internal sd card to the external one?
2 - the script was written for a Galaxy note II, would it work for the Galaxy Note 8?
3 - When you mention to download and save the script do SD card, do you mean the internal one?
4 - Did you write this script?
Thanks for your help. The lack of internal memory is my biggest issue with the note 8.
Yours,
Alex

MicroSD corrupted only on Marshmallow update.

When the Samsung Galaxy S5 (SM-G900F) received official Android 6.0.1, I have manually installed that firmware on my device. Within few weeks ago it shows that my microSD card (64GB) corrupted. At that time if i connect to the PC I can access the SD card without any error. When I tap on "fix it" it format the SD and again it shows the exact same issue.
If I connect this sd card to a PC or a another Android device (runs ICS), these devices are not detect any error. Then I rebooted my S5 into a safe mode and again it shows that issue. However, this issue will fix if I reset the phone. After few days left it again appear that error.
So how do I fix this matter?
My wifes phone has the same issue.
Non rooted phone - 100% stock. Never messed with it.
After the MM update the sdcard just says corrupted.
As soon as a photo is stored or if google play music downloads a track to it it is corrupted.
Really annoying.
Going to try a full wipe now but I'm glad it's not just her phone. I thought the SD card had died and we haven't had it long.
Looks like it's something samsung have done.
Tried formatting the SDCard with a PC?
My SDCard is the same one I've had since I got the phone, through KitKat > Lollipop > MarshMallow, and has never been wiped or formatted, still got the very first photo I ever took with the phone on it
ownjoouk said:
My wifes phone has the same issue.
Non rooted phone - 100% stock. Never messed with it.
After the MM update the sdcard just says corrupted.
As soon as a photo is stored or if google play music downloads a track to it it is corrupted.
Really annoying.
Going to try a full wipe now but I'm glad it's not just her phone. I thought the SD card had died and we haven't had it long.
Looks like it's something samsung have done.
Click to expand...
Click to collapse
No need to wipe SD. Connect that SD to a PC and copy all the files.
*Detection* said:
Tried formatting the SDCard with a PC?
My SDCard is the same one I've had since I got the phone, through KitKat > Lollipop > MarshMallow, and has never been wiped or formatted, still got the very first photo I ever took with the phone on it
Click to expand...
Click to collapse
I think this issue caused by some sort of app or its a firmware issue.
Yeah it's been formatted. I did pop it into a pc to try and save everything but it demanded a wipe.
So I did.
It worked for a little bit and corrupted again. Now when I pit it in the pc it struggles to read it and the phone won't "fix it" either.
Tried to wipe it in a few different programs but it appears the card is corrupted.
It's a 64gb Samsung card. Only had it since January this year. Bought brand new from amazon.
I have another in my note 3 and that is still perfect.
The only saving grace is that Google photos had all the photos synced.
So i'm going to email Samsung about it as there has been no issues with the card until the moment the MM update hit.
ownjoouk said:
Yeah it's been formatted. I did pop it into a pc to try and save everything but it demanded a wipe.
So I did.
It worked for a little bit and corrupted again. Now when I pit it in the pc it struggles to read it and the phone won't "fix it" either.
Tried to wipe it in a few different programs but it appears the card is corrupted.
It's a 64gb Samsung card. Only had it since January this year. Bought brand new from amazon.
I have another in my note 3 and that is still perfect.
The only saving grace is that Google photos had all the photos synced.
So i'm going to email Samsung about it as there has been no issues with the card until the moment the MM update hit.
Click to expand...
Click to collapse
Try MiniTool Partition Wizard
Delete all partitions on the card > create new primary partition > Format to FAT32
MiniTool Partition Wizard free
https://www.partitionwizard.com/free-partition-manager.html
Used that to repair SDCards and USB drives a few times
You can also do it manually with elevated CMD: (Hit enter after each)
------------
diskpart
list disk
select disk x (x = being the disk number of your USB drive/card)
clean
create partition primary
active
format fs=fat32 quick
assign
exit
--------------
Try the card again
*Detection* said:
Try MiniTool Partition Wizard
Delete all partitions on the card > create new primary partition > Format to FAT32
MiniTool Partition Wizard free
https://www.partitionwizard.com/free-partition-manager.html
Used that to repair SDCards and USB drives a few times
You can also do it manually with elevated CMD: (Hit enter after each)
------------
diskpart
list disk
select disk x (x = being the disk number of your USB drive/card)
clean
create partition primary
active
format fs=fat32 quick
assign
exit
--------------
Try the card again
Click to expand...
Click to collapse
Already tried diskpart. No dice.
Just tried MiniTool Partition Manager. Still nothing. It lets you delete the partition and then creates a new partition instantly.
It has however now loaded in windows and shows 4 android folders but even after a delete on the partition and create new it makes no changes to the card.
It also wont let me add anything. Almost as if it is locked to read only.
So thanks for the advice as I can now see the card in windows "sort of". It's really slow though. But I can't put anything on it or wipe it or do anything with it really!
Windows 10 also says there are errors and when you let it error check it just stops responding.
ownjoouk said:
Already tried diskpart. No dice.
Just tried MiniTool Partition Manager. Still nothing. It lets you delete the partition and then creates a new partition instantly.
It has however now loaded in windows and shows 4 android folders but even after a delete on the partition and create new it makes no changes to the card.
It also wont let me add anything. Almost as if it is locked to read only.
So thanks for the advice as I can now see the card in windows "sort of". It's really slow though. But I can't put anything on it or wipe it or do anything with it really!
Windows 10 also says there are errors and when you let it error check it just stops responding.
Click to expand...
Click to collapse
If it still shows android folders on it, then none of the partition commands you've used, nor minitool have done anything, as you'll know, deleting all partitions on a disk completely wipes it
With MiniTool, it works a weird way, you have to basically tell it what you want to do, all steps, and then hit apply at the top, once you hit apply, it then performs the steps it looked like you had already done manually
EDIT - Just a thought, a live Linux CD/DVD/USB might have more luck, Linux doesn't care about permissions etc
*Detection* said:
If it still shows android folders on it, then none of the partition commands you've used, nor minitool have done anything, as you'll know, deleting all partitions on a disk completely wipes it
With MiniTool, it works a weird way, you have to basically tell it what you want to do, all steps, and then hit apply at the top, once you hit apply, it then performs the steps it looked like you had already done manually
EDIT - Just a thought, a live Linux CD/DVD/USB might have more luck, Linux doesn't care about permissions etc
Click to expand...
Click to collapse
I see... I have used Partition Magic in the past and if I recall you had to do this back in the old version. Completely forgot.
I've done that and it's trying to do it. It's going very sloooooooow. But it is getting further than diskpart did!
Will update when it decides to finish.
Good luck, might find it takes a few runs to undo whatever the phone/droid did to it
Unless of course it is physically damaged, but I've not had any problems with MM and my SD
EDIT - Found this from way back in 2010 in my repair folder, "Pen drive repair"
Code:
https://mega.nz/#!XdAW2R5I!sSVna0O4av5rnkTPpGuh_bkXatZpcfmr6X-R-3yjrzw
I tend to keep random programs that have fixed something difficult in the past, and put them in that repair folder, worth a shot
*Detection* said:
Good luck, might find it takes a few runs to undo whatever the phone/droid did to it
Unless of course it is physically damaged, but I've not had any problems with MM and my SD
EDIT - Found this from way back in 2010 in my repair folder, "Pen drive repair"
Code:
https://mega.nz/#!XdAW2R5I!sSVna0O4av5rnkTPpGuh_bkXatZpcfmr6X-R-3yjrzw
I tend to keep random programs that have fixed something difficult in the past, and put them in that repair folder, worth a shot
Click to expand...
Click to collapse
Will take a look at that tomorrow.
It formatted the card but as soon as it finished and mounted it Windows popped up and said there was a problem and it needed scanning.
Once it opened there were still 4 android folders on it....
Annoying.
Yea very, well it's definitely not deleting the partitions if it's still got all the old folders on it
Running the tool as Admin?
It does sound like it's physically damaged, but I thought that about a 16GB flash drive I had, and another 8GB I'd left in a tub on my desk for years because it was dead, then I used diskpart and repaired both of them the same day, and since then, minitool has fixed them
Tell you what you could try, Win32DiskImager, grab any image, say a Raspberry Pi image, and use Win32DiskImager to write the image to the card, I think that uses disk/device rather than partitions to write to, so it should overwrite absolutely everything
Then you can use Minitool to wipe and format back to FAT32 (Hopefully)
*Detection* said:
Yea very, well it's definitely not deleting the partitions if it's still got all the old folders on it
Running the tool as Admin?
It does sound like it's physically damaged, but I thought that about a 16GB flash drive I had, and another 8GB I'd left in a tub on my desk for years because it was dead, then I used diskpart and repaired both of them the same day, and since then, minitool has fixed them
Tell you what you could try, Win32DiskImager, grab any image, say a Raspberry Pi image, and use Win32DiskImager to write the image to the card, I think that uses disk/device rather than partitions to write to, so it should overwrite absolutely everything
Then you can use Minitool to wipe and format back to FAT32 (Hopefully)
Click to expand...
Click to collapse
The trouble with that is I can't write anything to it. It gives an i/o error ever time I try.
I'm tired now so i'm going to head to bed but tomorrow when I have a fresher head i'll take another look.
Will let you know how I go on. Will try that other tool you suggested.
The way Win32DiskImager writes to the disk is different to how Windows tries to write to it, basically like burning an ISO, vs copying files to a DVD
Yea, get some shut-eye, things are usually much simpler after a good nights sleep
Hi, i lost a kingstom 9GB after take out this card from a Samsung. I formatted, and after a few days , i disvovered, that card was set to be encrypted inside the phone, if someone takes out, and formats without unencrypt, on 2 or 3 cycles mor, the card will die, or lock, io root, i never found a solution for this, in my case, the card was locked, (ro), without any error in the partition.
Sent from my XT687 using XDA Premium 4 mobile app
---------- Post added at 11:33 PM ---------- Previous post was at 11:08 PM ----------
Sorry, i wrote wrong, is 8Gb, was the second sdcard lost by me, the first, was a 2Gb used on a nokia e7, that, after format this card the card was locked (ro) at all on all type of sdcard reader , usb, pc. The name, i found, is Cyclic Redundance Error, (formatted without unencrypt the filesystem)
Sent from my XT687 using XDA Premium 4 mobile app
*Detection* said:
The way Win32DiskImager writes to the disk is different to how Windows tries to write to it, basically like burning an ISO, vs copying files to a DVD
Yea, get some shut-eye, things are usually much simpler after a good nights sleep
Click to expand...
Click to collapse
Pen Drive Repair does nothing. Can't even find it.
Tried it another 2 times in MiniTool but still goes through all the motions but returns with the same four folder on the card.
I did a surface test and it found no errors. So reading it is fine. It's the writing to it where it fails.
EDIT: What I have just noticed is MiniTool states:
Capacity 59.64 Used 59.64 Unused 0B
So the card thinks it's full but there is nothing on it.
EDIT 2: And now in MiniTool is just says BadDisk. Looks like it is completely dead.
Well, there's nothing to lose by trying Win32 DI, unlikely to work,. but might as well try before writing it off
*Detection* said:
Well, there's nothing to lose by trying Win32 DI, unlikely to work,. but might as well try before writing it off
Click to expand...
Click to collapse
Gave it a shot. It wont even let me pick it as a device. Windows has stopped adding it to the "My Computer" list also.
I've wasted enough time with it. Only bought it in January this year so I've emailed Samsung both about the warranty on it and also that there is a possibility the upgrade to MM caused it on the S5.
It seems to have happened to the OP and me so I thought I would mention it to them in case.

Categories

Resources