[Tutorial][A.I.O. Rescue & Recovery] My Android Solutions. [Help & Troubleshooting]
Welcome to
My Android Solutions
for Galaxy PhonesThis is part of [All-in-One Rescue and Recovery] package for Galaxy Phones .
The others are
My Android Collections
My XDA Directory
My Secure Digital [SD Card] Storage
Be Advised that Most Mobile Phones have their own WIKI page on XDA Forum providing compiled knowledge about that particular phone and using them can provide many details that you may not be aware of, so always do a search first on the Wiki page for your unit.
Whatever you have done or may do with your phone because someone said so, is still your responsibility ...so take your time READ carefully to avoid making mistakes in haste, be calm and recheck the details.Index to Problems and Solutions mentioned below
0) All Problems :- Do the First Step - can solve many problems that you may have
1) Problem:- Cannot enter Download or Recovery Mode
2) Problem:- Cannot connect to PC or Unknown Device, getting Code 43 or any other code or NO response when using USB cable
3) Problem:- Odin gets Stuck on <ID:0/008> Set PIT file. or <ID:0/003> SetupConnection.. or <ID:0/007> Removed!
4) Problem:- i9001 Odin 4.43 gets stuck on amss.mbn download..
5) Problem:- When upgrading to ICS, Stuck on boot screen
6) Problem:- Lost my IMEI or changed on upgrading to JB CM 10
7) Problem:- Don't boot after IMEI restore
8) Problem:- Boot Loops or Stuck on booting or Force close or lags
9) Problem:- E:Can't mount /dev/block/stl10 (invalid Argument)
10) Problem:- E:format_volume: rfs format failed on /dev/block/stl11
11) Problem:- E:failed to mount /sdcard (File exists)
12) Problem:- E:format_volume: rfs format failed on /dev/block/mmcblk0p2
13) Problem:- E: format_volume: rfs format failed on /dev/block/mmcblk0p1. or E: format_volume: rfs format failed on /dev/block/mmcblk0p2
14) Problem:- Internal SD card UNKNOWN or Unavailable
15) Problem:- Corrupt or incorrect ( FAKE) IMEI number. (International Mobile Equipment Identity)
16) Problem:- No Network and Signal ( calls, sms and mobile Internet not working)
17) Problem:- No base Band or Unknown Baseband
18) Problem:- Sim card lock missing
19) Problem:- HW: Not Active
20) Problem:- E: failed to mount /efs (invalid argument) E: check_selective_file:Can´t mount /efs
21) Problem:- E: failed to mount /efs (invalid argument) install_application_for_customer:Can´t mount /efs copy application failed.
22) Problem:- E: failed to mount /efs (invalid argument) E: multi_csc: Can´t mount /efs Multi-csc applied failed.
23) Problem:- E: failed to mount /dev/block/stl3 or E: failed to mount /dev/block/bml3 corrupted
24) Problem:- BOOT Animation Problems
25) Problem:- Phone completely DEAD, Not Charging and NO response, only this SEC S5PC110 TEST B/D
26) Problem:- ClockWorkMod Recovery Giving Status 0 errors
27) Problem:- ClockWorkMod Recovery giving Status 7 errors
28) Problem:- ClockWorkMod Recovery giving E:unknown volume for path
29) Problem:- RAMDUMP MODE, Cause:Force Upload, in Recovery or Download Mode
30) Problem:- ClockWorkMod Recovery giving "back button disabled"
31) Problem:- ClockWorkMod Recovery giving "MD5 Mismatch"
32) Problem:- Other problems a) Broken screen-need data
33) Other solutions to problems by XDA members (scroll to find out)
For any Softwares, Kits, Recovery Packages, Tools and How to Guides, visit My Android Collections
[0] FIRST STEP for ALL Problems:-
Whenever you have a problem with your Phone, power it down, remove battery, remove SIM card and Ext SD card and press and hold your power button for at least 30 seconds to a min, before reinserting battery and trying any solution
Click to expand...
Click to collapse
This alone can solve many problems that you may have , so DO THIS POWERING DOWN AGAIN FOR EVERY ATTEMPT TO FIX YOUR PROBLEM. Most of all make sure you have at least 80% Battery Charge, when attempting to Flash with Odin and 100% with KIES and follow proper Flashing Guide
M110S Flashing Guide
i9000 Flashing Guide
i9001 Flashing Guide
Click to expand...
Click to collapse
[1] Problem:- Cannot enter Download or Recovery Mode
Solution :-If your phone is booting alright but cannot enter download or recovery mode:- You can download Quick Boot app or Hot Boot app from play Store to get recovery mode in an instant and use update.zip from recovery to flash a 14 panel toggle (from SD card) , which will replace your Notification panel with 14 toggle switches including download and Recovery boot up on one click.
M110S 14 Toggles
i9000 14 Toggles
i9001 14 Toggles
i9100 15 Toggles
Solution:- when Phone can go into recovery but Not download mode and you have CWM, use CWM to boot into Download mode by its Universal Lag Fix menu
Click to expand...
Click to collapse
When Phone cannot boot
Normal SGS i9000 buttons
Normal SGS i9001 Buttons
Normal SGS SHW M110S Buttons
But this can Change in some ROM's like UGKG3, the 3 button combination to get into recovery mode can change from [Power+Volume Up+Home] to Power+CenterofVolume+home]
In ICS recovery mode can change from [volume up+home+power] to [Volume up + down+home+power].
When using windows use this Reboot tool
Click to expand...
Click to collapse
In the event this fails, you should First try
Power down, Pull out Battery, Pull out Sim Card and Ext. SD card, press power button for a Minute than power up again to try the combo buttons again...
(This works for Jelly Bean, when you cannot get into recovery mode but only download mode)
Click to expand...
Click to collapse
IF it Fails again
you can try power down, remove battery, press combo keys and insert battery
1) To enter download mode [volumedown+home+power] or as per your model
2) While in this position, insert the battery
Click to expand...
Click to collapse
If it Fails again
Than you Should try ADB method via your PC
1) Install adb drivers in your PC, (If you don't have one yet)
2) Click on Run on your PC start menu
3) Type:- cmd
4) Type:- adb reboot recovery or adb reboot download
Your phone will go to recovery mode or download mode as typed
Click to expand...
Click to collapse
or you can try some Tools like AndroPlatina Utlity or Easy Reboot at My Android Collection that will try to connect when the phone is powering on. or other methods like mentioned here
Click to expand...
Click to collapse
IF still no luck
Than the JIG will do it, the Home Made USB JIG, can be made by yourself ( like here & here ) or can be bought from ebay or a parts supply store near you or you can borrow one here
Click to expand...
Click to collapse
if the JIG fails, its time to use the JTAG remove the motherboard, connect it to the riff box and flash your version of bootloaders back onto the rom chips directly. If that failed it may be a hardware problem like this
Click to expand...
Click to collapse
Click to expand...
Click to collapse
[2] Problem:- Cannot connect to PC, Unknown Device, getting Code 43 or any other code or NO response when using USB cable
Solution:- USB Problems and Solutions
Click to expand...
Click to collapse
And IF nothing worked and USB connection still fails no matter what, than it would be best to look into this
Click to expand...
Click to collapse
[3] Problem:- Odin gets Stuck on <ID:0/008> Set PIT file. or <ID:0/003> SetupConnection.. or <ID:0/007> Removed!Note:
When using Odin to Flash, Open task manager and close these : Kies.exe , KiesTrayAgent.exe, and KiesPDLR.exe
IF your downloaded File (.tar, .zip, .md5 .rar ) is corrupted, Odin could get stuck too, so download from another source, if it happens repeatedly
Solution:-
First reboot PC after a power cord unplug and also reboot the Phone after a battery pull. Always use a Fresh Odin after any attempt to flash, than make sure you "Uncheck Repartition", If you had checked it or clicked Pit when you are not using one. You should also be running Odin as an Admin and ensure that KIES is not running when using Odin. Most of all, only use Samsung USB cable and not others as they may be incompatible and trying it out on a lap top or another PC ( when it happens repeatedly)
Click to expand...
Click to collapse
[4] Problem:- i9001 Odin 4.43 gets stuck on amss.mbn download.. Note:
When using Odin to Flash, Open task manager and close these : Kies.exe , KiesTrayAgent.exe, and KiesPDLR.exe
IF your downloaded File (.tar, .zip, .md5 .rar ) is corrupted, Odin could get stuck too, so download from another source, if it happens repeatedly
Solution:-
Flash i9001 CWM 6.0 together with AriesVE.ops in Odin 4.43
Click to expand...
Click to collapse
Click to expand...
Click to collapse
[5] Problem:- when upgrading to ICS, Stuck on boot screen
Solution:-When you Flash ICS from GB, Flashing will be quick, after which you should remove and reinsert battery and go to recovery again, to flash the ROM again
Click to expand...
Click to collapse
[6] Problem:- lost my IMEI or changed on upgrading to JB CM 10
Solution:- Reason is you had Jumped from GB to JB (should be on ICS before JB), so now you need to
1) Download Root Explorer, or Xplore, or any root browser from Play Store and use it to
2) Search you internal SD card for sdcard/backup/efs or any other backup you have for your efs
3) Copy nv_data.bin, nv_data.bin.md5 paste them (means overwrite existing files) into /efs in your Internal Phone memory
4) Fix permissions by Click on efs folder and keep it pressed to open the menu and click on permissions and set them to rw_r_r_ ( Owner = read & write - Group = read only and Others = Read only), after this Save using menu and exit using menu
5) Power down phone and reboot into recovery and wipe cache before rebooting phone to get back your original IMEI
or
you can start from the beginning.. go back to GB 2.36 (use a JVU ROM + Root, upgrade to ICS CM 9 and than to CM10 :victory:
Solution for i9000 on JB:-Try not to jump from Gingerbread to Jellybean, as all upgrades should be done progressively. meaning you need to be on a GB 2.3.6> than into ICS and finally into JB.
For others, like missing IMEI, NO service, NO network problems, scroll down to EFS problems and Solutions
Click to expand...
Click to collapse
[7] Problem:- Don't boot after IMEI restore
Solution:- get back into CWM and Fix Permissions
Click to expand...
Click to collapse
Click to expand...
Click to collapse
[8] Problem :- Boot Loops, Booting Problems, Stuck at Boot Screen
Solution:- Boot Loops, Lags and FC's are often caused by not clearing and wiping cache, data and dalvik cache from recovery console prior to and after flashing a new ROM.
Click to expand...
Click to collapse
or
Solution:- Flash a 512 Pit File using Odin3 v1.0 with Repartition unticked (only Odin3 version 1.0 can flash this way)
Click to expand...
Click to collapse
or
Solution:- Flash a 512 PIT FILE with REPARTITION MUST BE UNCHECKED with a kernel or just the kernel
For i9000 on Gingerbread with GB Semaphore Kernel
For i9000 on ICS with ICS Semaphore Kernel phone will Boot up
For i9000 on Jelly Bean Semaphore JB kernel
Click to expand...
Click to collapse
When none of the above solved your problem. its time to flash a Rescue kit from My Android Collections, with a PIT File and Repartition (Ticked)
Click to expand...
Click to collapse
Problem:- i9001 Bootloops after flashing CWM recovery
Solution:- Flash i9001 Boot.tar with AriesVe.ops in Odin 4.43
Click to expand...
Click to collapse
Click to expand...
Click to collapse
[9] Problem:- Getting this when you try to Boot...
E:failed to mount /sdcard (files exists),
E:copy_dbdata_media:Can't mount /sdcard.
E:Can't mount /dev/block/stl10 (invalid Argument)
Solution:-
For Galaxy S - Flash dbdata.rfs to solve this
For M110S - Flash dbdata .rfs to solve
or Flash a Rescue Kit from My Android Collections
Click to expand...
Click to collapse
Click to expand...
Click to collapse
[10] Problem:- Getting this when you boot
E:format_volume: rfs format failed on /dev/block/stl11
Solution:- Flash a cache.rfs file meant for your model as PDA with Odin. For i9000 i9000 cache.rfs file, For M110S M110s Cache.rfs
or Flash a Rescue Kit from My Android Collections
Click to expand...
Click to collapse
Click to expand...
Click to collapse
[11] Problem:- Getting this when you try to Boot...
--copying media files
E:failed to mount /sdcard (File exists)
E:copy_dbdata_media:Can't mount /sdcard
your storage not prepared yet. please use UI menu
for format and reboot actions.
Meida files copy failed.
Solution:- Flash dbdata.rfs as PDA using Odin3
For Galaxy S - Flash dbdata.rfs to solve this
For M110S - Flash dbdata .rfs
IF above did not solve it, try the undermentioned methods
For i9000, Do the full wipes and factory reset First than Flash JVU ROM once with 512 PIT (TICKED) and Auto boot UNTICKED, do not boot, Flash again ROM with 803 PIT (UNTICKED)
or Flash a Rescue Kit from My Android Collections
Click to expand...
Click to collapse
Click to expand...
Click to collapse
[12] Problem:- Getting this when you try to Boot...
E:format_volume: rfs format failed on /dev/block/mmcblk0p2
Solution:- For M110S, follow this guide use repair kit from Pit Stop
For i9000, Do the FULL wipes and factory reset first (formating the Internal SD card will greatly help, so safe all your contacts, images backups to PC or Ext SD card First) Use i9000 Rescue kit with heimdall or on linux , select files as follows...
primary boot > boot.bin
secondary boot > Sbl.bin
repartition > s1_odin_20100512.pit
factoryfs > factoryfs.rfs
cache > cache.rfs
dbdata > dbdata.rfs
param > param.lfs
modem > modem.bin
kernel > zImage
The reboot may request for "Confirm password", just enter any password about 5 times until prompted that, "this will wipe the card." Yes wipe, ..Should solve the problem
If it did not go in recovery by combo keys and wipe all (cache/data/delvick cache) and Flash a JVU+Root with a 512 Pit (repartition ticked) with Odin3 and finally root+CWM as PDA in Odin 3 .
Once rooted with CWM, enter CWM using combo keys or CWM Manger ...here enter "mounts and storage" and format everything except Boot and also do the full wipes one more time
Finally Flash the JVU+Root again one more time with PIT (repartition) to resolve this issue ...in-effect you will be flashing twice or more to solve this
Reason for this is system unable to Format /data... hence on ICS ROM, moving /data to External SD Card will solve this problem
another solution http://www.youtube.com/watch?v=zdMhYYdMB08
Click to expand...
Click to collapse
[ 13 & 14] Problem:-Getting this when you try to Boot...
E: format_volume: rfs format failed on /dev/block/mmcblk0p1. or
E: format_volume: rfs format failed on /dev/block/mmcblk0p2 or
Internal SD card unknown or
Internal SD card Unavailable or
Internal SD card cannot be mounted
Solution:- Read Internal SD card Failure & Failure to undo (lag fix) partition format Vibrant SD switching due to Data wipe error or Can't mount /dev/block/mmcblk0p1, i9001 swap SD cards, i9000 swap SD card and Vold.fstab files for M110S, SGS Plus and N7000
Click to expand...
Click to collapse
Click to expand...
Click to collapse
[15 to 23] Problem:-
1) Corrupt or incorrect ( FAKE) IMEI number. (International Mobile Equipment Identity)
2) No Network and Signal ( calls, sms and mobile Internet not working)
3) No base Band or Unknown Baseband
4) Sim card lock missing
Undermentioned appearing in red on your desktop after phone boots up normally
HW: Not Active
BOOT: SHW-M110S Vj04.1944
PDA:SHW-M110S Vj04.1944
Phone: M110S.VI27.0941.ST
Undermentioned appearing when you try to boot
E: failed to mount /efs (invalid argument)
E: check_selective_file:Can´t mount /efs
Undermentioned appearing when you try to boot
E: failed to mount /efs (invalid argument)
install_application_for_customer:Can´t mount /efs
copy application failed.
Undermentioned appearing when you try to boot
E: failed to mount /efs (invalid argument)
E: multi_csc: Can´t mount /efs
Multi-csc applied failed.
Undermentioned appearing when you try to boot
E: failed to mount /dev/block/stl3 or
E: failed to mount /dev/block/bml3 corrupted
Solution:- Try EFS Problems and Solutions
[Guide] How to get IMEI to stick across reboots
Restore Bml3 for /dev/block/stl3 and / or /dev/block/bml3 problems
Restore Galaxy S2 EFS or EFS.bak
Restore Galaxy S 2 efs
Restore I9000 efs
Click to expand...
Click to collapse
Click to expand...
Click to collapse
[24] Problem:- BOOT Animation Problems
Solution:- Flash Param.lfs file using Odin3
For M110S Param.lfs
For Galaxy i9000 Param.lfs
Click to expand...
Click to collapse
Click to expand...
Click to collapse
[25] Problem:- Phone completely DEAD, Not Charging and NO response, only this SEC S5PC110 TEST B/D
This happens, when boot loader is being flashed and Phone loses power. (Mostly caused by Power failure during Flashing)
Always have above 50% charge when you Flash and NEVER interrupt the process Samsung recommends 100% charge even on KIES
Only Known DO-It-Yourself Solution:-
UnBrickable Resurrector Revision 37 and Developer & Guide
UnBrickable Mod
Final Solution:-
use JTAG (Riff, z3x, medusa, spt etc) to fix broken boot-loader, so take it to your Phone repair shop to resolve
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Continued next post >>>>> Below
Unbricking the Galaxy S [i9000]
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If you are unable to enter download or recovery mode use this guide or this tool or i9000 Easy Reboot Recovery using ADB to get recovery modeIf you have USB connection problems use this guide
Flashing Guide (Follow it to avoid making mistakes)
Unbricking the i9000 can be easily achieved by flashing any of these Rescue kits
Rescue Packages
i9000 Rescue EzBase Rescue and Recovery by nitr8 Full Graphical HOW To and Tutorial download
i9000 Rescue EzBase Rescue with CF Root & semaphore root by nitr8 & chainfire, repacked by slaphead20
i9000 Rescue Rescue Kit for i9000 using heimdall packed by ldq
i9000 Rescue GB Flash Kit packed by psyqiq
i9000 Rescue Darky's ROM Resurrection edition, Guide , Mirror download or here
or any of these ROM's
Upgrade or Downgrade i9000 Stock ROM's (Firmware)
i9000 upgrade or downgrade without changing ROM Ezboot
i9000 Upgrade or Downgrade to GingerBread 2.3.6 ROM JVU + Root with a 512 Pit File (repartition Ticked) Ideal base for upgrading to ICS and J.Bean
i9000 [Deodexed Firmware] Stock XXJVU, Flashed using CWM , zip-aligned and root
i9000 [Deodexed Firmware] Stock XXJVU Flashed using Odin3
i9000 Downgrade to GingerBread 2.3.5 JVT
i9000 Downgrade to Froyo 2.2 JPU
i9000 Downgrade to Eclair 2.1 JM1 Initial Stock ROM, without Combo key functions, use KIES or ADB or JIG for upgrades, Included flash-able FIX for Combo Keys. Eclair XWJM2 - Eclair XWJM3But it may not work on some phones, so we need to flash various other files to solve them (undermentioned files are for JVU ROM)
B+ SBL (primary and secondary Bootloaders is meant for restoring Recovery and download combo buttons as well as boot loader problems, should be flashed as " PDA " with update Phone Boot Loader ticked in Odin3
Param is used for restoring Boot animation, stuck problems, flashed as PDA using Obin3
Cache is for clearing cache flashed as PDA using Odin3
dbdata.rfs is for clearing data flashed as PDA using Odin3
other files that can be used
i9000 2e Recovery
i9000 CWM
i9000 B+SBL.tar
i9000 param.lfs.tar
i9000 cache.rfs.tarCheck this out! Links to useful Guides and " Banned " Documentaries
ClockWorkMod Menu[26] Problem:- ClockworkMod Recovery giving Status 0 error "Installation aborted".
Solution:- Most likely you have a incompatible CWM, or your Zip files are corrupted or you have mounted /system or /data
Click to expand...
Click to collapse
[27] Problem:- ClockworkMod Recovery giving Status 7 error "Installation aborted".
Solution:- One or some of the prerequisite requirement for the needed upgrade is missing or corrupted . So you may need to identify and replace that requirement for the installation to continue. Most likely could be due to wrong bootloader, wrong CWM, Wrong IMEI, Wrong Radio etc
Click to expand...
Click to collapse
[28] Problem:- ClockworkMod Recovery giving E:unknown volume for path [/cache/recovery/command]
Solution:- This is due to the Installed version of CWM on your Phone is incompatible/corrupt so change to another version of CWM
Click to expand...
Click to collapse
[29] Problem:- Getting RAMDUMP MODE, Cause:Force Upload, in Recovery or Download Mode
Reason:- its caused by pressing the combo keys while the device is powering on.
Solution:- 1) By pressing volume+power (2 buttons) and release the buttons after a few seconds when you see the samsung logo.
If It Fails
2) You can try to use ADB to boot into recovery or Download mode. If it Fails
3) You can use this Reboot tool
Click to expand...
Click to collapse
[30] Problem:- ClockworkMod Recovery giving "back button disabled"
Solution:- Just move the cursor 3 times up or down to enable it
Click to expand...
Click to collapse
[31] Problem:- MD5 mismatch, unable to use Nandroid backup
Solution:- Change "nandroid.md5" file found in clockworkmod/backup folder in your SD Card
Use any file explorer with root and read write permission > Open your clockworkmod/backup/nandroid folder you want to use ( that is giving you this error) open folder and scroll to "nandroid.md5" file > Open it and delete everything inside it or you can replace it with an empty file with same name > "Save" that nandroid.md5 file before quitting the app you used to do this function.
Click to expand...
Click to collapse
[32] Other problems
Click to expand...
Click to collapse
Problem:- Broken Screen, need to retrieve data
Solution;- In normal i9001 CWM Version 5 Recovery (if you have other versions, you need to flash version 5 first for this to work)
Enter CWM Recovery mode by using combo keys
Volume Up button pressed "twice" >> Home button pressed "once" >> Volume up button pressed "once" >> USB cable plugged into PC >> will get you USB storage mode. In USB storage mode you can copy and delete files on your SD cards with your PC
For i9000 look at Version of CWM
or CWM ver 6 here and here be warned wrong key press can endup formating your phone (so do it at your own risk) or flash the CWM recovery you are sure of and do the key press
or
ADB Method here or use recoverdata tool
Click to expand...
Click to collapse
[33] Other solutions by XDA members
[FIX] Data wipe error or Can't mount /dev/block/mmcblk0p1
Internal SD card Solutions :- Here & Here & Here
How to Solve Encryption Unsuccessful ICS issue
How to change SMSC
Fix status 6 while flashing ROM
[GUIDE] status 7 error while flashing rom
Play Store No Connection Error Fix
Can't establish a reliable connection to the server
[FIX] Broken cache partition / recovery
Click to expand...
Click to collapse
Click to expand...
Click to collapse
This post is linked to Pit Stop and will be updatedYou , YES! you are an " Android ". Not your phone but U.
You Must watch this documentary concerning your privacy Terms & Conditions we had agreed to, by using a PC or Smartphone
Good post :good:
very helpful, this was missing here and good work, a lot of people use it.
Phone completely DEAD, Not Charging and NO response.... a REQUEST !
xsenman said:
Index to Problems and Solutions mentioned below
1) Problem:- Cannot enter Download or Recovery Mode
2) Problem:- Cannot connect to PC or Unknown Device, getting Code 43 or any other code or NO response when using USB cable
3) Problem:- Odin gets Stuck on <ID:0/008> Set PIT file. or <ID:0/003> SetupConnection.. or <ID:0/007> Removed!
4) Problem:- i9001 Odin 4.43 gets stuck on amss.mbn download..
5) Problem:- When upgrading to ICS, Stuck on boot screen
6) Problem:- Lost my IMEI or changed on upgrading to JB CM 10
7) Problem:- Don't boot after IMEI restore
8) Problem:- Boot Loops or Stuck on booting or Force close or lags
9) Problem:- E:Can't mount /dev/block/stl10 (invalid Argument)
10) Problem:- E:format_volume: rfs format failed on /dev/block/stl11
11) Problem:- E:failed to mount /sdcard (File exists)
12) Problem:- E:format_volume: rfs format failed on /dev/block/mmcblk0p2
13) Problem:- E: format_volume: rfs format failed on /dev/block/mmcblk0p1. or E: format_volume: rfs format failed on /dev/block/mmcblk0p2
14) Problem:- Internal SD card UNKNOWN or Unavailable
15) Problem:- Corrupt or incorrect ( FAKE) IMEI number. (International Mobile Equipment Identity)
16) Problem:- No Network and Signal ( calls, sms and mobile Internet not working)
17) Problem:- No base Band or Unknown Baseband
18) Problem:- Sim card lock missing
19) Problem:- HW: Not Active
20) Problem:- E: failed to mount /efs (invalid argument) E: check_selective_file:Can´t mount /efs
21) Problem:- E: failed to mount /efs (invalid argument) install_application_for_customer:Can´t mount /efs copy application failed.
22) Problem:- E: failed to mount /efs (invalid argument) E: multi_csc: Can´t mount /efs Multi-csc applied failed.
23) Problem:- E: failed to mount /dev/block/stl3 or E: failed to mount /dev/block/bml3 corrupted
24) Problem:- Problem:- BOOT Animation Problems
25) Problem:- Phone completely DEAD, Not Charging and NO response, only this SEC S5PC110 TEST B/D
For any Softwares, Kits, Recovery Packages, Tools and How to Guides, visit My Android Collections
Hello,
i have a request. Plz make a jtag video about this phone. In here many shops said korean phone is different and boot loader repair via jtag takes time and confuse in this phone, i think its same to fix bootloader via jtag in all samsung phones.
If you make a video showing the jtag process on this phone so it will be very awesome. I shall be really thankful to you.
Please make it possible,as soon as possible.
Thanks
This post is linked to Pit Stop and will be updated
Click to expand...
Click to collapse
sd
A Request Please!
Hello,
i have a request. Plz make a jtag video about this phone. In here many shops said korean phone is different and boot loader repair via jtag takes time and confuse in this phone, i think its same to fix bootloader via jtag in all samsung phones.
If you make a video showing the jtag process on this phone so it will be very awesome.or make a video in which Adam Outler's Method is used in Galaxy M11os .I shall be really thankful to you.
Please make it possible,as soon as possible.
Thanks
xsenman said:
Index to Problems and Solutions mentioned below
0) All Problems :- Do the First Step - can solve many problems that you may have
1) Problem:- Cannot enter Download or Recovery Mode
2) Problem:- Cannot connect to PC or Unknown Device, getting Code 43 or any other code or NO response when using USB cable
3) Problem:- Odin gets Stuck on <ID:0/008> Set PIT file. or <ID:0/003> SetupConnection.. or <ID:0/007> Removed!
4) Problem:- i9001 Odin 4.43 gets stuck on amss.mbn download..
5) Problem:- When upgrading to ICS, Stuck on boot screen
6) Problem:- Lost my IMEI or changed on upgrading to JB CM 10
7) Problem:- Don't boot after IMEI restore
8) Problem:- Boot Loops or Stuck on booting or Force close or lags
9) Problem:- E:Can't mount /dev/block/stl10 (invalid Argument)
10) Problem:- E:format_volume: rfs format failed on /dev/block/stl11
11) Problem:- E:failed to mount /sdcard (File exists)
12) Problem:- E:format_volume: rfs format failed on /dev/block/mmcblk0p2
13) Problem:- E: format_volume: rfs format failed on /dev/block/mmcblk0p1. or E: format_volume: rfs format failed on /dev/block/mmcblk0p2
14) Problem:- Internal SD card UNKNOWN or Unavailable
15) Problem:- Corrupt or incorrect ( FAKE) IMEI number. (International Mobile Equipment Identity)
16) Problem:- No Network and Signal ( calls, sms and mobile Internet not working)
17) Problem:- No base Band or Unknown Baseband
18) Problem:- Sim card lock missing
19) Problem:- HW: Not Active
20) Problem:- E: failed to mount /efs (invalid argument) E: check_selective_file:Can´t mount /efs
21) Problem:- E: failed to mount /efs (invalid argument) install_application_for_customer:Can´t mount /efs copy application failed.
22) Problem:- E: failed to mount /efs (invalid argument) E: multi_csc: Can´t mount /efs Multi-csc applied failed.
23) Problem:- E: failed to mount /dev/block/stl3 or E: failed to mount /dev/block/bml3 corrupted
24) Problem:- BOOT Animation Problems
25) Problem:- Phone completely DEAD, Not Charging and NO response, only this SEC S5PC110 TEST B/D
For any Softwares, Kits, Recovery Packages, Tools and How to Guides, visit My Android Collections
This post is linked to Pit Stop and will be updated
Click to expand...
Click to collapse
awaisdbz said:
Hello,
i have a request. Plz make a jtag video about this phone. In here many shops said korean phone is different and boot loader repair via jtag takes time and confuse in this phone, i think its same to fix bootloader via jtag in all samsung phones.
If you make a video showing the jtag process on this phone so it will be very awesome.or make a video in which Adam Outler's Method is used in Galaxy M11os .I shall be really thankful to you.
Please make it possible,as soon as possible.
Thanks
Click to expand...
Click to collapse
sorry, I don't have a broken M110S or a JTAG box to do video for you
Oh...
xsenman said:
sorry, I don't have a broken M110S or a JTAG box to do video for me
Click to expand...
Click to collapse
Its Ok but Can you ask anyone?
awaisdbz said:
Its Ok but Can you ask anyone?
Click to expand...
Click to collapse
Register and post your request here http://forum.gsmhosting.com/vbb/f258/ these are mobile technicians with many kinds of boxes to solve varying problems
Solved.
Solved my few problems with this guide. Thanks.
Problems after trying First Step for all Problems
After Googling an issue I was having with my Nexus S phone, it directed me here. Unfortunately, I didn't notice this guide was specifically for Galaxy phones. After trying the First Step you mentioned (Remove battery, press power button for 30 sec, etc), I powered up my phone to see that it no longer recognizes the SIM card. My other phones will work with the SIM so it has to be an issue with the phone after performing the above sequence. I tried doing a factory reset, which fixed the original problem I was having, but the phone is useless at this point. I'm hoping there's a simple explanation and fix. Any ideas? Thanks.
---------- Post added at 06:05 PM ---------- Previous post was at 05:15 PM ----------
I knew there was a simple explanation...I'm an idiot for putting the SIM card in backwards (in my defence, it goes in the other way in my other phone). Thanks.
cammy7 said:
I knew there was a simple explanation...
Click to expand...
Click to collapse
well, you are not the first ( I know of at least of ten others ) and there will be many more, as the directions to insert sim is very vague in these phones and the sim holder is not designed to reject wrong insertion
Help please!
Hi!
I just want to know that,
when I installed Tegrak Kernel (Root) and whenever I reboot my phone, it always shows the T kernel menu.
What I want is that, I don't want it to show and I want the original boot menu back (M110S Anycall)
Is it possible it do it? If yes, how?
And one thing is that, I accidently deleted Titanium Backup file containing system apps from the internal SD and lost all the phone's system backup apps. (Like User Dictionary, Gallery, etc.)
Is there anyway to reinstall those phone system apps? If yes, how?
yunantidus said:
I just want to know that,
Click to expand...
Click to collapse
sorry, you need to post this in M110S thread for all maters related to M110S. We need to be organized...please post there
This is a wonderful solution guid.
As you mentioned your guid in another thread to me, I have to tell you that you're at least in parts wrong about IMEI lost.
It's not true that IMEI lost depends on the update path only. I lost it both times from GB2.3.6 > 4.0.4 and GB2.3.6 > 4.1.1 and 4.0.4 (already lost) > 4.1.1 doesn't recover it of course. My 2.3.6 efs dir contains 14 files + 2 dirs at this moment (e.g. imei, mac + some security files) and the mentioned solution only describes to backup 3 imei files - so there would be something missing.
The problem is, that even with root-feature enabled file explorers you simply can't copy & save all these files. The only solution I found was using terminal + dd (sector disk dump).
Hayabusa_XDA said:
It's not true that IMEI lost depends on the update path only. I lost it both times from GB2.3.6 > 4.0.4 and GB2.3.6 > 4.1.1 and 4.0.4 (already lost) > 4.1.1 doesn't recover it of course.
Click to expand...
Click to collapse
read this post, quote:- It is clear that Flashing custom ROMS can cause your IMEI to Change or get deleted ....
Hayabusa_XDA said:
My 2.3.6 efs dir contains 14 files + 2 dirs at this moment (e.g. imei, mac + some security files) and the mentioned solution only describes to backup 3 imei files - so there would be something missing.
The problem is, that even with root-feature enabled file explorers you simply can't copy & save all these files. The only solution I found was using terminal + dd (sector disk dump).
Click to expand...
Click to collapse
This is what I had mentioned in that post
1) You can use an application Like EFS Pro developed by an XDA member lyriquidperfection
2) S2 repair or Nitrility or GPS AIDS apps from google (Its Free)
3) Or use a Root Explorer to Zip it and save it in another location
apparently you have misread it
But to overwrite the IMEI, you only need the 3 files mentioned on this thread .
Can't establish a reliable connection to the server
Please ADD these Solution...
Maybe it Work.
worked on me...
http://forum.xda-developers.com/showthread.php?t=772718&page=598
Problem:- Getting this when you try to Boot...
--copying media files
E:failed to mount /sdcard (File exists)
E:copy_dbdata_media:Can't mount /sdcard
your storage not prepared yet. please use UI menu
for format and reboot actions.
Meida files copy failed.
Solution:- For i9000, Do the full wipes and factory reset First than Flash JVU ROM once with 512 PIT (TICKED) and Auto boot UNTICKED, do not boot, Flash again ROM with 803 PIT (UNTICKED)
or Flash a Rescue Kit from My Android Collections
Click to expand...
Click to collapse
Hi I can't understand this procedure: at first I have to flash the ROM with repartition and then I have to flash again the ROM without repartition? (In this last case, why I have to use 803 PIT?)
I'm very grateful for this guide because I am trying to fix this problem since one week! I'm an italian user and I hope that this is the right way!
Ps. sorry for my bad english
bricked samsung galaxy s anycall
hi, i hope you can help. i think i bricked my friends phone after trying to root. after rooting, it was stuck in boot loop. so i followed your instructions but forgot to uncheck the Re-Partition box when using the Pit file. now am stuck in screen image with "Upgrade" and some Korean or Chinese characters..
This post is linked to Pit Stop and will be updated[/QUOTE]
I recently rooted my Samsung Galaxy S GTI9000 ZSJW4 with SuperOneClickv2.3.3-ShortFuse & flashed Semaphore_2.7.4 with Odin3 v3.04. Then updated to cm-10.0.0-galaxysmtd with Semaphore CWM Recovery V5.0.2.7. Everything went well.
Before these steps, I did a backup and saved in my Pc. and then did another backup after i flashed everything, it was working just fine until I tried to restore it using my first backup where everything got messed up. It seemed to complete the restoration from backup just fine, but after I rebooted it from CWM. On startup the bootlogo blinked once and went straight back into recovery which I wasn't expecting. And this is what it shows up on recovery.
Semaphore CWM Recovery C5.0.2.7
-----------------------------------------------------------------------------------------
E:failed to open /etc/recovery.fstab (No such file or directory)
E:unknown volume for path [/cache/recovery/command]
E:Can't mount /cache/recovery/command
E:unknown volume for path [/cache/recovery/log]
E:Can't mount /cache/recovery/log
E:unknown volume for path [/cache/recovery/last_log]
E:Can't mount /cache/recovery/last_log
E: Can't open /cache/recovery/last_log
E:unknown volume for path [/cache/recovery/command]
-------------------------------------------------------------------------------------------------------
(This keeps on coming up every time i reboot , I still have access to download mode and recovery, thats about it, not further than that)
I am not sure what caused this, I have tried to find posts on similar issues and haven't come across any that explains clearly how to fix the issue:
Can somebody please explain what part I went wrong and perhaps someway to fix it?
Any help will be greatly appreciated!
ahadh.h4x0r said:
I recently rooted my Samsung Galaxy S GTI9000 ZSJW4 with SuperOneClickv2.3.3-ShortFuse & flashed Semaphore_2.7.4 with Odin3 v3.04. Then updated to cm-10.0.0-galaxysmtd with Semaphore CWM Recovery V5.0.2.7. Everything went well.
Before these steps, I did a backup and saved in my Pc. and then did another backup after i flashed everything, it was working just fine until I tried to restore it using my first backup where everything got messed up. It seemed to complete the restoration from backup just fine, but after I rebooted it from CWM. On startup the bootlogo blinked once and went straight back into recovery which I wasn't expecting. And this is what it shows up on recovery.
Semaphore CWM Recovery C5.0.2.7
-----------------------------------------------------------------------------------------
E:failed to open /etc/recovery.fstab (No such file or directory)
E:unknown volume for path [/cache/recovery/command]
E:Can't mount /cache/recovery/command
E:unknown volume for path [/cache/recovery/log]
E:Can't mount /cache/recovery/log
E:unknown volume for path [/cache/recovery/last_log]
E:Can't mount /cache/recovery/last_log
E: Can't open /cache/recovery/last_log
E:unknown volume for path [/cache/recovery/command]
-------------------------------------------------------------------------------------------------------
(This keeps on coming up every time i reboot , I still have access to download mode and recovery, thats about it, not further than that)
I am not sure what caused this, I have tried to find posts on similar issues and haven't come across any that explains clearly how to fix the issue:
Can somebody please explain what part I went wrong and perhaps someway to fix it?
Any help will be greatly appreciated!
Click to expand...
Click to collapse
These links may be helpful:
- Flashing To Original Rom - Using Odin on GT-i9000
- Flashing To Original Rom - Using Heimdall on GT-i9000
- Rooting GT-I9000 2.3.3 [DDJV9]
flash darky 10.2 re
http://www.darkyrom.com/index.php?threads/darkyrom-first-aid.8178/
see if that works
gopalasubramanium said:
These links may be helpful:
- wwwfixmystuff dot in/FMS_Forum/threads/samsung-galaxy-s-gt-i9000-flashing-to-original-rom-using-odin.46/"
Flashing To Original Rom - Using Odin on GT-i9000
]
Click to expand...
Click to collapse
I tried your first link /Odin,
After it reboots, it goes into Android system recovery and this shows up:
E:failed to mount /dbdata (Invalid argument)
-- Copying media files...
E:failed to mount /dbdata (files exists)
E:copy_dbdata_media: Can't mount /dbdata
your storage not prepared yet, please use UI menu for format and reboot actions.
Meida files copy failed.
# MANUAL MODE #
--Applying Multi-CSC...
Installing Multi-CSC
Can't access to '/system/csc/TGY/system/'.
Successfully applied multi-CSC.
gopalasubramanium said:
These links may be helpful:
"fixmystuff in/FMS_Forum/threads/samsung-galaxy-s-gt-i9000-flashing-to-original-rom-using-odin.46/"]Flashing To Original Rom - Using Odin on GT-i9000
"fixmystuff in/FMS_Forum/threads/samsung-galaxy-s-gt-i9000-flashing-to-original-rom-using-heimdall.126/"]Flashing To Original Rom - Using Heimdall on GT-i9000
"fixmystuff in/FMS_Forum/threads/samsung-galaxy-s-gt-i9000-rooting-gt-i9000-2-3-3-india-ddjv9.47/"]Rooting GT-I9000 2.3.3 [DDJV9]
Click to expand...
Click to collapse
I tried the steps on your second post:
docsgoogle/open?id=0B67As4gsEH4XODdZSnhMMGtaUEU
Step 1: Start Odin
Step 2:
a. Select PIT file as 's1_odin_20100513.pit'
b. Select PDA file as 'PDA_DXJV9_Deodexed_Zipaligned.tar'
c. Select PHONE file as 'PHONE_DXJV9.tar'
d. Select CSC file as 'CSC_OLBJV9.tar'
Step 3: Under Options: Check Re-partition, Check Auto Reboot and Check F. Reset Time
Step 4: Start the phone in the download mode
Step 5: Once ID:COM/phone is 'Added!!' click Start
Step 6: You will see a lot of red text after the flash is done, don't panic, just do a 'wipe data/factory reset' and reboot the device when done.
Step 7: Let the device boot all the way then turn it off.
Step 8: Re-enter Download Mode and re-flash only the CSC file [Step 2 d] without pit and without re-partition.
It should work now...ENJOY
THIS WORKS!
where is the lockscreen file of a rom?and whats its name?
and the wallpapers of the rom?
Hi, I hope some can help me
Here´s my story, the phone is a Galaxy Ace GT-S5830m, that had GingerBread 2x, I wanted to take it to Kit kat 4x, then I downloaded the CWM 6.0.4.6, but, because of my ignorance, I didn't downloaded the KitKat rom file at the same time, I successfully installed the CWM file, but after this the phone won't boot. The only thing it does is:
Enter recovery mode by pressing Volume Up+Home+Power
Show the Samsung logo
But I cannot make it enter download mode, if I hit VolumeDown+Home+Power it just shows the Samsung logo
If I connect it to the PC via USB cable, the PC won't recognize the phone on the USB drivers list. I already downloaded the Samsung USB drivers
When I enter recovery mode I see the four options for
rebbot system now
apply update from sdcard
wipe date/factory reset
wipe cache partition
And below that I see --Appling Multi-CSC --
E:failed to mount /system (Invalid argument)
E:failed to mount /system (Invalid argument)
What can I do? I'm I done? Please help! Thanks!
egomezmx said:
Hi, I hope some can help me
Here´s my story, the phone is a Galaxy Ace GT-S5830m, that had GingerBread 2x, I wanted to take it to Kit kat 4x, then I downloaded the CWM 6.0.4.6, but, because of my ignorance, I didn't downloaded the KitKat rom file at the same time, I successfully installed the CWM file, but after this the phone won't boot. The only thing it does is:
Enter recovery mode by pressing Volume Up+Home+Power
Show the Samsung logo
But I cannot make it enter download mode, if I hit VolumeDown+Home+Power it just shows the Samsung logo
If I connect it to the PC via USB cable, the PC won't recognize the phone on the USB drivers list. I already downloaded the Samsung USB drivers
When I enter recovery mode I see the four options for
rebbot system now
apply update from sdcard
wipe date/factory reset
wipe cache partition
And below that I see --Appling Multi-CSC --
E:failed to mount /system (Invalid argument)
E:failed to mount /system (Invalid argument)
What can I do? I'm I done? Please help! Thanks!
Click to expand...
Click to collapse
Hi
Flash a custom recovery like cwm v5 n then erase all like data sytem etc then download the .zip file that roots ur fone n flash it n then do a wipe data n thn place any custom rom of ur device n flash. . . If dsnt wrk do tl me
Hit Thanks
more questions
Raakib Zargar said:
Hi
Flash a custom recovery like cwm v5 n then erase all like data sytem etc then download the .zip file that roots ur fone n flash it n then do a wipe data n thn place any custom rom of ur device n flash. . . If dsnt wrk do tl me
Hit Thanks
Click to expand...
Click to collapse
Hi Raakib, thanks for taking the time to answer! But how can I put the cwm v5 in the phone if the PC doesn't see the phone? Sorry for the basic questions? I'm new in this things. The first time I did this I pluged the phone to the PC and I was able to see the memory card in the windows explorer so I only did a drag and drop, but that doesn't work any more, please advice, thanks!
just do 1 thing download the recovery file on your pc and then plug your sd card using any sort of card reader and then copy the file to memory card . Then insert the memory card in the phone and go to recovery and flash it. Hit thanks.
---------- Post added at 03:30 AM ---------- Previous post was at 03:28 AM ----------
if u want that your pc should recognize your phone, take it to download mode and see it gets detected in odin or not , if not then swap the drivers maybe upgrade or downgrade.
still no luck
Raakib Zargar said:
just do 1 thing download the recovery file on your pc and then plug your sd card using any sort of card reader and then copy the file to memory card . Then insert the memory card in the phone and go to recovery and flash it. Hit thanks.
---------- Post added at 03:30 AM ---------- Previous post was at 03:28 AM ----------
if u want that your pc should recognize your phone, take it to download mode and see it gets detected in odin or not , if not then swap the drivers maybe upgrade or downgrade.
Click to expand...
Click to collapse
Hi Raakib, just to let you know that I haven't had any luck with this, this is what I have tried, with a memory card reader connect to my PC, because the PC still doesn't see the phone
Using CWM v5.0.2.6 and with that version trying to install the original rom I get this
-- Installing: /sdcard/Downloads/S5830MUMnD1_S5830MTCEND1_TCE.zip
Finding update package...
Opening update package...
Installing update...
Installation aborted.
So my attempt to recover gingerbread was unsuccessful, now, in all honesty I have no idea if I'm using the correct zip file of gingerbread, I mean, I downloaded from the sammobile page and choose the one for my country, but the instructions call for odin and to unzip the fiel, so I don't know if this zip file can just be copied to the SDcard and be unziped with CWM. So CMW needs special rom files different from the ones odin uses?
On my second attempt using CWM 6.0.4.6 to try to install kit kat 4.4 using the instructions from the androidcure website called "How to install Android KitKat on Samsung Galaxy Ace S5830", it mentions that I must use cwm v6 and the rom file called cm-11.0.0-RC4-GT-S5830-cooper-PS.zip I get this
-- Install /sdcard/Downloads ...
Finding update package...
Opening update package...
This package is for "cooper.GT-S5830" devices: this is a "".
E:Error in /tmp/sideload/package.zip
(status 7)
Installation aborted
If I use cwm v5 to try to mount /system (which is permanently un-mounted) I get this
mount: mounting /dev/block/stl9 on /system failed: Invalid argument
W:failed to mount /dev/block/stl9 (File exists)
W:failed to mount /dev/blockstl9 (no such device)
Error mounting system!
The phone still won't go in download mode and is still not visible by the PC
Any other suggestion? Thanks!!!!
egomezmx said:
Hi Raakib, just to let you know that I haven't had any luck with this, this is what I have tried, with a memory card reader connect to my PC, because the PC still doesn't see the phone
Using CWM v5.0.2.6 and with that version trying to install the original rom I get this
-- Installing: /sdcard/Downloads/S5830MUMnD1_S5830MTCEND1_TCE.zip
Finding update package...
Opening update package...
Installing update...
Installation aborted.
So my attempt to recover gingerbread was unsuccessful, now, in all honesty I have no idea if I'm using the correct zip file of gingerbread, I mean, I downloaded from the sammobile page and choose the one for my country, but the instructions call for odin and to unzip the fiel, so I don't know if this zip file can just be copied to the SDcard and be unziped with CWM. So CMW needs special rom files different from the ones odin uses?
On my second attempt using CWM 6.0.4.6 to try to install kit kat 4.4 using the instructions from the androidcure website called "How to install Android KitKat on Samsung Galaxy Ace S5830", it mentions that I must use cwm v6 and the rom file called cm-11.0.0-RC4-GT-S5830-cooper-PS.zip I get this
-- Install /sdcard/Downloads ...
Finding update package...
Opening update package...
This package is for "cooper.GT-S5830" devices: this is a "".
E:Error in /tmp/sideload/package.zip
(status 7)
Installation aborted
If I use cwm v5 to try to mount /system (which is permanently un-mounted) I get this
mount: mounting /dev/block/stl9 on /system failed: Invalid argument
W:failed to mount /dev/block/stl9 (File exists)
W:failed to mount /dev/blockstl9 (no such device)
Error mounting system!
The phone still won't go in download mode and is still not visible by the PC
Any other suggestion? Thanks!!!!
Click to expand...
Click to collapse
the stock/original rom wont flash in the recovery. try to flash some other custom rom in CWM 5 and before flahing any rom you need to do a full factory reset and whether in cwm5 or 6 i m nt sure go into advance and wipe efs etc there then flash a rom. If still nothing then contact me i will tell you some great thing +918715031141. (my personal number)