GSM Shop GSM Shop
GSM-Forum  

Welcome to the GSM-Forum forums.

You are currently viewing our boards as a guest which gives you limited access to view most discussions and access our other features.
Only registered members may post questions, contact other members or search our database of over 8 million posts.

Registration is fast, simple and absolutely free so please - Click to REGISTER!

If you have any problems with the registration process or your account login, please contact contact us .

Go Back   GSM-Forum > GSM & CDMA Phones / Tablets Software & Hardware Area > Samsung > Samsung Android based phones


Samsung Android based phones Discussion and all of your questions relating to the Samsung Android based phones.

Reply
 
LinkBack Thread Tools Display Modes
Old 05-22-2015, 22:03   #76 (permalink)
Freak Poster
 
Join Date: Aug 2009
Posts: 173
Member: 1090661
Status: Offline
Thanks Meter: 15

Can anyone explain me what are the sympthons of a death boot? apart from not turning on the phone...
  Reply With Quote
Old 05-23-2015, 00:26   #77 (permalink)
Freak Poster
 
Join Date: Aug 2009
Posts: 173
Member: 1090661
Status: Offline
Thanks Meter: 15
I am trying to fix a phone using your method, here the log from tera term...

Code:
PMIC rev = PASS2(4)
BUCK1OUT(vdd_mif) = 0x05
BUCK3DVS1(vdd_int) = 0x20
[MMC] there are pending interrupts 0x00010000
[MMC] response timeout error : 00000104 cmd 1, ret -2147483665.
mshci: ============== REGISTER DUMP ==============
mshci: MSHCI_CTRL:      0x00000010
mshci: MSHCI_PWREN:     0x00000001
mshci: MSHCI_CLKDIV:    0x0000007d
mshci: MSHCI_CLKSRC:    0x00000000
mshci: MSHCI_CLKENA:    0x00000001
mshci: MSHCI_TMOUT:     0xffffffff
mshci: MSHCI_CTYPE:     0x00000000
mshci: MSHCI_BLKSIZ:    0x00000200
mshci: MSHCI_BYTCNT:    0xf0000000
mshci: MSHCI_INTMSK:    0x00000000
mshci: MSHCI_CMDARG:    0x40300000
mshci: MSHCI_CMD:       0x20002041
mshci: MSHCI_MINTSTS:   0x00000000
mshci: MSHCI_RINTSTS:   0x00000000
mshci: MSHCI_STATUS:    0x0001f906
mshci: MSHCI_FIFOTH:    0x20400040
mshci: MSHCI_CDETECT:   0x00000001
mshci: MSHCI_WRTPRT:    0x00000001
mshci: MSHCI_GPIO:      0x00000000
mshci: MSHCI_TCBCNT:    0x000ffe00
mshci: MSHCI_TBBCNT:    0x00000000
mshci: MSHCI_DEBNCE:    0x000fffff
mshci: MSHCI_USRID:     0xffffffff
mshci: MSHCI_VERID:     0x5342240a
mshci: MSHCI_HCON:      0x00e424c1
mshci: MSHCI_UHS_REG:   0x00000000
mshci: MSHCI_BMOD:      0x00000200
mshci: MSHCI_PLDMND:   0x00000000
mshci: MSHCI_DBADDR:    0x00000000
mshci: MSHCI_IDSTS:     0x00000000
mshci: MSHCI_IDINTEN:   0x00000000
mshci: MSHCI_DSCADDR:   0x00000000
mshci: MSHCI_BUFADDR:   0x00000000
mshci: MSHCI_WAKEUPCON: 0x00000000
mshci: MSHCI_CLOCKCON:  0x00000000
mshci: MSHCI_FIFODAT:   0x00000000
mshci: ===========================================
card_init: mmc_send_op_cond fail! ret = -2147483665
mmc_initialize: mmc init fail once! ret = -2147483663
[MMC] there are pending interrupts 0x00010000
[MMC] response timeout error : 00000104 cmd 1, ret -2147483665.
mshci: ============== REGISTER DUMP ==============
mshci: MSHCI_CTRL:      0x00000010
mshci: MSHCI_PWREN:     0x00000001
mshci: MSHCI_CLKDIV:    0x0000007d
mshci: MSHCI_CLKSRC:    0x00000000
mshci: MSHCI_CLKENA:    0x00000001
mshci: MSHCI_TMOUT:     0xffffffff
mshci: MSHCI_CTYPE:     0x00000000
mshci: MSHCI_BLKSIZ:    0x00000200
mshci: MSHCI_BYTCNT:    0xf0000000
mshci: MSHCI_INTMSK:    0x00000000
mshci: MSHCI_CMDARG:    0x40300000
mshci: MSHCI_CMD:       0x20002041
mshci: MSHCI_MINTSTS:   0x00000000
mshci: MSHCI_RINTSTS:   0x00000000
mshci: MSHCI_STATUS:    0x0001f906
mshci: MSHCI_FIFOTH:    0x20400040
mshci: MSHCI_CDETECT:   0x00000001
mshci: MSHCI_WRTPRT:    0x00000001
mshci: MSHCI_GPIO:      0x00000000
mshci: MSHCI_TCBCNT:    0x000ffe00
mshci: MSHCI_TBBCNT:    0x00000000
mshci: MSHCI_DEBNCE:    0x000fffff
mshci: MSHCI_USRID:     0xffffffff
mshci: MSHCI_VERID:     0x5342240a
mshci: MSHCI_HCON:      0x00e424c1
mshci: MSHCI_UHS_REG:   0x00000000
mshci: MSHCI_BMOD:      0x00000200
mshci: MSHCI_PLDMND:   0x00000000
mshci: MSHCI_DBADDR:    0x00000000
mshci: MSHCI_IDSTS:     0x00000000
mshci: MSHCI_IDINTEN:   0x00000000
mshci: MSHCI_DSCADDR:   0x00000000
mshci: MSHCI_BUFADDR:   0x00000000
mshci: MSHCI_WAKEUPCON: 0x00000000
mshci: MSHCI_CLOCKCON:  0x00000000
mshci: MSHCI_FIFODAT:   0x00000000
mshci: ===========================================
card_init: mmc_send_op_cond fail! ret = -2147483665
mmc_initialize: mmc->capacity = 0
mmc_initialize: mmc init fail twice! ret = -2147483663
ü[MMC] response timeout error : 00000104 cmd 18, ret -2147483665.
mshci: ============== REGISTER DUMP ==============
mshci: MSHCI_CTRL:      0x02000030
mshci: MSHCI_PWREN:     0x00000001
mshci: MSHCI_CLKDIV:    0x0000007d
mshci: MSHCI_CLKSRC:    0x00000000
mshci: MSHCI_CLKENA:    0x00000001
mshci: MSHCI_TMOUT:     0xffffffff
mshci: MSHCI_CTYPE:     0x00000000
mshci: MSHCI_BLKSIZ:    0x00000200
mshci: MSHCI_BYTCNT:    0x00002000
mshci: MSHCI_INTMSK:    0x00000000
mshci: MSHCI_CMDARG:    0x00000022
mshci: MSHCI_CMD:       0x20002352
mshci: MSHCI_MINTSTS:   0x00000000
mshci: MSHCI_RINTSTS:   0x00000104
mshci: MSHCI_STATUS:    0x0001f906
mshci: MSHCI_FIFOTH:    0x20400040
mshci: MSHCI_CDETECT:   0x00000001
mshci: MSHCI_WRTPRT:    0x00000001
mshci: MSHCI_GPIO:      0x00000000
mshci: MSHCI_TCBCNT:    0x00000000
mshci: MSHCI_TBBCNT:    0x00000000
mshci: MSHCI_DEBNCE:    0x000fffff
mshci: MSHCI_USRID:     0xffffffff
mshci: MSHCI_VERID:     0x5342240a
mshci: MSHCI_HCON:      0x00e424c1
mshci: MSHCI_UHS_REG:   0x00000000
mshci: MSHCI_BMOD:      0x00000282
mshci: MSHCI_PLDMND:   0x00000000
mshci: MSHCI_DBADDR:    0x44f00000
mshci: MSHCI_IDSTS:     0x00000000
mshci: MSHCI_IDINTEN:   0x00000000
mshci: MSHCI_DSCADDR:   0x44f00010
mshci: MSHCI_BUFADDR:   0x00000000
mshci: MSHCI_WAKEUPCON: 0x00000000
mshci: MSHCI_CLOCKCON:  0x00000000
mshci: MSHCI_FIFODAT:   0x00000000
mshci: ===========================================
dev 0 rw failed rw_flag = 1
pit_check_integrity: invalid pit.(0x0)
[MMC] response timeout error : 00000104 cmd 17, ret -2147483665.
mshci: ============== REGISTER DUMP ==============
mshci: MSHCI_CTRL:      0x02000030
mshci: MSHCI_PWREN:     0x00000001
mshci: MSHCI_CLKDIV:    0x0000007d
mshci: MSHCI_CLKSRC:    0x00000000
mshci: MSHCI_CLKENA:    0x00000001
mshci: MSHCI_TMOUT:     0xffffffff
mshci: MSHCI_CTYPE:     0x00000000
mshci: MSHCI_BLKSIZ:    0x00000200
mshci: MSHCI_BYTCNT:    0x00000200
mshci: MSHCI_INTMSK:    0x00000000
mshci: MSHCI_CMDARG:    0x00000000
mshci: MSHCI_CMD:       0x20002351
mshci: MSHCI_MINTSTS:   0x00000000
mshci: MSHCI_RINTSTS:   0x00000104
mshci: MSHCI_STATUS:    0x0001f906
mshci: MSHCI_FIFOTH:    0x20400040
mshci: MSHCI_CDETECT:   0x00000001
mshci: MSHCI_WRTPRT:    0x00000001
mshci: MSHCI_GPIO:      0x00000000
mshci: MSHCI_TCBCNT:    0x00000000
mshci: MSHCI_TBBCNT:    0x00000000
mshci: MSHCI_DEBNCE:    0x000fffff
mshci: MSHCI_USRID:     0xffffffff
mshci: MSHCI_VERID:     0x5342240a
mshci: MSHCI_HCON:      0x00e424c1
mshci: MSHCI_UHS_REG:   0x00000000
mshci: MSHCI_BMOD:      0x00000282
mshci: MSHCI_PLDMND:   0x00000000
mshci: MSHCI_DBADDR:    0x44f00000
mshci: MSHCI_IDSTS:     0x00000000
mshci: MSHCI_IDINTEN:   0x00000000
mshci: MSHCI_DSCADDR:   0x44f00000
mshci: MSHCI_BUFADDR:   0x00000000
mshci: MSHCI_WAKEUPCON: 0x00000000
mshci: MSHCI_CLOCKCON:  0x00000000
mshci: MSHCI_FIFODAT:   0x00000000
mshci: ===========================================
dev 0 rw failed rw_flag = 1
[MMC] response timeout error : 00000104 cmd 18, ret -2147483665.
mshci: ============== REGISTER DUMP ==============
mshci: MSHCI_CTRL:      0x02000030
mshci: MSHCI_PWREN:     0x00000001
mshci: MSHCI_CLKDIV:    0x0000007d
mshci: MSHCI_CLKSRC:    0x00000000
mshci: MSHCI_CLKENA:    0x00000001
mshci: MSHCI_TMOUT:     0xffffffff
mshci: MSHCI_CTYPE:     0x00000000
mshci: MSHCI_BLKSIZ:    0x00000200
mshci: MSHCI_BYTCNT:    0x00002000
mshci: MSHCI_INTMSK:    0x00000000
mshci: MSHCI_CMDARG:    0x00000022
mshci: MSHCI_CMD:       0x20002352
mshci: MSHCI_MINTSTS:   0x00000000
mshci: MSHCI_RINTSTS:   0x00000104
mshci: MSHCI_STATUS:    0x0001f906
mshci: MSHCI_FIFOTH:    0x20400040
mshci: MSHCI_CDETECT:   0x00000001
mshci: MSHCI_WRTPRT:    0x00000001
mshci: MSHCI_GPIO:      0x00000000
mshci: MSHCI_TCBCNT:    0x00000000
mshci: MSHCI_TBBCNT:    0x00000000
mshci: MSHCI_DEBNCE:    0x000fffff
mshci: MSHCI_USRID:     0xffffffff
mshci: MSHCI_VERID:     0x5342240a
mshci: MSHCI_HCON:      0x00e424c1
mshci: MSHCI_UHS_REG:   0x00000000
mshci: MSHCI_BMOD:      0x00000282
mshci: MSHCI_PLDMND:   0x00000000
mshci: MSHCI_DBADDR:    0x44f00000
mshci: MSHCI_IDSTS:     0x00000000
mshci: MSHCI_IDINTEN:   0x00000000
mshci: MSHCI_DSCADDR:   0x44f00010
mshci: MSHCI_BUFADDR:   0x00000000
mshci: MSHCI_WAKEUPCON: 0x00000000
mshci: MSHCI_CLOCKCON:  0x00000000
mshci: MSHCI_FIFODAT:   0x00000000
mshci: ===========================================
dev 0 rw failed rw_flag = 1
pit_check_integrity: invalid pit.(0xc0c0c0c0)
update_guid_partition_table: There is no pit binary.
[MMC] response timeout error : 00000104 cmd 6, ret -2147483665.
mshci: ============== REGISTER DUMP ==============
mshci: MSHCI_CTRL:      0x02000030
mshci: MSHCI_PWREN:     0x00000001
mshci: MSHCI_CLKDIV:    0x0000007d
mshci: MSHCI_CLKSRC:    0x00000000
mshci: MSHCI_CLKENA:    0x00000001
mshci: MSHCI_TMOUT:     0xffffffff
mshci: MSHCI_CTYPE:     0x00000000
mshci: MSHCI_BLKSIZ:    0x00000200
mshci: MSHCI_BYTCNT:    0x00002000
mshci: MSHCI_INTMSK:    0x00000000
mshci: MSHCI_CMDARG:    0x03b34900
mshci: MSHCI_CMD:       0x20002146
mshci: MSHCI_MINTSTS:   0x00000000
mshci: MSHCI_RINTSTS:   0x00000000
mshci: MSHCI_STATUS:    0x0001f906
mshci: MSHCI_FIFOTH:    0x20400040
mshci: MSHCI_CDETECT:   0x00000001
mshci: MSHCI_WRTPRT:    0x00000001
mshci: MSHCI_GPIO:      0x00000000
mshci: MSHCI_TCBCNT:    0x00000000
mshci: MSHCI_TBBCNT:    0x00000004
mshci: MSHCI_DEBNCE:    0x000fffff
mshci: MSHCI_USRID:     0xffffffff
mshci: MSHCI_VERID:     0x5342240a
mshci: MSHCI_HCON:      0x00e424c1
mshci: MSHCI_UHS_REG:   0x00000000
mshci: MSHCI_BMOD:      0x00000282
mshci: MSHCI_PLDMND:   0x00000000
mshci: MSHCI_DBADDR:    0x44f00000
mshci: MSHCI_IDSTS:     0x00000000
mshci: MSHCI_IDINTEN:   0x00000000
mshci: MSHCI_DSCADDR:   0x44f00010
mshci: MSHCI_BUFADDR:   0x00000000
mshci: MSHCI_WAKEUPCON: 0x00000000
mshci: MSHCI_CLOCKCON:  0x00000000
mshci: MSHCI_FIFODAT:   0x00000000
mshci: ===========================================
if_ddi_data:33 fail!
init_param_part: can't find partition.
set_charger_current: chg curr(3f), in curr(17)
set_charger_state: buck(1), chg(1), reg(0x05)
microusb_get_attached_device: STATUS1:0x3d, 2:0x40
set_auto_current: ta_state(0), curr(1000)
init_fuelgauge: fuelgauge power ok
init_fuelgauge: POR status
fuelgauge_por: POR start: vcell(4021), vfocv(4072), soc(85)
fuelgauge_por: update SDI M0 parameter
fuelgauge_por: RCOMP(0x0065), TEMPCO(0x0930)
fuelgauge_por: POR finish: vcell(4020), vfocv(4151), soc(78)
init_fuelgauge: disable charging for soc-cal
set_charger_current: chg curr(3f), in curr(17)
set_charger_state: buck(1), chg(0), reg(0x04)
init_fuelgauge: vcell comp. = 3963
get_table_soc: vcell(3963) is caculated to t-soc(74.595)
init_fuelgauge: start: vcell(3963), vfocv(4138), soc(78), table soc(74)
init_fuelgauge: finish: vcell(3963), vfocv(4138), soc(78), table soc(74)
init_microusb_ic: MUIC: CONTROL1:0x1b
init_microusb_ic: MUIC: CONTROL1:0x1b
init_microusb_ic: MUIC: CONTROL2:0x3b
init_microusb_ic: MUIC: CONTROL2:0x3b
PMIC_ID      = 0x02
PMIC_IRQSRC  = 0x00
PMIC_IRQ1    = 0x7f
PMIC_IRQ2    = 0x00
PMIC_IRQ1M   = 0xc0
PMIC_IRQ2M   = 0x03
PMIC_STATUS1 = 0x14
PMIC_STATUS2 = 0x00
PMIC_PWRON   = 0x04
PMIC_RTCINT  = 0x11
PMIC_RTCINTM = 0x3f
s5p_check_keypad: 0x100000
s5p_check_reboot_mode: INFORM3 = 0 ... skip
s5p_check_upload: MAGIC(0xc0c0c0c0), RST_STAT(0x10000)
microusb_get_attached_device: STATUS1:0x3c, 2:0x40
s5p_check_download: 0
[MMC] response timeout error : 00000104 cmd 6, ret -2147483665.
mshci: ============== REGISTER DUMP ==============
mshci: MSHCI_CTRL:      0x02000030
mshci: MSHCI_PWREN:     0x00000001
mshci: MSHCI_CLKDIV:    0x0000007d
mshci: MSHCI_CLKSRC:    0x00000000
mshci: MSHCI_CLKENA:    0x00000001
mshci: MSHCI_TMOUT:     0xffffffff
mshci: MSHCI_CTYPE:     0x00000000
mshci: MSHCI_BLKSIZ:    0x00000200
mshci: MSHCI_BYTCNT:    0x00002000
mshci: MSHCI_INTMSK:    0x00000000
mshci: MSHCI_CMDARG:    0x03b34900
mshci: MSHCI_CMD:       0x20002146
mshci: MSHCI_MINTSTS:   0x00000000
mshci: MSHCI_RINTSTS:   0x00000000
mshci: MSHCI_STATUS:    0x0001f906
mshci: MSHCI_FIFOTH:    0x20400040
mshci: MSHCI_CDETECT:   0x00000001
mshci: MSHCI_WRTPRT:    0x00000001
mshci: MSHCI_GPIO:      0x00000000
mshci: MSHCI_TCBCNT:    0x00000000
mshci: MSHCI_TBBCNT:    0x00000008
mshci: MSHCI_DEBNCE:    0x000fffff
mshci: MSHCI_USRID:     0xffffffff
mshci: MSHCI_VERID:     0x5342240a
mshci: MSHCI_HCON:      0x00e424c1
mshci: MSHCI_UHS_REG:   0x00000000
mshci: MSHCI_BMOD:      0x00000282
mshci: MSHCI_PLDMND:   0x00000000
mshci: MSHCI_DBADDR:    0x44f00000
mshci: MSHCI_IDSTS:     0x00000000
mshci: MSHCI_IDINTEN:   0x00000000
mshci: MSHCI_DSCADDR:   0x44f00010
mshci: MSHCI_BUFADDR:   0x00000000
mshci: MSHCI_WAKEUPCON: 0x00000000
mshci: MSHCI_CLOCKCON:  0x00000000
mshci: MSHCI_FIFODAT:   0x00000000
mshci: ===========================================
emmc boot partition open failed.

