[Q] I9000B really damaged internal sdcard? - Galaxy S I9000 Q&A, Help & Troubleshooting

Hello everyone!
I have a galaxy s i9000b with 8gb.
was using the Christian rom a gingerbread 2.3.3.
of a sudden he started to restart on lopping and ended up entering the system after some time. until it stopped booting the system permanently.
this is a recurring problem found much information on google about it!
solves the problem most easily by using the stock rom tim.
in my case.
after much research I learned to use the adb basically and was following a tutorial
parted on then it should go to the directory / dev / block and find mmcblk0.
but he was not there!
I tried to copy the etc / fstab file to a folder on your pc so I can read and see if mmcblk0 was listed there.
I used the command:
C: \ android-sdk-windows \ platform-tools> adb push / etc / fstab c :/
and I returned this:
can not stat '/ etc / fstab': No such file or directory
though I see him there in the adb shell browsing the folder / etc
finally began to get discouraged with the problem and for not having found the mmcblk0 there in / dev / block.
I'm beginning to think that with the 8GB internal memory of my beloved GS I9000B actually damaged.
Can someone help me confirm this or help me somehow?
just pointing out that the system does not start, but I have access to recovery mode and download
I'm using the recovery is the CMW RECOVERY v2.5.1.0 SPEEDMOD ULFK
to have access to the cell by adb!
sorry for bad english!

re:
Very sorry to hear this . You can try to find some solutions in this thread:
http://forum.xda-developers.com/showthread.php?t=845708
There are some more topics here on xda, try anything, before a year, i had one i9000 int dead, and there is no solution , hope your problem can be solved.
At the end if nothing helps, now we have some sort of fix, and this can be found in this thread:
http://forum.xda-developers.com/showthread.php?t=973687&page=3
look at Catanni post, this must work if anything else fail. This is vold file needed for this.
Good luck.

hey! tanks man!
thanks for the reply! I'll read all these topics and then I see that fstab!
then write here what happened!
Thank you so!

bispoom said:
I tried to copy the etc / fstab file to a folder on your pc so I can read and see if mmcblk0 was listed there.
I used the command:
C: \ android-sdk-windows \ platform-tools> adb push / etc / fstab c :/
and I returned this:
can not stat '/ etc / fstab': No such file or directory
Click to expand...
Click to collapse
your command that you used above is incorrect.
To transfer from phone to computer use "pull"
To transfer from computer to phone use "push"

re: read this please
It is very important, before u start flashing and work with abd, to do backup your /efs folder if u dont have already. If your phone really have dead internal sd then is almost impossible to recover your imei if /efs folder become corrupted. This is covered by this thread:
http://forum.xda-developers.com/showthread.php?t=859914
After that you can try to flash some older firmwares, try with repartition, try to manually set up partitions, and u have full procedure in first link on my previous post.
You can try this command from adb:
echo /dev/block/mmcblk0 > /sys/devices/platform/s3c-usbgadget/gadget/lun1/file
this command will mount your internal sd in windows, and then u can try to partition in windows
In second link, is procedure how to change internal and external sd, this is last that u can try (that mean that your internal sd is really dead). Attached fold.fstab will make your external sd to work like internal (this is not tested by myself, but a lot of people have succsess with this).
Bye and good luck, and please tell us how progress work.

hi!
result of command:
echo /dev/block/mmcblk0 > /sys/devices/platform/s3c-usbgadget/gadget/lun1/file
is here
cannot create /sys/devices/platform/s3c-usbgadget/gadget/lun1/file: directory no
nexistent
to access the folder dev / block there is no a mmcblk0
and not one or the other as mmcblk0p1 or p2
and inside the folder / sys/devices/platform/s3c-usbgadget/gadget / folder does not exist lun1 / ...
sorry for bad English, and tanks for the help

re:
If mmcblk do not exist, best u can do is to try to flash with repartition in odin. If this does not help, always can try this
http://forum.xda-developers.com/show...=973687&page=3
Wish u best

broken link
hi!
man tanks for the help but this link
http://forum.xda-developers.com/show...=973687&page=3
is broken!!!

Related

[HELP] MY SGSI9000 can't mount sdcard

