Database Develop

PLEASE HELP!!! Can't boot system

I am so hosed. I have been fighting with my Sprint Tab for the last few days and would really appreciate someone's help. I have had the phone ! computer error, stuck on the Samsung screen issue and now have finally successfully got back into CWM, and keep getting the following error. I can't get the system to reboot.
E:failed to mount /system (invalid argument)
/system may be rfs. Checking...
Checking /data...
Checking /datadata...
E:failed to moun /datadata (invalid argument)
/datadata may be rfs. Checking...
Checking /cache...
Done!
I successfully flashed a rom but when I reboot system it comes right back to CWM with this error. Tried to install the update.zip on page one for Gingerbread and get the following error:
Installing update...
file_getprop: failed to stat "/system/build.prop": no such file or directory
e:Error in /sdcard/update.zip
(status 7)
Installing aborted.

the dbdata is corrupt
its mean you have to re-flash back with PIT and pit file
basically follow the guide here : http://forum.xda-developers.com/showthread.php?t=1133590

k0sh said:
the dbdata is corrupt
its mean you have to re-flash back with PIT and pit file
basically follow the guide here : http://forum.xda-developers.com/showthread.php?t=1133590
Click to expand...
Click to collapse
Thanks for the info. I have been on this page and tried the link for Sprint, I will try again and see if I have any success.

tallen said:
Thanks for the info. I have been on this page and tried the link for Sprint, I will try again and see if I have any success.
Click to expand...
Click to collapse
try to put the pit file and flash it 1st , and then flash your rom . separate

k0sh said:
try to put the pit file and flash it 1st , and then flash your rom . separate
Click to expand...
Click to collapse
I had done this before with Odin but kept having issues with the EA24 update, it would fail. I am going to try again.

Result from running P1_20100909.pit
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/003> Removed!!

Tried to run the Odin EA24 update but received error Odin3 Communicator has stopped working...ugh!!!!!!

what odin are you using ? ?
you can't update odin ? ? there is no options to file\tools etc ?
use odin 1.7

k0sh said:
what odin are you using ? ?
you can't update odin ? ? there is no options to file\tools etc ?
use odin 1.7
Click to expand...
Click to collapse
Mine says Odin3 v1.7, I believe I got it off the Sprint forum. My freaking system is all shanked up. I think I am going to delete all of the files I have downloaded and start over because nothing is working for me. I have used Odin and Heimdall to no success.

[Q] Help! Can't Delete Files on Galaxy S

Hi everyone,
My galaxy S recently had the "System UID Inconsistent" problem. As solution, everyone says to wipe data, or reinstall the rom. I've did it a lot of times, and this still continues. I've now installed the clockwork recovery mod to try to wipe the data and fix permissions.
The strange thing is that I mount the USB Storage, delete ALL FILES ON THE PHONE, and go back to the recovery ALL FILES ARE BACK THERE. I don't have any clue on what is happening, why all files get back to the phone, and why i can't delete the files on it. Can someone help me?

Hi Mate,
Follow the link posted below and hopefully your problem will be fixed.
http://www.theandroidsoul.com/ezbase-ezrom-for-android-2-2-install-revert-back/
Cheers