: Entering usb mode for GT-I9300 (6)..
scr_draw_image: draw 'download_error.jpg'...
read_param_file: param is not initialized.
cmu_div:1, div:7, src_clk:800000000, pixel_clk:57153600
s5p_dsim_display_config : VIDEO MODE
a2, 60, 90,
Download mode turn to AP_USB(4)
øt_dev_pm: hello! I'm USB.(1)
exynos4 usbd2 phy init
usb old tune = 0x2819b3
usb new tune = 0x2831b3
CPU MODE

Last edited by ...:::::NP™:::::...; 04-14-2017 at 21:23. Reason: code added
  Reply With Quote
Old 05-23-2015, 09:15   #78 (permalink)
No Life Poster
 
allumts's Avatar
 
Join Date: Apr 2011
Age: 58
Posts: 16,408
Member: 1564612
Status: Offline
Thanks Meter: 12,343
Donate money to this user
@gjalvarez,

from this Log you can see that you device is Dead Boot or have damaged EMMC or No P.Name itc... you device must need OBBLIGATORY one EMMC Direct connection for reset and write all partition in it, from User Area, Boot1 and Boot2...but you need enough knowledge in this field and one Box like ATF that permitte of do all repair operaction...in this moment you EMMC is BROKEN

BR
allumts
  Reply With Quote
