Good afternoon. I need help, URGENT!
I can say that I have some experience with S2, S3 and S4 currently with sufficient skills to perform upgrades, installations, restorations.
What happens, that recently got an S I9070 Advantage and how it was decided to perform the ROM 2.3.6 update to the ROM with CSC DBT latest 4.1.2.
Update fallhou to restart the first time (when you enter the recovery mode to format the cell) appeared the following error message:
E: failed to mount / efs (invalid argument)
E: failed to mount / efs (invalid argument)
# MANUAL MODE #
- Appling Multi-CSC ...
Applied the CSC-code: unknow
Successfully applied multi-CSC.
E: failed to mount / efs (invalid argument)
E: Can not mount / efs / log / boot_cause
E: Can not open / dft / log / boot_cause
Restarted manually and when you perform the initial settings of the Samsung, I get an alert with the following error:
The process com.google.process.gapps has stopped
Clicking Ok and proceed with the setup, but once you get to the last step I get the following error:
The SecSetupWizard stopped.
I click OK again, but this time returns the option to choose the language, making it impossible to access the cell.
Performed the downgrade to 2.3.6 it starts, it works normally, have the IMEI BACKUP, but I can not restore, need a form, a script to format the phone completely, even if you delete the IMEI.
Nor is it possible to install any CUSTOM ROM. Only this version that comes with the file. PIT, CSC and CODE.
Does anyone have a light, guidance?!
I look back.
Which firmwares were they exactly?
Sent from whatever the hell you want to think it is. I ain't yo mama.
I do not know the exact version 2.3.6 had, considering I got this phone yesterday. And knowledge to update other models, such as S2, S3, S4've downloaded the FW-Updates.com-Samsung GT-I9070-DBT-I9070XXLQE-1365486223 and gave this error when installing.
I found a complete FW Forum here to perform the downgrade, did, went back to GB, the phone works as usual, however, when you first start the errors appears to start in recovery mode:
E:failed to mount /efs (No such file or directory)
E:failed to mount /efs (Invalid argument)
E:failed to mount /efs (Invalid argument)
E:check_selective_file:Can't moun /efs
-- Copyng media files...
E:failed to mount /efs (invalid argument)
Sucessfully copied media files.
# MANUAL MODE #
-- Updating application...
Copying Contents.
Successfully updated application.
-- Appling Multi-CSC...
E:failed to mount /efs (Invalid argument)
E:multi_csc:Can't mount /efs
Multi-csc applied failed.
The following report from ODIN - Downgrade 2.3.6.
Added <ID:0/005>!
<OSM> Enter CS for MD5 ..
<OSM> Check MD5 .. Do not unplug the cable ..
<OSM> Please wait ..
<OSM> CODE_GT-I9070_I9070DXLD1_CL1068093_REV00_user_SEC_KEY_LD1_8G.tar.md5 is valid.
<OSM> CSC_GT-I9070-MULTI-CSC-OLBLD1_SEC_KEY_8G.tar.md5 is valid.
<OSM> Checking MD5 finished sucessfully ..
<OSM> Leave CS ..
<ID:0/005> Odin v.3 engine (ID: 5) ..
<ID:0/005> File analysis ..
<ID:0/005> SetupConnection ..
<ID:0/005> Initialzation ..
<ID:0/005> Set PIT file ..
<ID:0/005> DO NOT TURN OFF TARGET!
<ID:0/005> Get PIT for mapping ..
<ID:0/005> Firmware update start ..
<ID:0/005> GT-I9070_EUR_XX_8G.pit.md5
<ID:0/005> NAND Write Start!
<ID:0/005> EFS.img.md5
<ID:0/005> STE_boot.bin.md5
<ID:0/005> Cspsa.img.md5
<ID:0/005> Ipl.bin.md5
<ID:0/005> Kernel.bin.md5
<ID:0/005> Kernel2.bin.md5
<ID:0/005> Mem_init.bin.md5
<ID:0/005> Modem.bin.md5
<ID:0/005> Modemfs.img.md5
<ID:0/005> Normal.bin.md5
<ID:0/005> Normal2.bin.md5
<ID:0/005> Param.lfs.md5
<ID:0/005> Power_management.bin.md5
<ID:0/005> Ssgtest.img.md5
<ID:0/005> System.img.md5
<ID:0/005> Ums.rfs.md5
<ID:0/005> Userdata.img.md5
<ID:0/005> GT-I9070_EUR_XX_8G.pit.md5
<ID:0/005> Cache.img.md5
<ID:0/005> Hidden.img.md5
<ID:0/005> RQT_CLOSE!
<ID:0/005> RES OK!
<ID:0/005> Completed ..
<OSM> All threads completed. (Succeed 1 / failed 0)
Added <ID:0/003>!
The ODIN steps were right....but why do you have so much efs errors? Is your phone network locked?
Sent from whatever the hell you want to think it is. I ain't yo mama.
Cell functioning normally to return to GB, JB but it does not start. Dandos the errors mentioned in the first post (The process com.google.process.gapps has stopped and The SecSetupWizard stopped.) Getting a constant loop. I need a solution to completely erase (the S2 / S3 / S4 - there is a script that does all this procedure, but this model did not find anything.
I have the backup of the IMEI (if it is corrupted) and the program EFS_Pro_1.9.12_Release even in the most current version EFS_Professional_2.0.40_Release gives error when trying to restore.
The EFS errors are because the S Advance has a special way of storing the EFS, much different from the SII.
But EFS errors are not my forte, hopefully someone will be able to help you out.
Sent from my GT-I9070P
Installing the JB by ODIN:
<OSM> Enter CS for MD5 ..
<OSM> Check MD5 .. Do not unplug the cable ..
<OSM> Please wait ..
<OSM> I9070VJLPD_I9070ZTMLPD_I9070VJLPD_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished sucessfully ..
<OSM> Leave CS ..
Added <ID:0/005>!
<ID:0/005> Odin v.3 engine (ID: 5) ..
<ID:0/005> File analysis ..
<ID:0/005> SetupConnection ..
<ID:0/005> Initialzation ..
<ID:0/005> Get PIT for mapping ..
<ID:0/005> Firmware update start ..
<ID:0/005> cache.img.md5
<ID:0/005> NAND Write Start!
<ID:0/005> hidden.img.md5
<ID:0/005> kernel2.bin.md5
<ID:0/005> kernel.bin.md5
<ID:0/005> modem.bin.md5
<ID:0/005> normal.bin.md5
<ID:0/005> param.lfs.md5
<ID:0/005> power_management.bin.md5
<ID:0/005> system.img.md5
<ID:0/005> RQT_CLOSE!
<ID:0/005> RES OK!
I don't see any problem.....weird....
Sent from my GT-I9070P
SOLVED!! (Y)
SOLVED!
Procedure:
1) If you are with a Gingerbread rom, first have to migrate to a Jelly Bean
2) Now that you're with Jelly Bean, download the CWM Temporary, extract the files to a folder of your choice and move to your memory card.
3) Unplug the device and plug it into recovery mode
volume p / up + home + power
4) Select using the volume button the option "Apply update from external storage" and press the power
5) It will open a list with several folders and files, now navigate to the "CWM.zip" and press power again
6) It started to install and the phone screen goes all hazy, wait 5 seconds, press HOME and wait about 3 seconds will open the CWM version in "Touch"
7) Select "Wipe Cache"
8) Now select "advanced", then select "fix permissions"
9) Select "reboot system", a counter appears never ending, this time take out the battery and restart the device in recovery mode
10) The error message should no longer appear, now just install the Stock ROM Jelly Bean desired.
Likely that when you have finished installing the ROM it goes straight to the home screen, without showing that the initial setup screen.
In this case, only those who have backup EFS folder do the following:
1) To make the procedure you need to have installed on the device Es File Explorer and access to ROOT
2) Copy the contents of folder EFS backup that you did and put inside the folder / efs of your device. If asked if you want sobscrever content, press OK.
3) Made the above procedures, unplug the unit and plug into recovery mode
4) Do Wipe Data / Wipe Cache and Factoy
5) Now elecione using the volume button the option "Apply update from external storage" and press the power
6) It will open a list with several folders and files, now navigate to the "CWM.zip" and press power again
7) It started to install and the phone screen goes all hazy, wait 5 seconds, press HOME and wait about 3 seconds will open the CWM version in "Touch"
8) Now select "advanced", then select "fix permissions"
9) Select "reboot system", a counter appears never ending, this time take off the battery switch on the phone normally.
10) You should open on the screen of your initial system configuration.
Download CWM: http://j.mp/cwm-temporario
Source: http://migre.me/flwBA
tiirabello said:
SOLVED!
Procedure:
1) If you are with a Gingerbread rom, first have to migrate to a Jelly Bean
2) Now that you're with Jelly Bean, download the CWM Temporary, extract the files to a folder of your choice and move to your memory card.
3) Unplug the device and plug it into recovery mode
volume p / up + home + power
4) Select using the volume button the option "Apply update from external storage" and press the power
5) It will open a list with several folders and files, now navigate to the "CWM.zip" and press power again
6) It started to install and the phone screen goes all hazy, wait 5 seconds, press HOME and wait about 3 seconds will open the CWM version in "Touch"
7) Select "Wipe Cache"
8) Now select "advanced", then select "fix permissions"
9) Select "reboot system", a counter appears never ending, this time take out the battery and restart the device in recovery mode
10) The error message should no longer appear, now just install the Stock ROM Jelly Bean desired.
Likely that when you have finished installing the ROM it goes straight to the home screen, without showing that the initial setup screen.
In this case, only those who have backup EFS folder do the following:
1) To make the procedure you need to have installed on the device Es File Explorer and access to ROOT
2) Copy the contents of folder EFS backup that you did and put inside the folder / efs of your device. If asked if you want sobscrever content, press OK.
3) Made the above procedures, unplug the unit and plug into recovery mode
4) Do Wipe Data / Wipe Cache and Factoy
5) Now elecione using the volume button the option "Apply update from external storage" and press the power
6) It will open a list with several folders and files, now navigate to the "CWM.zip" and press power again
7) It started to install and the phone screen goes all hazy, wait 5 seconds, press HOME and wait about 3 seconds will open the CWM version in "Touch"
8) Now select "advanced", then select "fix permissions"
9) Select "reboot system", a counter appears never ending, this time take off the battery switch on the phone normally.
10) You should open on the screen of your initial system configuration.
Download CWM: http://j.mp/cwm-temporario
Source: http://migre.me/flwBA
Click to expand...
Click to collapse
this really can be solved?
Efs.img help
This procedure actually works if done with the files available in the posting. In my case solved this problem, but now face a bigger problem. My backup IMEI is corrupted, and you can not restore it.
I need a file EFS.img to perform some tests. Someone with courage and willingness to send me that file?!
HELP
Didn't work for me :crying:
PLS HELP
I did every step till 10 but after i can't continue cause secsetup wizard had stopped!!!
Sorry if im n00b
Help
I get my imei with *#06# (the correct).And i can phone others,so guess there is no problem with the efs folder :S
2.3.6 runs gr8 but 4.1.2 still doesn't.Help me!!!!!!
God....Tussi great hooo....
It worked perfectly......saved my phone....:good:
tgabor7 said:
I get my imei with *#06# (the correct).And i can phone others,so guess there is no problem with the efs folder :S
2.3.6 runs gr8 but 4.1.2 still doesn't.Help me!!!!!!
Click to expand...
Click to collapse
Hi, tgabor , I had exactly same problem, I have tried everything, finally I have come to the conclusion that it can be solved by service centre or some tools like octopus box. Buying those tools are costly option. I have taken my phone to service centre after flashing jb(my phone was in warranty) and they repair it within one day for free . before going to service centre you should wipe your custom rom count using triangle away. You can see your count in download mode.
Sent from my GT-I9070 using XDA Free mobile app
tiirabello said:
SOLVED!
Procedure:
1) If you are with a Gingerbread rom, first have to migrate to a Jelly Bean
2) Now that you're with Jelly Bean, download the CWM Temporary, extract the files to a folder of your choice and move to your memory card.
3) Unplug the device and plug it into recovery mode
volume p / up + home + power
4) Select using the volume button the option "Apply update from external storage" and press the power
5) It will open a list with several folders and files, now navigate to the "CWM.zip" and press power again
6) It started to install and the phone screen goes all hazy, wait 5 seconds, press HOME and wait about 3 seconds will open the CWM version in "Touch"
7) Select "Wipe Cache"
8) Now select "advanced", then select "fix permissions"
9) Select "reboot system", a counter appears never ending, this time take out the battery and restart the device in recovery mode
10) The error message should no longer appear, now just install the Stock ROM Jelly Bean desired.
Likely that when you have finished installing the ROM it goes straight to the home screen, without showing that the initial setup screen.
In this case, only those who have backup EFS folder do the following:
1) To make the procedure you need to have installed on the device Es File Explorer and access to ROOT
2) Copy the contents of folder EFS backup that you did and put inside the folder / efs of your device. If asked if you want sobscrever content, press OK.
3) Made the above procedures, unplug the unit and plug into recovery mode
4) Do Wipe Data / Wipe Cache and Factoy
5) Now elecione using the volume button the option "Apply update from external storage" and press the power
6) It will open a list with several folders and files, now navigate to the "CWM.zip" and press power again
7) It started to install and the phone screen goes all hazy, wait 5 seconds, press HOME and wait about 3 seconds will open the CWM version in "Touch"
8) Now select "advanced", then select "fix permissions"
9) Select "reboot system", a counter appears never ending, this time take off the battery switch on the phone normally.
10) You should open on the screen of your initial system configuration.
Download CWM: http://j.mp/cwm-temporario
Source: http://migre.me/flwBA
Click to expand...
Click to collapse
what if i dont have the efs backup? can i still get the phone working?
tiirabello said:
SOLVED!
Procedure:
1) If you are with a Gingerbread rom, first have to migrate to a Jelly Bean
2) Now that you're with Jelly Bean, download the CWM Temporary, extract the files to a folder of your choice and move to your memory card.
3) Unplug the device and plug it into recovery mode
volume p / up + home + power
4) Select using the volume button the option "Apply update from external storage" and press the power
5) It will open a list with several folders and files, now navigate to the "CWM.zip" and press power again
6) It started to install and the phone screen goes all hazy, wait 5 seconds, press HOME and wait about 3 seconds will open the CWM version in "Touch"
7) Select "Wipe Cache"
8) Now select "advanced", then select "fix permissions"
9) Select "reboot system", a counter appears never ending, this time take out the battery and restart the device in recovery mode
10) The error message should no longer appear, now just install the Stock ROM Jelly Bean desired.
Likely that when you have finished installing the ROM it goes straight to the home screen, without showing that the initial setup screen.
In this case, only those who have backup EFS folder do the following:
1) To make the procedure you need to have installed on the device Es File Explorer and access to ROOT
2) Copy the contents of folder EFS backup that you did and put inside the folder / efs of your device. If asked if you want sobscrever content, press OK.
3) Made the above procedures, unplug the unit and plug into recovery mode
4) Do Wipe Data / Wipe Cache and Factoy
5) Now elecione using the volume button the option "Apply update from external storage" and press the power
6) It will open a list with several folders and files, now navigate to the "CWM.zip" and press power again
7) It started to install and the phone screen goes all hazy, wait 5 seconds, press HOME and wait about 3 seconds will open the CWM version in "Touch"
8) Now select "advanced", then select "fix permissions"
9) Select "reboot system", a counter appears never ending, this time take off the battery switch on the phone normally.
10) You should open on the screen of your initial system configuration.
Click to expand...
Click to collapse
hi
my problem in step 6
my screen phone is off and phone will be restart and cwm can't be install : (
Aminhitman said:
hi
my problem in step 6
my screen phone is off and phone will be restart and cwm can't be install : (
Click to expand...
Click to collapse
I think there are 2 versions of CWM, one maybe not working on JB. Use right one.
Related
Tried using odin 1 click and 3 button but both fail on file analysis
<ID:0/008> Added!!
<ID:0/008> Odin v.3 engine (ID:8)..
<ID:0/008> File analysis..
<OSM> All threads completed. (succeed 0 / failed 1)
I have no problems flashing other roms from Clockwork recovery
though
Thanks Randall
i suppose you are in the download mode, then try odin3, not one click.
rduncan1974 said:
Tried using odin 1 click and 3 button but both fail on file analysis
<ID:0/008> Added!!
<ID:0/008> Odin v.3 engine (ID:8)..
<ID:0/008> File analysis..
<OSM> All threads completed. (succeed 0 / failed 1)
I have no problems flashing other roms from Clockwork recovery
though
Thanks Randall
Click to expand...
Click to collapse
Randall,
I wrote up some instructions on going back to stock a while back. Here ya go:
1. Download Odin One Click from: http://www.mediafire.com/?0w2y31maz8mdom4
2. Download your Windows Drivers from:
Windows 64bit: http://www.mediafire.com/?3dh4d6up72me9re
Windows 32bit: http://www.mediafire.com/?0b45zo7o75rc5d5
3. Make sure your USB cable is connected directly to the back of your computer, not a USB hub or to a front connection and all of your drivers have been properly installed
4. Do not connect your USB cable yet.
5. On your phone, go to ; Settings/Applications/Development/and check “USB Debugging”
6. Turn your phone off
7. Remove your SIM card and Micro SD if you have one
8. Open Odin One Click
9. On your phone, press and hold the Volume up and the Volume down buttons. Do not touch the power button. If you have a ROM that supports a extended power menu, just press and hold the power button until the extended power menu comes up
10. While holding them, or after you select DOWNLOAD mode, insert your USB cable, wait for a couple of seconds and a yellow triangle with the Android figure will show up
11. You’ll see in Odin, that your phone has been discovered
12. Press “Start”
13. ***VERY IMPORTANT*** Do Not mess with your phone at all. If you lose your USB connection, you could brick your device, and will possibly have to make a jig
14. When it is done, your phone will reboot and Odin will display “Removed”
15. Unplug your USB cable from your phone
16. If you are proceeding to Master clear, you must close Odin BEFORE Master Clear
Master Clear:
1. Ensure you have backed up all of your information onto your Micro SD or your desktop BEFORE doing this. IT WILL ERASE EVERYTHING ON YOUR INTERNAL SD!!
2. Make sure to remove your SIM and Micro SD if you have one
3. With your USB cable disconnected from your phone, open Odin One Click
4. On your phone, go to: Settings/Applications/Development/and check “USB Debugging”
5. Connect your USB cable to your phone
6. You’ll see in Odin, that your phone has been discovered
7. Click “Master Clear”
8. When the Master Clear has completed, your phone will reboot.
9. The phone is now as it was when it came from the factory
So I've never rooted my phone, but one day my phone just stopped responding.. it entered into an endless loop of that white screen.
I believe its due to water damage from steam/heat or something because when I took it in, they said the water damage sticker was activated... anyways, I'm able to get into reboot mode by hitting the power button + volume.
However, there are some errors that pop up:
E: Can't mount /dev/block/mmcblk0p1 (No such file or directory)
E: Can't mount SDCARD:update.zip
Installation aborted.
I tried plugging it into the PC to see if it is recognized but it is not...
Any leads on what I should do? My phone is completely stock with default software.
Thanks in advance!
If you can get it into 'reboot mode', you should be able to get it to download mode too.
First of all, if you look underneath where your battery is (so on the phone itself), you should see a bunch of numbers. One of them will be something like 1006,1007,1008,1009,1010,etc.
This is important, if the numbers are from 1006-1009 then follow these steps, but remember... nobody here is responsible for what you do to your own phone:
0. Make sure your USB isn't connected.
1. Download this: http://www.mediafire.com/?fr8bkogcu923wdu
2. Install the correct version for your computer (32-bit or 64-bit).
3. Download this: http://www.megaupload.com/?d=SBSMALFJ
4. Turn off your phone and pull the battery out.
5. Open the I897UCJF6-final-OCD-REV0.exe
6. Press the Volume + and - both at the same time and keep holding them
7. Put your battery in, and plug the USB in (never press the power button).
8. You should see a screen that says "Downloading now..." Or something like that.
9. Your Odin should show that your phone is connected (you can let go of the volume keys at this point), and just press on the 'Start' button.
10. Wait until it all finishes, NEVER pull the USB cable out.
If you're on a number that's 1010 or bigger, then tell me.
It says 1007. Trying now. Will keep you updated in the next 10 minutes
At the end of it all... It says device driver software was not successfully installed...
The Odin3 One-Click Downloader seemed to be successful though.
<ID:0/003> Firmware update start..
<ID:0/003> Sbl.bin
<ID:0/003> boot.bin
<ID:0/003> cache.rfs
<ID:0/003> dbdata.rfs
<ID:0/003> factoryfs.rfs
<ID:0/003> param.lfs
<ID:0/003> zImage
<ID:0/003> modem.bin
<ID:0/003> cache.rfs
<ID:0/003> Removed!!
I tried going into reboot mode after, and it says:
#Manual Mode#
-- Appling Muti-CSC...
Installing Muti-CSC
And it stalls there..
However, it's acting the same as before. Any other solutions?
Not really I'm afraid... I think it'll be best for you to try one more time, and if it still doesn't work try using this version of ODIN next: http://www.megaupload.com/?d=QL6NX702
venomio said:
Not really I'm afraid... I think it'll be best for you to try one more time, and if it still doesn't work try using this version of ODIN next: http://www.megaupload.com/?d=QL6NX702
Click to expand...
Click to collapse
I think your first post is the most recent version of Odin
How long ago did it get moisture in it?
one of the things to try(if it was fairly recent) take the SIM/Micro SD, if you have one/and battery out. Put the phone IN a small bag of rice for 24 hours. If there is any moisture left in the device the rice will absorb it. When you take it out, use a can of compressed air to blow out any residue
kangi26 said:
Try this version of Odin. I think it's the "latest"
http://www.mediafire.com/?0w2y31maz8mdom4
How long ago did it get moisture in it?
Click to expand...
Click to collapse
The same version as in my first reply... But it's the thought that counts
venomio said:
The same version as in my first reply... But it's the thought that counts
Click to expand...
Click to collapse
I just saw that and edited my post
it got moisture in a few days ago... 4? 5?
method still doesnt work with alternate odin version...
looks like im screwed...
it says movinand read fail
movinand checksum confirmation fail
-- movi_checking done!
edit: actually. I feel like there's hope. Now it shows the galaxy s screen after the att screen.... but still no luck.
Anyone know what the next step should be?
did you flash with your sd card in? no promises but i forget what or when but once, flashing with sd card in caused me to stall, now i just always do it, give it a shot.
How do I flash with my sd-card in? I'm sort of unfamiliar with the terminology...
xpiamchris said:
How do I flash with my sd-card in? I'm sort of unfamiliar with the terminology...
Click to expand...
Click to collapse
If you have a micro SD card, make sure you take it out before you start the Odin process
Sent from a autonomous device
Just to give an update, I've tried flashing with sd card both in and out.. and its the same..
Updated list:
When rebooting phone:
ATT World Phone Screen comes up
Galaxy S Screen Comes up
Screen goes black after.
Booting phone under reboot mode:
ATT World Phone Screen comes up
--Movi_check Start..!!
movinand read fail
Movinand Checksum Confirmation Fail
--movi_checking done!!...
update media, please wait
E: Can't mount /dev/block/mmcblk0p1 (No such file or directory)
E:copy_dbdata_media:Can't mount SDCARD:
your storage not prepared yet. please use UI menu for format and reboot actions.
copy default media content failed.
So after this pops up, I try to format internal sd-card, and this pops up:
update media, please wait
E: Can't mount /dev/block/mmcblk0p1 (No such file or directory)
E:copy_dbdata_media:Can't mount SDCARD:
your storage not prepared yet. please use UI menu for format and reboot actions.
When I try to reinstall packages:
Install from sdcard...
Finding update package...
E:Can't mount /dev/block/mmcblk0p1 (No such file or directory)
E:Can't mount SDCARD:update.zip
Installation aborted.
(Still hoping there is a solution!)
Okay... this is the final step you can try.
This is the manual (or "full") Odin, it's taken from a post by icezar1 in the Development Forum:
Do not use this if you want to send your phone back to ATT or Samsung for warranty!
Do not use this if you know you flashed a -LOW- ODIN package (when opening the PDA***.tar or CODE***.tar you will find inside boot.bin or sbl.bin)
Use this if you want to go back to stock before flashing a custom ROM.
Use this without worries if you changed your boot screen image or if you flashed the secondary boot loader which allows you to enter download/recovery with key combos.
Download the package from here
Download the phone drivers from DG's thread if you dont have them already. [Note: You should already have this xpiamchris, it will be the same one I asked you to download and install]
How to:
Remove sdcard and SIM card from the phone
Extract JF6_secure.zip somewhere.
Boot your phone in Download Mode
Run Odin3 v1.3.exe
Plug in your phone via USB
Click on the button PDA
Choose JF6_secure.tar.md5
Click start
Wait and do not unplug cable until it is finished
I noticed on the reboot, the phone said "data wipe failed"
But phone is acting the same as before..
Hi,
I am new to this and seeking help from you all.
I have some problems and after the restart it stops at Galaxy S main screen. When in CWM Recovery Mode v3.0.0.5, I found that the volume is not mounted. When I try to mount the volume under Mounts and Storage > mount USB storage, I get:
E: unknown volume for path [/data]
E: unknown volume for path [/data]
E: Unable process volume! Skipping...
Checking /cache...
E: unknown volume for path [/cache]
E: unknown volume for path [/cache]
E: Unable process volume! Skipping...
Done!
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: Can't open /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]
I cannot do anything. Please guide me as I am new to all this.
Regards,
A Failed I9000
you need to get the latest CWM here
you will have to run partition sdcard and, YOU will lose everything on it. So take out sdcard and copy all to pc.
See this post
Okay.. that's a bootloop..
No need to worry.. Just flash a stock gingerbread firmware like jw4 or jvu via Odin...
u Can get it from samfirmware.com for Ur country..
If my post helped, don't mind hitting THANKS 
drakester20 said:
Okay.. that's a bootloop..
No need to worry.. Just flash a stock gingerbread firmware like jw4 or jvu via Odin...
u Can get it from samfirmware.com for Ur country..
If my post helped, don't mind hitting THANKS 
Click to expand...
Click to collapse
Thank you... This is the result from Odin
<ID:0/005> Added!!
<ID:0/005> Removed!!
<ID:0/005> Added!!
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> RQT_CLOSE !!
<ID:0/005> RES OK !!
<ID:0/005> Removed!!
<ID:0/005> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
Please guide me next as I have no clue here. My phone only goes into the download mode and not to Recovery Mode anymore. Did I screw it up?
Please help.
Taysider said:
you need to get the latest CWM here
you will have to run partition sdcard and, YOU will lose everything on it. So take out sdcard and copy all to pc.
See this post
Click to expand...
Click to collapse
I have clicked on the link but it said it will get downloaded to your phone. nothing happened even after 30 mins.
U flashed the correct firmware, right?
If my post helped, don't mind hitting THANKS
Hey
Dies your fone boot properly?
Cheers
If my post helped, dont forget to hit the thanks button..
tchindalia said:
Hey
Dies your fone boot properly?
Cheers
If my post helped, dont forget to hit the thanks button..
Click to expand...
Click to collapse
I flashed it two times more but nothing happens... the previous ROM is flashed out and I can now see the phone in only Download mode...
1. Go to samfirmware.com.
2. Download stock firmware
3. Flash in odin with repartition checked. Pit file dont matter
4. Wipe data/factory reset from stock recovery
5. Flash Semaphore ICS kernel tar in pda through odin, no repartition.
6. Boot into recovery
7. Flash whatever you want
8. Sucess.
No format of sd needed.
AlwaysDroid said:
1. Go to samfirmware.com.
2. Download stock firmware
3. Flash in odin with repartition checked. Pit file dont matter
4. Wipe data/factory reset from stock recovery
5. Flash Semaphore ICS kernel tar in pda through odin, no repartition.
6. Boot into recovery
7. Flash whatever you want
8. Sucess.
No format of sd needed.
Click to expand...
Click to collapse
Thank you, AlwaysDroid. This worked.. You saved my phone...
This may be the last chance to get back the needed important data (please don't ask the awkward question: why not back up the data first) .....
Tried the official SAMSUNG repair office, they said no way!!! Tried search the net and not much available either!
Any expert here can help?
Problem:
Galaxy Note 1 GT-N7000, possibly still in unrooted Ginger Bread, suddenly stuck at boot logo. Press+hold Power/Vol Up/Home brings the machine into recovery mode showing:
1. the green Android robot and yellow arrow out from a file box logo,
2. messages displayed:
<in red>
E: failed to mount /sdcard (I/O error)
E:copy_cache_media:Can’t mount /sdcard
Your storage not prepared yet, please use UI menu for format and rebootactions.
<in Red>
<in yellow>
Media files copy failed.
# MANUAL MODE #
-- Updating application …
<in yellow>
..<in red>
E: failed to mount /sdcard (I/O error)
E:copy_cache_media:Can’t mount /sdcard
Your storage not prepared yet, please use UI menu for format and rebootactions.
Copy application failed.
<in Red>
..<in yellow>
-- Applying Multi-CSC…
Installing Multi-CSC
Can’t access to ‘/system/csc/TGY/system/’.
Successfully applied Multi-CSC
<in yellow>
Then, the usual Android system recovery message <in blue> for reboot, apply update, wipe data/factory reset, wipe cache, test redbend fota displayed at the top part of the screen.
3. Tried wiping cache partition and reboot, no luck with the same situation after reboot.
4. The SAMSUNG repair office said it’s not the battery problem. All data will be gone for rebooting the machine.
The data are more important than the machine, ie, saving the data is more important than saving the machine.
Any suggestions and directions for a workable solution will be highly appreciated.
there is a possible way ... do at your on risk..
1. boot into dwonload mode and connect the phone to PC.. open odin and check if connecting fine
2. download philz kernel for for ICS/JB (tar version) and flash it using the PDA tab in odin. (This will not boot the GB rom but should give you access to CWM)
3.Once flash is completed, remove the cabe and battery.. put the battery back in and boot into recovery mode, (vol up+home+power) .. You should see CWM recovery
4. Contacts can be backuped up by doing a nandroid backup of your rom. for the data in InternalSD, go to mounts and storage and choose mount USB storage.
conect phone to pc and wait for the drivers to appear.
5. copy what ever data you need.
It is possible.
Flash CF Root Gingerbread kernel using PC Odin.
Drop into recovery and connect your phone to PC.
From ADB you'll be able to copy (backup) ANY file you need.
DO NOT perform factory reset / wipe data or you'll lose the data.
---------- Post added at 05:56 PM ---------- Previous post was at 05:54 PM ----------
Ohh yes nandroid backup too will work.
Easier way. Do a nandroid backup on recovery. Flash the same rom you were using. Advanced restore of data partition of the nandroid.
Thank you very much guys for all of your quick and valuable replies.:good::good:
Please excuse my ignorance as I’m only a dummy, actually the worst, an old dummy!!
In order not to make the suitation worse, I’d like to know/clarify the following details before proceeding to the suggested ways:
@nokiamodeln91:
1. Connected to PC with the N7000 in SAMSUNG logo display, opened Odin3 v1.85, ID:COM column shows <in yellow>0:[COM4] and Message column shows<ID:0/004>Added!!
Is download mode=press&hold [power+vol up+home] keys?
2. In the thread: http://forum.xda-developers.com/showthread.php?t=1901191
Trying to download philz-cwm6-n7000, found the following 5 tar files:
PhilZ-cwm6-XXLT5-OXX-5.03.0.tar.md5
PhilZ-cwm6-ZSLO2-OZS-5.03.0.tar.md5
PhilZ-cwm6-DDLSC-ODD-5.03.0.tar.md5
PhilZ-cwm6-DXLSE-OLB-5.03.0.tar.md5
PhilZ-cwm6-JPLSB-UAE-5.03.0.tar.md5
Which one is suitable for an UNROOTED GingerBread N7000 with csc/TGY/system?
Will try to follow the other steps after clarifying the suitable tar file.
@Boy124:
1. What is CF Root Gingerbread kernel? Where can I download a copy for an UNROOTED N7000?
2. Please elaborate on or direct me to detailed ADB procedures, preferably a step-by-step guide if not asking too much. I’ve downloaded adt-bundle-windows-x86-20130219. How to copy (backup) the contacts data?
3. Thanks for reminding not to wipe data and perform factory reset.
@projeto56 and Boy124:
Search a bit on nandroid. But how to add nandroid in the machine as it is (stuck in boot logo)?
The machine has not been flashed with any ROM since purchase. No modifications, flashing or anything, no rooting, just add apps (as said, I’m an old dummy!). When booting in recovery mode, cannot see any backup or restoring options
Hope you guys have enough patience to bear with me and answer the questions.
Thanks again.
@liway
CF Root is not necessary.
As nokiamodeln91 said flash PhilZ kernel with PC Odin - any version will do the job.
After flashing with PC Odin, drop into recovery. (home key + volume up + power)
Then back up your current ROM.
Flash Gingerbread firmware with PC Odin again.
Root it. If you have Titanium Backup Pro, you can directly restore data from a nand backup. Or restore data only after rooting your ROM.
Lemme know if you need further assistance.
liway said:
Search a bit on nandroid. But how to add nandroid in the machine as it is (stuck in boot logo)?
The machine has not been flashed with any ROM since purchase. No modifications, flashing or anything, no rooting, just add apps (as said, I’m an old dummy!). When booting in recovery mode, cannot see any backup or restoring options
Click to expand...
Click to collapse
Do this:
Boy124 said:
As nokiamodeln91 said flash PhilZ kernel with PC Odin - any version will do the job.
After flashing with PC Odin, drop into recovery. (home key + volume up + power)
Then back up your current ROM.
Click to expand...
Click to collapse
But afterwards, i recommend you to flash a JB stock ROM directly from your new recovery. And after you've set it up, you either restore your data from your nandroid, or you use titanium backup pro to restore only what you need (recommended).
Anyway, if you've set up your google account previously, probably your contacts are already saved in the cloud.
You need to connect the phone in download mode (vol down + home + power). Then volume up to continue. The screen should show downloading.
Now connect the phone to pc and use odin to flash any tar version of the kernel. (like ddlsc). Select on pda tab.
None of these kernels are suitable as it will not boot on GB. This is just for you to get into an advanced recovery to backup your data before you wipe and get your phone working.
Following the suggested procedures, set the machine in downloading mode to download PhilZ-cwm6-DDLSC-ODD-5.03.0.tar, the bar below KERNEL square in Odin becomes completely green with the Message displayed:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> PhilZ-cwm6-DDLSC-ODD-5.03.0.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> zImage
<ID:0/005> NAND Write Start!!
It stayed at this stage for hours and seems stopped there.
Tried to boot it in recovery mode [vol up+home+power], this time only the boot logo with an exclamation mark (!) in yellow triangle. Odin message:
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!
Put back in downloading mode again, and the machine now is exactly at the same stage with the above message displayed and apparently halted at "NAND Write Start!!". The machine's screen remains in the downloading mode.
What should I do next?
Make sure kies process is not running in task manager. Use the main usb ports. Use samsung usb cable only. Reboot the phone in download mode and try again. The tar file should be in pda.
kies process is not running in task manager.
using one of the main usb ports.
Cannot locate the original samsung usb cable, using ordinary USB 2.0 cable. Will try to find the original samsung usb cable and try again later.
The tar file is in pda.
Thanks.
maybe a pciture of where file should be added in odin will help him/her. flashing kernel takes only seconds. as i can see drivers were properly installed from the descriptions above.
In Odin, I've ticked the box for PDA, then put the file with the whole path name for the folder in the column after PDA.
Tried again with
1. sure that all kies process is not running in task manager.
2. using one of the main usb ports at the back plate of a desktop PC.
3. Using an original samsung usb cable from Note 2 (should be the same as for this Note 1?),
4. The tar file is in pda, and path/location stated in the box after ticked PDA in Odin.
....
Still halted at the stage of NAND Write Start!!:crying:
did you reboot into download mode? you should not continue from a failed flash. reboot
restart the pc and run odin as admin.
disable any AV and Firewall softwares.
if still a no go then try on a different pc
Disconnected the machine. Taken away and put back the battery. Rebooted in download mode [vol dn+home+power].
Restarted the pc and run under a user with administrator right.
Disabled all norton internet security protections. Turned off modem/router connection.
Connect to Odin, still no go. Same situation, halted at NAND Write Start.
Will try to arrange another pc next day or so.
In the meantime, any other alternatives worth trying?
Even a bricked phone in download mode should be able to flash a kernel.
What you could try is unintall kies and usb drivers. And then download samsung usb drivers from developer. Samsung.com and install it again. Then try.
- deleted Kie and SAMSUNG USB driver. Restart the PC.
- reinstall samsung usb driver.
- restart in download mode and connect PC.
still no go!
to recap: using Odin3-v1.85 and PhilZ-cwm6-DDLSC-ODD-5.03.0.tar
diff PC seems to be the last option
though you could try this. download http://d-h.st/FVh. its the PIT file. Select the PIT file in PIT Tab.. and kernel in PDA tab..
make sure repartition is checked.. then flash again and see..
flash wit PIT and kernel.
In Odin, Set Partition shows up in the 1st square and message:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> PhilZ-cwm6-DDLSC-ODD-5.03.0.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
seems halted there!
How long will I have to wait?
Hi ya!
I am a long time lurker and am always amazed that the collective knowledge here.
I've never spent much time with the inner workings of mobile phones, but am otherwise quite good with tech and very very persevering
My problem is a S3 LTE GT-I9305.
HISTORY (just FYI, as the phone is currently soft bricked):
It was working fine for ages. Delivered with stock 4.1.2 and last had stock 4.4.4 (I9305XXUFNL1_DBTFNL1) running (via OTA - Triangle Away worked well to hide the root). It was rooted (@ 4.1.2) using CF Autoroot and SuperSU worked fine. I am not sure if I ever installed Custom Recovery (if, then it was CWM).
Then about two months ago I started getting persistent error Messages about Media, Media Storage, Download Manager, Hangouts, etc having stopped.
After a lot of reading and troubleshooting I finally backed up my stuff and did a factory wipe. Everthing worked fine after that.
I never restored everything, so the phone and firmware was lightly loaded only, when ...
YESTERDAY:
Having not looked at the phone for a day or so, I surprisingly heard the Samsung shut down tone and went to have a look. What I saw (some 20-30 seconds later) was the white on black boot logo and it never went past that. Thinking that it might have been crunching on an OTA update or similar, I hooked it up to my charger and watched it for 3 hours (I swear, 3 hours). I then pulled the battery and it now (continues) to get stuck on the white on black boot logo.
NOW:
(1) Booting gets stuck at the white on black logo.
(2) I can start it in recovery but it is the Samsung stock recovery only. Please refer below for the error messages I get. I can't clear the cache and even the factory wipe does not work.
(3) I can start it in download mode but ODIN 1.85, 3.04 and 3.10.7 give me persistent FAIL results when trying to flash TWRP 3.0.2-1, 3.3.1-0 or CF-Auto-Root-m3-m3zh-gti9305.tar.md5. I have tried 2 otherwise good cables and all 3 USB2 ports available on my Win7 laptop.
(4) Kies 3 says 'not supported device'
I am at a loss right now. The water is way too deep for my knowledge level.
I have read more than 50 websites and forum posts (includung pretty similar ones, before deciding to write myself).
If someone could point me in the right direction ... eternal gratitude will be yours
What I have downloaded but not used yet (since ODIN is not able to write at the moment) is the I9305XXUFNL1 factory ROM containing:
AP_I9305XXUFNL1.tar.md5
BL_I9305XXUFNL1.tar.md5
CP_I9305XXUFNL1.tar.md5
CSC_I9305XXUFNL1.tar.md5
M3_EUR_OPEN.pit
Since I can't make any screenshots or provide log files ... here is more (and hopefully all) Information needed.
Top right of the screen in download mode:
ODIN MODE
PRODUCT NAME: GT-I9305
CUSTOM BINARY DOWNLOAD: No
CURRENT BINARY: Samsung Official
SSTEM STATUS: Custom
Secure Download: Enabled
KNOX WARRANTY VOID: 1
AP SWREV: A3
ODIN 1.85 after attempting to flash TWRP 3.3.1-0 (using PDA button and only 'F. Reset Time' checked):
Setup Connection..
Initialization..
Get PIT for mapping..
Firmware update start..
recovery.img
NAND Write Start!!
Complete(Write) Operation failed.
All threads completed. (succeed 0 / failed 1)
Recovery mode upon start:
E:failed to mount /efs (No such file or directory)
E:failed to mount /system (No such file or directory)
# MANUAL MODE #
-- Applying Multi-CSC...
E:failed to mount /system (No such file or directory)
can't mount '/system' (No such file or directory)
E:failed to mount /cache (No such file or directory)
E:failed to mount /cache (No such file or directory)
E:Can't mount /cache/recovery/last_recovery
E:failed to mount /system (No such file or directory)
E:failed to mount /cache (No such file or directory)
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:failed to mount /cache (No such file or directory)
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:failed to mount /cache (No such file or directory)
E:Can't mount /cache/recovery/last_install
E:Can't open /cache/recovery/last_install
E:failed to mount /cache (No such file or directory)
Recovery mode upon selection of 'wipe cache partition' or 'wipe data/factory reset':
Much of the above 'can't open+mount' error messages, but with additional mention of:
/cache/recovery/last_log
(Block device required)
@chinaman88 Never used stock on the i9305 but we still have two i9305's in not really daily but current use.
First, for all of our Samsung devices I use Odin v3.13.1; maybe you should also search the web (or XDA) for that version. You will experience some differences to your versions e.g. no PDA button. And you're correct, "Auto Reboot" must not be ticked because you need to immediately boot into TWRP after it has been flashed, otherwise TWRP won't stick.
Regarding TWRP: My own experiences is that no TWRP version above 3.0.2-1 works on the i9305. I always got flash errors with them. But 3.0.2-1 runs without any problems. My recommendation is to only use v3.0.2-1 and to flash that via Odin v3.13.1
If you succeeded with flashing of TWRP, then I'm happy to recommend the custom ROM that is still in use here.
@Oswald
I obtained Odin3 v3.13.1 and tried flashing both:
CWM_touch_6.0.4.7_i9305.tar
twrp-3.0.2-1-i9305.img.tar
Sadly the end result is the same ...
<ID:0/010> Odin engine v(ID:3.1301)..
<ID:0/010> File analysis..
<ID:0/010> Total Binary size: 6 M
<ID:0/010> SetupConnection..
<ID:0/010> Initialzation..
<ID:0/010> Get PIT for mapping..
<ID:0/010> Firmware update start..
<ID:0/010> NAND Write Start!!
<ID:0/010> SingleDownload.
<ID:0/010> recovery.img
<ID:0/010> FAIL!
<ID:0/010>
<ID:0/010> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
If I (with the help of the community) can't get my old I9305 running again (the SDS Sudden Death Syndrome has crossed my mind), then I will likely buy a used I9305 from someone and use that instead. But right now (unless it is really SDS in my case) I will still fight for my old phone ... thinking there has to be some way to get it working again. What is really strange to me is that I did nothing MYSELF to soft brick it - it happened all alone.
Thanks so far and I surely will take your offer to give me some advice on Custom ROMs (as more and more apps no longer support KitKat)!
I was thinking about Lineage 14.1 before all this happened. Is there anything better than that and, for Lineage 14.1, do you happen to remember which build was fully stable / most stable?
@chinaman88 First, happy new year to you. And I apologise for the delayed reponse but in your mention there was an error i.e. I didn't receive a notification.
As you have/had Kies installed you should have the driver for the i9305 installed on your PC but you may want to confirm. Additionally, I'm convinced you're aware that ODIN doesn't work if Kies is running in the background. I suggest to completely uninstall Kies prior to the launch of Odin (but do not uninstall the driver).
Are you able to flash the stock ROM via Odin?
And this is still my favourite ROM for the i9305, actually still runing daily: https://forum.xda-developers.com/ga...m-resurrection-remix-4-4-2-kitkat-v5-t2704828
This respective Q&A thread: https://forum.xda-developers.com/ga...resurrection-remix-4-4-2-kitkat-v5-1-t2950817
Search for my posts on both, and you'll find my current configuration including the custom kernel (a Boeffla mod).