S7562 MTK6575 flash file needed - Samsung Galaxy S Duos

please help me i need this file so urgent
Analysis of USB port,Please insert phone USB cable.
Connecting...
CPU TYPE:MT6575
Hardware version:CB00
Software version:E201
Boot downloading complete!
EMMC_ID:0x45010053454D303447900521989B5067
EMMC_PRODUCT_NAME: SAMSUNG :0x53454D303447
EMMC_BOOT1_SIZE: 0x00100000
EMMC_BOOT2_SIZE: 0x00100000
EMMC_PRMB_SIZE: 0x00020000
EMMC_GP1_SIZE: 0x00000000
EMMC_GP2_SIZE: 0x00000000
EMMC_GP3_SIZE: 0x00000000
EMMC_GP4_SIZE: 0x00000000
EMMC_USER_SIZE: 0x0EC000000(3.69 G)
Analysis of system files...
PRELOADER: addr:0x000000 --length:0x040000
DSP_BL: addr:0x040000 --length:0x5C0000
MBR: addr:0x600000 --length:0x004000
EBR1: addr:0x604000 --length:0x05C000
__NODL_PMT: addr:0x660000 --length:0x400000
__NODL_NVRAM: addr:0xA60000 --length:0x300000
__NODL_SECCFG: addr:0xD60000 --length:0x020000
UBOOT: addr:0xD80000 --length:0x060000
BOOTIMG: addr:0xDE0000 --length:0x600000
RECOVERY: addr:0x13E0000 --length:0x600000
SEC_RO: addr:0x19E0000 --length:0x600000
__NODL_MISC: addr:0x1FE0000 --length:0x060000
LOGO: addr:0x2040000 --length:0x300000
__NODL_EXPDB: addr:0x2340000 --length:0x0A0000
EBR2: addr:0x23E0000 --length:0x004000
ANDROID: addr:0x23E4000 --length:0x19000000
CACHE: addr:0x1B3E4000 --length:0x5000000
USRDATA: addr:0x203E4000 --length:0x74300000
__NODL_FAT: addr:0x946E4000 --length:0x000001
__NODL_BMTPOOL: addr:0xFFFF0050 --length:0x000000
Format addr:0x243E4000 --Format length:0x70300000
Read phone information success.
Click to expand...
Click to collapse

Related

[Q] Reboot due to kernel panic

