Hey everybody, I spent the last two days reading up and down the forum and simply cant find an solution to recover my soft bricked SCH-545.
I was on a MK2 firmware. I rooted my phone using the saferootmethod which worked fine. Than I wanted to flash Hiperdrive RLS 15 on my device using safestrap. Here the flash ran all the way through but my phone simply wouldnt boot anymore (boot freeze). At this point I still could go into safestrap recovery mode. So I decided to select another rom. Unfortunatelly I dont know anymore which one. Stupid me! The end of the story, it didnt work "Firmware upgrade encountred an issue. Please select recovery mode in Kies and try again". I cant go into recovery mode anymore and Kies wont detect the device. I only can go into download mode. This works still fine.
So I decided to follow this threat (http://forum.xda-developers.com/showthread.php?t=2578209) in order to recover the device. I tried both, full-wipe and no-wipe / with and without pit file. I also tried different USB cable (original samsung and other) and different USB hubs. But I always get following error:
<ID:0/003> Removed!!
<ID:0/003> Added!!
<ID:0/003> Removed!!
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> ALL_I545VRUEMK2_I545VZWEMK2_1937946_REV06_user_low_ship_MULTI_CERT.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> 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> SingleDownload.
<ID:0/003> sbl1.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl2.mbn
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> aboot.mbn
<ID:0/003> tz.mbn
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> persdata.img.ext4
<ID:0/003> system.img.ext4
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
The next end last attempt was to download the stock firmware from sammobile.com (I545VRUEMJ7, I545VRUEMK2, I545VRUFNC5). But also the same error. I know now that you cannot downgrade but I still gave it a shot thinking that I might was mistaken with the built number MK2. But when I bought the phone it came with 4.2.2 and I know that I upgraded it to 4.3 at some point later.
Also, In the downloading mode, in the top left corner it says:
Write protection: enabled
eMMC Burst Mode: enabled
Now I simply dont know what I can do anymore. Is there somebody else you experiences / experienced similar issues or somebody who could point me in the right direction. Any help would be greatly appreciated. Thanks a thousand times!!!
BabelDev said:
Hey everybody, I spent the last two days reading up and down the forum and simply cant find an solution to recover my soft bricked SCH-545.
I was on a MK2 firmware. I rooted my phone using the saferootmethod which worked fine. Than I wanted to flash Hiperdrive RLS 15 on my device using safestrap. Here the flash ran all the way through but my phone simply wouldnt boot anymore (boot freeze). At this point I still could go into safestrap recovery mode. So I decided to select another rom. Unfortunatelly I dont know anymore which one. Stupid me! The end of the story, it didnt work "Firmware upgrade encountred an issue. Please select recovery mode in Kies and try again". I cant go into recovery mode anymore and Kies wont detect the device. I only can go into download mode. This works still fine.
So I decided to follow this threat (http://forum.xda-developers.com/showthread.php?t=2578209) in order to recover the device. I tried both, full-wipe and no-wipe / with and without pit file. I also tried different USB cable (original samsung and other) and different USB hubs. But I always get following error:
<ID:0/003> Removed!!
<ID:0/003> Added!!
<ID:0/003> Removed!!
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> ALL_I545VRUEMK2_I545VZWEMK2_1937946_REV06_user_low_ship_MULTI_CERT.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> 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> SingleDownload.
<ID:0/003> sbl1.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl2.mbn
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> aboot.mbn
<ID:0/003> tz.mbn
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> persdata.img.ext4
<ID:0/003> system.img.ext4
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
The next end last attempt was to download the stock firmware from sammobile.com (I545VRUEMJ7, I545VRUEMK2, I545VRUFNC5). But also the same error. I know now that you cannot downgrade but I still gave it a shot thinking that I might was mistaken with the built number MK2. But when I bought the phone it came with 4.2.2 and I know that I upgraded it to 4.3 at some point later.
Also, In the downloading mode, in the top left corner it says:
Write protection: enabled
eMMC Burst Mode: enabled
Now I simply dont know what I can do anymore. Is there somebody else you experiences / experienced similar issues or somebody who could point me in the right direction. Any help would be greatly appreciated. Thanks a thousand times!!!
Click to expand...
Click to collapse
Well, this is different. Normally, the "Complete (Write) operation failed." has some info displayed on the phone that says why it failed.
I'd start with installing Samsung Kies and trying to recover using that.
k1mu said:
Well, this is different. Normally, the "Complete (Write) operation failed." has some info displayed on the phone that says why it failed.
I'd start with installing Samsung Kies and trying to recover using that.
Click to expand...
Click to collapse
Hi thank for your quick response. I get this message on Odin. In the screen of the device you only see a progress bar that stops. Thats It.
I also tried installing / reinstalling Kies and the samsung driver but it wont detect my device. So it seems that this is not an option either.
BabelDev said:
Hi thank for your quick response. I get this message on Odin. In the screen of the device you only see a progress bar that stops. Thats It.
I also tried installing / reinstalling Kies and the samsung driver but it wont detect my device. So it seems that this is not an option either.
Click to expand...
Click to collapse
PS: Odin detects the device but Kies does not.
BabelDev said:
Hey everybody, I spent the last two days reading up and down the forum and simply cant find an solution to recover my soft bricked SCH-545.
I was on a MK2 firmware. I rooted my phone using the saferootmethod which worked fine. Than I wanted to flash Hiperdrive RLS 15 on my device using safestrap. Here the flash ran all the way through but my phone simply wouldnt boot anymore (boot freeze). At this point I still could go into safestrap recovery mode. So I decided to select another rom. Unfortunatelly I dont know anymore which one. Stupid me! The end of the story, it didnt work "Firmware upgrade encountred an issue. Please select recovery mode in Kies and try again". I cant go into recovery mode anymore and Kies wont detect the device. I only can go into download mode. This works still fine.
So I decided to follow this threat (http://forum.xda-developers.com/showthread.php?t=2578209) in order to recover the device. I tried both, full-wipe and no-wipe / with and without pit file. I also tried different USB cable (original samsung and other) and different USB hubs. But I always get following error:
<ID:0/003> Removed!!
<ID:0/003> Added!!
<ID:0/003> Removed!!
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> ALL_I545VRUEMK2_I545VZWEMK2_1937946_REV06_user_low_ship_MULTI_CERT.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> 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> SingleDownload.
<ID:0/003> sbl1.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl2.mbn
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> aboot.mbn
<ID:0/003> tz.mbn
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> persdata.img.ext4
<ID:0/003> system.img.ext4
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
The next end last attempt was to download the stock firmware from sammobile.com (I545VRUEMJ7, I545VRUEMK2, I545VRUFNC5). But also the same error. I know now that you cannot downgrade but I still gave it a shot thinking that I might was mistaken with the built number MK2. But when I bought the phone it came with 4.2.2 and I know that I upgraded it to 4.3 at some point later.
Also, In the downloading mode, in the top left corner it says:
Write protection: enabled
eMMC Burst Mode: enabled
Now I simply dont know what I can do anymore. Is there somebody else you experiences / experienced similar issues or somebody who could point me in the right direction. Any help would be greatly appreciated. Thanks a thousand times!!!
Click to expand...
Click to collapse
This is what you should do;
1. First boot in to linux (google "dual-boot linux and windows 7" or "boot linux live cd" if you dont know how to get linux)
2. Download this file and this file
3. Next, open terminal emulator (google "how to open terminal emulator in linux" if you dont know how to open terminal emulator.) and then copy and paste the following into terminal:
Code:
find . -name "Heimdall1.4c2debian.sh" -exec cp {} ~/ \;
find ~/ -name "Heimdall1.4c2debian.sh" -type f -exec chmod 755 {} \;
sh ~/Heimdall1.4c2debian.sh
4. Type in your password (dont worry if it looks like no characters are being entered when you type your password, this is normal hit enter after your done typing your password) if all went well heimdall-frontend should open up.
5. In the "flash" tab under "PIT" select browse and find the pit file i had you download in step 2.
6. Under "Partitions (Files)" select add then change the Partition type to SYSTEM and choose the system.img.ext4 file that you can get from the ALL_I545VRUEMK2_I545VZWEMK2_1937946_REV06_user_low_ship_MULTI_CERT.tar.md5 you downloaded earlier (rename the end of the file from tar.md5 to .tar then extract it) then click "Add" and then "Remove"
7. Go over to the "Utilities" tab and select "detect" then go back to the flash tab and select "start". If all goes well this should recover your device.
Sorry about telling you to google this or that, but if I had to type out the whole process I think I would've just given up typing a response at all.
Code:
find . -name "Heimdall1.4c2debian.sh" -exec cp {} ~/ \;
find ~/ -name "Heimdall1.4c2debian.sh" -type f -exec chmod 755 {} \;
sh ~/Heimdall1.4c2debian.sh
Hey and thank you. I am installing Ubuntu right now. Just for clarity, you want me to copy and paste the exact code including ";" or do I need to modify it in any way?
I will keep the forum updated on my "progress".
Thank you guys a thousand times.
So I installed Ubuntu via VMware on my OSX, copied all the files on my virtual machine and opened the terminal. So far, so good.
But when I entered the commands I get following error "missing argument to `-exec'" (see screenshot).
Help would be greatly appreciated. Thank you!
BabelDev said:
So I installed Ubuntu via VMware on my OSX, copied all the files on my virtual machine and opened the terminal. So far, so good.
But when I entered the commands I get following error "missing argument to `-exec'" (see screenshot).
Help would be greatly appreciated. Thank you!
Click to expand...
Click to collapse
you removed both semi-colons. Literally copy and paste what I typed.
Sent from my SCH-I545 using XDA Premium 4 mobile app
Surge1223 said:
you removed both semi-colons. Literally copy and paste what I typed.
Sent from my SCH-I545 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I did that to but receive an "Syntax error: redirection unexpected"
Thanks for you quick response!!
BabelDev said:
I did that to but receive an "Syntax error: redirection unexpected"
Thanks for you quick response!!
Click to expand...
Click to collapse
try typing this in terminal:
Code:
bash ~/Heimdall1.4c2debian.sh
and if that doesnt work try:
Code:
cd ~/
chmod 777 Heimdall1.4c2debian.sh
./Heimdall1.4c2debian.sh
Sent from my SCH-I545 using XDA Premium 4 mobile app
Surge1223 said:
try typing this in terminal:
Code:
bash ~/Heimdall1.4c2debian.sh
and if that doesnt work try:
Code:
cd ~/
chmod 777 Heimdall1.4c2debian.sh
./Heimdall1.4c2debian.sh
Sent from my SCH-I545 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I tried both commands now and both seem to work. I type in the passwords and it runs. Than it asks me a second time for the pass and than I get an "Authentication failure". Tried it multiple times with both commands, always the same (see screenshot)
If it doesnt work with ubuntu, do you think I just should tried it with the OSX version of Heimdall?
Thank you!
BabelDev said:
I tried both commands now and both seem to work. I type in the passwords and it runs. Than it asks me a second time for the pass and than I get an "Authentication failure". Tried it multiple times with both commands, always the same (see screenshot)
If it doesnt work with ubuntu, do you think I just should tried it with the OSX version of Heimdall?
Thank you!
Click to expand...
Click to collapse
ok open terminal and type this in, when it asks for the password just hit enter, dont actually type a password.
Code:
sudo su
then finally copy and paste the below:
Code:
find . -name "Heimdall1.4c2debian.sh" -exec cp {} ~/ \;
find ~/ -name "Heimdall1.4c2debian.sh" -type f -exec chmod 755 {} \;
bash ~/Heimdall1.4c2debian.sh
you can replace the last line with the below if it the above doesnt work.
Code:
cd ~/
chmod 777 Heimdall1.4c2debian.sh
./Heimdall1.4c2debian.sh
Thanks again surge1223. This time Heimdall fronted started but after following your instructions I get a "Failed to begin session!". I attached again a screenshot. Any leads on went wrong? Thank you.
PS: Here the full status description from Heimdall:
Heimdall v1.4.1
Copyright (c) 2010-2014 Benjamin Dobell, Glass Echidna
http://www.glassechidna.com.au/
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
http://www.glassechidna.com.au/donate/
Initialising connection...
Detecting device...
Claiming interface...
Attempt failed. Detaching driver...
Claiming interface again...
Setting up interface...
Initialising protocol...
Protocol initialisation successful.
Beginning session...
ERROR: Failed to begin session!
Releasing device interface...
Re-attaching kernel driver...
BabelDev said:
Thanks again surge1223. This time Heimdall fronted started but after following your instructions I get a "Failed to begin session!". I attached again a screenshot. Any leads on went wrong? Thank you.
Click to expand...
Click to collapse
connect the phone to a different usb port, then type this in terminal hit enter when it asks for pass
Code:
sudo su
then:
Code:
sudo apt-get update && sudo apt-get upgrade
if you're not using a live cd then I would recommend rebooting here but if you are using a live cd dont reboot then in the same terminal window type the following (if you didnt reboot)
Code:
heimdall-frontend
and try again
Sent from my SCH-I545 using XDA Premium 4 mobile app
Surge1223 said:
connect the phone to a different usb port, then type this in terminal hit enter when it asks for pass
Code:
sudo su
then:
Code:
sudo apt-get update && sudo apt-get upgrade
if you're not using a live cd then I would recommend rebooting here but if you are using a live cd dont reboot then in the same terminal window type the following (if you didnt reboot)
Code:
heimdall-frontend
and try again
Sent from my SCH-I545 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I followed your instructions and rebooted ubuntu. Afterwards I started heimdall-fronted again and followed the your initial instructions. I made sure that my S4 is in download mode.
Now I receive follwoing error however:
Initialising connection...
Detecting device...
ERROR: Failed to access device. libusb error: -3
BabelDev said:
Initialising connection...
Detecting device...
ERROR: Failed to access device. libusb error: -3
Click to expand...
Click to collapse
I meanwhile installed libusb on ubuntu using following commands:
sudo apt-get install libusb-dev
sudo bash -c "apt-get update && apt-get upgrade"
After rebooting I still get the same error on Heimdall as before
Initialising connection...
Detecting device...
ERROR: Failed to access device. libusb error: -3
Any leads on whats going on? Thanks!
BabelDev said:
I followed your instructions and rebooted ubuntu. Afterwards I started heimdall-fronted again and followed the your initial instructions. I made sure that my S4 is in download mode.
Now I receive follwoing error however:
Initialising connection...
Detecting device...
ERROR: Failed to access device. libusb error: -3
Click to expand...
Click to collapse
ok now in terminal, type the following and hit enter when it asks for pass
Code:
sudo su
Then copy and paste all of the below into terminal and reboot once they're done installing and try again (we're almost there!)
Code:
sudo apt-get update && sudo apt-get upgrade && sudo dpkg --configure -a && sudo dpkg --add-architecture i386 ; sudo apt-get update ; sudo apt-get --yes --force-yes install build-essential pkg-config zlib1g-dev libusb-dev libqt4-dev qt4-qmake autoconf libtool libusb-1.0-0-dev debhelper libusb-1.0-0 libgcc1 libc-bin tzdata libc-bin libdb1-compat initscripts libdb1-compat locales psmisc git-core ia32-libs libusb-ocaml libhpmud0 libdevice-usb-perl libusb-0.1-4 libusb-1.0-0-dev libusb-dev libusb-1.0-0 libusb++0.1-4c2 libusbprog-dev libusb++-dev libusbtc08-1 libusbmuxd-dev libusbmuxd1 libusbprog0
Sent from my SCH-I545 using XDA Premium 4 mobile app
Surge1223 said:
ok now in terminal, type the following and hit enter when it asks for pass
Code:
sudo su
Then copy and paste all of the below into terminal and reboot once they're done installing and try again (we're almost there!)
Code:
sudo apt-get update && sudo apt-get upgrade && sudo dpkg --configure -a && sudo dpkg --add-architecture i386 ; sudo apt-get update ; sudo apt-get --yes --force-yes install build-essential pkg-config zlib1g-dev libusb-dev libqt4-dev qt4-qmake autoconf libtool libusb-1.0-0-dev debhelper libusb-1.0-0 libgcc1 libc-bin tzdata libc-bin libdb1-compat initscripts libdb1-compat locales psmisc git-core ia32-libs libusb-ocaml libhpmud0 libdevice-usb-perl libusb-0.1-4 libusb-1.0-0-dev libusb-dev libusb-1.0-0 libusb++0.1-4c2 libusbprog-dev libusb++-dev libusbtc08-1 libusbmuxd-dev libusbmuxd1 libusbprog0
Sent from my SCH-I545 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thank you. I followed your instruction but it seems that the "package is missing, has been obsoleted, or is only available from another source". I also attached a screenshot.
I tried to flash using heimdall again anyway but received the same libusb error.
Thanks once again. I followed your last instructions but received following notice "package is missing, has been obsoleted, or is only available from another source". I rebooted and tried the to flash using heimdall again but received the same libusb error. I also attached a screenshot.
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?
I've tried multiple methods, but I can't seem to get the pre-rooted ROM to flash properly, however, the completely stock ROM flashes just fine, so I'm wondering what in the heck I'm doing wrong.
Here's what I've done after I add the su binaries and deodexed:
-- make_ext4fs WITH -s
-- make_ext4fs WITHOUT -s
-- make_ext4fs WITHOUT -s THEN img2simg
-- This method
After those, I tried these:
-- tar -H ustar -c sboot.bin cm.bin boot.img recovery.img system.img cache.img modem.bin >> Flash.tar
-- tar cfx Flash.tar sboot.bin cm.bin boot.img recovery.img system.img cache.img modem.bin
-- Using 7zip to add the file to a pre-existing tar
-- Renaming system.img to system.img.ext4 (Didn't fail, but it just hanged at recovery at the top and system.img.ext4 as the last log entry)
However, every time it gets to the system.img, it fails, saying "Complete(Write) operation failed."
Is there any fix to this? Or is my phone not accepting a custom system.img?
I've used both Odin3 v3.10.7 and v1.85
Thanks in advance!
Hello everybody,
This is about my Samsung Galaxy Note with 100% original/untouched hardware/software (all stock) which is currently hanged on the boot screen.
However, it can be applied to any android phone and therefore I posted it here.
What happened:
I plugged in the charger into my Samsung Galaxy Note (it was functioning normal).
After an hour I realized that the phone is constantly showing the SAMSUNG logo which appears at the boot time.
I unplugged the charger and let the phone untouched for another 5 minutes but nothing happened.
The screen was keep showing the SAMSUNG logo.
I removed the battery and inserted it back again, then phone started automatically but hanged again on the SAMSUNG logo.
I switched off the phone via long pressing the POWER button, immediately after power down the phone automatically turned on in the same hanged situation.
What I have tried so far:
0. Removing the MMC and SIM and removing the battery for more than an hour.
No success here!
1. Booting up the phone into recovery menu using the key combination (VOLUME UP + HOME + POWER).
Result: a dead Android figure appears with an exclamation mark, following by a bunch of red error messages like below:
Code:
E: failed to mount /efs (No such file or directory)
E: failed to mount /system (No such file or directory)
# MANUAL MODE #
-- Appling 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)
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: Can't mount /cache/recovery/log
E: Can't open mount /cache/recovery/log
Afterwards the blue recovery menu appears on top of these errors and regardless of the chosen option similar error messages appear on the screen.
No Success here!
2. Flashing a custom recovery tool (WTRP) using ODIN
Downloading the WTRP from their official vebsite.
Downloading the ODIN software (various versions).
Booing up the device into Download menu using the key combination (VOLUME DOWN + HOME + POWER).
Connecting the phone to ODIN (ran as administrator).
Starting the process and immediately ODIN said:
Code:
<ID:0/007> Complete(Write) operation failed.
No success here!
3. Flashing the Stock firmware using ODIN
Downloading the proper stock firmware (from various sources).
Downloading the ODIN software (various versions).
Booing up the device into Download menu using the key combination (VOLUME DOWN + HOME + POWER).
Connecting the phone to ODIN (ran as administrator).
Starting the process and immediately ODIN said:
Code:
<ID:0/007> Added!!
<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> Firmware update start..
<ID:0/007> SingleDownload.
<ID:0/007> sboot.bin
<ID:0/007> FAIL!
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
All above steps were done multiple times, using multiple cables, multiple ODIN versions, stock firmware download from multiple sources and the result was always identical... "Complete(Write) operation failed".
No success here!
My guess is a dead eMMC.
Any suggestion is highly appreciated.
Thanks in advance!
Update:
Still I do not have any solution but searching...
I realized that if I remove the battery for a long time and then put it back in the device, it will not turn on automatically.
But, if I switch it on once and then turn it off via long pressing the power button, the phone automatically and immediately turns on again.
Any suggestions?
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