Tryed it, FAILED
With the "Repartition" ticked, it give an error that can't do the repartition... Without it checked, it completes the proccess, but he doesn't finish to boot.
I think that the data partition is really ****ed up... when it finish to install the official rom when it comes to the recovery mode, it gave me some errors on dbdata (he can't write it) and some errors to wipe the data partition.
here are some errors that usually occurs.
Flash errors said:
E:failed to mount /dbdata (File Exists)
E:delete_data_files:Can't mount /dbdata
your storage not prepared yet, please use UI menu for format and reboot actions.
Media File copy Error
-- Deleting files...
E:failed to mount /dbdata (File Exists)
E:delete_data_files:Can't mount /dbdata
your storage not prepared yet, please use UI menu for format and reboot actions.
-- Updateing filesystem...
E:failed to mount /dbdata (File exists)
E:discard_filesystem_for_rfs:Can't mount /dbdata
-- Wiping cache
Formating /cache...
Cache wipe failed.
--Applying Multi-CSC...
(here all goes ok)
Click to expand...
Click to collapse

Nobody? No one knows why files can't be Deleted? It's really bricked?

an idea..
hi dark,
you have a re-partition problem which means probably you made lagfix and you just install a new firmware wout taking lagfix back
you should install a firmware which has an ability to repart your phone. Your best alternative is I9000XXJPU 2.2 Froyo Rom which has a future with it. download it. from samfirmware and install it.
and then upgrade as u want to girgerbread etc..
i hope this helps

Ok. I'll try soon... but, I've never made a lagfix on my phone

hello,
i have the same problem. Have you found a solution?
thanks

Try what everyone said befora... but still don't get any clue about the problem

Do you have the I9000 M << by any chance ? These are know for SD card failures, resulting in strange behaviour like you have mentioned..
Also what firmwares have you tried to flash with odin ?
something waaaaay back always works for me, Something like Eclair with all 3 files and 512PIT... No matter whats issues i have encountered, That firmware always makes my phone better
Good luck, Hope you get it sorted

Mine is T ... I have read about the M problems and tryed the same with T ... but nothing worked... I've flashed 2.1 2.2 and 2.3 official roms but doesn't worked... I still have the "Undeletable partition" issue... I think that it'll be a Time Capsule, frozen files in time to record later.

undeletable partition sdcard and "System UID Inconsistent"
Hi Dark FlameS,
have you found a solution to your problem, I also have the same?
The only ROM that don't give me at the beginning the "System UID Inconsistent" is probably the last one I installed 2.3.5 i9000XXXJVS before the partition /sdcard became undeletable.
With that ROM I can use at least the phone to make phone call and navigate, but I can't install or delete any program on /sdcard.
This is very frustrating!
Please someone help us thank you very much in advance!
This is the log of ODIN and it seems there are no error but the /sdcard (internal sd) are always there!
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> PDA_XFJVA_Sbl.tar.md5 is valid.
<OSM> PHONE_XXJVT.tar.md5 is valid.
<OSM> CSC_OXFJV1.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!!
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> param.lfs
<ID:0/004> NAND Write Start!!
<ID:0/004> zImage
<ID:0/004> boot.bin
<ID:0/004> Sbl.bin
<ID:0/004> factoryfs.rfs
<ID:0/004> dbdata.rfs
<ID:0/004> modem.bin
<ID:0/004> Transmission Complete..
<ID:0/004> Now Writing.. Please wait about 2 minutes
<ID:0/004> Receive Response form LOKE
<ID:0/004> cache.rfs
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!
<ID:0/004> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/004> Removed!!

No, Haven't found any solution
I'm from Brazil, and this phone was bought over the internet and it's not from Brazil. I'm not sure if it is from New Zealand or Mexico...
I had seen some people telling that this occurs only with I9000T Early versions, and people who had this problem had changed their phone on the warranty... But, samsung Brazil says that they can't do nothing for me 'cause they don't have the software for my phone, just for the Brazillian version of the phone (I9000B)...
If your phone is not an I9000T, search a bit more for a solution, it may be just corrupted files. My case is that the filesystem won't write nothing more, so the phone can't delete the files there and neither write files.
I've seen that some Galaxy phones crash sometimes with files that has large names and lightbox photo app sometimes write files with these large names and the system file goes crazy, if you handle to delete these files, maybe your phone could work, if you're lucky.
Lightbox might have been the sparkle to this occurs to me, as it has occured in the day that I have instaled it. Or maybe it was changing the sd card that i had in there, that I've done in the same day...
I just could say to you know that I have no solution, the only solution will be buy a new phone. Hope that you're luckyer than me...

Thank you for the reply, mine it's a I9000 but I installed superuser.apk and for the same reason (undeletable file, apk, and partition) I can't delete it, so I don't think they will accept the warranty!

But you still could try the payed fix... they can't refuse... The problem with me is that samsung brazil only fix brazillian phones

[Q] SecSetupWizard stopped - 4.1.2

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.

Randomly Stuck on Boot logo? (Possible eMMC issue?)

Hi Guys,
I have a Galaxy S3 (i9305) Rooted on Stock 4.4, Knox disabled, w Xposed. Running Philz Recovery.
Anyways, I woke Saturday morning to my phone stuck on the Samsung Boot Logo.
I tried rebooting several times to no avail, so tried a recovery via Philz. (I can get into Odin Mode / Recovery no problems)
However when I try to do a restore, it fails. When I initially boot up Philz I get this;
E: Can't mount /cache/recovery/command
E: Can't mount /cache/recovery/log
E: Can't open /cache/recovery/log
E: Can't mount /cache/recovery/last_log
E: Can't open /cache/recovery/last_log
And when I try to wipe caches / system etc I get an error message;
E: format_volume: make_ext4fs failed on /dev/block/mmcblk0p12
Tried flashing stock FW via Odin and that fails.
So not sure what I can do? From my research it looks like the eMMC (internal SD) has croaked, but how can I be
absolutely sure? Has anyone had a similar situation and been able to recover?
Thanks in Advance!

BrikHaus said:
Hi Guys,
I have a Galaxy S3 (i9305) Rooted on Stock 4.4, Knox disabled, w Xposed. Running Philz Recovery.
Anyways, I woke Saturday morning to my phone stuck on the Samsung Boot Logo.
I tried rebooting several times to no avail, so tried a recovery via Philz. (I can get into Odin Mode / Recovery no problems)
However when I try to do a restore, it fails. When I initially boot up Philz I get this;
E: Can't mount /cache/recovery/command
E: Can't mount /cache/recovery/log
E: Can't open /cache/recovery/log
E: Can't mount /cache/recovery/last_log
E: Can't open /cache/recovery/last_log
And when I try to wipe caches / system etc I get an error message;
(will enter exact info when an home and can see phone)
Can't format /system/ doesn't exist?
Tried flashing stock FW via Odin and that fails.
So not sure what I can do? From my research it looks like the eMMC (internal SD) has croaked, but how can I be
absolutely sure? Has anyone had a similar situation and been able to recover?
Thanks in Advance!
Click to expand...
Click to collapse
Try TWRP.
Flash: http://d-h.st/users/psndna88/?fld_id=34039#files (all files). But attention, when you format 'data' partition, you lost all files from internal (you can skip format data, or if you not have important files, format)
After this, flash a new rom with Odin (or if you have custom rom, flash again)

il3gal said:
Try TWRP.
Flash: http://d-h.st/users/psndna88/?fld_id=34039#files (all files). But attention, when you format 'data' partition, you lost all files from internal (you can skip format data, or if you not have important files, format)
After this, flash a new rom with Odin (or if you have custom rom, flash again)
Click to expand...
Click to collapse
Thanks il3gal.
When I try to flash TWRP (Which I had before I installed Philz) I get the following from Odin;
<ID:0/007> Added!!
<ID:0/007> Odin engine v(ID:3.1005)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> SingleDownload.
<ID:0/007> recovery.img
<ID:0/007> NAND Write Start!!
<ID:0/007> FAIL!
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)​
Can you provide a bit more info about how I flash those 4 files? If I can?