Hello,
I've had a few reboots and debugging the problem, I've discovered this:
last_kmsg:
----
[90978.707145] mmc1: data txfr (0x00100000) error: -110 after 671 ms
[90978.707258] sdhci: =========== REGISTER DUMP (mmc1)===========
[90978.707300] sdhci: Sys addr: 0x80000008 | Version: 0x00003802
[90978.707373] sdhci: Blk size: 0x00007200 | Blk cnt: 0x00000008
[90978.707413] sdhci: Argument: 0x003f0a10 | Trn mode: 0x0000002b
[90978.707486] sdhci: Present: 0x01e80100 | Host ctl: 0x00000035
[90978.707526] sdhci: Power: 0x0000000b | Blk gap: 0x00000000
[90978.707598] sdhci: Wake-up: 0x00000000 | Clock: 0x00000007
[90978.707639] sdhci: Timeout: 0x0000000c | Int stat: 0x00000000
[90978.707680] sdhci: Int enab: 0x03ff800b | Sig enab: 0x03ff800b
[90978.707752] sdhci: AC12 err: 0x00000000 | Slot int: 0x00000000
[90978.707793] sdhci: Caps: 0x642dc8b2 | Caps_1: 0x00008007
[90978.707864] sdhci: Cmd: 0x0000193a | Max curr: 0x00000000
[90978.707905] sdhci: Resp 1: 0x00000000 | Resp 0: 0x00000900
[90978.707978] sdhci: Resp 3: 0x00000900 | Resp 2: 0x00000000
[90978.708017] sdhci: Host ctl2: 0x00000003
[90978.708057] sdhci: ADMA Err: 0x00000003 | ADMA Ptr: 0x35a40008
[90978.708128] mmc1: clk: 200000000 clk-gated: 0 claimer: mmcqd/1 pwr: 10
[90978.708199] mmc1: rpmstatus[pltfm](runtime-suspend:usage_count:disable_depth)(0:0:0)
[90978.708239] sdhci: ===========================================
[90978.712431] mmcblk0: error -110 transferring data, sector 4131344, nr 8, cmd response 0x900, card status 0x100c02
[90978.712514] end_request: I/O error, dev mmcblk0, sector 4131344
[90978.712559] end_request: I/O error, dev mmcblk0, sector 4131344
[90978.712667] Aborting journal on device mmcblk0p28-8.
[90978.713769] journal commit I/O error
[90978.714748] done.
---
---
[90979.265686] EXT4-fs error (device mmcblk0p28): ext4_journal_start_sb:328: Detected aborted journal
[90979.265968] EXT4-fs (mmcblk0p28): Remounting filesystem read-only
[90979.267079] Kernel panic - not syncing: EXT4-fs panic from previous error
[90979.267085]
[90979.267243] [<c010de1c>] (unwind_backtrace+0x0/0x144) from [<c09fd44c>] (dump_stack+0x20/0x24)
[90979.267385] [<c09fd44c>] (dump_stack+0x20/0x24) from [<c09fde5c>] (panic+0x9c/0x21c)
[90979.267526] [<c09fde5c>] (panic+0x9c/0x21c) from [<c030f298>] (__ext4_abort+0xe0/0xf4)
[90979.267668] [<c030f298>] (__ext4_abort+0xe0/0xf4) from [<c030f624>] (ext4_journal_start_sb+0xa0/0x1a4)
[90979.267757] [<c030f624>] (ext4_journal_start_sb+0xa0/0x1a4) from [<c02f7920>] (ext4_dirty_inode+0x24/0x50)
[90979.267905] [<c02f7920>] (ext4_dirty_inode+0x24/0x50) from [<c028c4ec>] (__mark_inode_dirty+0x3c/0x1e0)
[90979.268048] [<c028c4ec>] (__mark_inode_dirty+0x3c/0x1e0) from [<c02f5538>] (ext4_setattr+0xd0/0x414)
[90979.268192] [<c02f5538>] (ext4_setattr+0xd0/0x414) from [<c027e6a4>] (notify_change+0x198/0x2b8)
[90979.268336] [<c027e6a4>] (notify_change+0x198/0x2b8) from [<c0262264>] (chown_common+0x7c/0x94)
[90979.268477] [<c0262264>] (chown_common+0x7c/0x94) from [<c0262fd8>] (sys_fchown+0x74/0x98)
[90979.268563] [<c0262fd8>] (sys_fchown+0x74/0x98) from [<c0107300>] (ret_fast_syscall+0x0/0x30)
[90979.268701] CPU0: stopping
[90979.268752] [<c010de1c>] (unwind_backtrace+0x0/0x144) from [<c09fd44c>] (dump_stack+0x20/0x24)
[90979.268836] [<c09fd44c>] (dump_stack+0x20/0x24) from [<c010c890>] (handle_IPI+0x198/0x1cc)
[90979.268919] [<c010c890>] (handle_IPI+0x198/0x1cc) from [<c0100590>] (gic_handle_irq+0xb0/0xf4)
[90979.269003] [<c0100590>] (gic_handle_irq+0xb0/0xf4) from [<c0106f00>] (__irq_svc+0x40/0x70)
[90979.269047] Exception stack(0xed7add28 to 0xed7add70)
[90979.269121] dd20: 00000004 00000004 00000004 00000001 ed7addac c2401bc0
[90979.269164] dd40: c2401bc0 013d1000 c2401bc8 00000001 00000001 ed7add9c 00000002 ed7add70
[90979.269236] dd60: c011969c c01e02c0 20000113 ffffffff
[90979.269312] [<c0106f00>] (__irq_svc+0x40/0x70) from [<c01e02c0>] (generic_exec_single+0x7c/0xa0)
[90979.269358] [<c01e02c0>] (generic_exec_single+0x7c/0xa0) from [<c01e06f0>] (smp_call_function_single+0x10c/0x1e8)
[90979.269435] [<c01e06f0>] (smp_call_function_single+0x10c/0x1e8) from [<c01e0ca0>] (smp_call_function_many+0x248/0x298)
[90979.269511] [<c01e0ca0>] (smp_call_function_many+0x248/0x298) from [<c01e0d40>] (smp_call_function+0x50/0x7c)
[90979.269591] [<c01e0d40>] (smp_call_function+0x50/0x7c) from [<c070ac0c>] (cpuidle_latency_notify+0x28/0x30)
[90979.269670] [<c070ac0c>] (cpuidle_latency_notify+0x28/0x30) from [<c01b9df0>] (notifier_call_chain+0x54/0x94)
[90979.269748] [<c01b9df0>] (notifier_call_chain+0x54/0x94) from [<c01ba270>] (__blocking_notifier_call_chain+0x58/0x70)
[90979.269829] [<c01ba270>] (__blocking_notifier_call_chain+0x58/0x70) from [<c01ba2b0>] (blocking_notifier_call_chain+0x28/0x30)
[90979.269914] [<c01ba2b0>] (blocking_notifier_call_chain+0x28/0x30) from [<c01cfd28>] (pm_qos_update_target+0xf0/0x13c)
[90979.269996] [<c01cfd28>] (pm_qos_update_target+0xf0/0x13c) from [<c01cff74>] (pm_qos_update_request+0x64/0x94)
[90979.270080] [<c01cff74>] (pm_qos_update_request+0x64/0x94) from [<c0729bf0>] (sdhci_disable+0x58/0x5c)
[90979.270131] [<c0729bf0>] (sdhci_disable+0x58/0x5c) from [<c070daa0>] (mmc_release_host+0xb0/0xc8)
[90979.270181] [<c070daa0>] (mmc_release_host+0xb0/0xc8) from [<c0722c40>] (mmc_blk_issue_rq+0x298/0x7a4)
[90979.270262] [<c0722c40>] (mmc_blk_issue_rq+0x298/0x7a4) from [<c0723aec>] (mmc_queue_thread+0xb0/0x17c)
[90979.270348] [<c0723aec>] (mmc_queue_thread+0xb0/0x17c) from [<c01b3690>] (kthread+0x98/0xa4)
[90979.270434] [<c01b3690>] (kthread+0x98/0xa4) from [<c0107f60>] (kernel_thread_exit+0x0/0x8)
[90980.270823] Rebooting in 5 seconds..
[90985.272517] Going down for restart now
[90985.273319] Calling SCM to disable SPMI PMIC arbiter
No errors detected
Boot info:
Last boot reason: kernel_panic
---
As far as I can tell, the device has problems writing to flash memory and panics. Is there a way to assing "bad blocks" to certain parts of the flash to make sure the OS won't try to write there any more?
Any way to do a manual fsck?
I'm proficient in Linux, but haven't had much contact with ARM based embedded devices so far.
RMA it, your flash storage seems to have died.
ApTeM said:
RMA it, your flash storage seems to have died.
Click to expand...
Click to collapse
Did some research and managed to fsck the filesystems through adb shell. Also, using linaro kernel now. Haven't had any random reboots after this.
Might have been a problem with the FS or a kernel hickup. Who knows.
If the problem returns then I probably have no other options than to RMA it, yes.
The problem is that the phome was bought through UK Play store by my sister and I live in Estonia myself. So RMA is a bit problematic
I'm in a worse boat - my phone was bought in the US and I live in eastern Europe.
What's wrong with yours?
m3ph1570 said:
What's wrong with yours?
Click to expand...
Click to collapse
11 dead pixels.
m3ph1570 said:
Did some research and managed to fsck the filesystems through adb shell. Also, using linaro kernel now. Haven't had any random reboots after this.
Might have been a problem with the FS or a kernel hickup. Who knows.
If the problem returns then I probably have no other options than to RMA it, yes.
The problem is that the phome was bought through UK Play store by my sister and I live in Estonia myself. So RMA is a bit problematic
Click to expand...
Click to collapse
Could you expand on the part how you fixed it? Especially the fsck part
Thanks
tasubo said:
Could you expand on the part how you fixed it? Especially the fsck part
Thanks
Click to expand...
Click to collapse
https://en.wikipedia.org/wiki/Fsck
The utility is available in TWRP.
Wasn't really able to fix it. The storage on my phone has some bad sectors and I experience some random reboots still. Haven't figured out a way to mark those sectors bad manually.
Because of the random reboots, I can't encrypt my storage (password protected boot). It'd be stuck at the password prompt after every reboot in my pocket.
Hi I'm facing same problem as you, even with a similar kmsg bug report, were you able to fix it?