Hello Everyone​
my phone was running good just battery got off charge i plug the charger then i try to open phone i saw it loopboot i just see the welcome message of samsung
but i can get on recovery and download mode
Here is the error message I get when I flash a new rom or i go into recovery :
update media. please wait
E:can't mount /dev/block/mmcbl0p1
(No such file or directory)
E:copy_dbdata_media:can't mount SDCARD:
your storage not prepared yet . please use UI menu for format reboot actions.
copy default media content failed.
---------------------------------------------------------------------------
Here was my phone stock configuration before all that happens:
Baseband version
I9000JPJV6
Firmware
2.3.3
Build number
GingerBread.JPJV6
---------------------------------------------------------------------------
Please help, thanks a lot in advance.
Note: I hope I posted at the right place, if not the mods can feel free to move it
Fail to mount /data
I have the same problem and have tried various fixes but none have worked so far.
I flashed different combinations of the three .pit files (512, 513 and 803) with GB and froyo roms. I flashed some other files than people said would work (dbdata.rfs.tar and P-SBL.tar.md5.tar) although I don't really know what they are supposed to do.
I also used parted in an adb shell to try and change the /dev/block/mmc/blk0. I printed the partitions (there was a FAT32 one and an ext4 one). Using 'rm' I tried to erase these partitions so hopefully a flash with re-partition would work. But afterwards I printed the partitions again and they were still there, exactly the same.
Does this mean that my problem is hardware-related?
If anyone has alternative solutions please share.

[Q] PT310 boot stays at "samsung galaxy tab 8.9"screen

I tried to install overcome 8.9 v2.3.1.
but I download the update & not the FULL zip [TEH N00B]
to make things worst I did not backup my system !!!!!!
I can access to the CWM-recovery so im not afraid of my tablet bricked
but the only zip i do have is not complete,
how i can move the the proper file to the tab?
or I need to go the odin route?
in that case what rom should I use?
many thanks
Don't have my tab with me at the moment but doens't the tab show up on a computer if it's in download or recovery mode?
Are you using CWM 5.5.0.4? if yes here is my suggestion...
First you need adb installed on your computer..
Second, you already have overcome full zip file..
This is the step..
Connect your device with computer
From device, Go to recovery - advance menu - mount /system and mount /data
From your computer go to adb terminal and type this
Code:
adb shell "ls /data/media/"
If you can see list of file from your device sdcard, so you make adb work for your device ..
Place your zip file on your path, says on C://overcome.zip and you want to copy the file to /sdcard/download/
This is the code
Code:
Adb push overcome.zip /data/media/download/.
wait for copying progress done..
After you done with moving file to device sdcard check content of your sdcard with this code
Code:
Adb shell "ls /data/media/download/"
When you found your file from list, you can flash overcome.zip from recovery
Thanks for you quick answer
I do have recovery 5.5.0.4
I can get to mount /system & mount/data
when i go to adb and use the command to list the files i got this error
C:\android\sdk-windows\platform-tools>adb shell "ls /data/media/
- exec '/system/bin/sh' failed: No such file or directory (2) -
and tryng to do this command i got this error
C:\android\sdk-windows\platform-tools>adb get-state
unknown
seems like the device is connected
i tried this and the tablet rebooted (not in recovery but reboot)
C:\android\sdk-windows\platform-tools>adb reboot-bootloader
many thanks
Ok I found the way to make that work
i post the reply maybe can help someone else.
suwandiapr should get the credit anyway.
In a phone you have one wrong rom or somenthing and you can get a good one
and copy that to the sd, in a tablet or any device without microsd you need to push the file using this command adb push
let's say you got a rom called supernoob.zip
adb push supernoob.zip /data/media/supernoob.zip
and remeber if you are using a tablet o phone without sd always keep 2 roms in case
Yes i made a simple batch file for windows in development section...
just bought p7310 today and same boot loop actually
hi all
even if i believed i was a geek with nexus or android phones i was wrong !!!!!i just brick my new P7310 wifi tab
-first i root OK
-after i ran rom manager (so manytimes used with my nexus one...) OK
-i flashed CWM but i chose "10.1" (no 8.9 choice at this time) so when rebooting i got this famous (hum) reboot loop just after the welcome screen "samsung galaxy tab 8.9" ..pffffffffff what a stupid beginer i fell about myself ....
- i tried to go in revovery but the loop appears and appaers .....
so i read and read and read forums and probably the solution or a step to a little begining of solution seems to be here ...
i dl Odin v3 and hope to be able to use it and installing a good version ...
thanks to read me and sorry for my english (i m french)
brunobassman said:
hi all
even if i believed i was a geek with nexus or android phones i was wrong !!!!!i just brick my new P7310 wifi tab
-first i root OK
-after i ran rom manager (so manytimes used with my nexus one...) OK
-i flashed CWM but i chose "10.1" (no 8.9 choice at this time) so when rebooting i got this famous (hum) reboot loop just after the welcome screen "samsung galaxy tab 8.9" ..pffffffffff what a stupid beginer i fell about myself ....
- i tried to go in revovery but the loop appears and appaers .....
so i read and read and read forums and probably the solution or a step to a little begining of solution seems to be here ...
i dl Odin v3 and hope to be able to use it and installing a good version ...
thanks to read me and sorry for my english (i m french)
Click to expand...
Click to collapse
Go to dowload menu and try to flash stock recovery in your tab..
Here is the stock recovery for p7300/p7310
Start odin, and put the file in pda slot..
Please see entire thread for your own safety..

