Related
Hello devs,
My phone is stuck at the start screen saying: Samsung Galaxy SIII GT-I9300
I can´t do anything. I can´t even turn it off. I have to pull out the battery for several mintues for it not to autostart, when I put back in the battery.
If I connect the charger, the chargingbattery graphic will show on the screen, but it's static.
There´s no animation for the charging, and even when I pull out the charger cabel, the graphic still shows untill the battery is removed.
My phone is just as it was when I bought it from stock, except for some apps from market.
I don´t understand it.. it did this overnight connected to the charger cable.
When I woke up, I used the phone for 3 minutes, then it 'hung'. I restarted it and now it's doing this.
I have tried to read several threads about it, but nothing seems to be accurate with my experience.
The phone dont seem to be recognized when connected with the usb cable to the pc.
I have installed KIES and Samsung USB drivers, but still no luck.
I can start the phone in download mode and in recovery mode.
When I start the phone in recovery mode i get the following errors:
E: failed to mount /efs (No such file or directory)
E: failed to mount /system (No such file or directory)
# Manual Mode#
E: failed to mount system (No such file or directory)
E: Can´t mount /system
E: failed to mount /cache (No such file or directory)
E: Can´t mount /cache/recovery/last_recovery
E: failed to mount /data (No such file or directory)
E: Can´t mount /data/log/recovery:log.txt
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/last_log
E: Can´t open /cache/recovery/last_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)
I have tried to wipe cache partition and do a data/factory reset, but without any luck.
When i try to do a data/factory reset it says:
-- Wiping data...
Formatting /data...
E:format_volume: make_extf4s failed on /dev/block/mmcblk0p12
Formatting /cache...
E:format_volume: make_extf4s failed on /dev/block/mmcblk0p8
Data wipe complete
E:failed to mount /cache (Block device required)
E:Can´t mount /cache/recovery/log
E:Can´t open /cache/recovery/log
E:failed to mount /cache (Block device required)
E:Can´t mount /cache/recovery/last_log
E:Can´t open /cache/recovery/last_log
E:failed to mount /cache (Block device required)
E:Can´t mount /cache/recovery/last_install
E:Can´t open /cache/recovery/last_install
E:failed to mount /cache (Block device required)
I hope someone here can tell me what I can try out to fix it, since I have no clue what caused this or what I can do about it (other than send it to repair, wich is the absolutely last resort). :crying:
Regards,
Lars S. Damsgaard
It appears your partition structure is corrupt, return it for a warranty repair.
Sent from my GT-I9300 using Tapatalk
boomboomer said:
It appears your partition structure is corrupt, return it for a warranty repair.
Sent from my GT-I9300 using Tapatalk
Click to expand...
Click to collapse
You could also flash it with ODIN, and include a *.pit file to repartition your phone. This will get your phone operational again. I had to do it about 2 weeks ago. Fire up ODIN, and flash the phone using the *.pit file I have attached to this post; and check the boxes marked "Auto-Reboot", "Re-Partition", "F. Reset Time", "Nand Erase All", and "Phone Bootloader Update". Doing all of this, and adding the *.pit file along with the *.tar.md5 file from sammobile, you will be able to get your phone back online. I have attached the *.pit file that I used to restore my phone. It is in the *.zip file. You'll need to extract it, and in ODIN, place it where it asks for a *.pit file. You can get an official ROM here:
http://www.sammobile.com/firmwares/1/?model=GT-I9300&pcode=0#firmware
Be sure kies is not running in the background before flashing thru odin.
Sent from my GT-I9300 using xda app-developers app
I did as you described with .pit and the right samsung update, but yet...
It says:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300XXUGNA5_I9300HTDGML1_I9300NEUGNA2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> Erase...
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Nand memory destroyed. Need new motherboard :c
Sent from my GT-I9300 using xda app-developers app
Was it the nand erase all that did that, or was my nand memory destroyed before trying out the .pit + rom restoration?
Have read some post and articles, that nand erase all should'nt be checked at anytime (mostly)..
Do you say, that I have a dead piece of plastic now? :crying:
godathuske said:
Was it the nand erase all that did that, or was my nand memory destroyed before trying out the .pit + rom restoration?
Have read some post and articles, that nand erase all should'nt be checked at anytime (mostly)..
Do you say, that I have a dead piece of plastic now? :crying:
Click to expand...
Click to collapse
U mean u selected nand erase all?
Sent from my GT-I9300 using xda app-developers app
JellyYogurt said:
U mean u selected nand erase all?
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
Yes, k-semler wrote: and flash the phone using the *.pit file I have attached to this post; and check the boxes marked "Auto-Reboot", "Re-Partition", "F. Reset Time", "Nand Erase All", and "Phone Bootloader Update".
I trusted this, since i believe you guys are experts :silly:
Was it wrong to trust this? Did I hardbrick my phone?
I can still start it in download mode. But I can´t get start it normally or in recoverymode. It just show alot of scrambled colors on the screen.
Try flashing a stock rom.
Sent from my GT-I9300 using xda app-developers app
Sorry for highjacking this thread, but my wifes S3 has nearly the same problem:
Stuck from one day to the other.
Running a custom mod for 1 1/2 years now, so no new change there..
Stuck at the S3 GT-i9300 Screen.
Can Start in download mode, but (little change here NOT in Recovery
Tried flashing an original rom via odin and downloadmode, and the pit file:
**********
Session begun.
Uploading PIT
ERROR: Failed to confirm end of PIT file transfer!
ERROR: PIT upload failed!
Ending session...
***********
Nothing more..
Any suggestions?
//I did not check the Nand erase box
Cholera said:
Sorry for highjacking this thread, but my wifes S3 has nearly the same problem:
Stuck from one day to the other.
Running a custom mod for 1 1/2 years now, so no new change there..
Stuck at the S3 GT-i9300 Screen.
Can Start in download mode, but (little change here NOT in Recovery
Tried flashing an original rom via odin and downloadmode, and the pit file:
**********
Session begun.
Uploading PIT
ERROR: Failed to confirm end of PIT file transfer!
ERROR: PIT upload failed!
Ending session...
***********
Nothing more..
Any suggestions?
//I did not check the Nand erase box
Click to expand...
Click to collapse
Don't be sorry... just dont hijack a thread?!?
hehe ok..
But as I had the time:
seems to be the sudden death syndrom:
http://forum.xda-developers.com/galaxy-s3/general/sudden-death-sds-dont-android-4-1-2-cwm-t2091045
Only solutions seems to send it to samsung
Having the same issue
Oh Well ..
i'm having the same issue .. i tried the following with my GT-i9300
http://forum.xda-developers.com/showthread.php?t=1840030 tried everything in this thread .. with no luck because each time i try flashing the VRALEC.bootchain.tar.md5 file it get stuck on "Start nand .."
I Tried flashing a new Stock ROM with no luck either
I Can Access the Download mode:
Product Name: GT- I9300
Custom Binary Download: NO
Current Binary: Samsung Official
System Status: Official
I Cannot access the Recovery mode as it keeps giving me lots of Red Lines with E: /sytem cannot found ..
I tried to use a PIT file with no Luck either
I used Odin 3.7, 3.9 & 1.85 .. and nothing is working
And I HAVE NOT IDEA WHAT IS WRONG with my phone whether it's a Hard or Soft Brick ..
Duhh .. am getting desperate ..
This is sds u have to replace emmc chip or motherboard
?★Sent from My GT-9300★?
If you can flash something via Odin, download this: http://techerrata.com/file/twrp2/i9300/openrecovery-twrp-2.6.3.1-i9300.tar . It is TWRP 2.6.3.1(2.7 does not work. Actually, when partitions are not read, it won't even show). You said your phone is as stock as possible, so i guess you tried to wipe using the stock Samsung Recovery.
Open the recovery, go to Wipe, and wipe everything in "Advanced wipe"(don't select the last one, as it is the external SD card). Then go to"Format data", type "yes"on the keyboard and let it format the data. Now reboot the recovery. ussualy, this solved my problems when playing with f2fs, rebooting recovery or the inability to mount the partitions you mentioned.
I would first try (after flashing the recovery) to flash a custom kernel, and if it still reboots, to flash this: http://forum.xda-developers.com/galaxy-s3/general/rom-justarchis-sammy-stock-deodex-root-t2689903 .It is the stock ROM, so you won't have FCs. I guess that this should add the missing files that does not allow the boot. But still, to flash a ROM, you will have to format at least data. Backup things first. See if you can backup data, and then restore it later to recover your photos or data.
You can connect the phone via USB, click "Mount" and then "Mount storage". Hopefully, you will be able to cces the internal SD card and save what you want.
Waiting for you to report
please need some help my Samsung s7273t is only giving it Samsung s7273t
Formatting /data...
E:format_volume: make_extf4s failed on /dev/block/mmcblk0p12
Formatting /cache...
E:format_volume: make_extf4s failed on /dev/block/mmcblk0p8
Data wipe complete
E:failed to mount /cache (Block device required)
E:Can´t mount /cache/recovery/log
E:Can´t open /cache/recovery/log
E:failed to mount /cache (Block device required)
E:Can´t mount /cache/recovery/last_log
E:Can´t open /cache/recovery/last_log
E:failed to mount /cache (Block device required)
E:Can´t mount /cache/recovery/last_install
E:Can´t open /cache/recovery/last_install
E:failed to mount /cache (Block device required)
Pablo Braga said:
please need some help my Samsung s7273t is only giving it Samsung s7273t
Formatting /data...
E:format_volume: make_extf4s failed on /dev/block/mmcblk0p12
Formatting /cache...
E:format_volume: make_extf4s failed on /dev/block/mmcblk0p8
Data wipe complete
E:failed to mount /cache (Block device required)
E:Can´t mount /cache/recovery/log
E:Can´t open /cache/recovery/log
E:failed to mount /cache (Block device required)
E:Can´t mount /cache/recovery/last_log
E:Can´t open /cache/recovery/last_log
E:failed to mount /cache (Block device required)
E:Can´t mount /cache/recovery/last_install
E:Can´t open /cache/recovery/last_install
E:failed to mount /cache (Block device required)
Click to expand...
Click to collapse
So many people having the same problem! =P
My i9300 isstuck on PIT file Error/NAND Write , on adb sideload apears failed to mount file!
Someone have a ideia with sdcard i can fix installing some custom recovery / rom ?
my phone is Samsung Galaxy SIII GT-I9300
can start the phone in download mode and in recovery mode.
When I start the phone in recovery mode i get the following errors:
E: failed to mount /efs (No such file or directory)
E: failed to mount /system (No such file or directory)
# Manual Mode#
E: failed to mount system (No such file or directory)
E: Can´t mount /system
E: failed to mount /cache (No such file or directory)
E: Can´t mount /cache/recovery/last_recovery
E: failed to mount /data (No such file or directory)
E: Can´t mount /data/log/recovery:log.txt
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/last_log
E: Can´t open /cache/recovery/last_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)
I have tried to wipe cache partition and do a data/factory reset, but without any luck.
When i try to do a data/factory reset it says:
-- Wiping data...
Formatting /data...
E:format_volume: make_extf4s failed on /dev/block/mmcblk0p12
Formatting /cache...
E:format_volume: make_extf4s failed on /dev/block/mmcblk0p8
Data wipe complete
E:failed to mount /cache (Block device required)
E:Can´t mount /cache/recovery/log
E:Can´t open /cache/recovery/log
E:failed to mount /cache (Block device required)
E:Can´t mount /cache/recovery/last_log
E:Can´t open /cache/recovery/last_log
E:failed to mount /cache (Block device required)
E:Can´t mount /cache/recovery/last_install
E:Can´t open /cache/recovery/last_install
E:failed to mount /cache (Block device required)
I hope someone here can tell me what I can try out to fix it, since I have no clue what caused this or what I can do about it
same problem...
baddooor1 said:
my phone is Samsung Galaxy SIII GT-I9300
can start the phone in download mode and in recovery mode.
When I start the phone in recovery mode i get the following errors:
E: failed to mount /efs (No such file or directory)
E: failed to mount /system (No such file or directory)
# Manual Mode#
E: failed to mount system (No such file or directory)
E: Can´t mount /system
E: failed to mount /cache (No such file or directory)
E: Can´t mount /cache/recovery/last_recovery
E: failed to mount /data (No such file or directory)
E: Can´t mount /data/log/recovery:log.txt
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/last_log
E: Can´t open /cache/recovery/last_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)
I have tried to wipe cache partition and do a data/factory reset, but without any luck.
When i try to do a data/factory reset it says:
-- Wiping data...
Formatting /data...
E:format_volume: make_extf4s failed on /dev/block/mmcblk0p12
Formatting /cache...
E:format_volume: make_extf4s failed on /dev/block/mmcblk0p8
Data wipe complete
E:failed to mount /cache (Block device required)
E:Can´t mount /cache/recovery/log
E:Can´t open /cache/recovery/log
E:failed to mount /cache (Block device required)
E:Can´t mount /cache/recovery/last_log
E:Can´t open /cache/recovery/last_log
E:failed to mount /cache (Block device required)
E:Can´t mount /cache/recovery/last_install
E:Can´t open /cache/recovery/last_install
E:failed to mount /cache (Block device required)
I hope someone here can tell me what I can try out to fix it, since I have no clue what caused this or what I can do about it
Click to expand...
Click to collapse
Any progress? I have the same problem with my GS3
mchagas said:
Any progress? I have the same problem with my GS3
Click to expand...
Click to collapse
Does your device boot normally?
GeekyDroid said:
Does your device boot normally?
Click to expand...
Click to collapse
My S3 is stuck at samsung logo... when I try to get on recovery mode, it appears the same messages as described...
Image is inside the ZIP. I'm at work, could not do anything better.
mchagas said:
Image is inside the ZIP. I'm at work, could not do anything better.
Click to expand...
Click to collapse
Seems like your partitions are messed up. Did you try to flash stock ROM through odin?
GeekyDroid said:
Seems like your partitions are messed up. Did you try to flash stock ROM through odin?
Click to expand...
Click to collapse
Yes, but no success... I get a error in the beggining of the process... I just don't remember the message exactly (maybe something related to NAND (?), I guess the preccess don't starts at all), and I haven't ODIN here to see the error... I tried wth diferent versions of ODIN, without success.
Everything started when my S3 started to shutdown ramdomly, I flashed it a stock rom and it worked for a week without so much problems, some reboots, but was fine.
Then it shutdown and got stuck at samsung logo... In recovery mode it showed me this screen... I'm new to ODIN, just don't know what to do next.
mchagas said:
Yes, but no success... I get a error in the beggining of the process... I just don't remember the message exactly (maybe something related to NAND (?), I guess the preccess don't starts at all), and I haven't ODIN here to see the error... I tried wth diferent versions of ODIN, without success.
Everything started when my S3 started to shutdown ramdomly, I flashed it a stock rom and it worked for a week without so much problems, some reboots, but was fine.
Then it shutdown and got stuck at samsung logo... In recovery mode it showed me this screen... I'm new to ODIN, just don't know what to do next.
Click to expand...
Click to collapse
Sorry, I also don't know how to help you further. I will do some research. Maybe I'll find something.
mchagas said:
Yes, but no success... I get a error in the beggining of the process... I just don't remember the message exactly (maybe something related to NAND (?), I guess the preccess don't starts at all), and I haven't ODIN here to see the error... I tried wth diferent versions of ODIN, without success.
Everything started when my S3 started to shutdown ramdomly, I flashed it a stock rom and it worked for a week without so much problems, some reboots, but was fine.
Then it shutdown and got stuck at samsung logo... In recovery mode it showed me this screen... I'm new to ODIN, just don't know what to do next.
Click to expand...
Click to collapse
As suggested looks like your partitions are corrupt you can try the rescue firmware here >> http://forum.xda-developers.com/showpost.php?p=30087735&postcount=6 << if not service recommended.
tallman43 said:
As suggested looks like your partitions are corrupt you can try the rescue firmware here >> http://forum.xda-developers.com/showpost.php?p=30087735&postcount=6 << if not service recommended.
Click to expand...
Click to collapse
I'll try it when I get home!
Anything else I should do? Or just flash it?
mchagas said:
I'll try it when I get home!
Anything else I should do? Or just flash it?
Click to expand...
Click to collapse
It contains a pit file so follow the instructions exactly.
tallman43 said:
It contains a pit file so follow the instructions exactly.
Click to expand...
Click to collapse
I forgot to mention, my S3 is from Brasil, any problem? May I use the files from the URL you sent me?
mchagas said:
I forgot to mention, my S3 is from Brasil, any problem? May I use the files from the URL you sent me?
Click to expand...
Click to collapse
Mmm..Depends what model is it the Galaxy S3 I9300 international? if not no! Also if it is not this model maybe the reason your phone is messed up is if you have flashed anything from this forum!:crying:
tallman43 said:
Mmm..Depends what model is it the Galaxy S3 I9300 international? if not no! Also if it is not this model maybe the reason your phone is messed up is if you have flashed anything from this forum!:crying:
Click to expand...
Click to collapse
No, I flashed a stock ROM for brazilians devices! And it worked for a week, after I flashed it
I don't know the S3 model exactly...
This is the tutorial I followed, it is in PT-BR and is designed for the brazilian model
http://www.smartzone.com.br/2013/12...d-4-3-oficial-do-brasil-para-o-galaxy-s3.html
May I use the PDA from this tuto and the others files from the URL you sent me?
When I try to flash the s3 again, this is what happens:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300UBUGNE1_I9300ZTOUGNE1_I9300UBUGNF1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> sboot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<ID:0/003> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
:crying:
mchagas said:
I'll try it when I get home!
Anything else I should do? Or just flash it?
Click to expand...
Click to collapse
I guess you just have to flash it.
GeekyDroid said:
I guess you just have to flash it.
Click to expand...
Click to collapse
Nothing seems to work... tried some pit files, without success.
Starting to guess it's a eMMC problem
Any ideas?
Yip as tallman43 says it sounds like this http://forum.xda-developers.com/galaxy-s3/general/sudden-death-sds-dont-android-4-1-2-cwm-t2091045
Hello,
I've got the same issue on a GT-S7710 (aka "Skomer") since I did a bad flashing.
I tried to flash again from the sdcard, but it is impossible. Lauching a file manager from sdcard is impossible too.
Concerning ADB, the phone is detected, but flashing is impossible. Odin doesn't detect the phone.
Anybody can help me ?
Pascal06 said:
Hello,
I've got the same issue on a GT-S7710 (aka "Skomer") since I did a bad flashing.
I tried to flash again from the sdcard, but it is impossible. Lauching a file manager from sdcard is impossible too.
Concerning ADB, the phone is detected, but flashing is impossible. Odin doesn't detect the phone.
Anybody can help me ?
Click to expand...
Click to collapse
Nope, everything here is for the i9300. Flash anything from here and it will ruin your phone further. You need to go into the threads for your model.
Hey guys, sorry for what seems like a duplicate post, but I promise the combination of problems here is unique (at least to XDA).
I'd really appreciate your help. And I'll try to be succint.
Current state:
Flashing anything using 'Bootloader' or 'PDA' options in Odin 3.07 leads to NAND Write problem (documented here) with this log:
<ID:0/010> Added!!
<ID:0/010> Odin v.3 engine (ID:10)..
<ID:0/010> File analysis..
<ID:0/010> SetupConnection..
<ID:0/010> Initialzation..
<ID:0/010> Get PIT for mapping..
<ID:0/010> Firmware update start..
<ID:0/010> sboot.bin
<ID:0/010> NAND Write Start!!
<ID:0/010> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/010> Removed!!
TWRP (Team Win Recovery Project v2.7.1.0) recovery shows this log:
E:Unable to find partition size for '/boot'
E:Unable to find partition size for '/recovery'
Erimary block device '/dev/block/mmcblk0p12' for mount point '/data' is not present!
E:Unable to mount '/data'
E:Unable to recreate /data/media folder.
E:Unable to mount '/efs'
E:Unable to mount '/cache'
E:Unable to mount '/system'
E:Unable to mount '/data'
E:Unable to mount '/preload'
E:Unable to mount internal storage.
E:Unable to mount /data/media during GUI startup.
E:Unable to mount '/cache'
Full SELinux support is present.
E:Unable to mount /data/media/TWRP/.twrp when trying to read settings file.
and this problem is documented here
I checked using TWRP's file manager and there are no mmcblk* files in /dev/block/. The file manager shows every other partition as blank btw.
TWRP says 'No OS installed' and I think it is (effectively) so since the relevant partitions cannot be accessed and are seen as being blank by recovery. Long pressing only the power button leads to a persistent 'Samsung Galaxy S3' logo, ie, a bootloop.
The phone is a GT-I9300
How I got here
I think it's because the Sudden Death Syndrome struck as I was trying to troubleshoot a regularly self-corrupting /data partition. Will add more details if you ask, but I've got a feeling they're really not relevant at this point.
Questions
It seems the first step to fixing the 'Can't mount partitions' problem is to be able to flash using Odin. I can't do that because of the NAND Write problem. The NAND Write XDA post which I linked to above as well says that flashing a PIT is the only way out, but I would hope someone experienced could verify whether this extreme step is the one I should be taking at this point.
You must repartition: it's the only way out. And easy, btw.
Awreccan said:
Hey guys, sorry for what seems like a duplicate post, but I promise the combination of problems here is unique (at least to XDA).
I'd really appreciate your help. And I'll try to be succint.
Current state:
Flashing anything using 'Bootloader' or 'PDA' options in Odin 3.07 leads to NAND Write problem (documented here) with this log:
<ID:0/010> Added!!
<ID:0/010> Odin v.3 engine (ID:10)..
<ID:0/010> File analysis..
<ID:0/010> SetupConnection..
<ID:0/010> Initialzation..
<ID:0/010> Get PIT for mapping..
<ID:0/010> Firmware update start..
<ID:0/010> sboot.bin
<ID:0/010> NAND Write Start!!
<ID:0/010> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/010> Removed!!
TWRP (Team Win Recovery Project v2.7.1.0) recovery shows this log:
E:Unable to find partition size for '/boot'
E:Unable to find partition size for '/recovery'
Erimary block device '/dev/block/mmcblk0p12' for mount point '/data' is not present!
E:Unable to mount '/data'
E:Unable to recreate /data/media folder.
E:Unable to mount '/efs'
E:Unable to mount '/cache'
E:Unable to mount '/system'
E:Unable to mount '/data'
E:Unable to mount '/preload'
E:Unable to mount internal storage.
E:Unable to mount /data/media during GUI startup.
E:Unable to mount '/cache'
Full SELinux support is present.
E:Unable to mount /data/media/TWRP/.twrp when trying to read settings file.
and this problem is documented here
I checked using TWRP's file manager and there are no mmcblk* files in /dev/block/. The file manager shows every other partition as blank btw.
TWRP says 'No OS installed' and I think it is (effectively) so since the relevant partitions cannot be accessed and are seen as being blank by recovery. Long pressing only the power button leads to a persistent 'Samsung Galaxy S3' logo, ie, a bootloop.
The phone is a GT-I9300
How I got here
I think it's because the Sudden Death Syndrome struck as I was trying to troubleshoot a regularly self-corrupting /data partition. Will add more details if you ask, but I've got a feeling they're really not relevant at this point.
Questions
It seems the first step to fixing the 'Can't mount partitions' problem is to be able to flash using Odin. I can't do that because of the NAND Write problem. The NAND Write XDA post which I linked to above as well says that flashing a PIT is the only way out, but I would hope someone experienced could verify whether this extreme step is the one I should be taking at this point.
Click to expand...
Click to collapse
Well done on the research etc you have done so far.
Only option left is to try this recovery firmware, if it fails replace motherboard as the emmc chip has died.
http://forum.xda-developers.com/galaxy-s3/help/compressing-roms-nandroid-backups-t2896030
Make sure you follow the instructions exactly, including the PIT.
If your partition regularly corrupted then likely the nand memory had too many bad blocks, now cascade failure of the emmc.
Repartitioning won't work
Thanks for the replies guys.
I've tried repartitioning with Odin versions 1.83, 1.85, 3.04, 3.05, and 3.07. I have tried using 3 .pit files I've found on various threads on XDA. I've tried 2 USB ports. That's 5 x 3 x 2 = 30 combinations - and I'm not saying I've tried all 30, but I've tried about 15 I think.
Consistently, with versions 1.83-3.05, I get this output in a second after pressing 'Start':
<ID:0/011> Added!!
<ID:0/011> Odin v.3 engine (ID:11)..
<ID:0/011> File analysis..
<ID:0/011> SetupConnection..
<ID:0/011> Initialzation..
<ID:0/011> Set PIT file..
<ID:0/011> DO NOT TURN OFF TARGET!!
<ID:0/011>
<ID:0/011> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
And with Odin version 3.07, I get stuck at:
<ID:0/011> Added!!
<ID:0/011> Odin v.3 engine (ID:11)..
<ID:0/011> File analysis..
<ID:0/011> SetupConnection..
<ID:0/011> Initialzation..
<ID:0/011> Set PIT file..
<ID:0/011> DO NOT TURN OFF TARGET!!
<ID:0/011> Get PIT for mapping..
Upon which I have to (with much trepidation) close Odin or pull out the USB cord.
Is there anything else I can do?
You have to flash PIT along with a firmware, like the rescue firmware thread. If you did try that then your emmc chip is corrupt or damage.
Try read the dead boot recovery thread in general forum.
boomboomer said:
You have to flash PIT along with a firmware, like the rescue firmware thread. If you did try that then your emmc chip is corrupt or damage.
Try read the dead boot recovery thread in general forum.
Click to expand...
Click to collapse
Is this the thread you're suggesting I follow?
[Galaxy S III][IMPORTANT] GT-I9300 Hard Brick Fix
No, this one
http://forum.xda-developers.com/showthread.php?t=2647558
boomboomer said:
No, this one
http://forum.xda-developers.com/showthread.php?t=2647558
Click to expand...
Click to collapse
Ok thanks for that. But since that solution requires a Z3X box and UART cable (the former being something I can't cheaply procure where I live - and I've spent too much money on various fixes for this GT-I9300), and that too only to check whether my phone can be salvaged or really needs the EMMC chip replaced, I'm not going follow through with the guide you've provided - which sounds fun to try nevertheless.
Thanks everyone here!
I have the same issue
boomboomer said:
No, this one
http://forum.xda-developers.com/showthread.php?t=2647558
Click to expand...
Click to collapse
I got this after downgrading from Lollipop(CM13) to KitKat(CM11). Should I follow this thread you suggested?
The phone can boot into Download Mode and Recovery mode. I've been googling about this problem for like a week now. the first attempt that I did was using Odin and downloading the *.md5.tar for my phone. It gave me several errors:
<Download mode details on the top left corner:>
ODIN MODE
PRODUCT NAME: GT-i9300
CUSTOM BINARY DOWNLOAD: No
CURRENT BINARY: Samsung Official
SYSTEM OFFICIAL: Official
<Odin GUI Errors:>
[FAIL]
ID/COM: [COM9]
<ID:0/009> Added!!
<ID:0/009> Odin v.3 engine (ID:9)..
<ID:0/009> File analysis..
<ID:0/009> SetupConnection..
<ID:0/009> Complete(Write) operation failed.
<ID:0/009> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
Next I tried recovery mode. While entering recovery. I got errors also:
Starting Recovery mode errors:
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)
can't mount '/cache' (No such file or directory)
E:failed to mount /cache (No such file or directory)
Can't mount /cache/recovery/last_recovery
E:failed to mount /data (No such file or directory)
E:Can't mount /data/log/recovery_log.txt
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/last_log
E:Can't open /cache/recovery/last_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)
<After those errors stop appearing. The top part gets replaced with:>
Android system recovery <3e>
Volume up/down to move highlights;
power button to select.
reboot system now
apply update from ADB
apply update from external storage
wipe data/factory reset
wipe cache partition
apply update from cache
----------------------------------------
<When selecting "Apply update from ADB sideload / cache / external storage (also known as sdcard)". Errors are:>
E:failed to mount /system (Block device required)
E:failed to mount /cache (Block device required)
<If ADB is selected. the last lines say:>
Now send the package you want to apply
to the device with "adb sideload <filena
me>"...
<If external storage is selected. the last lines say:>
E:failed to mount /sd card (No such file or directory)
<When selecting "wipe data and fatory reset and/or wipe cache partition". Errors are:>
E:format_volume: make_extf4fs failed on /dev/block/MMCBLK0P12
E:format_volume: make_extf4fs failed on /dev/block/MMCBLK0P8
Please help
UPDATE: While I'm attempting to restore the *.zip update with ADB. The process goes to:
loading update.zip
sending update.zip ?? % (with underscores spazing from left to right)
and then looking from the phone.
it says:
<<<some things that I forgot after the sideload. the errors goes too fast for me>>>
Installation aborted
E: Can't mount /cache (Block device required)
E: Can't mount /system (Block device required)
E: Can't mount /efs (Block device required)
Try using different USB cables and USB ports to flash with Odin. I also recommend using Odin 3.07 as that has always worked for me.
Borked recovery. Flash back to stock is the best option but if that is failing then you don't really have much choice.
Beamed in by telepathy
audit13 said:
Try using different USB cables and USB ports to flash with Odin. I also recommend using Odin 3.07 as that has always worked for me.
Click to expand...
Click to collapse
I did borrow an original cable from my friend. The error is still there. I also tried plugging the cable from the rear usb port.
But thanks for the reply. I hope that others can find this helpful too
shivadow said:
Borked recovery. Flash back to stock is the best option but if that is failing then you don't really have much choice.
Beamed in by telepathy
Click to expand...
Click to collapse
Hmm.. "Borked recovery"? You mean that every command / operation that the recovery mode is performing are being blocked by the system itself? or you mean by errors in files inside the eMMC? There is no proof that the eMMC is damaged because it can boot to Download mode and recovery mode. I am still wondering if the recovery, download mode have their own eMMC.
BTW is it "ok" to use an SDHC for recovery image (selecting "Apply Update from external storage")? bcoz its the only one I have ATM (and no cash)
I am willing to go for SD card as an internal memory for the phone. I've read many articles about running your phone from SD card if the internal memory. But with one disadvantage. Read and Write are slower than eMMC. As much as I want to perform this operation but I don't have JTAG or other tools to start with. I also don't know what resistor to short.
Hi All,
I have a Samsung Galaxy S7 - SM-G930FD - Dual sim . I received a pop up message to apply a update, however since then I've had issues.
Initially phone Displayed Android icon and Yellow warning.
Currently the Phone will not boot and the only things I can do is get into download mode, see several errors and cannot load up phone.
Download Mode shows:
====================
ODIN MODE
DOWNLOAD SPEED: FAST
PRODUCT NAME: SM-G9030F
CURRENT BINARY: SAMSUNG OFFICIAL
SYSTEM STATUS: OFFICIAL
FRP LOCK: ON
SECURE DOWNLOAD: ENABLED
WARRANTY VOID: 0(0X0000)
AP SWREV: B:7 K:5 S: 6
======================
-Sometimes Phone displays: An error has occurred while updating the device software. Use the Emergency recovery function in the Smart PC software.
-Occasionally it displayed following Erasing (blue screen with Android icon), Installing system update (blue screen with Android icon) and then the 3rd screen goes to
=============================================
#fail to open recovery_cause(No such file or dictory)#
#Reboot recovery cause is [unknown]#
No support single-SKU
File-Based OTA
E: failed to mount /efs (invalid argument)
Supported API: 3
E: failed to mount /efs (invalid argument)
E: failed to mount /persdata (invalid argument)
--Wiping persdata
Formatting /persdata
E: NDF_RECOVERY: cannot initialize
Persdata wipe failed
E: failed to mount /persdata (invalid argument)
dm-verity verification failed...
E: failed to mount /cache (invalid argument)
E: failed to mount /cache (invalid argument)
E: failed to mount /cache (invalid argument)
E: failed to mount /cache (invalid argument)
E: Can't mount /cache/recover/last_locale
=========================================
The steps I've taken so far is:
-Tried to clear cache however I am no longer able to do this any more...
-Downloaded Odin3 v3.14
-Downloaded firmware from Sam mobile ...galaxy-s7/firmware/SM-G930FD/INS/download/G930FXXU7ETA9/323883
-Put phone in boot mode, loaded Odin .........once Odin said added and 0 : [COM7] in blue selected the BL, AP, CP & Home_CSC & clicked start (left all options as default in Odin)
it carries out steps until param.bin and eventually fails 5-10mins later.
I tried with just the CSC instead of Home_CSC...however does not pass.
I've charged my mobile with mains connection, however phone does not have any red indication light, however when I plug phone to PC I'm able to leave phone in Download mode for a long period of time with blue screen on.
I've also tried the SM-G930F firmware (from Sammobile) as though as my ODIN Download screen does not mention D at the end of SM-G930F it may be wrong version, however sticker on the back of phone indicates SM-G930FD...
I've also tried downloading SmartSwitchPC_Setup.exe, however once installed it says my device is not compatible.
I've also tried 2 other genuine Samsung cables and tried this on another PC, but this does not seem to work.
Please could someone help resolve?
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Odin engine v(ID:3.1401)..
<ID:0/007> File analysis..
<ID:0/007> Total Binary size: 3992 M
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Set PIT file..
<ID:0/007> DO NOT TURN OFF TARGET!!
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> NAND Write Start!!
<ID:0/007> SingleDownload.
<ID:0/007> sboot.bin
<ID:0/007> param.bin
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Clearing /cache won't do anything for you what so ever. What did you do to end up at this point?
TheExploitedOne said:
Clearing /cache won't do anything for you what so ever. What did you do to end up at this point?
Click to expand...
Click to collapse
I ran software update (prompt which came from Samsung), which restarted my phone and I couldn't access my phone after this point.....as the Andriod image kept saying erasing and installing and then kept restarting my device. I then put into Download mode and tried to flash with latest Firmware from Sam Mobile
Shriji said:
I ran software update (prompt which came from Samsung), which restarted my phone and I couldn't access my phone after this point.....as the Andriod image kept saying erasing and installing and then kept restarting my device. I then put into Download mode and tried to flash with latest Firmware from Sam Mobile
Click to expand...
Click to collapse
I found your device firmware and it should be the latest version. I'm uploading it now to my Mega cloud storage and can give you the download link. I'll keep it hosted in case others need it as well
UPDATE:
Here is the link to your device firmware (SM-G390FD)
https://mega.nz/file/eUs1kTYD#TWGvpN4gzt2cZ938ERPcoLcrsGz2Qr71GM9rHjoQnlQ
When flashing don't use home_csc just use the normal csc. This should flash normally to your device