[Q] Reboot receving a call when charging - Klog

Hi, I have a problem with my phone, i dont know if is a hw or sw issue. When my phone is charging and i receive a call, rings for 2 or 3 seconds and then reboots. I tried many fw: .14, .17, cm11, and the behaviour is almost the same. (in .14 and .17 the phone suddenly shut down with no reason, in cm11 NOT ) I reach the klog and it seems to me a modem issue :S, please someone can give it a look and tell me, thanks in advance.
============================= KLog Information =============================
magic:FATALM003
prev_reboot_reason:FATALM
kernel_time:[000006EE.358A20E7]
first_rtc:[537A025A.1B89D3DE]
last_rtc:[537A0B5E.27AB99C4]
normal_boot:1
prev_normal_boot:1
klog_userdata_count:5
klog_internal_count:5
klog_external_count:5
system_on_off_state:0x10
sbl_bootup_time:0
aboot_bootup_time:0
android_bootup_time:0
android_shutdown_time:0
sysfs_sync_time:0
kernel_power_off_time:0
suspend_time:2335
resume_time:2870
android_version:4.2.2
modem_version:8930B-BAAAATAZQ-3228109-14-1014
flex_version:FF_SHP_SA77.0.1.1016
rpm_version:3.0.16842938
bootloader_version:1269-1300_S1_Boot_MSM_8X30_R1_25
linux_version:3.4.0-g74b701b-00054-gde56c65-dirty
version_id:15.3.A.1.17
build_version:SA77.0.1.1016
build_date:Wed Mar 26 00:50:55 CST 2014
build_type:user
build_user:cme
build_host:androidbs-desktop
build_key:release-keys
secure_mode:1
debug_mode:0
hw_id:7241
cpuinfo_max_freq:1026000
scaling_max_freq:1026000
sim_state:READY
============================= KLog Start =============================
KLog Category #0:
name:CRASH
size:8192
index:2290
overload:0
<2>[klog]fault_level=0x5, fault_type=-1, fault_msg=modem
<2>[klog]modem crash log:Error Crash Log Report. Version 3.
<2>
<2>Error in file: fws_task.c, line: 245
<2>Time of crash (m-d-y h:m:s): 05-19-2014 13:47:03
<2>Uptime (h:m:s): 0000:38:53
<2>Build ID: M8930B-AAAATAZM-3.2.28109
<2>REX_TCB ptr: 0x8cf18458
<2>tcb.task_name: IST 98
<2>Coredump ARCH type is: ERR_ARCH_QDSP6
<2>R0: 0x00000000
<2>R1: 0x8cee43f8
<2>R2: 0x00000000
<2>R3: 0x8ce28288
<2>R4: 0x000000fe
<2>R5: 0x06c0c5a0
<2>R6: 0x00000000
<2>R7: 0x00000001
<2>R8: 0xe353f7cf
<2>R9: 0x20c49ba5
<2>R10: 0xffdf7b00
<2>R11: 0x00000000
<2>R12: 0xffdf7b00
<2>R13: 0x0004afff
<2>R14: 0x8900cd98
<2>R15: 0x00000002
<2>R16: 0x8ad51378
<2>R17: 0x00000000
<2>R18: 0x00000000
<2>R19: 0x00000000
<2>R20: 0x89a76840
<2>R21: 0x00000000
<2>R22: 0x00000000
<2>R23: 0x00000000
<2>R24: 0x00000000
<2>R25: 0x00000000
<2>R26: 0x00000000
<2>R27: 0x00000000
<2>R28: 0x00000000
<2>SP: 0x8cf18d30
<2>FP: 0x8cf18d38
<2>LR: 0x89d6a88c
<2>PC: 0x895bab98
<2>
<3>modem subsystem failure reason: fws_task.c:245:Firmware generated fatal error..
<2>[klog]fault already exist:5, ignore:5
<2>[klog]klog_magic=FIQHNG###
<2>[klog]preset magic(warn-boot higher):magic=FATALM, state=1, buf=FATALM###
<2>[klog]new klog_magic:klog_magic=FATALM001, buf=FATALM001
<2>[klog]fault already exist:5, ignore:1
<0>Kernel panic - not syncing: subsys-restart: Resetting the SoC - modem crashed.
<2>[klog]klog_magic=FATALM001
<2>[klog]preset magic(warn-boot lower):magic=PANICA, state=2, buf=FATALM001
<2>[klog]new klog_magic:klog_magic=FATALM003, buf=FATALM003
<1>[<c0013e54>] (unwind_backtrace+0x0/0x11c) from [<c07fc2cc>] (panic+0x1c8/0x33c)
<1>[<c07fc2cc>] (panic+0x1c8/0x33c) from [<c005fd40>] (subsystem_restart_dev+0x29c/0x398)
<1>[<c005fd40>] (subsystem_restart_dev+0x29c/0x398) from [<c00369ac>] (notify_smsm_cb_clients_worker+0xa4/0x1c0)
<1>[<c00369ac>] (notify_smsm_cb_clients_worker+0xa4/0x1c0) from [<c009f4ec>] (process_one_work+0x280/0x488)
<1>[<c009f4ec>] (process_one_work+0x280/0x488) from [<c009f908>] (worker_thread+0x214/0x3b4)
<1>[<c009f908>] (worker_thread+0x214/0x3b4) from [<c00a3800>] (kthread+0x84/0x90)
<1>[<c00a3800>] (kthread+0x84/0x90) from [<c000eac8>] (kernel_thread_exit+0x0/0x8)
<3>wcnss_8960: crash shutdown : 0
<0>Rebooting in 5 seconds..
============================== KLog End ==============================
============================= KLog Start =============================
KLog Category #1:
name:APPSBL
size:6144
index:0
overload:0
<Empty>
============================== KLog End ==============================