The Following User Says Thank You to allumts For This Useful Post:
Old 05-23-2015, 18:26   #79 (permalink)
Freak Poster
 
Join Date: Aug 2009
Posts: 173
Member: 1090661
Status: Offline
Thanks Meter: 15
Quote:
Originally Posted by allumts View Post
@gjalvarez,

from this Log you can see that you device is Dead Boot or have damaged EMMC or No P.Name itc... you device must need OBBLIGATORY one EMMC Direct connection for reset and write all partition in it, from User Area, Boot1 and Boot2...but you need enough knowledge in this field and one Box like ATF that permitte of do all repair operaction...in this moment you EMMC is BROKEN

BR
allumts
I have easy jtag, and also z3x, know how to use z3x but not much about easy jtag... does it work?
  Reply With Quote
Old 05-23-2015, 18:48   #80 (permalink)
No Life Poster
 
allumts's Avatar
 
Join Date: Apr 2011
Age: 58
Posts: 16,408
Member: 1564612
Status: Offline
Thanks Meter: 12,343
Donate money to this user
With Z3x not solve Nothingh, only with EMMC direct can solve and if you have this Easy Jtag use this.

Read the Update of Atf or from this Easy Jtag, now can repair also EMMC TOTALLY DEAD, if you have knowledge about Jtag and microwelder.