BrikHaus said:
Thanks il3gal.
When I try to flash TWRP (Which I had before I installed Philz) I get the following from Odin;
<ID:0/007> Added!!
<ID:0/007> Odin engine v(ID:3.1005)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> SingleDownload.
<ID:0/007> recovery.img
<ID:0/007> NAND Write Start!!
<ID:0/007> FAIL!
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)​
Can you provide a bit more info about how I flash those 4 files? If I can?
Click to expand...
Click to collapse
This 4 files is for format your partition in ext4. (if you try to modify partitions with f2fs or others)
Try 2/3 times with Odin and TWRP. If not work, download stock rom from http://www.sammobile.com/firmwares/database/GT-I9305/ and install with Odin
What Odin are you use to flash TWRP? Reinstall usb drivers or change usb port

il3gal said:
This 4 files is for format your partition in ext4. (if you try to modify partitions with f2fs or others)
Try 2/3 times with Odin and TWRP. If not work, download stock rom from http://www.sammobile.com/firmwares/database/GT-I9305/ and install with Odin
What Odin are you use to flash TWRP? Reinstall usb drivers or change usb port
Click to expand...
Click to collapse
Do you use Odin to flash those 4 files? If so what are they 'AP'?
I've tried to flash on 2 different computers using (5) different cables. Still no luck at all..
Using Odin 3.10.6
I think I'm screwed..

BrikHaus said:
Do you use Odin to flash those 4 files? If so what are they 'AP'?
I've tried to flash on 2 different computers using (5) different cables. Still no luck at all..
Using Odin 3.10.6
I think I'm screwed..
Click to expand...
Click to collapse
For .zip files you need flash with recovery (cwm/twrp/philz)...but if you try with Odin and is not work..i dont now if my method is work for you..

download odin 3.09.....i tried odin 3.10 and it did not recognized my phone and download the usb drivers from the recovery thread on the developing section.
http://forum.xda-developers.com/gal...covery-i9305-cwm-philz-twrp-versions-t2694249

Thanks il3gal, tried to flash those zips and get an error message;
E: Failed to setup expected mounts for install; Aborting

hexisg said:
download odin 3.09.....i tried odin 3.10 and it did not recognized my phone and download the usb drivers from the recovery thread on the developing section.
http://forum.xda-developers.com/gal...covery-i9305-cwm-philz-twrp-versions-t2694249
Click to expand...
Click to collapse
Thanks hexisg. Tried 3.09 and same issue. No Luck.

Stock 4.4.4 suddenly stuck on boot logo and ODIN always fails

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).