somthing intresting help unbrick

[PWRAP] pwrap_init_preloader
[PWRAP] pwrap_init
[PWRAP] _pwrap_init_sidly [Read Test] pass,SIDLY=0 rdata=5AA5
[PWRAP] _pwrap_init_sidly [Read Test] pass,SIDLY=1 rdata=5AA5
[PWRAP] _pwrap_init_sidly [Read Test] pass,SIDLY=2 rdata=5AA5
[PWRAP] _pwrap_init_sidly [Read Test] pass,SIDLY=3 rdata=5AA5
[PMIC_WRAP]wrap_init pass,the return value=0.
pl pmic init start
pl pmic efuse start
pl pmic efuse BUCK trim
[0x1C8]=0xF802
[0x1CA]=0x807F
[0x20E]=0xE0
[0x260]=0xF0
[0x286]=0xF0
pl pmic efuse end
pl pmic en rst [0x126]=0x13
[0xE]=0x1
[0x540]=0xA0
Battery exist
[0xE]=0x1
[0x540]=0xA0
pl vm read [0x290]=0x50
pl vm set [0x290]=0x52
pl vm check [0x290]=0x52
pl pmic init done
[PLFM] Init I2C: OK(0)
[PLFM] Init PWRAP: OK(0)
[PLFM] Init PMIC: OK(0)
[PLFM] chip[CA00]
[I2C][PL] [i2c0 write] i2c transaction complate
[BLDR] Build Time: 20140218-141828
==== Dump RGU Reg ========
RGU MODE: 75
RGU LENGTH: FFE0
RGU STA: 40000000
RGU INTERVAL: FFF
RGU SWSYSRST: 0
==== Dump RGU Reg End ====
RGU: g_rgu_satus:2
mtk_wdt_mode_config mode value=35, tmp:22000030
PL RGU RST: ??
SW reset with bypass power key flag
Find bypass powerkey flag
mtk_wdt_mode_config mode value=70, tmp:22000071
kpd register for pmic set!
mt_usb_calibraion: input_reg = 0x0
mt_usb_calibraion: term_vref = 0x0, clkref = 0x0, vrt_vref = 0x0,
[RTC] bbpu = 0x5, con = 0x426
[RTC] irqsta = 0x0, pdn1 = 0x0, pdn2 = 0x201, spar0 = 0x40, spar1 = 0x800
[RTC] new_spare0 = 0x0, new_spare1 = 0x1, new_spare2 = 0x1, new_spare3 = 0x1
[RTC] bbpu = 0x5, con = 0x424
SW reset with bypass power key flag
SW reset with bypass power key flag
[PLFM] WDT reboot bypass power key!
p1 pmic read INT_RSV(bit7)[0x138][0x80]
[RTC] rtc_bbpu_power_on done
[SD0] Bus Width: 1
[SD0] SET_CLK(260kHz): SCLK(259kHz) MODE(0) DDR(0) DIV(193) DS(0) RS(0)
[SD0] Switch to High-Speed mode!
[SD0] SET_CLK(260kHz): SCLK(259kHz) MODE(2) DDR(1) DIV(96) DS(0) RS(0)
[SD0] Bus Width: 8
[SD0] Size: 3696 MB, Max.Speed: 52000 kHz, blklen(512), nblks(7569408), ro(0)
[SD0] Initialized
[SD0] SET_CLK(52000kHz): SCLK(50000kHz) MODE(2) DDR(1) DIV(0) DS(0) RS(0)
msdc_ett_offline_to_pl: size<2> m_id<0x90>
msdc <0> <HYNIX > <H4G1d>
msdc <1> <xxxxxx> <H4G1d>
msdc failed to find
*******EMMC_INFO*******
eMMC partition size(1 block = 512Bytes):
BOOT1:<4096> blocks
BOOT2:<4096> blocks
RPMB :<4096> blocks
GP1 :<0> blocks
GP2 :<0> blocks
GP3 :<0> blocks
GP4 :<0> blocks
USER :<7569408> blocks
*******EMMC_INFO*******
fw id len:1
found:1,i:1
[EMI] DDR2
[EMI] eMMC/NAND ID = 90,1,4A,48,34,47,31,64,4
[EMI] MDL number = 1
[MEM] 1066 MHZ
rank 0 coarse = 15
rank 0 fine = 48
10:| 0 0 1 1 1 0
opt_dle value:8
rank 1 coarse = 15
rank 1 fine = 48
10:| 0 0 1 1 1 0
opt_dle value:8
byte:0, (DQS,DQ)=(8,8)
byte:1, (DQS,DQ)=(8,A)
byte:2, (DQS,DQ)=(8,8)
byte:3, (DQS,DQ)=(8,A)
[EMI] DRAMC calibration passed
[EMI] DQSINCTL:50000
[MEM] complex R/W mem test pass
[PLFM] Init Boot Device: OK(0)
[ROM_INFO] 'v2','0x2700000','0x20000','0x46C0000','0x2C00'
[SEC_K] SML KEY AC = 0
[SEC_K] SBC_PUBK Found
[SEC] AES Legacy : 0
[SEC] SECCFG AC : 1
[SEC] read '0x2700000'
0x41,0x4E,0x44,0x5F,0x53,0x45,0x43,0x43,
[LIB] SecLib.a '20121226-155014'
[LIB] CFG read size '0x4000' '0x1860'
[LIB] Name = SOMC
[LIB] Config = 0x11, 0x11
0x31,0x41,0x35,0x35
0x6F679858
[LIB] HW DEC
0x49494949
[LIB] SEC CFG 'v3' exists
[LIB] Status = 0x43434343
[LIB] ty = 0 , ld = 0
[PART] Image with part header
[PART] name : LK
[PART] addr : FFFFFFFFh
[PART] size : 316772
[PART] magic: 58881688h
[PART] load "UBOOT" from 0x0000000003960200 (dev) to 0x81E00000 (mem) [SUCCESS]
[PART] load speed: 9374KB/s, 316772 bytes, 33ms
[LIB] HW DEC
[SECRO] secroimg '0x41414141'
[SECRO] secroimg '0x35353535'
[SECRO] factory mode enabled
[AUTHEN] rsa.N length = 1024 bytes
[AUTHEN] rsa.E length = 20 bytes
[LIB] Verify 'UBOOT'
0x43434343
[LIB] part load '0x3960000'
[AUTHEN] 0x53,0x53,0x53,0x53
[AUTHEN] verify signature ... pass
[LIB] Verify 'LOGO'
0x43434343
[LIB] part load '0x4D40000'
[AUTHEN] 0x53,0x53,0x53,0x53
[AUTHEN] verify signature ... failed, error is 7
[SECLIB_IMG_VERIFY] Signature Fail.
[LIB] Fail (0x0)
<ASSERT> sec_boot.c:line 181 0
[PLFM] preloader fatal error...
[PLFM] emergency download mode(timeout: 30s).
mtk_arch_reset at pre-loader!
this is console with serial interface
i will post picture with pin layaut
how to unbrick?
botioni said:
[PWRAP] pwrap_init_preloader
[PWRAP] pwrap_init
[PWRAP] _pwrap_init_sidly [Read Test] pass,SIDLY=0 rdata=5AA5
[PWRAP] _pwrap_init_sidly [Read Test] pass,SIDLY=1 rdata=5AA5
[PWRAP] _pwrap_init_sidly [Read Test] pass,SIDLY=2 rdata=5AA5
[PWRAP] _pwrap_init_sidly [Read Test] pass,SIDLY=3 rdata=5AA5
[PMIC_WRAP]wrap_init pass,the return value=0.
pl pmic init start
pl pmic efuse start
pl pmic efuse BUCK trim
[0x1C8]=0xF802
[0x1CA]=0x807F
[0x20E]=0xE0
[0x260]=0xF0
[0x286]=0xF0
pl pmic efuse end
pl pmic en rst [0x126]=0x13
[0xE]=0x1
[0x540]=0xA0
Battery exist
[0xE]=0x1
[0x540]=0xA0
pl vm read [0x290]=0x50
pl vm set [0x290]=0x52
pl vm check [0x290]=0x52
pl pmic init done
[PLFM] Init I2C: OK(0)
[PLFM] Init PWRAP: OK(0)
[PLFM] Init PMIC: OK(0)
[PLFM] chip[CA00]
[I2C][PL] [i2c0 write] i2c transaction complate
[BLDR] Build Time: 20140218-141828
==== Dump RGU Reg ========
RGU MODE: 75
RGU LENGTH: FFE0
RGU STA: 40000000
RGU INTERVAL: FFF
RGU SWSYSRST: 0
==== Dump RGU Reg End ====
RGU: g_rgu_satus:2
mtk_wdt_mode_config mode value=35, tmp:22000030
PL RGU RST: ??
SW reset with bypass power key flag
Find bypass powerkey flag
mtk_wdt_mode_config mode value=70, tmp:22000071
kpd register for pmic set!
mt_usb_calibraion: input_reg = 0x0
mt_usb_calibraion: term_vref = 0x0, clkref = 0x0, vrt_vref = 0x0,
[RTC] bbpu = 0x5, con = 0x426
[RTC] irqsta = 0x0, pdn1 = 0x0, pdn2 = 0x201, spar0 = 0x40, spar1 = 0x800
[RTC] new_spare0 = 0x0, new_spare1 = 0x1, new_spare2 = 0x1, new_spare3 = 0x1
[RTC] bbpu = 0x5, con = 0x424
SW reset with bypass power key flag
SW reset with bypass power key flag
[PLFM] WDT reboot bypass power key!
p1 pmic read INT_RSV(bit7)[0x138][0x80]
[RTC] rtc_bbpu_power_on done
[SD0] Bus Width: 1
[SD0] SET_CLK(260kHz): SCLK(259kHz) MODE(0) DDR(0) DIV(193) DS(0) RS(0)
[SD0] Switch to High-Speed mode!
[SD0] SET_CLK(260kHz): SCLK(259kHz) MODE(2) DDR(1) DIV(96) DS(0) RS(0)
[SD0] Bus Width: 8
[SD0] Size: 3696 MB, Max.Speed: 52000 kHz, blklen(512), nblks(7569408), ro(0)
[SD0] Initialized
[SD0] SET_CLK(52000kHz): SCLK(50000kHz) MODE(2) DDR(1) DIV(0) DS(0) RS(0)
msdc_ett_offline_to_pl: size<2> m_id<0x90>
msdc <0> <HYNIX > <H4G1d>
msdc <1> <xxxxxx> <H4G1d>
msdc failed to find
*******EMMC_INFO*******
eMMC partition size(1 block = 512Bytes):
BOOT1:<4096> blocks
BOOT2:<4096> blocks
RPMB :<4096> blocks
GP1 :<0> blocks
GP2 :<0> blocks
GP3 :<0> blocks
GP4 :<0> blocks
USER :<7569408> blocks
*******EMMC_INFO*******
fw id len:1
found:1,i:1
[EMI] DDR2
[EMI] eMMC/NAND ID = 90,1,4A,48,34,47,31,64,4
[EMI] MDL number = 1
[MEM] 1066 MHZ
rank 0 coarse = 15
rank 0 fine = 48
10:| 0 0 1 1 1 0
opt_dle value:8
rank 1 coarse = 15
rank 1 fine = 48
10:| 0 0 1 1 1 0
opt_dle value:8
byte:0, (DQS,DQ)=(8,8)
byte:1, (DQS,DQ)=(8,A)
byte:2, (DQS,DQ)=(8,8)
byte:3, (DQS,DQ)=(8,A)
[EMI] DRAMC calibration passed
[EMI] DQSINCTL:50000
[MEM] complex R/W mem test pass
[PLFM] Init Boot Device: OK(0)
[ROM_INFO] 'v2','0x2700000','0x20000','0x46C0000','0x2C00'
[SEC_K] SML KEY AC = 0
[SEC_K] SBC_PUBK Found
[SEC] AES Legacy : 0
[SEC] SECCFG AC : 1
[SEC] read '0x2700000'
0x41,0x4E,0x44,0x5F,0x53,0x45,0x43,0x43,
[LIB] SecLib.a '20121226-155014'
[LIB] CFG read size '0x4000' '0x1860'
[LIB] Name = SOMC
[LIB] Config = 0x11, 0x11
0x31,0x41,0x35,0x35
0x6F679858
[LIB] HW DEC
0x49494949
[LIB] SEC CFG 'v3' exists
[LIB] Status = 0x43434343
[LIB] ty = 0 , ld = 0
[PART] Image with part header
[PART] name : LK
[PART] addr : FFFFFFFFh
[PART] size : 316772
[PART] magic: 58881688h
[PART] load "UBOOT" from 0x0000000003960200 (dev) to 0x81E00000 (mem) [SUCCESS]
[PART] load speed: 9374KB/s, 316772 bytes, 33ms
[LIB] HW DEC
[SECRO] secroimg '0x41414141'
[SECRO] secroimg '0x35353535'
[SECRO] factory mode enabled
[AUTHEN] rsa.N length = 1024 bytes
[AUTHEN] rsa.E length = 20 bytes
[LIB] Verify 'UBOOT'
0x43434343
[LIB] part load '0x3960000'
[AUTHEN] 0x53,0x53,0x53,0x53
[AUTHEN] verify signature ... pass
[LIB] Verify 'LOGO'
0x43434343
[LIB] part load '0x4D40000'
[AUTHEN] 0x53,0x53,0x53,0x53
[AUTHEN] verify signature ... failed, error is 7
[SECLIB_IMG_VERIFY] Signature Fail.
[LIB] Fail (0x0)
<ASSERT> sec_boot.c:line 181 0
[PLFM] preloader fatal error...
[PLFM] emergency download mode(timeout: 30s).
mtk_arch_reset at pre-loader!
this is console with serial interface
i will post picture with pin layaut
Click to expand...
Click to collapse
how did you check this out?
theonecallednick said:
how did you check this out?
Click to expand...
Click to collapse
I found uart pin on mainboard for debuging .
with serial usb cable pl2303
This is the red light only and unknown hardware found (the unknown hardware is in fact mtk usb vcom driver buth sony version ) if you try sp flash tool for mtk then it comunicates with de phone buth it needs some authentication file.
Help..
I am also having same problem..I falshed wrong rom..
It just shows red led and does not detects by PC...
Were you able to solve the problem..if yes..please help..
botioni said:
[PWRAP] pwrap_init_preloader
[PWRAP] pwrap_init
[PWRAP] _pwrap_init_sidly [Read Test] pass,SIDLY=0 rdata=5AA5
.........................
this is console with serial interface
i will post picture with pin layaut
Click to expand...
Click to collapse
Samuel Wankhede said:
I am also having same problem..I falshed wrong rom..
It just shows red led and does not detects by PC...
Were you able to solve the problem..if yes..please help..
Click to expand...
Click to collapse
Try the guide given in thread linked below
http://forum.xda-developers.com/showpost.php?p=57614511&postcount=13
Please share uart pinout
Baudrate should be 115200??
Thanks
uart
please share the uart pinout , thanks