BR
allumts
  Reply With Quote
Old 08-05-2015, 13:46   #81 (permalink)
Insane Poster
 
Join Date: Mar 2013
Posts: 81
Member: 1909191
Status: Offline
Thanks Meter: 3
Quote:
Originally Posted by mike_shinoda View Post
download efs n7100
new link, please ...efs n7100
  Reply With Quote
Old 08-05-2015, 13:48   #82 (permalink)
Insane Poster
 
Join Date: Mar 2013
Posts: 81
Member: 1909191
Status: Offline
Thanks Meter: 3
Firmware available

N7100_Mx-MDM_t03gpit

N7100XXDLJ2_OXA_FACTORY.zip

Last edited by ...:::::NP™:::::...; 04-14-2017 at 21:37. Reason: Firmware link update
  Reply With Quote
Old 08-05-2015, 13:59   #83 (permalink)
No Life Poster
 
saifjaan009's Avatar
 
Join Date: Feb 2015
Location: PAKISTAN (OMAN)
Age: 35
Posts: 637
Member: 2340225
Status: Offline
Sonork: 100.1662389
Thanks Meter: 367
Donate money to this user
Arrow

Quote:
Originally Posted by bollicine View Post
new link, please ...efs n7100
Download Here


N7100efs.tar - Download - 4shared - Saif Ur Rahman


