phone model : I9000
Original condition : was working ok but doesn't read internal or external memory
Present condition : phone doesn't boot , always black screen Look here
Original firmware: unknown " for sure it was froyo 2.2 "
i've tried to flash it with lots of firmwares with Odin and no luck
can someone plz help me
thanks alot
Is download mode working ?
Hi,
If you've flashed with ODIN I'm assuming you've tried to get into download mode and that still works - but whatever ROM you flash, you get stuck at the black screen after the Samsung Logo and the Samsung animation.
How do you know it doesn't read from the SD memory?
Can you try mounting the SD memory from inside CWM and try reading? (Bear in mind some CWM version do not support mounting SD memory for USB reading)
i had the same problem as you on 2.2.1, just install new firmware and everything will be ok.
To Enter Recovery Mode:
Switch your phone off. Wait until vibrate
Now Press and HOLD the following Keys in the same order: First Volume UP, Second Home Key, and Lastly The Power Button.
Keep the Buttons Held until you see the phone Light up, then Let go off the power button, but keep the Volume and Home Keys Pressed.
Once you see a menu with the caption Recovery Mode on the Top let go of all the buttons.
after hard reset everything will work fine, after that install new firware with odin or kies (since you are on 2.2)
jayeshup said:
Is download mode working ?
Click to expand...
Click to collapse
yes phone still can enter Download mode and recovery mode
torrentship said:
Hi,
If you've flashed with ODIN I'm assuming you've tried to get into download mode and that still works - but whatever ROM you flash, you get stuck at the black screen after the Samsung Logo and the Samsung animation.
How do you know it doesn't read from the SD memory?
Can you try mounting the SD memory from inside CWM and try reading? (Bear in mind some CWM version do not support mounting SD memory for USB reading)
Click to expand...
Click to collapse
the phone was working when it came to me and it reads internal memory 0.0 and external SD memory didn't read it at all .
i guess you mean by CWM is to use clock work mod , the phone now doesn't boot to cwm recovery mode , it boots to samsung recovery mode only and download mode .
milets said:
i had the same problem as you on 2.2.1, just install new firmware and everything will be ok.
To Enter Recovery Mode:
Switch your phone off. Wait until vibrate
Now Press and HOLD the following Keys in the same order: First Volume UP, Second Home Key, and Lastly The Power Button.
Keep the Buttons Held until you see the phone Light up, then Let go off the power button, but keep the Volume and Home Keys Pressed.
Once you see a menu with the caption Recovery Mode on the Top let go of all the buttons.
after hard reset everything will work fine, after that install new firware with odin or kies (since you are on 2.2)
Click to expand...
Click to collapse
mate i tried to flash the phone with many files like 2.1 , 2.2 , 2.2.1 , 2.3 , 2.3.3 , 2.3.5 , 2.3.6
but always same result , the thing is that the phone was working before i flash it the first time ,
thank you all for help and plz share with me a solution
wbr
Have you tried flash phone with full (3 part) rom + pit file?
Firstly, I think ke_be's suggestion is spot on; give that a try.
But,
the phone was working when it came to me and it reads internal memory 0.0 and external SD memory didn't read it at all .
Click to expand...
Click to collapse
I'm not sure how to read this - do you mean the external SD memory (which to avoid confusion is the SD card that you can put into the phone physically rather than the internal partition called sd_ext) was not readable from the beginning?
Also - does ODIN give any warnings at all or does it always say "Success!" and then reboot?
Becuase it sounds like it thinks it's flashing the image properly but in fact it is not which could very well be symptomatic of memory read/write problems.
(It's difficult to tell without DMESG!)
torrentship said:
Firstly, I think ke_be's suggestion is spot on; give that a try.
But,
I'm not sure how to read this - do you mean the external SD memory (which to avoid confusion is the SD card that you can put into the phone physically rather than the internal partition called sd_ext) was not readable from the beginning?
Also - does ODIN give any warnings at all or does it always say "Success!" and then reboot?
Becuase it sounds like it thinks it's flashing the image properly but in fact it is not which could very well be symptomatic of memory read/write problems.
(It's difficult to tell without DMESG!)
Click to expand...
Click to collapse
i've tried kebe's and flashed many many flashes 3 parts + PIT file same result
what i meant is the external SD memory which i insert in phone under the battery cover , this one the phone does not recognise at all , also the internal partition which is originally comes inside phone from samsung also was not readable , when i go to setting storage it was 0.0 MB , or something like that .
Odin does not give any errors and always it success flashing and reboot
and what is DMESG! ?
thank you for your help
Hi there,
Ok - well I think that as the phone couldn't read the Internal or External SD memory when you got it that despite it appearing to be semi-functional, it was essentially broken!
The internal SD memory was clearly able to be read as the kernel and android is stored on it (the /system directory for example). So the question is - why were the SD_EXT directory and the external SD directory not readable and indeed do these issues have a bearing on the inability to start the phone!
Well.. both sd_Ext and external_sd are using the VFAT filesystem which is different from the rest of the mountpoints which use RFS or EXT or the like. (It's so Windoze can access it) So I wonder if somehow the driver that accessed that has a problem.. though there's not much we can do about that..
Also - when a new ROM is flashed, it doesn't actually do much with sd_ext an external_sd so that's also curious... I'm wondering if there is a "write" error on the phone's memory interface.
So - to check that - find a rom which has CWM and USB Mounting working in it (most GB roms have this) and flash it using ODIN but do not boot into it. Instead, try to get into CWM and then mount the USB storage from the Mounts menu option and try to write a file to it.
Indeed, if you are able to flash a new kernel or bootloader that implies it does NOT have a memory write problem! But it serves a purpose becuase it'll be useful having CWM on there rather than the Samsung recovery menu.
Essay over!
BTW DMESG is a little linux prog which displays the kernel output - it would probably show us some info about what's stopping the boot but I don't know how to view it prior to a ROM successfully booting - if someone does that'd help a lot.
torrentship said:
Hi there,
Ok - well I think that as the phone couldn't read the Internal or External SD memory when you got it that despite it appearing to be semi-functional, it was essentially broken!
The internal SD memory was clearly able to be read as the kernel and android is stored on it (the /system directory for example). So the question is - why were the SD_EXT directory and the external SD directory not readable and indeed do these issues have a bearing on the inability to start the phone!
Well.. both sd_Ext and external_sd are using the VFAT filesystem which is different from the rest of the mountpoints which use RFS or EXT or the like. (It's so Windoze can access it) So I wonder if somehow the driver that accessed that has a problem.. though there's not much we can do about that..
Also - when a new ROM is flashed, it doesn't actually do much with sd_ext an external_sd so that's also curious... I'm wondering if there is a "write" error on the phone's memory interface.
So - to check that - find a rom which has CWM and USB Mounting working in it (most GB roms have this) and flash it using ODIN but do not boot into it. Instead, try to get into CWM and then mount the USB storage from the Mounts menu option and try to write a file to it.
Indeed, if you are able to flash a new kernel or bootloader that implies it does NOT have a memory write problem! But it serves a purpose becuase it'll be useful having CWM on there rather than the Samsung recovery menu.
Essay over!
BTW DMESG is a little linux prog which displays the kernel output - it would probably show us some info about what's stopping the boot but I don't know how to view it prior to a ROM successfully booting - if someone does that'd help a lot.
Click to expand...
Click to collapse
wow , dude seriously thank you for your effort ,
i dont know much in linux and also on samsung hardware and software ways ,
but i love the idea you said about CWM rom ,
so what is that GB roms ? and where to find them ? noob questions i know , but i really i'm new to samsung android stuff .
with best regards,
Ok not to worry.
To test if you have CWM (clockworkmod) :
Turn off your phone
Hold down the UP volume button and the HOME button on your phone
Now, whilst keeping those two buttons held down, turn on the phone.
When you see the Samsung logo on there, you can release all the buttons.
If it says "2e" or "3e" recovery - you DO NOT have CWM so you'll need to get it. Otherwise you do have it - let me know.
If you don't have it:
Use this link to Ramad's Firmware Collection to get yourself a copy of the ODIN package for JVT (imo the best GB rom) and flash it to your phone (using ODIN!).
Then you should have ClockworkMod installed.
Let me know how you get on / any questions.
Related
First of all let me say hello to everyone as I am new to here and that if there is a thread about this please point me there as I have searched far and wide and tried everything imaginable and nothing helped whatso ever.
I recently got myself the HTC touch with these specs
sapphire pvt 32b ship s-on g
hboot-1.33.0006 (sapp10000)
cpld-10
radio-2.22.19.261
I tried a tutorial I had found on how to flash it (Sorry in my frustration I lost the link for it) everything went well I know I had to get a file manager to activate an apk program for it then type in a code...after that it prompted to restart which I did and now it wont go past the vodafone loading screen.
its not bricked as I can get to the hboot screen still and I can go to the other screen the black one where you can wipe the card/ use the update.zip etc.
I took the sd card out of my phone to put the files needed onto it as my phone couldn't be mounted anymore and now when I put it back in I get the
can't mount SD card error (cant mount /dev/block/mmcblk0p1 or /dev/block/mmcblk0) (no such file or directory)
so now it seems like I am royaly screwed here as my phone doesnt even read its own sd card...could I have accidently removed something from the SDcard which was needed for it to be recognized or is there a way to work around this
please can someone help me as I have been searching for a good 14 hours straight as I need my phone for work...
thanks in advance
Is the sdcard formatted as FAT32? Most come partitioned as FAT but all the tutorials say updating rom requires FAT32.
sorry I forgot to mention that yes it is formatted to FAT32, I did the format on the pc so I lost all the files that were on it, but as it is an sd card and not the internal memory it shouldn't have had any information on it required to mount it otherwise if I would get a new sd card it wouldn't work
the sd card that came with mine btw is an 8gb micro SD HC
I have a normal 2gb Micro SD but it doesn't read that one either.
so in otherwords I have just flashed my phone with the flashrec-20090815.apk which then asked to restart...I did that and then wiped before the backup, which should only mean I cannot go back to the stock settings unless some other dutch vodafone magic user would be so kind as to send me his nandroid backup
but other than that I would really like to figure out why my phone can't mount the SD card, either of them
EDIT: When I searched around the net about can't mount SD card error (cant mount /dev/block/mmcblk0p1 or /dev/block/mmcblk0) (no such file or directory)
I found that every other person that has this problem is a HTC dream user which makes me think I accidently got a Dream file flashed to my phone, yet wouldn't just the right sappimg.nbh be able to return things to normal? Or is this just wishful thinking...
Well second this story from me. I have the exact problem as you have. Hope someone will stumble upon this thread and give us guidance..
//N
well I don't know how much of a difference it makes but I just got both fastboot AND ADB to work, at first only fastboot worked for me, so now when I am in the recovery screen I can put adb commands in even though it is not started up fully (Cant get past loading screen yet)
hmm...latest update, I think I did something horribly wrong now...it no longer goes into the recovery-RAv1.2.1G screen (The black screen with green words) it now brings me to a different recovery screen, the one with the phone and the exclamation (!) mark
As long as you can go into fastbood hope is not lost.
Did you already do an SPL update? if yes you can just install any rom you want.
try to put an rom (lets say cyanogenmod) via microsd to usb adapter on the drive and call it update.zip.
Get this tools: http://www.megaupload.com/?d=EZU065GP
You need to install the USB driver for the phone if you not already have.
Connect the phone to the PC and boot you phone by holding "Back" and "On" into fastboot.
then run the "Boot Modified Recovery" script. Select "Apply sdcard:update.zip", make an wipe and the Phone start normally with the rom you selected.
It would be very helpful if you write would you already did to the phone.
ok, first things first...tired the program you sent me (Awesome by the way thanks) but the SPL I am using is a non engineerings spl meaning I cannot actually DO anything in fastboot
so without being able to start my phone up fully or use adb (I Lost that option once the recovery part disapeared for some reason) it would be great to know if I can still change the spl to an engineering one.
and now for a long list of what I did in the order I did it in so you can tell me just where I went wrong and tell me if I screwed up my phone completey or not (if not I have a special insurance on this that I pay extra for and might...JUST might cover this problem)
anyways.
At first I looked for a theme for the phone when realizing it wasn't going to be easy, I needed to flash them which is nothing I had done before (Should have realized then an there not to do it, knowing my luck)
anyways.
I turned on the usage of unkown applications and turned USB debugging on.
I put the flashrec-20090815.apk and recovery-RAv1.2.1G onto my sd card as told by the tutorial I downloaded linda file manager (Or something around those lines) to activate the flashrec thingy...followed by using the recovery thing and then it said it needed to be restarted.
I restarted it into the recovery like it told me to do, everything was going perfect.
This tutorial did not say to make a backup first so I never did (ARGH i hate that part the most) it told me to do a wipe, so I did...followed by sending the update.zip (This part confused me as they did not tell me to have the update.zip on it.
So I popped the sd card out (This may be where I went horribly wrong) put it into the SD card reader and put the update.zip rom on it I wanted to use.
Put the SD card back into my phone, and then it went wrong, I tried to run the update.zip and it said that it could not mount the sd card do to the dev/block thingy I posted above.
I have tried everything against that, I wiped the card...tried to format it through the phone (Same thing, could not mount) I formatted it on the pc to FAT32 (I made sure it was 32) and still, no matter what I do it wont mount...
strangely though someone suggested using the sappimg.nbh somewhere else, I got it...put it onto my SD card, started up hboot and it read it, tried to apply it but it said something about my CID or something being incorrect...but that DOES mean that the phone reads my SD cards (Since I have a 2gb sd and an 8gb sd HC (The one it came with)) and both of them work for doing that, but the sappimg part doesnt work.
after trying that sappimg.zip one though also with no good results, I tried to get back into the recovery part for the adb so that I could try something someone suggested about mounting the sd card image thingy through that...but when I booted up the recovery I got the normal android recovery (the one with only three choices and the phone with the exclamation mark) meaning I somehow lost my recovery RAv.......
so that is what has been done, please, please, please tell me I didnt horribly screw things up...if someone can help me I promise never to mess around with things I don't know about...
odanion said:
hmm...latest update, I think I did something horribly wrong now...it no longer goes into the recovery-RAv1.2.1G screen (The black screen with green words) it now brings me to a different recovery screen, the one with the phone and the exclamation (!) mark
Click to expand...
Click to collapse
I was wondering what happen when you press both Home and Power buttons at this moment. What the phone shows. Is there any menu we can use?
Is the ADB recognizes the phone in recovery mode in this moment?
I am also having similar problems with my sapphire. I can fastboot to recovery rom but cannot mount the SD card I can use adb
/dev/block/mmcblk0p1 no such file or directory when I try to access sdcard.
I have tried 4 different sd cards with different partitions on them but it will not read any of them.
I have tried to restore a nandroid backup by using adb push to put the img files in /sdcard. I assume it is just using the phone internal memory as the sdcard does not mount. I have used adb shell to flash_image the nandroid img files but it still does boot up succesfully. Just hangs at vodafone screen...
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
I've worked ever so hard trying to configure and get the aesthetics of my cm7 rom up and running and apps in my testing might have triangulated and caused this error, I don't know.
Whenever I try to install a rom, boot into recovery, do a backup-- basically my clockwork is broken. Not broken, it still tries. It just pops this up on the screen:
Populating /dev using udev: done
Initializing random number generator....done
modprobe: chdir (2.6.32.9): No such file or directory
Starting network...
Detected Standard B&N nook layout, emmc first
It appears the SD card is already properly formatted
Skipping format
Mounting /dev/mmcblk1p1 as /boot
Looking for the install images....
Initial Install files not found
Please download it from nook.linuxhacker.ru
and put on first partition of this SD card
the name should start with updatei-cm and end with .zip
Click to expand...
Click to collapse
I'm using a recently nightly build of CM7.
I really love how I have it set-up, but if I don't have anyway to ever back it up my results are effortless.
How can I fix this situation without removal of the system. anyone, please?
First of all, have you done a nandroid backup in CWM? If so you can definitely recover.
Second it looks like your boot file is corrupted, always sending you to recover rather than a normal boot. What boot setup are you using?
echoedge said:
I've worked ever so hard trying to configure and get the aesthetics of my cm7 rom up and running and apps in my testing might have triangulated and caused this error, I don't know.
Whenever I try to install a rom, boot into recovery, do a backup-- basically my clockwork is broken. Not broken, it still tries. It just pops this up on the screen:
I'm using a recently nightly build of CM7.
I really love how I have it set-up, but if I don't have anyway to ever back it up my results are effortless.
How can I fix this situation without removal of the system. anyone, please?
Click to expand...
Click to collapse
You have installed your ROM to SD. There is no CWM recovery on SD installs. You cannot do a nandroid backup with the SD recovery.
See my post here for an explanation of the difference between emmc installs and SD installs:
http://forum.xda-developers.com/showthread.php?p=25354258
However, there is a way to back it up. Keep reading further down in my post.
thank you.
but how do i get access to uAltRam and uAltImg.
Multi SD Mount APP isn't working.
R/W permission difficulties in root explorer..
Using the 4202012 nightly build..
please help,
this shouldn't be too hard, don't let it drive me crazy
echoedge said:
thank you.
but how do i get access to uAltRam and uAltImg.
Multi SD Mount APP isn't working.
R/W permission difficulties in root explorer..
Using the 4202012 nightly build..
please help,
this shouldn't be too hard, don't let it drive me crazy
Click to expand...
Click to collapse
Take the card out and put in your PC. It will see the boot partition and you can copy the files there.
leapinlar said:
Take the card out and put in your PC. It will see the boot partition and you can copy the files there.
Click to expand...
Click to collapse
Hmm.. somehow I got it doing that. I of course tried that before and only the two partitions were loading. This time I was messing with it and clicking the multi sd mount widget and somehow the boot drive came up and I transferred the files on there.
So now I can do a nandroid backup as usual? Or sense it's an (Alt) instead of a recovery thing must it be different?
I'll try some things in the mean time..
Okay, so I have to boot into recovery and choose alternative and do it manually.
Can't do it with Rom Manager/Rom Tool Kit. Tried and it did the same error as in the OP.
Off to try now.
This is really strange though.
I've been messing with Nooks for a while and always used rom manager and the recovery console just fine.. but i've always ever done dual sd boots.This is my first time really doing a single one.
I'm in the boot menu (encore u-boot menu by j4mm3r), 1.2 port + extras.
It's been at
'Booting. One Moment'..." for at least a minute. Assuming it's frozen itself..
edit: Yeah, the Alt files didn't work.. I reset and pressed the N button, went to alternate and SD card. Nothing.
Reset it and it works as usual, but still no ability to backup..
echoedge said:
Okay, so I have to boot into recovery and choose alternative and do it manually.
Can't do it with Rom Manager/Rom Tool Kit. Tried and it did the same error as in the OP.
Off to try now.
This is really strange though.
I've been messing with Nooks for a while and always used rom manager and the recovery console just fine.. but i've always ever done dual sd boots.This is my first time really doing a single one.
I'm in the boot menu (encore u-boot menu by j4mm3r), 1.2 port + extras.
It's been at
'Booting. One Moment'..." for at least a minute. Assuming it's frozen itself..
Click to expand...
Click to collapse
Do not use ROM Manager with the verygreen SD installation. It does not work. Use the boot menu to boot into the alternate. Hold the n key while booting. Choose sd, alt.
Edit: you said two partitions showed up. Did you physically take the card out and insert into a card reader in your PC? It should see just one drive. Make sure those two files are there or it will hang when you choose it in the boot menu. I suspect you put the files on emmc boot since you used that strange program to do it.
Sent from my Nook Color running ICS and Tapatalk
No,
it's something with the multi mount sd app widget.
I hook mini usb to usb.
then hit the widget.
and JUST the boot partition comes up.
It says something about disk F: is not formatted correctly as well.
Just plugging it in without the multi mount app the outward sd card partition and the nook color come up, just those two.
And can't believe I didn't think to take the mini SD out and use an adapter. I'll try it again with that.
You're right I did mess something up with my EMMC.
Before I had it on a stock nook.
Now it goes to the cyanomod thing.
I took the miniSD card out, plugged it in for power and it turned on.
Went to that, had a bunch of force closed issues nothing worked, dry and empty, etc.
Any suggestions?
I'm gonna check out the miniSD card partitions now and try to get something going with that.
echoedge said:
You're right I did mess something up with my EMMC.
Before I had it on a stock nook.
Now it goes to the cyanomod thing.
I took the miniSD card out, plugged it in for power and it turned on.
Went to that, had a bunch of force closed issues nothing worked, dry and empty, etc.
Any suggestions?
I'm gonna check out the miniSD card partitions now and try to get something going with that.
Click to expand...
Click to collapse
There are many threads here that will tell you how to restore stock to emmc. Search for them.
But to get the SD working, do what I said. And I would suggest getting rid of that mount program so you don't mess it up again.
Edit: The problem with those mount programs is, if you mount the wrong partition, windows can only read fat partitions and will ask you to format. System and data are ext4 which windows cannot read.
Sent from my Nook Color running ICS and Tapatalk
Thanks a bunch.
In ubuntu once the sd card is inserted all 4 partititions automatically came up so I was able to copy and paste the Alt images.
Am backing up right now
And yeah getting the emmc back to stop np.
One thing i'm confused about.. you're saying one cannot update rom's if booting from an SD card?
also, i assume all in eed to do to make a back-up on my hard drive or usb (so its not just inclusive to the minisd), i can just root browser into mnt/sdcard/clockworkmod/backup and and create a zip of the 2012.5.5.etc.etc.etc. made folder and trnasfer it onto external device? If needed all I would need to do is a transfer back?
echoedge said:
One thing i'm confused about.. you're saying one cannot update rom's if booting from an SD card?
Click to expand...
Click to collapse
Yes you can update the ROM. Just not with CWM. You place the update-...zip in the boot partition of the SD and then using the boot menu (hold n during boot) select SD and recovery. The script in the boot partition will install the ROM for you. You need to read the first post in the agnostic image thread. It tells you all this.
On the second question, you can do it that way, but the files are already compressed there so just copy the folder to your PC to archive them.
is it okay to just boot into alternative (power + vol up/down) instead of going through the manual booting with the 'N' on start-up?
echoedge said:
is it okay to just boot into alternative (power + vol up/down) instead of going through the manual booting with the 'N' on start-up?
Click to expand...
Click to collapse
Yes. I didn't know you could do it that way. See, you taught me something. LOL. As long as you are getting into the 3.0.2.8 CWM recovery it's OK.
Sent from my NookColor using Tapatalk
Ok lets start from the beginning:
I was trying to upade from 2.2.2 official to 2.3 official and now i'm messed up because after the step : "upgrade sd card" my phone restarted and my usb cabel was still on and phone started charging,after that i tried to turn on my phone.It worked but after 20secs my screens freezes and cant do anything even turn off i need to take battery out,also phone not detects my sim card...
Any idea? My phone is rooted,have installed CWM5.0.2.3,but have no backup only public one...But i can't mount usb storage because i get error like "E:Unable to open ums lunfile(no such file or directory)
ANY IDEAS????
I can get to pinkscreen aswell
If you have an external sd card put the public backup there and try to restore via cwm (if you get boot till there). You can also try the update procedure(the dload folder and stuff) but put them in the external sd card! The phone should boot from there.
Anyway,better wait for more answers since I'm not the best in here.I just know how to flash some custom roms.
Moihack said:
If you have an external sd card put the public backup there and try to restore via cwm (if you get boot till there). You can also try the update procedure(the dload folder and stuff) but put them in the external sd card! The phone should boot from there.
Anyway,better wait for more answers since I'm not the best in here.I just know how to flash some custom roms.
Click to expand...
Click to collapse
sorry for dumb question but microsd = external sd? if yes - then i placed the backup in the card but in cwm only phone memory shows no sdcard...
Edit: external i got that
well it actually is an external microsd card
did you manage to restore via cwm?
P.S. if cwm doesn't see your se card go to advaced->reboot into recovery
should be able to see it now
Moihack said:
well it actually is an external microsd card
did you manage to restore via cwm?
P.S. if cwm doesn't see your se card go to advaced->reboot into recovery
should be able to see it now
Click to expand...
Click to collapse
When i do "reboot into recovery" my phone double restarts and 2nd time it turns on normally not into recovery...
Don't know why this is done,but I think we should be happy that your phone isn't bricked
Maybe someone else here can help you and provide better solutions than mine
Have a read through http://forum.xda-developers.com/showthread.php?t=1639761.
Has a link in it to how I solved my issue of constant reboots.
Also , since you can load pink screen, you can connect through usb and change your recovery to 5.0.2.7. That's the one i used. Make sure that you have a cust.img file in the "image" folder. That is where the recovery should be too but am guessing you already know that.
If for some reason you dont have cust.img you can find and download a generic version in these forums. Did not need it so I did not bookmark the post I found it in but I think it was the Kalo's Honor Port thread in the pro development section.
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