HELP!!!!! I NEED TO REINsTALL LINUX ON A TV BOX

Hello all ,
I linked a serial cable to my allwinner a20 based Android Tv box.
It can not pass after the boot logo and next is all what it display in serial console.
Somebody pelase help i need to reisntall linux on it ,if you knwo any u boot keys that i have to press on the uboot serial consoel pelase help.I tryed to press ransom keys but i see nothin.
Here is all i see when it start:
====================================
HELLO! BOOT0 is starting!
boot0 version : 3.0.0
dram size =512
sum=0x9c3bd8cf
src_sum=0x9c3bd8cf
Ready to disable icache.
Jump to secend Boot.
[ 0.133]
U-Boot 2011.09-rc1-dirty (Nov 08 2013 - 11:06:32) Allwinner Technology
[ 0.141]version: 1.1.0
[ 0.144]pmbus: ready
axp read error
probe axp20x failed
axp_probe error
boot_clock = 912
dcdc2_vol = 1400
axp set dcdc2_vol to 1400 failed
dcdc3_vol = 1250
ldo2_vol = 3000
ldo3_vol = 2800
ldo4_vol = 2800
power_start = 0
storage_type = -1
usb_recovery = 0
find power_sply to end
fel key old mode
run key detect
no key found
no key input
dram_para_set start
dram_para_set end
[ 0.293]DRAM: 512 MiB
relocation Offset is: 15b27000
user_gpio config
user_gpio ok
DRV_DISP_Init: opened
[ 0.560]boot_disp.output_type=2
[ 0.563]boot_disp.output_mode=5
[ 0.567]boot_disp.auto_hpd=1
workmode = 0
[ 1.871]NAND: NAND_UbootInit
NB1 : enter NAND_LogicInit
nand : get id_number_ctl from script, 3
not burn nand partition table!
NB1 : nftl num: 3
init nftl: 0
NB1 : NAND_LogicInit ok, result = 0x0
[ 2.381]sunxi flash init ok
In: serial
Out: serial
Err: serial
--------fastboot partitions--------
-total partitions:12-
-name- -start- -size-
bootloader : 1000000 1000000
env : 2000000 1000000
boot : 3000000 1000000
system : 4000000 20000000
recovery : 24000000 2000000
databk : 26000000 2000000
misc : 28000000 1000000
private : 29000000 1000000
sysrecovery : 2a000000 21000000
data : 4b000000 40000000
cache : 8b000000 17000000
UDISK : a2000000 0
-----------------------------------
base bootcmd=run setargs_nand boot_normal
bootcmd set setargs_nand
key 0
recovery key high 6, low 4
cant find fstbt value
Fastboot detected, will boot fastboot
to be run cmd=run setargs_nand boot_fastboot
the user data'magic is bad
WORK_MODE_BOOT
board_status_probe
sunxi_bmp_display
WORK_MODE_BOOT
[ 2.509]Hit any key to stop autoboot: 0
run usb fastboot
sunxi_fastboot_init
recv addr 0x41000000
send addr 0x582580a8
delay time 0
usb init ok
------------------------------------------------------------------
After this nothing .Please help me
After searching all google and reading documantation ,I contacted the box seller and he gied me the files i neeeded.
I used a image file named sun7i_A20v2.0_android_sugar-ref001_2014.09.04_TakenYBSJ.img and a windwos software to flash it via usb named PhoenixPacketV333
To flash teh device you muist hava a serial console to the box (veru easy to do if you have the cable ) ,and keep pushed the key 2
on serial consle (putty) while powering the device ,so it enter in fel mode ( something like recovery mode ,it accept usb connection) .Then oyu need a usb male to male cable to conect the android tv box usb port to the windows usb port ,and start flasing using the PhoenixPacketV333 software.
If somebody needs more help or files just write here I check daily .
have a nice day all!