Best Regards
Saif Ur Rahman
  Reply With Quote
Old 08-05-2015, 14:19   #84 (permalink)
No Life Poster
 
allumts's Avatar
 
Join Date: Apr 2011
Age: 58
Posts: 16,408
Member: 1564612
Status: Offline
Thanks Meter: 12,343
Donate money to this user
Please anybody have PIT file for N7100 to 32GB version?...or if anyone have one N7100 to 32GB can read PIT file and please post here or send to me?.. who have need more explanaction can write here...but please Read Pit 32GB from N7100, (can read with any Box/Tool), or if have post here..

BR
allumts
  Reply With Quote
Old 08-05-2015, 14:51   #85 (permalink)
No Life Poster
 
saifjaan009's Avatar
 
Join Date: Feb 2015
Location: PAKISTAN (OMAN)
Age: 35
Posts: 637
Member: 2340225
Status: Offline
Sonork: 100.1662389
Thanks Meter: 367
Donate money to this user
Arrow

Quote:
Originally Posted by allumts View Post
Please anybody have PIT file for N7100 to 32GB version?...or if anyone have one N7100 to 32GB can read PIT file and please post here or send to me?.. who have need more explanaction can write here...but please Read Pit 32GB from N7100, (can read with any Box/Tool), or if have post here..

