Develop Bugs

Galaxy S3 Randomly Died

Hi all I have an old S3 that seems to have kicked the bucket. I am hoping there is some way to save it though. I have been running the last CM 11 milestone for a long while now. I just use the phone with an archlinux chroot to do some linuxy-things. I tried ssh'ing into the phone while I was at work the other day and the ssh session hung. Upon getting home the screen was black and wouldn't turn on. I tried pulling the power and restarting and it just hung at the CM boot logo.
It would boot into TWRP recovery or download mode but never boot. I eventually noticed in TWRP that it said my internal storage was 0MB large and found that the userdata partition was corrupt (e2fsck wouldn't work)
I've tried every combination of flashing a stock .tar and/or .pit file but nothing seems to change.
Here is the output I get when trying to repartition with odin:
Code:
<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> I747UCDLK3_I747ATTDLK3_I747UCDLK3_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> 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> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
and heimdall:
heimdall flash --repartition --verbose --RECOVERY openrecovery-twrp-2.7.1.0-d2att.img --pit ../sgh-i747-16gb.pit --no-reboot
Code:
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...
Manufacturer: "Sasmsung"
Product: "MSM8960"
length: 18
device class: 2
S/N: 0
VID:PID: 04E8:685D
bcdDevice: 0100
iMan:iProd:iSer: 1:2:0
nb confs: 1
interface[0].altsetting[0]: num endpoints = 1
Class.SubClass.Protocol: 02.02.01
endpoint[0].address: 82
max packet size: 0010
polling interval: 09
interface[1].altsetting[0]: num endpoints = 2
Class.SubClass.Protocol: 0A.00.00
endpoint[0].address: 81
max packet size: 0200
polling interval: 00
endpoint[1].address: 01
max packet size: 0200
polling interval: 00
Claiming interface...
Attempt failed. Detaching driver...
Claiming interface again...
Setting up interface...
Initialising protocol...
WARNING: Control transfer #1 failed. Result: -9
WARNING: Control transfer #2 failed. Result: -9
WARNING: Control transfer #3 failed. Result: -9
WARNING: Control transfer #4 failed. Result: -9
WARNING: Control transfer #5 failed. Result: -9
WARNING: Control transfer #6 failed. Result: -9
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 unpack received packet.
ERROR: Failed to confirm end of PIT file transfer!
ERROR: PIT upload failed!
Ending session...
Releasing device interface...
Re-attaching kernel driver...
I'm out of ideas, any suggestions?
Thanks

I could be wrong here, but it sounds like your eMMC Chip may have died. I don't have specific experience of this ever happening to any of my phones, but it just popped into my head as an idea.
http://mobiletechvideos.mybigcommerce.com/samsung-galaxy-s-iii-emmc-chip-repair-replacement/

Yeah, this is what it sounds like to me. Anyone know if there is a way to verify this?
Sent from my Nexus 5 using XDA Free mobile app

[Q] Can't start or flash my cell phone. how to trouble shot and solve this issue ?

I am lost reading a lot of articles about how to solve my issue, but before solving it I need to know what is it ?
I have N7100 which:
In normal mode: hangs on Samsung logo while starting up and it never go further than that,
In Recovery mode: restarts when I see the TWRP logo.
In download mode: works fine
I read lots of article and I tried to flash the stock ROM from SamFirmware with now luck "although it is successful". Check my log:
Code:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7100XXUFND4_N7100OJVFND3_N7100XXUFND3_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> sboot.bin
<ID:0/005> NAND Write Start!!
<ID:0/005> tz.img
<ID:0/005> boot.img
<ID:0/005> recovery.img
<ID:0/005> system.img
<ID:0/005> modem.bin
<ID:0/005> cache.img
<ID:0/005> hidden.img
<ID:0/005> RQT_CLOSE !!
<ID:0/005> RES OK !!
<ID:0/005> Completed..
<ID:0/005> Added!!
<OSM> All threads completed. (succeed 1 / failed 0)
Another useful information to mention is that in the download mode here are what is written:
Code:
ODIN MODE
PRODUCT NAME: GT-N7100
CUSTOM BINARY DOWNLOAD: Yes (4 Counts)
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
I tried flashing different firmwares and different recoveries with no luck, by mistake I flashed TWRP N7100 AT&T version "openrecovery-twrp-2.7.2.2-t0lteatt.img", after that I am now able to get in recovery mode but
it asks for a password
it displayed a title Team Win Recovery Project v2.6.3.1 "although it is not the AT&T version"
I cancelled the password and opened the log and I was chocked with what I saw:
Code:
E: unable to find partition size for '/boot'
E: unable to find partition size for '/recovery'
E: unable to find partition size for '/modem'
E: unable to find partition size for '/data'
Updating partition details...
E: unable to mount '/efs'
E: unable to mount '/cache'
E: unable to mount '/system'
E: unable to mount '/cache'
E: unable to mount '/cache'
The question is what is my phone problem, how to trouble shot it and solve it ??? :crying::crying::crying::crying:

Gabrianoo said:
I am lost reading a lot of articles about how to solve my issue, but before solving it I need to know what is it ?
I have N7100 which:
In normal mode: hangs on Samsung logo while starting up and it never go further than that,
In Recovery mode: restarts when I see the TWRP logo.
In download mode: works fine
I read lots of article and I tried to flash the stock ROM from SamFirmware with now luck "although it is successful". Check my log:
Code:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7100XXUFND4_N7100OJVFND3_N7100XXUFND3_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> sboot.bin
<ID:0/005> NAND Write Start!!
<ID:0/005> tz.img
<ID:0/005> boot.img
<ID:0/005> recovery.img
<ID:0/005> system.img
<ID:0/005> modem.bin
<ID:0/005> cache.img
<ID:0/005> hidden.img
<ID:0/005> RQT_CLOSE !!
<ID:0/005> RES OK !!
<ID:0/005> Completed..
<ID:0/005> Added!!
<OSM> All threads completed. (succeed 1 / failed 0)
Another useful information to mention is that in the download mode here are what is written:
Code:
ODIN MODE
PRODUCT NAME: GT-N7100
CUSTOM BINARY DOWNLOAD: Yes (4 Counts)
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
I tried flashing different firmwares and different recoveries with no luck, by mistake I flashed TWRP N7100 AT&T version "openrecovery-twrp-2.7.2.2-t0lteatt.img", after that I am now able to get in recovery mode but
it asks for a password
it displayed a title Team Win Recovery Project v2.6.3.1 "although it is not the AT&T version"
I cancelled the password and opened the log and I was chocked with what I saw:
Code:
E: unable to find partition size for '/boot'
E: unable to find partition size for '/recovery'
E: unable to find partition size for '/modem'
E: unable to find partition size for '/data'
Updating partition details...
E: unable to mount '/efs'
E: unable to mount '/cache'
E: unable to mount '/system'
E: unable to mount '/cache'
E: unable to mount '/cache'
The question is what is my phone problem, how to trouble shot it and solve it ??? :crying::crying::crying::crying:
Click to expand...
Click to collapse
You could try Samsungs kies emergency recovery as describes here:
http://forum.xda-developers.com/showthread.php?t=2261153
http://www.samsung.com/us/support/faq/FAQ00059169/81100
Mabye it will fix it, but it is a long shot.
Edit:
Small addition emergency recovery requires kies 3, if emergency recovery doesn't work you can try the firmware upgrade and initialisation option from kies (which also flashes everything trough download mode)

m.n.mulder1992 said:
You could try Samsungs kies emergency recovery as describes here:
http://forum.xda-developers.com/showthread.php?t=2261153
http://www.samsung.com/us/support/faq/FAQ00059169/81100
Mabye it will fix it, but it is a long shot.
Edit:
Small addition emergency recovery requires kies 3, if emergency recovery doesn't work you can try the firmware upgrade and initialisation option from kies (which also flashes everything trough download mode)
Click to expand...
Click to collapse
Couldn't get it done stuck at "the device's version cannot be updated" because I am on a custom recovery.

Other idea
Gabrianoo said:
Couldn't get it done stuck at "the device's version cannot be updated" because I am on a custom recovery.
Click to expand...
Click to collapse
Ok other idea did you try repartitioning with Odin?
5th post has the PIT file needed for repartitioning http://forum.xda-developers.com/showthread.php?t=1927983
The main thing emergency recovery does is: repartitioning and flashing all partitions anyway.
PS.
Also weird i can use emergency recovery with CWM installed

mnm1992 said:
Ok other idea did you try repartitioning with Odin?
5th post has the PIT file needed for repartitioning http://forum.xda-developers.com/showthread.php?t=1927983
The main thing emergency recovery does is: repartitioning and flashing all partitions anyway.
PS.
Also weird i can use emergency recovery with CWM installed
Click to expand...
Click to collapse
Regarding the mentioned thread I tried it before with no luck, I repeated it and here are the log results:
Code:
<ID:0/005> Added!!
<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> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> RQT_CLOSE !!
<ID:0/005> RES OK !!
<ID:0/005> Removed!!
<ID:0/005> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
Nothing changed after the re-partitioning :crying:
About your note I don't know why ? but I am expecting the wired behavior
I started to lose hope and I guess I will go to the mother board replacement solution although I feel like it can be solved by a software solution.

Gabrianoo said:
Regarding the mentioned thread I tried it before with no luck, I repeated it and here are the log results:
Code:
<ID:0/005> Added!!
<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> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> RQT_CLOSE !!
<ID:0/005> RES OK !!
<ID:0/005> Removed!!
<ID:0/005> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
Nothing changed after the re-partitioning :crying:
About your note I don't know why ? but I am expecting the wired behavior
I started to lose hope and I guess I will go to the mother board replacement solution although I feel like it can be solved by a software solution.
Click to expand...
Click to collapse
Just a check:
You did:
1: start Odin
2 select repartition
3: select pit file
4: click pda select some archive from sammmobile right?
Otherwise it won't work cause:
Repartition creates the empty partitions (System, data, recovery, etc ) specified in the PIT file
The archive under the PDA option fills those partitions with the needed files
If you did just the repartition it won,t boot cause the partitions are empty.

N7100 help to find rom with pit

Hello guys i hope you can help me and i hope im writing on the right threads.
i have a N7100..this smartphone not start, i see only for few seconds the logo start and go to loop.
I try to use different version of ODIN and firmware but i get this kind of error:
<ID:0/022> Added!!
<ID:0/022> Odin v.3 engine (ID:22)..
<ID:0/022> File analysis..
<ID:0/022> SetupConnection..
<ID:0/022> Initialzation..
<ID:0/022> Get PIT for mapping..
<ID:0/022>
<ID:0/022> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
Also i try to make the hard reset but not start the menu.
I think the only solution is use a firmware with PIT partition but is very very difficult find it , all the link is offline.
Can you help me?

[help] bricked n7100

Issue: Only can enter download mode, nothing else.
download mode screen:
Code:
ODIN MODE
PRODUCT NAME: GT-N7100
CUSTOM BINARY DOWNLOAD: No
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
KNOX WARRANTY VOID: 0
AP SWAEV:
already tried several computers (Win7, 8, 10, x86, x64), all USB ports (no hub), original samsung cable and several known-good cable, failed.
troubleshoot or odin log (PIT unchecked) done:
Code:
<ID:0/003> Added!!
<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>
<ID:0/003> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
When I try with PIT_N7100_16GB_20121102.pit, it logs:
Code:
<ID:0/003> Added!!
<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> FAIL!
<ID:0/003>
<ID:0/003> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
please help, thanks.

It looks to me like you tried everything I would try. Without the pit information, a stock rom can be flashed either.
At this point, I would take it to a cell repair shop to see if the phone can be revived through jtag.

Need Help! Note 2 N7105 odin result re-partition operation failed.

Hope someone can help me
phone: note 2 GT-N7105
OS: windows 10 64bit/windows 7 64 bit
tried with several odins 3.04, 3.10.7, 3.07, 3.09, 3.11.1, 3.12.3, 3.10.6, 3.10.7
2 PIT files
-T0LTE_EUR_OPEN_8G.pit
-N7105_t0_Mx-MDM.pit
full 4 files: N7105ZHUEMK3
one tar file: N7105XXUFOB2_N7105OLBFOD1_N7105XXUFNI2_HOME.tar.md5
My phone can go into recovery and download mode.
Cannot clear cache or data in recovery mode as mount or read error occur
When flash in odin, re-parition operating error
Is there anyway to flash from sd card or anything like that?
Hope someone kindly shed the light.
Thank you!
Error without PIT file
<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> sboot.bin
<ID:0/005> NAND Write Start!!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Error with PIT file
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Set PIT file..
<ID:0/006> DO NOT TURN OFF TARGET!!
<ID:0/006>
<ID:0/006> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

Tried different usb cables and usb ports?

audit13 said:
Tried different usb cables and usb ports?
Click to expand...
Click to collapse
Yes different ports
Yes different usb cable but none are samsung's cable though. thanks.

Btw, firmware and pit file must be the same or doesn't need to be?
PIT file is only matter for the model?
Thanks.

The pit file must match the model number and amount of memory.
Do you get pit error when trying to flash without the pit file?

audit13 said:
The pit file must match the model number and amount of memory.
Do you get pit error when trying to flash without the pit file?
Click to expand...
Click to collapse
No, I didn't get PIT error without PIT file.

In my experience, pit files are only required if Odin is not able to pull the partition information from the phone during the flash process.
You might want to look into having the phone flashed via jtag.