Hello!
I'm trying to repartition internal memory of Captivate Glide. Downloaded PIT file from device using latest GIT version of heimdall, but trying to flash it back to phone (even unmodified) I'm get error:
Code:
sudo ./heimdall flash --repartition --pit pit.pit --13 recovery.img
Heimdall v1.4.0
Copyright (c) 2010-2013, 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...
Some devices may take up to 2 minutes to respond.
Please be patient!
Session begun.
Uploading PIT
ERROR: Failed to confirm end of PIT file transfer!
ERROR: PIT upload failed!
Ending session...
ERROR: Failed to receive session end confirmation!
Releasing device interface...
Re-attaching kernel driver...
Using Odin3 v3.04 with PIT file set and Repartition checkbox checked I'm get next error:
Code:
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003>
<ID:0/003> Re-Partition operation failed.
<ID:0/003> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
Below attached photos of phone's display after errors.
How can I flash PIT file into Glide?
Thank You.
Tried the root method here.
And got the error:
Code:
image size too large!! W:1080, H:1920
display image fail
SECURE FAIL: KERNEL
I panicked, but figured it'd be alright if I just flashed the stock firmware. I re-downloaded the unmodified stock firmware and not I am getting the error
Code:
sw rev check fail fused 3 > binary 2
Odin fails to flash stock at all. It seems to flash it if it's the modified one (the attempt to remove the bootloader) but it then doesn't boot.
If I try to boot phone after flashing stock and failing it says "Firmware upgrade encountered an issue. Please select revoery mode in kies & try again."
What can I do? I want to try re downloading/flashing the PIT file but i can't seem to find a download for that anywhere. Could anyone link me or maybe create a backup pit from their phones I could use?
I have no idea what to do...
Same Issue
I flashed Cyanogenmod and it was working smoothly until I would attempt to load certain apps like Tribal wars or if I was in Game of war, the text would lag after I type a single line of wording then it would jerk up and cause the app to crash. Also, after a few reboots I noticed it automatically uninstalled half of my total apps and I had to redownload them all. I would like to reverse what I did so I installed the stock firmware for my SPH-L520 with this method.
My phone's specs mentioned on Odin Download Mode..
PRODUCT NAME: SPH-L520
CURRENT BINARY: CUSTOM
SYSTEM STATUS: CUSTOM
KNOX KERNAL LOCK: 0x0
KNOX WARRENTY VOID: 0x1
CSB-CONFIG-LSB: 0x30
BOOTLOADER AP SWREV: 4
WRITE PROTECTION: ENABLE
I would get the following error after attempting to flash stock firmware..
What it says on Odin3 v3.07..
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> L520VPUAMK2_L520SPTAMK2_L520VPUAMK2_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> sbl2.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> aboot.mbn
<ID:0/003> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
What it says on my phone...
SW REV CHECK FAIL : Fused 4 > Binary 2
Anyone mind shedding some light on this?
I'm trying to wipe and restore an unlocked maguro Galaxy Nexus. No custom recovery, no root, stock ROM. But I can't wipe it at all. Recovery Mode factory reset doesn't work, it just reboots, and boots up as if it wasn't wiped at all. fastboot doesn't work, it gives the error 'remote: Wipe Failed'
Code:
fastboot -w
erasing 'userdata'...
OKAY [ 0.007s]
formatting 'userdata' partition...
Creating filesystem with parameters:
Size: 15961423872
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 3896832
Block groups: 119
Reserved block group size: 951
Created filesystem with 11/974848 inodes and 103467/3896832 blocks
sending 'userdata' (137971 KB)...
writing 'userdata'...
FAILED (remote: Write Fail)
finished. total time: 264.655s
Even ODIN won't wipe, it fails with and without NAND Erase All. Not even ODIN can wipe the thing.
Without erasing NAND
Code:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> odin.takju.jwr66y.4.3.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> boot.img
<ID:0/003> NAND Write Start!!
<ID:0/003> bootloader.img
<ID:0/003> radio.img
<ID:0/003> recovery.img
<ID:0/003> system.img
<ID:0/003> Complete(Write) operation failed.
Erasing NAND
Code:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> odin.takju.jwr66y.4.3.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> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I'm starting to think that it's a hardware problem with the NAND itself. I've been looking all over the web and I can't find anyone who has the same problems as I. Where should I go from here?
Lock your bootloader if its still unlocked after doing that your nand is fried.
Sent from my Nexus 10 using XDA Free mobile app
mrgnex said:
Lock your bootloader if its still unlocked after doing that your nand is fried.
Sent from my Nexus 10 using XDA Free mobile app
Click to expand...
Click to collapse
Once its unlocked and it reboots, it relocks
blabdude said:
Once its unlocked and it reboots, it relocks
Click to expand...
Click to collapse
Your nand has been fried. Sucks man..
Sent from my Galaxy Nexus using XDA Free mobile app
Background
I was using my N7105 on Cyanogenmod 12.1 and updating the nightlies whenever they came about. All good for a long time. Then last week with no reason that I could see the phone started boot looping.
What I realised
Internal SD card is not mounted. Therefore all CWM commands that use the internal SD card are not working. ODIN cant flash the unmounted internal memory. The SD is empty but the file still exists. This is confusing future installs. ADB wont connect as it appears I had debugging disabled when the crash happened.
Any attempt to factory reset fails, since the SD to be formatted cant be mounted.
What I tried
Recovery in CWM - Passed but didnt fix bootloop
Factory Reset - Fails as SD cant be mounted, didnt fix bootloop
Cache reset - Fails as SD cant be mounted, didnt fix bootloop
Odin Stock - Passed but didnt work
Odin Stock with partition - Passed but didnt work
Odin Stock with partion and PIT- Passed but didnt work
Kies Stock - Passed but didnt work
ADB - Cant swith on debug mode as phone stuck in bootloop.
ODIN Output 1
Result : Fail
Code:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7105XXDMB2_N7105EVRDMA2_N7105BVDLL3_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin engine v(ID:3.1005)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Can't open the specified file. (Line: 2012)
<OSM> All threads completed. (succeed 0 / failed 1)
ODIN Output 2
Auto Reboot, F. Reset Time , Stock Rom
Result: Pass
Effect: None
Code:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7105XXDMB2_N7105EVRDMA2_N7105BVDLL3_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin engine v(ID:3.1005)..
<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> SingleDownload.
<ID:0/004> sboot.bin
<ID:0/004> NAND Write Start!!
<ID:0/004> tz.img
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img
<ID:0/004> modem.bin
<ID:0/004> cache.img
<ID:0/004> hidden.img
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!
<ID:0/004> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/004> Removed!!
I am out of ideas. Anyone got anything I missed?
ADB Brute force
is there a method to brute force ADB even when debug is potentially disabled?
Im thinking doing a manual format from ADB could be the solution.
Odin version
I have tried with the Odin version 1.85 today with no luck. Originally I used the latest version.
ODIN 1.85 log
Code:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7105XXDMB2_N7105EVRDMA2_N7105BVDLL3_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> sboot.bin
<ID:0/004> NAND Write Start!!
<ID:0/004> tz.img
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img
<ID:0/004> modem.bin
<ID:0/004> cache.img
<ID:0/004> hidden.img
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!
<ID:0/004> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/004> Removed!!
Boot Screen
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This is where my boot up stops. It sticks on this screen forever until the battery dies. It not exactly a boot loop I suppose, more a boot freeze. ( this is not my photo, but one I found online that is identical to my current screen)
This is the pit file I used.
View attachment N7105_PIT_File.zip
Stock ROM version
I used the ROM version N7105XXDMB2_N7105EVRDMA2_N7105BVDLL3_HOME.tar.md5 ( too big to upload)
Is this the only way to fix it?
https://www.youtube.com/watch?v=dHPoWDQJdZg
Is this the solution? Will this work on the N7105?
ADB attemps
So I tried ADB
The result was
Code:
adb shell
~ # $su
~ # mount /sdcard
mount: can't find /sdcard in /etc/fstab
~ # $su
~ # parted /dev/block/mmcblk0
Error: Could not stat device /dev/block/mmcblk0 - No such file or directory.
Retry/Cancel? r
r
Error: Could not stat device /dev/block/mmcblk0 - No such file or directory.
Retry/Cancel? r
r
Error: Could not stat device /dev/block/mmcblk0 - No such file or directory.
Retry/Cancel? r
r
Error: Could not stat device /dev/block/mmcblk0 - No such file or directory.
Retry/Cancel? c
c
~ # rm 1
rm: can't remove '1': No such file or directory
~ # rm /dev/block/mmcblk0
rm: can't remove '/dev/block/mmcblk0': No such file or directory
~ # su parted /dev/block/mmcblk0
/sbin/sh: su: not found
~ # $su parted /dev/block/mmcblk0
Error: Could not stat device /dev/block/mmcblk0 - No such file or directory.
Retry/Cancel? c
c
~ # dd if=/dev/block/mmcblk0p3 i←[←[J
dd: can't open '/dev/block/mmcblk0p3': No such file or directory
~ # of=/sdcard/efs.img
~ # mkdir /efs
~ # mkesfs /dev/bllock/mmcblk0p3
/sbin/sh: mkesfs: not found
~ # mount -t ext4/dev/block/mmcblk0p3 /efs
mount: can't find /efs in /etc/fstab
~ # ←[J
~ # $su mkdir /efs
mkdir: can't create directory '/efs': File exists
~ # mount -t ext4 /dev/block/mmcblk0p3 /efs
mount: mounting /dev/block/mmcblk0p3 on /efs failed: No such file or directory
~ # mkdir /system
mkdir: can't create directory '/system': File exists
~ # mkdir /cache
mkdir: can't create directory '/cache': File exists
~ # rm /cache
rm: '/cache' is a directory
~ # fdisk /cache←[J
'/cache' is opened for read only
fdisk: can't read from /cache
~ #
adb shell
~ # $su
~ # cd /dev/block/platform
/sbin/sh: cd: can't cd to /dev/block/platform
~ # cd dw_mmc
/sbin/sh: cd: can't cd to dw_mmc
~ # cd by-name
/sbin/sh: cd: can't cd to by-name
~ # ll
/sbin/sh: ll: not found
~ # ii
/sbin/sh: ii: not found
~ # mke2fs /dev/block/
mke2fs 1.41.14 (22-Dec-2010)
/dev/block/ is not a block special device.
Proceed anyway? (y,n) y
mke2fs: Device size reported to be zero. Invalid partition specified, or
partition table wasn't reread after running fdisk, due to
a modified partition being busy and in use. You may need to reboot
to re-read your partition table.
~ # mount -w -t ext4 /dev/block/
mount: can't find /dev/block/ in /etc/fstab
~ # mount
rootfs on / type rootfs (rw)
tmpfs on /dev type tmpfs (rw,seclabel,nosuid,relatime,mode=755)
devpts on /dev/pts type devpts (rw,seclabel,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,seclabel,relatime)
selinuxfs on /sys/fs/selinux type selinuxfs (rw,relatime)
tmpfs on /storage type tmpfs (rw,seclabel,relatime,mode=050,gid=1028)
tmpfs on /mnt/secure type tmpfs (rw,seclabel,relatime,mode=700)
tmpfs on /mnt/fuse type tmpfs (rw,seclabel,relatime,mode=775,gid=1000)
~ # make_extf4fs /devblock/mmcblk0p13
/sbin/sh: make_extf4fs: not found
~ # rm /dev/block/mmcblk0p13
~ # rm /dev/block/mmcblk0p12
~ # mount -w -t ext4 /dev/block/mmcblk0p12
mount: mounting /dev/block/mmcblk0p12 on /cache failed: No such file or director
y
~ # rm /data
rm: '/data' is a directory
~ # fdisk /data
'/data' is opened for read only
fdisk: can't read from /data
~ # $su fdisk /data
'/data' is opened for read only
fdisk: can't read from /data
~ # ?
/sbin/sh: ?: not found
~ # help
/sbin/sh: help: not found
~ # mount -o remount, rw /
~ # mount -t exfat -o umask=0000 /dev/block/vold/179.17/storage/sdcard0
mount: can't find /dev/block/vold/179.17/storage/sdcard0 in /etc/fstab
~ # mount -t exfat -o umask=0000 /dev/block/vold/179:17 /storage/sdcard0←[J
mount: mounting /dev/block/vold/179:17 on /storage/sdcard0 failed: No such file
or directory
~ # mount -t exfat -o umask=0000 /dev/block/vold/179:17 /storage/sdcard0
mount: mounting /dev/block/vold/179:17 on /storage/sdcard0 failed: No such file
or directory
~ # sleep 8
~ # mount -o bind /data/media /storage/extSdCard
mount: mounting /data/media on /storage/extSdCard failed: No such file or direct
ory
~ # chmod 777 /storage/extSdCard
chmod: /storage/extSdCard: No such file or directory
~ #
Ok so my plan is to swap the internal sd for the external SD in the boot sequence. I ampretty sure that could negatively effect performance and is risky since the external micro sd could die at any time. However its potentially a way to kick the device back into action from which I can try and fic the internal sd.
In my research in order to try fix this, I am seeing a lot of people with the same problem as me on Cyanogenmod 12.1 . I wouldnt like to make accusations without evidence but is there something in CM 12.1 that is causing this?
I ran dmesg | grep mmc0 and this is what I found
Code:
~ # dmesg | grep mmc0
<3>[ 1.928761] c1 mmc0: Version ID 0x5342240a.
<6>[ 1.929011] c1 mmc0: FIFO WMARK FOR RX 0x80 WX 0x40. ###########
<6>[ 1.930521] c1 mmc0: MSHCI controller on samsung-mshci [dw_mmc] using IDMA
<3>[ 1.960830] c0 mmc0: cmd 52 response timeout error
<3>[ 1.961673] c0 mmc0: cmd 52 response timeout error
<3>[ 1.965697] c0 mmc0: cmd 8 response timeout error
<3>[ 1.966538] c0 mmc0: cmd 5 response timeout error
<3>[ 1.967364] c0 mmc0: cmd 5 response timeout error
<3>[ 1.968190] c0 mmc0: cmd 5 response timeout error
<3>[ 1.969014] c0 mmc0: cmd 5 response timeout error
<3>[ 1.969854] c0 mmc0: cmd 55 response timeout error
<3>[ 1.970693] c0 mmc0: cmd 55 response timeout error
<3>[ 1.971535] c0 mmc0: cmd 55 response timeout error
<3>[ 1.972374] c0 mmc0: cmd 55 response timeout error
<3>[ 1.991786] c0 mmc0: PERM_WRITE_PROTECT was set.
<6>[ 1.991817] c0 mmc0: MAG4FB: 1501004d4147344642f7af0086069fc3
<3>[ 2.200979] c0 mmc0: cmd 13 response timeout error
<6>[ 2.201074] c2 mmc0 : disable PON feature : ffffff92 : 00(0c) : 00000000
<3>[ 2.201911] c0 mmc0: cmd 6 response timeout error
<3>[ 2.202738] c0 mmc0: cmd 6 response timeout error
<3>[ 2.203564] c0 mmc0: cmd 6 response timeout error
<3>[ 2.204390] c0 mmc0: cmd 6 response timeout error
<3>[ 2.204439] c2 mmc0: error -110 whilst initialising MMC card
~ #
Notice <3>[ 2.204439] c2 mmc0: error -110 whilst initialising MMC card showing the Memory card error
Hello All
Can anyone tell me flashing using .PIT file will erase my EFS partition I don't have EFS backup I have same problem
I am reallt stuck guys. Does anyone have any ideas. Still cant fix this.
I also realised that nothing is flashing my device and that I am still on the same CWM despite flashing several different versions. I also tried to flash TWRP to no avail.
Plus all my attempts to flash roms came to nothing.
Is there a such thing as flash protect? can I remove it if so? how?
ODIN LOG
Code:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7105XXALIJ_N7105EVRALIC_N7105BVALIG_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin engine v(ID:3.1005)..
<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> SingleDownload.
<ID:0/003> system.img
<ID:0/003> NAND Write Start!!
<ID:0/003> boot.img
<ID:0/003> cache.img
<ID:0/003> hidden.img
<ID:0/003> recovery.img
<ID:0/003> modem.bin
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Removed!!
<ID:0/003> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
attempted super Flash
In this I flashed BL, AP, CP, CSC and PIT
Code:
<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> N7105XXUFNF2_N7105EVRFNF1_N7105BVUFNE1_HOME.tar.md5 is valid.
<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> N7105XXUFNF2_N7105EVRFNF1_N7105BVUFNE1_HOME.tar.md5 is valid.
<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> N7105XXUFNF2_N7105EVRFNF1_N7105BVUFNE1_HOME.tar.md5 is valid.
<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> N7105XXUFNF2_N7105EVRFNF1_N7105BVUFNE1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin engine v(ID:3.1005)..
<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> sboot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> tz.img
<ID:0/003> system.img
<ID:0/003> boot.img
<ID:0/003> cache.img
<ID:0/003> hidden.img
<ID:0/003> recovery.img
<ID:0/003> modem.bin
<ID:0/003> sboot.bin
<ID:0/003> tz.img
<ID:0/003> system.img
<ID:0/003> boot.img
<ID:0/003> cache.img
<ID:0/003> hidden.img
<ID:0/003> recovery.img
<ID:0/003> modem.bin
<ID:0/003> sboot.bin
<ID:0/003> Transmission Complete..
<ID:0/003> Now Writing.. Please wait about 2 minutes
<ID:0/003> Receive Response from boot-loader
<ID:0/003> tz.img
<ID:0/003> Transmission Complete..
<ID:0/003> Now Writing.. Please wait about 2 minutes
<ID:0/003> Receive Response from boot-loader
<ID:0/003> system.img
<ID:0/003> Transmission Complete..
<ID:0/003> Now Writing.. Please wait about 2 minutes
<ID:0/003> Receive Response from boot-loader
<ID:0/003> Transmission Complete..
<ID:0/003> Now Writing.. Please wait about 2 minutes
<ID:0/003> Receive Response from boot-loader
<ID:0/003> Transmission Complete..
<ID:0/003> Now Writing.. Please wait about 2 minutes
<ID:0/003> Receive Response from boot-loader
<ID:0/003> Transmission Complete..
<ID:0/003> Now Writing.. Please wait about 2 minutes
<ID:0/003> Receive Response from boot-loader
<ID:0/003> Transmission Complete..
<ID:0/003> Now Writing.. Please wait about 2 minutes
<ID:0/003> Receive Response from boot-loader
<ID:0/003> Transmission Complete..
<ID:0/003> Now Writing.. Please wait about 2 minutes
<ID:0/003> Receive Response from boot-loader
<ID:0/003> Transmission Complete..
<ID:0/003> Now Writing.. Please wait about 2 minutes
<ID:0/003> Receive Response from boot-loader
<ID:0/003> Transmission Complete..
<ID:0/003> Now Writing.. Please wait about 2 minutes
<ID:0/003> Receive Response from boot-loader
<ID:0/003> Transmission Complete..
<ID:0/003> Now Writing.. Please wait about 2 minutes
<ID:0/003> Receive Response from boot-loader
<ID:0/003> Transmission Complete..
<ID:0/003> Now Writing.. Please wait about 2 minutes
<ID:0/003> Receive Response from boot-loader
<ID:0/003> Transmission Complete..
<ID:0/003> Now Writing.. Please wait about 2 minutes
<ID:0/003> Receive Response from boot-loader
<ID:0/003> Transmission Complete..
<ID:0/003> Now Writing.. Please wait about 2 minutes
<ID:0/003> Receive Response from boot-loader
<ID:0/003> Transmission Complete..
<ID:0/003> Now Writing.. Please wait about 2 minutes
<ID:0/003> Receive Response from boot-loader
<ID:0/003> Transmission Complete..
<ID:0/003> Now Writing.. Please wait about 2 minutes
<ID:0/003> Receive Response from boot-loader
<ID:0/003> Transmission Complete..
<ID:0/003> Now Writing.. Please wait about 2 minutes
<ID:0/003> Receive Response from boot-loader
<ID:0/003> Transmission Complete..
<ID:0/003> Now Writing.. Please wait about 2 minutes
<ID:0/003> Receive Response from boot-loader
<ID:0/003> Transmission Complete..
<ID:0/003> Now Writing.. Please wait about 2 minutes
<ID:0/003> Receive Response from boot-loader
<ID:0/003> Transmission Complete..
<ID:0/003> Now Writing.. Please wait about 2 minutes
<ID:0/003> Receive Response from boot-loader
<ID:0/003> boot.img
<ID:0/003> Transmission Complete..
<ID:0/003> Now Writing.. Please wait about 2 minutes
<ID:0/003> Receive Response from boot-loader
<ID:0/003> cache.img
<ID:0/003> Transmission Complete..
<ID:0/003> Now Writing.. Please wait about 2 minutes
<ID:0/003> Receive Response from boot-loader
<ID:0/003> Transmission Complete..
<ID:0/003> Now Writing.. Please wait about 2 minutes
<ID:0/003> Receive Response from boot-loader
<ID:0/003> hidden.img
<ID:0/003> Transmission Complete..
<ID:0/003> Now Writing.. Please wait about 2 minutes
<ID:0/003> Receive Response from boot-loader
<ID:0/003> Transmission Complete..
<ID:0/003> Now Writing.. Please wait about 2 minutes
<ID:0/003> Receive Response from boot-loader
<ID:0/003> recovery.img
<ID:0/003> Transmission Complete..
<ID:0/003> Now Writing.. Please wait about 2 minutes
<ID:0/003> Receive Response from boot-loader
<ID:0/003> modem.bin
<ID:0/003> Transmission Complete..
<ID:0/003> Now Writing.. Please wait about 2 minutes
<ID:0/003> Receive Response from boot-loader
<ID:0/003> sboot.bin
<ID:0/003> tz.img
<ID:0/003> system.img
<ID:0/003> boot.img
<ID:0/003> cache.img
<ID:0/003> hidden.img
<ID:0/003> recovery.img
<ID:0/003> modem.bin
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Remain Port .... 0
<ID:0/003> Removed!!
<OSM> All threads completed. (succeed 1 / failed 0)
ODIN Suceeded but still stuck on boot screen!!! What the hell is wrong with my phone??
Finaly fixed this. I bought a new motherboard online for $27 USD . Wasnt worth wasting more time trying to fix the burn out chip. New motherboard works fine and phone is fixed.
@XDAiiClassic So it was a hardware failure?
Option58 said:
@XDAiiClassic So it was a hardware failure?
Click to expand...
Click to collapse
I am inclined to beleive so. As per my pst showing the chip was dead when I ran the code.
Havent spent a considerable amount of time on the problem, paying the $27 USD made more sense. I simply had to flash the new motherboard and voila.
I cannot say 100% but I think the phone was a victim of the sudden death chip problem. Either way, I would probably advise someone in a similar situation to skip weeks of fruitless effort and buy the new motherboard. That is unless you enjoy it for the challenge, in which case go ahead.
Hello!
I have a bricked Galaxy S4 Mini Duos GT-I9192. It doesn't turn on anyway. I tried download mode (Home+Volume down+Power on).
I put the debrick.img file on an sd and done as said in the guide.
With the SD in, device turned on, show the messages below:
BOOT RECOVERY MODE
CHECK BOOT PARTITIONS
COPY FROM T-FLASH
BOOT RECOVERY
WRITE 139008 sectors
FLASH WRITE FAILURE
ddi: mmc_read failed
ODIN MODE
PRODUCT NAME: GT-I9192
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
CSB-CONFIG-LSB: 0x30
BOOTLOADER AP SWREV: 2
WRITE PROTECTION: Enable
On Odin, when i try to install firmware and pit file, show the errors below:
<ID:0/008> 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/008> Odin engine v(ID:3.1101)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Get PIT for mapping..
<ID:0/008>
<ID:0/008> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/008> Odin engine v(ID:3.1101)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Set PIT file..
<ID:0/008> DO NOT TURN OFF TARGET!!
<ID:0/008> FAIL!
<ID:0/008>
<ID:0/008> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/008> Odin engine v(ID:3.1101)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Get PIT for mapping..
<ID:0/008>
<ID:0/008> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
On device screen show messages below:
MMC: mmc_read fail
ODIN : flash read failure
PIT FAIL : TOTAL SECTORS (0)
Please, can you help me recover this device? Is there any hope and solution? Thanks so much. Best regards.
Please, can anybody help me?!
Enviado de meu XT1225 usando Tapatalk
I'm no expert about bricked phones but I think it's probably your emmc chip that has problem, so probably need a new chip or motherboard (as pit file not working).
marcosgdias said:
Hello!
I have a bricked Galaxy S4 Mini Duos GT-I9192. It doesn't turn on anyway. I tried download mode (Home+Volume down+Power on).
I put the debrick.img file on an sd and done as said in the guide.
With the SD in, device turned on, show the messages below:
BOOT RECOVERY MODE
CHECK BOOT PARTITIONS
COPY FROM T-FLASH
BOOT RECOVERY
WRITE 139008 sectors
FLASH WRITE FAILURE
ddi: mmc_read failed
ODIN MODE
PRODUCT NAME: GT-I9192
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
CSB-CONFIG-LSB: 0x30
BOOTLOADER AP SWREV: 2
WRITE PROTECTION: Enable
On Odin, when i try to install firmware and pit file, show the errors below:
<ID:0/008> 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/008> Odin engine v(ID:3.1101)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Get PIT for mapping..
<ID:0/008>
<ID:0/008> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/008> Odin engine v(ID:3.1101)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Set PIT file..
<ID:0/008> DO NOT TURN OFF TARGET!!
<ID:0/008> FAIL!
<ID:0/008>
<ID:0/008> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/008> Odin engine v(ID:3.1101)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Get PIT for mapping..
<ID:0/008>
<ID:0/008> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
On device screen show messages below:
MMC: mmc_read fail
ODIN : flash read failure
PIT FAIL : TOTAL SECTORS (0)
Please, can you help me recover this device? Is there any hope and solution? Thanks so much. Best regards.
Click to expand...
Click to collapse
I'm facing the same problem too. mine happened while playing a game. the game froze and died. was able to get to boot recovery mode using the debrick.img but not the download mode i was expecting to see. i also got the same output from odin except fr the last one which in my case is "flash read failure"... man i really want to fix this unit...