Related
Hello everyone!
I have Samsung Galaxy Tab 10.1v (GT-P7100, Hungarian Vodafone).
I rooted unlocked it. Last day I tried to push the latest version of (beta) Ice Cream Sandwich (Galaxy Tab) rom from XDA-developers.
This went wrong. I scrwed up my Tablet. It is frozen on the opening screen.
I tought, no problem, I can push the older ROM. But I can't.
It seems to be the partition layout changed and I can't push any rom into the Tab.
I tried everything. What function can use on the Tablet?
I can use the Tablet in download mode with Odin3 v1.85.
I tried many older ROM install to my tablet with Odin.
Apparently finished Odin with success, but the boot process failed. (Frozen Galaxy Tab logo)
At least I tried to use correct PIT file with the ROM, but the same.
I can boot via fastboot, and I can boot the Tab with clockworkmod recovery image (4.0.0.4 or 5.0.2.3) but I can't use the "mount USB" function. -> "E:Unable to open ums lunfile (No such file or directory)"
After clockworkmod factory reset -> Frozen Galaxy Tab logo.
I tought, no problem, I can use the adb to push my older image to my Tab.
I did it, I found the uploaded ZIP file in Clockworkmod recovery (install zip from card). The install process started, and finished with this error: E: failed to mount /efs (invalid argument)
I use adb shell to check my system.
This is what I say after the boot:
Code:
#df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 362.1M 32.0K 362.1M 0% /dev
/dev/block/mmcblk0p5 189.0M 4.2M 184.7M 2% /cache
Code:
# mount
mount
rootfs on / type rootfs (rw)
tmpfs on /dev type tmpfs (rw,relatime,mode=755)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
/dev/block/mmcblk0p5 on /cache type ext4 (rw,nodev,noatime,nodiratime,barrier=1,
data=ordered)
Code:
# cat /etc/fstab
cat /etc/fstab
/dev/block/mmcblk0p5 /cache ext4 rw
/dev/block/mmcblk0p8 /data ext4 rw
/dev/block/mmcblk0p4 /system ext4 rw
I can mount /data partition manualy.
Code:
~ # mount /data
mount /data
~ # df -h
df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 362.1M 32.0K 362.1M 0% /dev
/dev/block/mmcblk0p5 189.0M 4.2M 184.7M 2% /cache
/dev/block/mmcblk0p8 14.1G 463.1M 13.7G 3% /data
~ #
So, I think the main problem is, that my partition layout is wrong.
What is the correct layout of Galaxy Tab 10.1?
It is possible to create the correct layout with a simple shell script?
Or maybe any other idea?
Basically I love how you have attempted everything, makes it easier for me to deal with this
The lunfile error is common only because it was not properly fixed, All CWM has this issue as this is a port over for the GTab.
Odin usually does the repartitioning automatically, so you don't need to worry about it, as per the frozen logo how long does it stay? as the initial first boot per flashed firmware takes about 2-3minutes as the dalvik cache is being generated. when it's done, you will feel a vibration that's when you know it's alright.
What you should do is, flash a stock firmware, 3.2, Then wait for it to boot up, if it loops, then you flash CWM, then go to CWM recovery, factory reset followed by fix permissions.
It should boot from there
Dear Misledz,
thank you your quick reply.
I found the latest rom in samfirmware.com.
It has only old ROMs for this Galaxy version.
Code:
GT-P7100 P7100BUKE2 ## 3.0.1. 2011 May
GT-P7100 P7100BUKDC ## 3.0.1. 2011 April
GT-P7100 P7100BUKDF ## 3.0.1. 2011 April
GT-P7100 P7100BUKC8 ## 3.0.1. 2011 March
I used thw P7500 series ROMs already (last good ROM was also P7500) so I downloaded from samfirmware.com this:
GT-P7500 P7500XWLA1 3.2 2012 January Hungary
I booted into download mode the tab. (Odin3 Download Mode (Protocol v2)
Put the file in Odin3 v1.85 into PDA section (P7500XWLA1_P7500OXXLA1_P7500XXKL4_HOME.tar.md5)
The flash process failed, here is the log from Odin.
Code:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> P7500XWLA1_P7500OXXLA1_P7500XXKL4_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/012> Odin v.3 engine (ID:12)..
<ID:0/012> File analysis..
<ID:0/012> SetupConnection..
<ID:0/012> Initialzation..
<ID:0/012> Get PIT for mapping..
<ID:0/012> Firmware update start..
<ID:0/012> boot.img
<ID:0/012> NAND Write Start!!
<ID:0/012> bootloader.bin
<ID:0/012>
<ID:0/012> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
The screen on the tablet in red border:
Invalid binary signature.
Now I try to download the old 3.0.1 P7100BUKE2 rom and reply again.
Thanks +1!
Misledz said:
Basically I love how you have attempted everything, makes it easier for me to deal with this
The lunfile error is common only because it was not properly fixed, All CWM has this issue as this is a port over for the GTab.
Odin usually does the repartitioning automatically, so you don't need to worry about it, as per the frozen logo how long does it stay? as the initial first boot per flashed firmware takes about 2-3minutes as the dalvik cache is being generated. when it's done, you will feel a vibration that's when you know it's alright.
What you should do is, flash a stock firmware, 3.2, Then wait for it to boot up, if it loops, then you flash CWM, then go to CWM recovery, factory reset followed by fix permissions.
It should boot from there
Click to expand...
Click to collapse
Well yes because you cannot flash a 7500 ROM on a 7100 that would obviously fail because the RAM disks are different and careful it may cause a brick, brother.
7500 and 7100 are different models, please don't mix them up.
Hi,
I tried to install the latest official Samsung GT-P7100 ROM (3.01.).
I downloaded this file from samfirmware ->
GT-P7100 P7100BUKE2 ## 3.0.1. 2011 May.
This Zip file contains 3 files.
I put this 3 files in Odin. (see screenshot 1 name: odin.jpg)
It was success process, here is the Odin log:
Code:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> BOOTLOADER_P7100BUKC8.tar.md5 is valid.
<OSM> PDA_SIGNED_HRI83_BUKE2.tar.md5 is valid.
<OSM> MODEM_HRI83_BUKDF_REV_03.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/012> Odin v.3 engine (ID:12)..
<ID:0/012> File analysis..
<ID:0/012> SetupConnection..
<ID:0/012> Initialzation..
<ID:0/012> Get PIT for mapping..
<ID:0/012> Firmware update start..
<ID:0/012> bootloader.bin
<ID:0/012> NAND Write Start!!
<ID:0/012> boot.img
<ID:0/012> system.img
<ID:0/012> recovery.img
<ID:0/012> modem.bin
<ID:0/012> Transmission Complete..
<ID:0/012> Now Writing.. Please wait about 2 minutes
<ID:0/012> Receive Response form LOKE
<ID:0/012> RQT_CLOSE !!
<ID:0/012> RES OK !!
<ID:0/012> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/012> Removed!!
After this, the Tablet started to reboot.
During the reboot I saw an android robot and above an exclamation mark.
I made photo with my phone. (screenshot 2: exclamation.jpg)
When this exclamation mark dissapiered the Tablet started to reboot.
Shown the Galaxy logo, then the blue LED indicator next to the front camera illuminated on the top.
The inticator LED switched off, but the logo remained.
Waited cc 20 mins, but nothing else. (screenshot 3: logo.jpg)
I didn't feel the little vibration as you mentioned.
After that I booted into ClockworkMod Recovery v4.0.0.4,
then made factory reset, and fix permition. (screenshot 4: clockwork.jpg)
At least I rebooted. Unfortunately the same, no boot after the Samsung logo.
At the end, I made recovery log with Clockwork.
I put here. (Only deleted my serial number.)
No more idea... (But I saw in the log, that the partition table is okay in the fstab)
Just for sure, I made pics from my USB mode and Download mode screen maybe you can see anything. (screenshot 5: usbmode.jpg, screenshot 6: downloadmode.jpg)
Recovery log: (I cange the http link in the log, because the forum doesn't allowed to send it.)
Code:
/data/media/clockworkmod # cat recovery.log
cat recovery.log
Starting recovery on Fri Mar 29 12:26:07 2019
framebuffer: fd 4 (1280 x 800)
ClockworkMod Recovery v4.0.0.4
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null)
1 /efs ext4 /dev/block/mmcblk0p1 (null)
2 /boot emmc /dev/block/mmcblk0p3 (null)
3 /cache ext4 /dev/block/mmcblk0p5 (null)
4 /data auto /dev/block/mmcblk0p8 (null)
5 /misc emmc /dev/block/mmcblk0p6 (null)
6 /recovery emmc /dev/block/mmcblk0p2 (null)
7 /system ext4 /dev/block/mmcblk0p4 (null)
W:Unable to get recovery.fstab info for /sdcard during fstab generation!
W:Unable to get recovery.fstab info for /sd-ext during fstab generation!
I:Completed outputting fstab.
I:Processing arguments.
I:Checking arguments.
I:device_recovery_start()
Command: "/sbin/recovery"
ro.secure=0
ro.allow.mock.location=1
ro.debuggable=1
persist.service.adb.enable=1
ro.build.id=HRI83
ro.build.display.id=HRI83.313
ro.build.version.incremental=eng.root.20110616.175603
ro.build.version.sdk=10
ro.build.version.codename=REL
ro.build.version.release=2.3.4
ro.build.date=Thu Jun 16 17:56:22 EDT 2011
ro.build.date.utc=0
ro.build.type=eng
ro.build.user=root
ro.build.host=pershoot-ubuntu
ro.build.tags=test-keys
ro.product.model=p7510
ro.product.brand=samsung
ro.product.name=p7510
ro.product.device=p7510
ro.product.board=p7100
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=samsung
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=tegra
ro.build.product=p7510
ro.build.description=GT-P7510-user 3.0.1 HRI83 313 release-keys
ro.build.fingerprint=samsung/GT-P7510/GT-P7510:3.0.1/HRI83/313:user/release-keys
ro.cwm.prefer_tar=true
keyguard.no_require_sim=true
ro.ril.hsxpa=1
ro.ril.gprsclass=10
ro.config.notification_sound=OnTheHunt.ogg
ro.config.alarm_alert=Alarm_Classic.ogg
ro.rommanager.developerid=cyanogenmod
ro.url.legal= *removed google link*
ro.url.legal.android_privacy=*removed google link*
ro.com.google.clientidbase=android-google
ro.com.android.wifi-watchlist=GoogleGuest
ro.setupwizard.enterprise_mode=1
ro.com.android.dateformat=MM-dd-yyyy
ro.com.android.dataroaming=false
ro.config.ringtone=Playa.ogg
ro.modversion=CyanogenMod-7.1.0-RC0-Harmony-KANG
ro.kernel.android.checkjni=1
ro.setupwizard.mode=OPTIONAL
net.bt.name=Android
net.change=net.bt.name
dalvik.vm.stack-trace-file=/data/anr/traces.txt
ro.factorytest=0
ro.serialno=*************************************
ro.bootmode=unknown
ro.baseband=%s
ro.carrier=unknown
ro.bootloader=P7100BUKB7
ro.hardware=p7100
ro.revision=0
init.svc.recovery=running
init.svc.adbd=running
I:Checking for extendedcommand...
I:Skipping execution of extendedcommand, file not found...
W:using /data/media, no /sdcard found.
/data/media/clockworkmod #
ps.: If you see in the log the Tab says from itself:
ro.product.model=p7510
ro.product.brand=samsung
ro.product.name=p7510
ro.product.device=p7510
ro.product.board=p7100
So I tought it is almost the same machine, and I used the 7500 ROM already...
Just a little more bad experience:
I tried upload every "factory" stock ROM for GT-P7100 via Odin3 but still nothing changed. This make me mad slowly.
This were the tried ROMs.
Code:
GT-P7100 P7100BUKE2 ## 3.0.1. 2011 May
GT-P7100 P7100BUKDC ## 3.0.1. 2011 April
GT-P7100 P7100BUKDF ## 3.0.1. 2011 April
GT-P7100 P7100BUKC8 ## 3.0.1. 2011 March
Why not flash a 3.2 rom directly? 3.1 is very buggy
Sent from my GT - I9003 in the bathroom
Unfortunately no 3.2 original (or stock) ROM for GT-P7100...
Only that ROMs...
What information can I provide to you to get closer to the un-brick...?
Holy crap, I just realized it's 7100 and not 7510
Yes 3.1 is the only firmware for it, Sorry was mistaken for another series.
When you say nothing has changed, what exactly do you mean?
The flash is completed but freezes? Or the flash fails? Let's tackle it down 1 by 1 I'm willing to help you see this through.
Fitz.
First of all: thank you your patient and help!!!
Before bricked my Tablet, I used this custom ROM from XDA-developers:
[ROM][4 Dec][HC32] isi-galaxy 1.2.5v with pershoot's kernel
(http://forum.xda-developers.com/showthread.php?t=1372432)
Because my Tablet is unusable, I tought put this isi-ram back on my P7100.
I did the install steps that wrote in the isi-galaxy article. (As I mentioned, I did already once and was everything fine.)
But now something went wrong.
The installation process was successful (seemingly) but when I began to reboot my tab, this error message welcome me (no galaxy tab logo).
See the attached file.
Basically you don't have a normalboot.img either your bootsector was written to another partition or you may need to repartition it again.
Have you attempted flashing the pit file and the firmware file together? That should reformat and recreate into one partition only.
Yes, I tried it already.
The only PIT file what the Odin accept with the ROM file is this: android_fastboot_emmc_full_p4_16G_32G.pit
But the problem remain the same.
I have two question:
1. If an another Tablet user make from his device a NANROID backup and send me
the backup file can I restore my device from this backup?
2. how can I check which partiton contains the bootimage?
You may be able to do that, you may need a CWM backup image from someone, but I wouldn't suggest it as it also contains the efs and it will overwrite your IMEI too with his. Which is a bad idea as whatever he downloads in the Market, will be downloaded to your's too, or so I've heard. Since CWM backs up the EFS partition too.
I think that should be in the normalboot.img, you can try to open up the firmware with 7zip or WinRar, you'll find it in there. I wouldn't mess around with it too much though, then again, have you tried Kies? what has kies detected about your tablet?
On another note, if you have an efs backup on your device you can always copy that and paste it into that guy's nandroid backup and replace it, so the data that get's replaced is with your IMEI instead. That's one workaround, but efs gets generated on first boot, which you seem to be unable to do right now.
Best bet would be to flash CWM Recovery and do a complete wipe with internal aswell. Something else is conflicting with it.
Finally I went to Samsung official service. They replaced the motherboard of my Tablet. Easy!
hi! I can confirm is bootloader problem , exactly same problems to me , but my tab had no root nor openbootloader, it just happened flashing with odin from 3.0.1 to 3.2.1 official smsung firm...
I have no posibility to purchase samsung sat so a bit of help may be thankfull... my tab is dead and useless.
Can´t find a repartition file, all ops found for 7500 model and 7510, can pit file may be fit for p7100???????
thx!!!!!!!!!!
I know that this is an old post, but I have exactly the same problem and find no easy solution ..
But I have not even Clockwork.
Has anyone perhaps now figured out how to fix it?
seems the problem is partitioning with p7500. got a tabled damaged like this as well. there is no pit file for p7100 thus no chance to recover original partitioning.. i guess?
anyway, cannot mount all needed paths, while /dev/block/mmc**** exist, mke2fs outputs "invalid block size". probably because of the 7500 pit.
---------- Post added at 04:37 PM ---------- Previous post was at 04:36 PM ----------
maybe it is worth trying installing a rom for non-3g tab? would it skip /efs checking?
Can someone create a pit file for p7100 (10.1v)? I guess the program is called Pit Magic, that extracts partition table settings..
Please help save a bricked device ?
Sent from my GT-N7000 using xda app-developers app
So can someone create pit file for P7100 or not? I got same device as others with damaged partitions (green robot with exclamation)
Wizard(LV) said:
So can someone create pit file for P7100 or not? I got same device as others with damaged partitions (green robot with exclamation)
Click to expand...
Click to collapse
Damn, I have the same problem.
Tried to repartion and now it only boots on ODIN3 download mode...
Guess it's just an expensive mirror now?
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 cant Flash or using odin, any help?
The log odin
<ID:0/004> Added!!
<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> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> sboot.bin
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
I want try this but dont work, i can't make work then adb....
Go to recovery, (If PhilZ, turn the screen off by swiping to the left - to prevent burn-ins.. )
Open adb shell,
umount /data
umount /cache
umount /system
umount /preload
dd if=/dev/zero of=/dev/block/mmcblk0p8 bs=16M
dd if=/dev/zero of=/dev/block/mmcblk0p9 bs=16M
dd if=/dev/zero of=/dev/block/mmcblk0p10 bs=16M
dd if=/dev/zero of=/dev/block/mmcblk0p12 bs=16M
sync
And reboot to download mode from the reboot menu, use ODIN to flash stock firmware.
After flashing stock firmware, it'll automatically enter recovery to apply CSC.
After recovery exits, be quick and enter recovery manually yourself.
It'll complain it can't mount /cache and /data. Ignore and do a factory reset, and reboot.
Don't flash anything custom until you get stock firmware running perfectly.
0p8 = cache
0p9 = system
0p10 = preload
0p12 = data (will take tens of minutes)
At the end of each dd command, it will complain that no more space is available. That's normal, however if you got some another error, that means your nand is hardwarelically corrupted..
Are you trying to flash the latest stock ROM from sammobile.com, updato.com, or samsung-firmware.org?
Tried using the original Samsung USB cable?
The phone is in stock recovery mode so you can only sideload, which is useless.
You need to be in download mode to flash but you get pit errors so can't flash anything, you need to have twrp to have full adb.
I'm afraid your phone is F00ked.
As a last resort, try flashing the stock recovery on its own via odin & download mode. If it doesn't take then the phone is good for keeping your shelf dust free..
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?