[HOWTO][CWM][4.2] Synchronizing clockworkmod Directory

Update 11-26-2012
The issue that this procedure was designed to overcome has been resolved in the latest version of CWM (6.0.1.9 or newer). Please view http://forum.xda-developers.com/showthread.php?t=1781899 for details and download links. If you do not want to upgrade to the latest CWM the directions below will still work but you should really just update.
Background
Due to the multi-user support capabilities of Android 4.2(+) the clockworkmod directory created by ClockworkMod and used to store downloads and backups is being created in /data/media. Unfortunately this directory is not accessible to individual users and therefore backups created in recovery can not be viewed or modified by ROM Manager and vice versa. ROM Manager will look for the directory /data/media/<user number> (e.g. /data/media/0) to which /sdcard is mounted when you are logged in as the user whose number is <user number> (e.g. 0).
Requirements
ClockworkMod Recovery installed and functioning
ROM Manager
ADB installed on your computer and functioning
Willingness to accept that you are on your own and I am not responsible if you mess something up!
Solution
1. Boot into CWM recovery
2. Attach your Nexus 7 to your computers USB port
3. Open an ADB shell using a console from your computer
Code:
adb shell
4. Confirm that you have a clockworkmod directory at /sdcard/clockworkmod (I am using user number 0 for the rest of this procedure, if you wish to use a different user substitute 0 with your user number)
Code:
cd /data/media/0
ls
4a. If you do not see a clockworkmod directory create one with the command below, otherwise proceed to step 5
Code:
mkdir /data/media/0/clockworkmod
5. See if you have a clockworkmod directory at /data/media
Code:
cd /data/media
ls
5a. If you see a clockworkmod directory type the command below, otherwise proceed to step 6
Code:
mv clockworkmod clockworkmod_bak
6. Create the symbolic link
Code:
ln -s /data/media/0/clockworkmod/ clockworkmod
7. If you already had backups in clockworkmod (now clockworkmod_bak) you can move them to the new folder by executing the following command
Code:
mv clockworkmod_bak/backup/ clockworkmod/
mv clockworkmod_bak/blobs/ clockworkmod/
mv clockworkmod_bak/download/ clockworkmod/
WARNING: I tested a backup from recovery and verified the backup was in ROM Manager, renamed the backup in ROM Manager, and confirmed the backup was renamed in recovery. Due to time constraints I did not restore the backup though I can't imagine why it would fail. As mentioned above do this at your own risk. If you do not have a unix/linux experience I would suggest that you wait for someone with experience to follow these steps (I wrote them after I did the procedure so they haven't been vetted) before you attempt it yourself.
Very helpful, i was wondering what they did to mess up clockwork mod
been trying to undo 4.2 for hours as i dont quite like it
truehybridx said:
Very helpful, i was wondering what they did to mess up clockwork mod
been trying to undo 4.2 for hours as i dont quite like it
Click to expand...
Click to collapse
I am on the fence about 4.2 myself and when I couldn't see my 4.1.2 backup I had a panic moment. I have to admit that either 4.2 is growing on me or I am already forgetting how good 4.1.2 was .
sandnap said:
I am on the fence about 4.2 myself and when I couldn't see my 4.1.2 backup I had a panic moment..
Click to expand...
Click to collapse
+1! Panic indeed! LOL
Great tutorial. Thanks and have a happy thanksgiving
Is there a way to do this without using adb? I don't know how to get it working.
It looks like you are just moving all the files from one location to another, right? If thats the case can I just move them with a file explorer? Also where are the back-ups from pre 4.2 stored, I thought it was sdcard/clockworkmod/ Can I move the back-ups from there to a data/media/clockworkmod folder?
StarOrc said:
Is there a way to do this without using adb? I don't know how to get it working.
It looks like you are just moving all the files from one location to another, right? If thats the case can I just move them with a file explorer? Also where are the back-ups from pre 4.2 stored, I thought it was sdcard/clockworkmod/ Can I move the back-ups from there to a data/media/clockworkmod folder?
Click to expand...
Click to collapse
Please see my update to the original post. Once you update to the latest CWM you can copy any existing backups to the new backup and blobs folders under /data/media/clocworkmod. This is discussed in more detail in the thread I linked to.
Code:
mv clockworkmod_bak/backup/ clockworkmod/
mv clockworkmod_bak/blobs/ clockworkmod/
mv clockworkmod_bak/download/ clockworkmod/
This is me just being nit picky, but this looks better:
Code:
mv clockworkmod_bak/* clockworkmod/
I guess for people not confident in their linux abilities that '*' misplaced could be deadly though...anyway thanks for the simple and great workaround/explanation.
Wiping/ Factory resets (in CWM or TWRP) don't erase this data folder? Are we confident in this?
255|[email protected]:/data/media/clockworkmod # mv backup/ /sdcard/clockworkmod/
failed on 'backup/' - Cross-device link
How are you able to move the directories?
This seriously annoys me. Despite the recent surge of newer android devices not containing any sd card slots for secure file storage away from ROM flashing, everything is now embedded. I have had several accidental internal storage deletions containing backups and roms and no the clockworkmod is even harder to locate and backup conveniently through usb/ftp. Thanks for the tut.
TheAtheistReverend said:
Wiping/ Factory resets (in CWM or TWRP) don't erase this data folder? Are we confident in this?
Click to expand...
Click to collapse
Yeah i am wondering that too.it doesnt feel safe for me that the backups are in the system but not in sdcard.
nexus file locations
On the nexus devices (certainly the 7, which has no external sdcard), the only real mounted portions are cache, system and data. Locations like /sdcard/ /storage/emulated/0 etc. are all fuse mounted from /data/media
Supposedly most of the data portion will survive flashing new ROMs and recoveries, everything except unlocking the boot loader, which wipes data f to meet the android security model.
Doesn't feel very safe, though.
amp said:
This seriously annoys me. Despite the recent surge of newer android devices not containing any sd card slots for secure file storage away from ROM flashing, everything is now embedded. I have had several accidental internal storage deletions containing backups and roms and no the clockworkmod is even harder to locate and backup conveniently through usb/ftp. Thanks for the tut.
Click to expand...
Click to collapse
I would use TWRP. I have switched and never looked back. It has quite a few more advanced options that I didn't see with clockworkmod, and overall has be MUCH more reliable.
The clockworkmod recovery issue stated in this thread does not affect TWRP at all.
Thanx for this, it seems to work even for the latest CWM.
Sent with desire from My One
angusc said:
Thanx for this, it seems to work even for the latest CWM.
Sent with desire from My One
Click to expand...
Click to collapse
Iget an error: Read-only File system :crying:
fokus said:
Iget an error: Read-only File system :crying:
Click to expand...
Click to collapse
If doing commands with adb did you remember to use
adb shell
And check that your command line starts with #......
Sent with desire from My One
angusc said:
If doing commands with adb did you remember to use
adb shell
And check that your command line starts with #......
Sent with desire from My One
Click to expand...
Click to collapse
Yes, that is exactly what i did.
I am on ARHD 11.0
S-off
ElementalX 2.2
I'm on ARHD 11.0 as well.
Strange, I followed the OP from step 1 to 6. I couldn't get step 7 to work so I just used my root explorer to copy the directory contents across in to the newly created clockworkmod folder, then deleted the clockworkmod.bak directory and all was good.
Tip: copy and paste each cmd from the OP in to your adb commands window......
Sent with desire from My One
angusc said:
I'm on ARHD 11.0 as well.
Strange, I followed the OP from step 1 to 6. I couldn't get step 7 to work so I just used my root explorer to copy the directory contents across in to the newly created clockworkmod folder, then deleted the clockworkmod.bak directory and all was good.
Tip: copy and paste each cmd from the OP in to your adb commands window......
Sent with desire from My One
Click to expand...
Click to collapse
THX. That is what i did. I also tried it via Terminal on the device - same error: System read only... hmmm
EDIT: Works fine now after e vew reboots. THX

HOW to back up EFS here in S5830

hi guys i am looking here for thread that will give tutorial on how are we going to back up the said EFS which is the very important file of the phone where IMEI resides, suddenly after searching for so many days still haven't found an answer. I already tried using EFS Pro 1.9.2 and it prompts that the said directory isn't there.. i checked it out on the root of my phone and found that EFS folder isn't there.. now my question is there any apps or tool that will backup our efs so that if incase we accidentally mess with our phone, it will be easy for us to revert back to the time when the phone is functioning well..
The EFS Partition is "stl5" .
So , for mounting the partition at boot , You need to unpack your boot.img, Open init.rc and add the following lines:
mkdir /efs
mount /dev/block/stl5 /efs
Click to expand...
Click to collapse
Then You have to repack the boot.img
----------------------------------------------------------------------------------------
We are done with the mounting part. |
----------------------------------------------------------------------------------------
Now , Flash the boot.img
Reboot Your phone
Connect it to your PC (Note : ADB must be enabled)
Run adb pull /efs command
................................
There might be a way using the "*#7284#" code . It creates a service com port on PC. (Stock Roms Only)
dev0xteam said:
The EFS Partition is "stl5" .
So , for mounting the partition at boot , You need to unpack your boot.img, Open init.rc and add the following lines:
Then You have to repack the boot.img
----------------------------------------------------------------------------------------
We are done with the mounting part. |
----------------------------------------------------------------------------------------
Now , Flash the boot.img
Reboot Your phone
Connect it to your PC (Note : ADB must be enabled)
Run adb pull /efs command
................................
There might be a way using the "*#7284#" code . It creates a service com port on PC. (Stock Roms Only)
Click to expand...
Click to collapse
hitted thanks...
this is a nice tutorial, but it will be very best if u can provide the complete step by step on how am i going to do this, and where to input the said line..sori for asking too much..just a noob one..hehe dont know much bout adb shell and commads not an advance user too..hehe
mizukage said:
hitted thanks...
this is a nice tutorial, but it will be very best if u can provide the complete step by step on how am i going to do this, and where to input the said line..sori for asking too much..just a noob one..hehe dont know much bout adb shell and commads not an advance user too..hehe
Click to expand...
Click to collapse
DON'T MOUNT EFS PARTITION!
You will most likely brick your phone.
Sent from my GT-S5830 using Tapatalk 2
(Frank) said:
DON'T MOUNT EFS PARTITION!
You will most likely brick your phone.
Sent from my GT-S5830 using Tapatalk 2
Click to expand...
Click to collapse
do u have any better idea on how are we going to save our efs partition so that we can revert back if we messed with our phone?flashing is risky especially for noobs..

Phone lock and data recovery

Hello to all.
My phone is locked on by forcing me to remove the battery. I rebooted the phone and you are stuck at the loading screen.
I reloaded the OS (version JW7_JW2_JW1) and recovery(version CF-Root-v4.4-XX_OXA_JW4-CWM3RFS) through ODIN, but the phone still does not start.
I booted the phone into recovery and made ​​a backup. I was able to manually copy all the documents.
From the backup of the recovery, through the tool unyaffs, I recovered the contact database (contacts2.db).
Now I started the trouble because I can not find the message database. I have read that you should find in the folder com.android.providers.telephony, but the folder is empty.
Fearful of losing these files, I used the tool ddrescue as follows:
Code:
sudo ddrescue -r 3 /dev/sdb /my_path/image /my_path/logfile
I then mounted the file image with the command:
Code:
sudo mount image /mnt
To my surprise, I do not see all the hidden files that is able to recover the recovery.
Do you think that I've lost forever the phone's message?
Thanks in advance for any help you will be able to provide me, hello to everyone.
PS: I apologize for any inaccuracies or technical errors, but they are new to this type of work.
===================================================================
Hello to all.
I was able to recover and restore the data of the Memo. The database is located in the folder com.sec.android.app.memo
No one has an idea on how to restart the phone and try to recover / export of SMS?
Thank you all.

Categories

Resources