BR
allumts
Check This One


N7100_Mx-MDM_t03g.pit - Download - 4shared - Saif Ur Rahman



Best Regards
Saif Ur Rahman
  Reply With Quote
The Following User Says Thank You to saifjaan009 For This Useful Post:
Old 08-05-2015, 14:55   #86 (permalink)
No Life Poster
 
allumts's Avatar
 
Join Date: Apr 2011
Age: 58
Posts: 16,408
Member: 1564612
Status: Offline
Thanks Meter: 12,343
Donate money to this user
Want to try with this...also i think have in my files but not have tested with this...

BR
allumts
  Reply With Quote
Old 08-05-2015, 14:55   #87 (permalink)
No Life Poster
 
allumts's Avatar
 
Join Date: Apr 2011
Age: 58
Posts: 16,408
Member: 1564612
Status: Offline
Thanks Meter: 12,343
Donate money to this user
edit......problem double email..........
  Reply With Quote
Old 08-10-2015, 11:35   #88 (permalink)
No Life Poster
 
allumts's Avatar
 
Join Date: Apr 2011
Age: 58
Posts: 16,408
Member: 1564612
Status: Offline
Thanks Meter: 12,343
Donate money to this user
Quote:
Originally Posted by saifjaan009 View Post
Check This One


N7100_Mx-MDM_t03g.pit - Download - 4shared - Saif Ur Rahman