Help A8 2018 A530F emmc file repair

Hello i have A8 2018 sm-a530f which has the emmc files corrupted , i need to revive and when i connect to the Easy Jtag Plus i get the error Partition info not found ,guide repair procedures and below is the log data
Setting interface to EasyJtag2/ISP
Setting bus width to 1 Bit
Setting frequence to 36 MHz
CMD Pullup Level: 445 mV
CMD Active Level: 1192 mV
EMMC Device Information :
EMMC CID: 150100424A5444345200523F424BB5A7
EMMC CSD: D02701320F5903FFF6DBFFEF8E40400D
EMMC Manufacture : SAMSUNG , EMMC NAME: BJTD4R , HEX: 424A544434xx , S/N: 523F42xx , rev. 0x00
EMMC Manufacture ID: 0x15 , OEM ID: 0x00 , Device Type: BGA (Discrete embedded) , Date: 11/2018
EMMC ROM 1 (Main User Data) Capacity: 29820 MB (000747C00000)
EMMC ROM 2/3 (Boot Partition 1/2) Capacity: 4096 KB (000000400000)
EMMC RPMB (Replay Protected Memory Block) Capacity: 16384 KB (000001000000) Counter: 0 , Response: Maybe not clean
EMMC Permanent Write Protection: No
EMMC Temporary Write Protection: No
Extended CSD Information :
Extended CSD rev: 1.8 (MMC 5.1)
Boot configuration [PARTITION_CONFIG]: 0x48 , Boot from: ROM2 (Boot partition 1)
Boot Bus Config: 0x01 , width 4bit
H/W Reset Function [RST_N_FUNCTION]: 0x01, RST_n signal is permanently enabled
Supported partition features [PARTITIONING_SUPPORT]: 0x07
Device supports partitioning features
Device can have enhanced technological features in partitions and user data area
Device can have extended partitions attribute
Partition Settings [PARTITION_SETTING_COMPLETED]: 0x00
Backup saved: BJTD4R_523F424B_20210404_201644.extcsd
EMMC Init completed.
Scanning soft partitions
Partition table not found
Get firmware version
Firmware info not found
NOTE: I HAVE THE BACK UP FILE BUT I DO NOT KNOW WHICH FILES TO LOAD , MAY SOMEONE CHECK THE ATTACHMENT AND TELL ME WHICH FILES TO LOAD LIKE (Select eMMC Image file *.bin) from THIS BACK UP.MAY SOMEONE TELL ME FROM THE BACK UP WHICH ONE IS ( eMMC ROM1 Image file, eMMC ROM2 Image file, eMMC ROM3 Image file, eMMC GP1 Image file, eMMC ExtCSD file. IN THEIR ORDER.
gruka said:
Hello i have A8 2018 sm-a530f which has the emmc files corrupted , i need to revive and when i connect to the Easy Jtag Plus i get the error Partition info not found ,guide repair procedures and below is the log data
Setting interface to EasyJtag2/ISP
Setting bus width to 1 Bit
Setting frequence to 36 MHz
CMD Pullup Level: 445 mV
CMD Active Level: 1192 mV
EMMC Device Information :
EMMC CID: 150100424A5444345200523F424BB5A7
EMMC CSD: D02701320F5903FFF6DBFFEF8E40400D
EMMC Manufacture : SAMSUNG , EMMC NAME: BJTD4R , HEX: 424A544434xx , S/N: 523F42xx , rev. 0x00
EMMC Manufacture ID: 0x15 , OEM ID: 0x00 , Device Type: BGA (Discrete embedded) , Date: 11/2018
EMMC ROM 1 (Main User Data) Capacity: 29820 MB (000747C00000)
EMMC ROM 2/3 (Boot Partition 1/2) Capacity: 4096 KB (000000400000)
EMMC RPMB (Replay Protected Memory Block) Capacity: 16384 KB (000001000000) Counter: 0 , Response: Maybe not clean
EMMC Permanent Write Protection: No
EMMC Temporary Write Protection: No
Extended CSD Information :
Extended CSD rev: 1.8 (MMC 5.1)
Boot configuration [PARTITION_CONFIG]: 0x48 , Boot from: ROM2 (Boot partition 1)
Boot Bus Config: 0x01 , width 4bit
H/W Reset Function [RST_N_FUNCTION]: 0x01, RST_n signal is permanently enabled
Supported partition features [PARTITIONING_SUPPORT]: 0x07
Device supports partitioning features
Device can have enhanced technological features in partitions and user data area
Device can have extended partitions attribute
Partition Settings [PARTITION_SETTING_COMPLETED]: 0x00
Backup saved: BJTD4R_523F424B_20210404_201644.extcsd
EMMC Init completed.
Scanning soft partitions
Partition table not found
Get firmware version
Firmware info not found
NOTE: I HAVE THE BACK UP FILE BUT I DO NOT KNOW WHICH FILES TO LOAD , MAY SOMEONE CHECK THE ATTACHMENT AND TELL ME WHICH FILES TO LOAD LIKE (Select eMMC Image file *.bin) from THIS BACK UP.MAY SOMEONE TELL ME FROM THE BACK UP WHICH ONE IS ( eMMC ROM1 Image file, eMMC ROM2 Image file, eMMC ROM3 Image file, eMMC GP1 Image file, eMMC ExtCSD file. IN THEIR ORDER.
Click to expand...
Click to collapse
I think there are not many users who are able to help in your case.
I only found this thread about emmc repair for your device:
Samsung A520f ,A530f Dead boot repair direct emmc file download
gsm flash,gsm flash file,gsm crack,combine file,easy firmware,frp file,gsm firmware,gsm file,samsung firmware,samsung dump,all android flashing tool,
www.awaismobile.com
Yes i downloaded the file ,how do i know this file is rom 1 ,Rom2,Rom 3, and ex PLEASE I DENTIFY FOR ME

Categories

Resources