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.
Related
yesterday I wrote to find a solution to E failed to mount/system invalid argument cant mount system I was reffered to wwjosdew video and also went onto viperboy thread on how to unbrick phones I did everything shown in the video and what viperboy said but when odin was running the file it failed and gave me this
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> SPH-L900_L900VPALJ1_L900VPALJ1_L900SPTALJ1.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> boot.img
<ID:0/003> NAND Write Start!!
<ID:0/003> cache.img
<ID:0/003> hidden.img
<ID:0/003> modem.bin
<ID:0/003> param.bin
<ID:0/003> recovery.img
<ID:0/003> sboot.bin
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<ID:0/003> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
can anynone help me out with this problem been working on this for hours I have wiped and reset the phone already and I also downloaded the toolkit and the kit recognizes my phone and serial is rcognized.........
S boot is going to fail when loading a Older tar ....it won't allow you to go back to a older boot loader ... use this and next time search it has been ask plenty of timeshttp://forum.xda-developers.com/showthread.php?t=2086769
Sent from my SPH-L900 using Xparent BlueTapatalk 2
Really need help! I starting having issues with my phone lately where it would just shut down after booting into the phone.
After a couple of days i now freezes on Samsung Galaxy SIII screen.
I tried using ODIN3 to recover a ROM and get this message (checking Auto Reboot and F.Reset Time option)
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> KIES_HOME_L710VPALEN_L710SPRALEN_618049_REV03_user_low_ship.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> Erase...
<ID:0/004> Get PIT for mapping..
<ID:0/004>
<ID:0/004> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
Tried a second time unchecking the Auto Reboot option and now getting
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> KIES_HOME_L710VPALEN_L710SPRALEN_618049_REV03_user_low_ship.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> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> sbl2.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL! (Write)
<OSM> All threads completed. (succeed 0 / failed 1)
When I tried to go into recovery mode I to wipe data/factory reset I get a string of red error messages
E:failed to mount /cache
e:failed to mount /system (invalid argument)
can't mount '/system (invalid argument)
e:failed to mount /data (invalid argument)
e:failed to mount /system (invalid argument)
e: failed to mount /cache (invalid argument)
can't mount /cache/recovery/log
can't open /cache/recover/log
Any assistance or suggestions would be greatly appreciated.
Were you using a stock ROM with Odin?
Sent from my SPH-L710 using xda app-developers app
IDontKnowMang said:
Were you using a stock ROM with Odin?
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
Yes, I tried numerous versions of the Stock ROM.4.0,4.1 all the same results
Hi all,
I have an AT&T Samsung Galaxy S3 16GB (SGH-I747). Recently my phone starting locking up and shutting down on occasion, and yesterday it got much more frequent before refusing to boot at all. When I power on the phone it proceeds as normal up until the "Samsung Galaxy S III" logo screen before and then hangs.
I can enter recovery and download modes. I am also able to flash new recoveries using Odin (I tried switching to stock, and when that didn't work, back to CWM. No problems either time) But when I try to flash the stock ROM again, Odin hangs up on the /cache section of the flash and produces the following log:
Note: The only option I have checked in Odin is Auto Reboot
Code:
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I747UCDLK3_I747ATTDLK3_I747UCDLK3_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> aboot.mbn
<ID:0/007> NAND Write Start!!
<ID:0/007> boot.img
<ID:0/007> cache.img.ext4
<ID:0/007> FAIL! (Write)
<OSM> All threads completed. (succeed 0 / failed 1)
It's worth mentioning that I've tried to clear/format the cache several times with Clockwork Recovery, but it can't seem to mount, write or read the partition. The message I receive after taking almost any action in Clockwork (presumably because it's trying to update the cache) is this:
Code:
E: Can't mount /cache/recovery/command
E: Can't mount /cache/recovery/log
E: Can't open /cache/recovery/log
E: Can't mount /cache/recovery/last_log
E: Can't open /cache/recovery/last_log
E: Can't mount /cache/recovery/last_install
E: Can't open /cache/recovery/last_install
I've also tried using Odin along with a pit file to repartition the device. It appears successful, but then still can't flash the image. Here's the log for that:
Note: In this case, I obviously have Re-Partition checked as well as Auto Reboot, but nothing else is selected.
Code:
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I747UCDLK3_I747ATTDLK3_I747UCDLK3_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<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> aboot.mbn
<ID:0/007> NAND Write Start!!
<ID:0/007> boot.img
<ID:0/007> cache.img.ext4
<ID:0/007> FAIL! (Write)
<OSM> All threads completed. (succeed 0 / failed 1)
Does anyone know how I can revive my phone? I'm not very familiar with the android environment or filesystem, and I'm hoping the problem is just that I'm doing something wrong/stupid.
Looks like you have the 4.3 bootloader and you cannot flash a stock 4.3 ROM in Odin unless you are using a a 4.3 ROM that has been compiled for flashing via Odin.
Don't use Odin with any ROM prior to 4.3.
audit13 said:
Looks like you have the 4.3 bootloader and you cannot flash a stock 4.3 ROM in Odin unless you are using a a 4.3 ROM that has been compiled for flashing via Odin.
Don't use Odin with any ROM prior to 4.3.
Click to expand...
Click to collapse
Thanks, any idea where I could find the correct ROM?
Have a look here: http://forum.xda-developers.com/showthread.php?t=2722660
Hi all.
My unrooted SHW-M480W got suddenly stuck in a samsung logo bootloop.
I can access system recovery and download mode, and my device is able to connect to odin (but not kies).
Recovery mode shows:
Code:
E: failed to mount / system (Invalid argument)
can't mount '/system' (invalid argument)
E: failed to mount / system (Invalid argument)
E: File Open error '/cache/recovery/log'
E: can't open /cache/recovery/log
E: File Open error '/cache/recovery/last_log'
E: can't open /cache/recovery/last_log
E: File Open error '/cache/recovery/last_install;'
E: can't open /cache/recovery/last_install
I downloaded the CF Auto-Root: p4notewifiany for the SHW-M480W (auto-reboot and F. Reset Time checked)
but Odin is unable to flash it:
Code:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CF-Auto-Root-p4notewifiany-p4notewifiany-shwm480w.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> recovery.img
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I also tried to flash the official Android 4.4.4 firmware PDA: M480WKXUBNI6 (2.7 GB)
same result:
Code:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> M480WKXUBNI6_M480WANYBNI6_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> boot.img
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
How do I go from here to recover my tablet?
Any help would be appreciated, I am very new to this whole flashing my tablet thing.
SHW-M480W is a variant of the original Note 10.1, and not of the Note 10.1 2014, right? You might have better luck in those forums.
Hello guys,
My S4 mini (GT-I9195) is restarting after the Samsung GalaxyS4mini GT-I9195 screen.
I can enter Odin mode. I can update firmware. see below log from Odin.
After that, phone enters recovery mode and restarts and i'm back at the begining.
Any ideas?
<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/004> Odin engine v(ID:3.1203)..
<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> sbl1.mbn
<ID:0/004> sbl2.mbn
<ID:0/004> sbl3.mbn
<ID:0/004> aboot.mbn
<ID:0/004> rpm.mbn
<ID:0/004> tz.mbn
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img.ext4
<ID:0/004> NON-HLOS.bin
<ID:0/004> cache.img.ext4
<ID:0/004> hidden.img.ext4
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!
<ID:0/004> Removed!!
<ID:0/004> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
Hello razvanells. Sorry for taking advantage of your topic, but I'm having the same problem as you.
This also happened with the S4 Mini (but I9192 version) of a my friend. This device had no root and had a stock rom. He hung up and did not turn on anymore, locking on the screen Samsung Galaxy S4 Mini I9192. I downloaded the stock rom from the sammobile site and installed it by Odin. The log I received was identical to yours, saying that the installation occurred successfully, but when the device reboots it goes to recovery mode and it does not start, I can only enter the download or recovery mode.
I tried the hard reset and received the following error:
Formatting / data ...
E: format_volume: make_extf4fs failed on /dev/block/platform/msm_sdcc.1/by-name/userdata
Formating / cache ...
E: format_volume: make_extf4fs failed on /dev/block/platform/msm_sdcc.1/by-name/cache
Data wipe complete.
Click to expand...
Click to collapse
I tried to recover the stock rom using Kies but it did not work either.
After a lot of research on google, I found a guy saying he was able to recover a smartphone using TWRP and formatting the memory in FAT and then reformatting it to EXT4 (at that link: http://forums.androidcentral.com/t-...850-encrypted-phone-freezes-when-turning.html).
I tried to install TWRP by Odin, which according to the log occurred perfectly, but after restarting the device the Android default recovery was there (even entering the recovery mode as soon as the phone rebooted).
I tried to install the CWM for Odin, and so it was. Odin's log said it was successful but when the phone was rebooted there was the default Android recovery again (even entering the recovery mode as soon as the phone rebooted).
I have no more ideas, and I wanted to ask if anyone knows how to solve this?
Thank you.
razvanells said:
Hello guys,
My S4 mini (GT-I9195) is restarting after the Samsung GalaxyS4mini GT-I9195 screen.
I can enter Odin mode. I can update firmware. see below log from Odin.
After that, phone enters recovery mode and restarts and i'm back at the begining.
Any ideas?
<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/004> Odin engine v(ID:3.1203)..
<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> sbl1.mbn
<ID:0/004> sbl2.mbn
<ID:0/004> sbl3.mbn
<ID:0/004> aboot.mbn
<ID:0/004> rpm.mbn
<ID:0/004> tz.mbn
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img.ext4
<ID:0/004> NON-HLOS.bin
<ID:0/004> cache.img.ext4
<ID:0/004> hidden.img.ext4
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!
<ID:0/004> Removed!!
<ID:0/004> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
Click to expand...
Click to collapse
même problème que vous