Best Regards
Saif Ur Rahman
This PIT get error, i've need one 32GB PIT for N7100 now have also Display with Grey Lines...(but this not one problem, can repair just flashing Default EFS), problem is that first phone was accepting also normal PIT 16GB not cannot flash nothing becouse stopping in PIT Failed.

GRRRRRRRRRRRRRRRRR was repaired from this method but i've flashed one Stock FW and no 4 part file +Pit take out the Sd card...

Quote:
àøPMIC rev = PASS2(4)
BUCK1OUT(vdd_mif) = 0x05
BUCK3DVS1(vdd_int) = 0x20
[MMC] there are pending interrupts 0x00010000
cardtype: 0x00000007
SB_MMC_HS_52MHZ_1_8V_3V_IO
mmc->card_caps: 0x00000311
mmc->host_caps: 0x00000311
mmc_initialize: mmc->capacity = 30777344
Current SBOOT version : VERSION_-+A2

Samsung S-Boot 4.0-2138564 for GT-N7100 (Nov 20 2013 - 19:56:56)

EXYNOS4412(EVT 2.0) / 2044MB / 15028MB / Rev 11 / N7100XXUEMK9 /(PKG_ID 0x502d058)

- read_bl1
pit_check_signature (PIT) valid.
initialize_ddi_data: usable! (2:0x0)
[RPMB] emmc_rpmb_open:
Get DATA success.
[RPMB] emmc_rpmb_close:
initialize_rpmb_data: usable! (GT-N7100:VERSION_-+A2)
PARAM ENV VERSION: v1.0..
set_charger_current: chg curr(3f), in curr(17)
set_charger_state: buck(1), chg(1), reg(0x05)
microusb_get_attached_device: STATUS1:0x3d, 2:0x00
set_auto_current: ta_state(0), curr(1800)
init_fuelgauge: fuelgauge power ok
init_fuelgauge: POR status
fuelgauge_por: POR start: vcell(4247), vfocv(4310), soc(115)
fuelgauge_por: update SDI T0 parameter
fuelgauge_por: RCOMP(0x0040), TEMPCO(0x0a1b)
fuelgauge_por: POR finish: vcell(4251), vfocv(4516), soc(99)
get_table_soc: vcell(4250) is caculated to t-soc(99.50)
init_fuelgauge: start: vcell(4250), vfocv(4503), soc(99), table soc(99)
init_fuelgauge: finish: vcell(4250), vfocv(4503), soc(99), table soc(99)
init_microusb_ic: MUIC: CONTROL1:0x1b
init_microusb_ic: MUIC: CONTROL1:0x1b
init_microusb_ic: MUIC: CONTROL2:0x3b
init_microusb_ic: MUIC: CONTROL2:0x3b
PMIC_ID = 0x02
PMIC_IRQSRC = 0x00
PMIC_IRQ1 = 0x02
PMIC_IRQ2 = 0x00
PMIC_IRQ1M = 0xc0
PMIC_IRQ2M = 0x03
PMIC_STATUS1 = 0x11
PMIC_STATUS2 = 0x00
PMIC_PWRON = 0x02
PMIC_RTCINT = 0x00
PMIC_RTCINTM = 0x3f
s5p_check_keypad: 0x11100000
s5p_check_reboot_mode: INFORM3 = 0 ... skip
s5p_check_upload: MAGIC(0xbc7689a1), RST_STAT(0x10000)
microusb_get_attached_device: STATUS1:0x3d, 2:0x00
s5p_check_download: 0
microusb_get_attached_device: STATUS1:0x3d, 2:0x00
check_pm_status: non chargable jig, bypass check power
ddi type = 1, S.LSI
cmu_div:6, div:2, src_clk:880000000, pixel_clk:62614944
s5p_dsim_display_config : VIDEO MODE
41, 16, a2,
<start_checksum:451>CHECKSUM_HEADER_SECTOR :4096
<start_checksum:453>offset:50, size:6296
<start_checksum:457>CHECKSUM_HEADER_INFO : NeedChecksum:0 PartNo:20
Not Need Movinand Checksum
Movinand Checksum Confirmation Pass
[mobi_drv] add: 0x43e50070, size: 3933
MobiCore INIT response = 0
MobiCore RTM has initialized!
MobiCore IDLE flag = 0
MobiCore driver address 43e50070, size = 3933
MobiCore RTM Notified back!
MobiCore Driver loaded and RTM IDLE!
MobiCore RTM has been uninitialized!
load_kernel: loading boot image from 106496..
pit_check_signature (BOOT) valid.
No need to update kernel type.

SMC Num = 0x83000001

mobismc success!!! [ret = 0]
[s5p_check_sboot_version_rpmb]cur_version:VERSION_-+A2, rpmb_version:VERSION_-+A2
rpmb_version:50, cur_version:50
ATAG_CORE: 5 54410001 0 0 0
ATAG_MEM: 4 54410002 20000000 40000000
ATAG_MEM: 4 54410002 20000000 60000000
ATAG_MEM: 4 54410002 20000000 80000000
ATAG_MEM: 4 54410002 1FC00000 A0000000
ATAG_SERIAL: 4 54410006 4df10c60 7c389f17
ATAG_INITRD2: 4 54420005 42000000 12fb2a
ATAG_REVISION: 3 54410007 b
ATAG_CMDLINE: 9b 54410009 'console=ram loglevel=4 androidboot.baseband=mdm sec_debug.level=0 sec_watchdog.sec_pet=5 androidboot.debug_level=0x4f4c sec_log=0x200000@0x46000000 sec_tima_log=0x200000@0x46202000 sec_avc_log=0x40000@0x46404000 s3cfb.bootloaderfb=0x5ec00000 lcdtype=1 consoleblank=0 lpcharge=0 lpj=3981312 vmalloc=176m oops=panic pmic_info=67 cordon=f8308b73e2763bb0c0635e376b9c4b9c connie=GT-N7100_OPEN_EUR_3b3e8c267f6eb119399bfda46cc5e865 androidboot.emmc_checksum=3 androidboot.odin_download=1 androidboot.bootloader=N7100XXUEMK9 androidboot.warranty_bit=1 androidboot.serialno=4df10c607c389f17 snd_soc_core.pmdown_time=1000'
ATAG_NONE: 0 0

Starting kernel at 0x40008000...

SWITCH_SEL(3)
Uncompressing Linux... done, booting the kernel.
N7100 was good for repair....now has stopped any flash type for PIT failed...
  Reply With Quote
Old 08-20-2015, 04:35   #89 (permalink)
No Life Poster
 
Join Date: Jan 2008
Posts: 1,171
Member: 683463
Status: Offline
Thanks Meter: 188
heres mine i cannot flash

Samsung S-Boot 4.0 for GT-N7100 (Dec 12 2014 - 20:47:46)

EXYNOS4412(EVT 2.0) / 2044MB / 0MB / Rev 11 / N7100XXUFNL1 /(PKG_ID 0x502c058)

BOOTLOADER VERSION : N7100XXUFNL1

PMIC rev = PASS2(4)
BUCK1OUT(vdd_mif) = 0x05
BUCK3DVS1(vdd_int) = 0x20
[MMC] response timeout error : 00000104 cmd 1, ret -19.
card_init: mmc CMD1 fail!
[mmc] mmc card init fail, ret = -29
card_init: mmc CMD1 fail!
[mmc] mmc card init fail, ret = -29
[MMC] response timeout error : 00000104 cmd 1, ret -19.
card_init: mmc CMD1 fail!
[mmc] mmc card init fail, ret = -29
card_init: mmc CMD1 fail!
[mmc] mmc card init fail, ret = -29
[MMC] response timeout error : 00000104 cmd 1, ret -19.
card_init: mmc CMD1 fail!
[mmc] mmc card init fail, ret = -29
[MMC] response timeout error : 00000104 cmd 1, ret -19.
card_init: mmc CMD1 fail!
[mmc] mmc card init fail, ret = -29
[MMC] response timeout error : 00000104 cmd 1, ret -19.
card_init: mmc CMD1 fail!

and it keep repeating this message
  Reply With Quote
Old 08-20-2015, 09:13   #90 (permalink)
No Life Poster
 
allumts's Avatar
 
Join Date: Apr 2011
Age: 58
Posts: 16,408
Member: 1564612
Status: Offline
Thanks Meter: 12,343
Donate money to this user
@yunaced, you emmc is damaged...or replace this or try to repair with New procedure from Atf via NAND TP to GND and direct emmc connection for format+update firmware..also is totally Dead can repair...with FREE tool any chanche

BR
allumts
  Reply With Quote
The Following User Says Thank You to allumts For This Useful Post:
Reply

Bookmarks


Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On


 



All times are GMT +1. The time now is 02:32.



Powered by Searchlight © 2024 Axivo Inc.
vBulletin Optimisation provided by vB Optimise (Pro) - vBulletin Mods & Addons Copyright © 2024 DragonByte Technologies Ltd.
- GSM Hosting Ltd. - 1999-2023 -
Page generated in 0.27514 seconds with 9 queries

SEO by vBSEO