Related
Hi,
a couple times a week my phone seems to freeze when I push the powerbutton. The hardware buttons light up, but the screen remains black. I always have to pull the battery, after that it works again.
I finally was near a pc when it happened and managed to make a dmesg log. This was taken while the phone wasn't responding. I just plugged it in and used adb to get a log. Here's the interesting part (at least I think it is):
Code:
<6>[ 5433.007232] bravo_ts_power: power 0
<7>[ 5433.007507] __capella_cm3602_power: Turn the capella_cm3602 power off
<6>[ 5433.008026] lcdc_suspend: suspending
<6>[ 5433.008331] [R] early_suspend: sync
<6>[ 5433.033782] active wake lock PowerManagerService
<6>[ 5433.033905] active wake lock SMD_DATA5, time left 21
<6>[ 5433.034149] active wake lock SMD_DS, time left 41
<6>[ 5433.034332] [R] early_suspend end
<3>[ 5438.615905] mmc1: Data CRC error
<3>[ 5438.616729] msmsdcc_data_err: opcode 0x00000019
<3>[ 5438.617156] msmsdcc_data_err: blksz 512, blocks 5
<3>[ 5438.618194] mmcblk0: error -84 transferring data, sector 1668966, nr 5, card status 0xf00
<3>[ 5438.620758] mmc1: Data timeout
<3>[ 5438.621612] end_request: I/O error, dev mmcblk0, sector 1668966
<3>[ 5438.622070] Buffer I/O error on device mmcblk0p1, logical block 1668965
<4>[ 5438.622833] lost page write due to I/O error on mmcblk0p1
<3>[ 5438.623291] end_request: I/O error, dev mmcblk0, sector 1668967
<3>[ 5438.624053] Buffer I/O error on device mmcblk0p1, logical block 1668966
<4>[ 5438.624511] lost page write due to I/O error on mmcblk0p1
<3>[ 5438.625305] end_request: I/O error, dev mmcblk0, sector 1668968
<3>[ 5438.625762] Buffer I/O error on device mmcblk0p1, logical block 1668967
<4>[ 5438.626525] lost page write due to I/O error on mmcblk0p1
<3>[ 5438.626983] end_request: I/O error, dev mmcblk0, sector 1668969
<3>[ 5438.627746] Buffer I/O error on device mmcblk0p1, logical block 1668968
<4>[ 5438.628173] lost page write due to I/O error on mmcblk0p1
<3>[ 5438.628967] end_request: I/O error, dev mmcblk0, sector 1668970
<3>[ 5438.629394] Buffer I/O error on device mmcblk0p1, logical block 1668969
<4>[ 5438.630187] lost page write due to I/O error on mmcblk0p1
<3>[ 5443.042205] mmcblk0: error -110 sending read/write command, response 0x920, card status 0x400900
<3>[ 5443.043090] mmc1: Data timeout
<3>[ 5443.043884] end_request: I/O error, dev mmcblk0, sector 1669055
<3>[ 5443.044311] Buffer I/O error on device mmcblk0p1, logical block 1669054
<4>[ 5443.045104] lost page write due to I/O error on mmcblk0p1
<3>[ 5443.045562] end_request: I/O error, dev mmcblk0, sector 1669056
<3>[ 5443.046325] Buffer I/O error on device mmcblk0p1, logical block 1669055
<4>[ 5443.046752] lost page write due to I/O error on mmcblk0p1
<3>[ 5443.047546] end_request: I/O error, dev mmcblk0, sector 1669057
<3>[ 5443.047973] Buffer I/O error on device mmcblk0p1, logical block 1669056
<4>[ 5443.048736] lost page write due to I/O error on mmcblk0p1
<3>[ 5443.049194] end_request: I/O error, dev mmcblk0, sector 1669058
<3>[ 5443.049987] Buffer I/O error on device mmcblk0p1, logical block 1669057
<4>[ 5443.050415] lost page write due to I/O error on mmcblk0p1
<3>[ 5443.051208] end_request: I/O error, dev mmcblk0, sector 1669059
<3>[ 5443.051635] end_request: I/O error, dev mmcblk0, sector 1669067
<3>[ 5443.052429] end_request: I/O error, dev mmcblk0, sector 1669075
<3>[ 5443.052856] end_request: I/O error, dev mmcblk0, sector 1669083
<3>[ 5443.053649] end_request: I/O error, dev mmcblk0, sector 1669091
<3>[ 5443.054077] end_request: I/O error, dev mmcblk0, sector 1669099
<3>[ 5443.054870] end_request: I/O error, dev mmcblk0, sector 1669107
<3>[ 5443.055664] end_request: I/O error, dev mmcblk0, sector 1669115
<3>[ 5443.056091] end_request: I/O error, dev mmcblk0, sector 1669123
<3>[ 5443.056884] end_request: I/O error, dev mmcblk0, sector 1669131
<3>[ 5443.057312] end_request: I/O error, dev mmcblk0, sector 1669139
<3>[ 5443.058105] end_request: I/O error, dev mmcblk0, sector 1669147
<3>[ 5443.058563] end_request: I/O error, dev mmcblk0, sector 1669155
<3>[ 5443.059326] end_request: I/O error, dev mmcblk0, sector 1669163
<3>[ 5443.059783] end_request: I/O error, dev mmcblk0, sector 1669171
<3>[ 5443.060546] end_request: I/O error, dev mmcblk0, sector 1669179
<3>[ 5443.066314] mmcblk0: error -110 sending read/write command, response 0x920, card status 0x400900
<3>[ 5443.067199] mmc1: Data timeout
<3>[ 5443.067626] end_request: I/O error, dev mmcblk0, sector 2112723
<3>[ 5443.068420] Buffer I/O error on device mmcblk0p1, logical block 2112722
<4>[ 5443.068847] lost page write due to I/O error on mmcblk0p1
<3>[ 5443.074676] mmcblk0: error -110 sending read/write command, response 0x920, card status 0x400900
<3>[ 5443.075653] mmc1: Data timeout
<3>[ 5443.076110] end_request: I/O error, dev mmcblk0, sector 2
<3>[ 5443.081573] mmcblk0: error -110 sending read/write command, response 0x920, card status 0x400900
<3>[ 5443.082427] mmc1: Data timeout
<3>[ 5443.082855] end_request: I/O error, dev mmcblk0, sector 833
<3>[ 5443.088745] mmcblk0: error -110 sending read/write command, response 0x920, card status 0x400900
<3>[ 5443.089599] mmc1: Data timeout
<3>[ 5443.090026] end_request: I/O error, dev mmcblk0, sector 15594
<3>[ 5443.483581] mmc1: Data CRC error
<3>[ 5443.484374] msmsdcc_data_err: opcode 0x00000011
<3>[ 5443.484802] msmsdcc_data_err: blksz 512, blocks 1
<3>[ 5443.485748] mmcblk0: error -84 transferring data, sector 833, nr 1, card status 0xb00
<3>[ 5443.486389] end_request: I/O error, dev mmcblk0, sector 833
<3>[ 5443.487609] FAT: FAT read failed (blocknr 832)
<3>[ 5443.488616] mmc1: DMA channel flushed (0x80000004)
<3>[ 5443.489410] Flush data: 0000c003 3b18e000 00000000 00400040 00050004 00004003
<6>[ 5480.704193] batt: 95%, 4030 mV, -119 mA (-215 avg), 23.6 C, 1275 mAh
<6>[ 5530.876739] batt: 95%, 4030 mV, -69 mA (-82 avg), 23.6 C, 1273 mAh
<6>[ 5563.668518] gpio_keys_scan_keys: key 1-74, 0 (94) changed to 1
<6>[ 5563.673858] request_suspend_state: wakeup (3->0) at 5555550724239 (2010-12-28 12:24:48.362411743 UTC)
<6>[ 5563.674713] [R] late_resume start
<6>[ 5563.675201] lcdc_resume: resuming
<6>[ 5563.675628] samsung_oled_panel_init: +()
<6>[ 5563.676788] samsung_oled_panel_init: -()
<6>[ 5563.677368] msmfb: ready, waiting for full update
<7>[ 5563.678131] __capella_cm3602_power: Turn the capella_cm3602 power on
<6>[ 5563.678955] bravo_ts_power: power 1
<6>[ 5563.680053] lightsensor_ioctl set value = 1
<6>[ 5563.680816] lightsensor_enable
After that I reformatted my SDcard, wiped everything and did a fresh install of CM instead of Oxygen RC4 which I was using before.
Today I was downloading a few apps from the market, when suddenly the downloads disappeared from the notification bar. I used quick system info to look at the logs (again only a small part, i still have the rest if the full log contains more useful information):
Code:
<3> [23578.803039] : mmc1: Data CRC error
<3> [23578.803466] : msmsdcc_data_err: opcode 0x00000019
<3> [23578.804229] : msmsdcc_data_err: blksz 512, blocks 49
<3> [23578.804657] : mmc1: DMA channel flushed (0x80000004)
<3> [23578.805084] : Flush data: 0000c003 3b252030 00000000 00400040 00170015 00008003
<3> [23578.810241] : mmcblk0: error -84 transferring data, sector 2556870, nr 49, card status 0x900
<3> [23578.811096] : mmc1: Data timeout
<3> [23578.811889] : end_request: I/O error, dev mmcblk0, sector 2556870
<3> [23578.812652] : end_request: I/O error, dev mmcblk0, sector 2556878
<3> [23578.813079] : end_request: I/O error, dev mmcblk0, sector 2556886
<3> [23578.813812] : end_request: I/O error, dev mmcblk0, sector 2556894
<3> [23578.814209] : end_request: I/O error, dev mmcblk0, sector 2556902
<3> [23578.814972] : end_request: I/O error, dev mmcblk0, sector 2556910
<3> [23578.815368] : end_request: I/O error, dev mmcblk0, sector 2556918
<3> [23578.821869] : mmcblk0: error -110 sending read/write command, response 0x920, card status 0x400900
<3> [23578.823883] : mmc1: Data timeout
<3> [23578.824524] : end_request: I/O error, dev mmcblk0, sector 2556934
<3> [23578.830535] : mmcblk0: error -110 sending read/write command, response 0x920, card status 0x400900
<3> [23578.832946] : mmc1: Data timeout
<3> [23578.833801] : end_request: I/O error, dev mmcblk0, sector 2049
<3> [23578.834564] : Buffer I/O error on device mmcblk0p1, logical block 1
<4> [23578.834991] : lost page write due to I/O error on mmcblk0p1
<3> [23578.844360] : mmcblk0: error -110 sending read/write command, response 0x920, card status 0x400900
<3> [23578.844635] : mmc1: Data timeout
<3> [23578.844757] : end_request: I/O error, dev mmcblk0, sector 4515
<3> [23578.844879] : Buffer I/O error on device mmcblk0p1, logical block 2467
<4> [23578.845092] : lost page write due to I/O error on mmcblk0p1
<3> [23579.089599] : mmc1: Data CRC error
<3> [23579.090057] : msmsdcc_data_err: opcode 0x00000011
<3> [23579.090454] : msmsdcc_data_err: blksz 512, blocks 1
<3> [23579.091919] : mmcblk0: error -84 transferring data, sector 4515, nr 1, card status 0xb00
<3> [23579.092315] : end_request: I/O error, dev mmcblk0, sector 4515
<3> [23579.093231] : FAT: FAT read failed (blocknr 2467)
<3> [23579.098968] : mmcblk0: error -110 sending read/write command, response 0xb00, card status 0x400b00
<3> [23579.105072] : end_request: I/O error, dev mmcblk0, sector 63598
<3> [23579.105529] : Buffer I/O error on device mmcblk0p1, logical block 61550
<4> [23579.105926] : lost page write due to I/O error on mmcblk0p1
<3> [23579.582916] : FAT: Filesystem error (dev mmcblk0p1)
<3> [23579.583038] : fat_get_cluster: invalid cluster chain (i_pos 984821)
<3> [23579.583465] : FAT: Filesystem has been set read-only
<6> [23585.658355] : wake lock SMD_DATA5, expired
<7> [23585.663910] : save exit: isCheckpointed 1
<6> [23585.666900] : suspend: enter suspend
<6> [23585.667297] : PM: Syncing filesystems ... done.
<4> [23585.670532] : Freezing user space processes ... (elapsed 0.02 seconds) done.
<4> [23585.699371] : Freezing remaining freezable tasks ... (elapsed 0.01 seconds) done.
<6> [23585.749786] : PM: suspend of devices complete after 28.841 msecs
<6> [23585.750854] : power_suspend_late return 0
<6> [23585.751281] : PM: late suspend of devices complete after 1.036 msecs
<6> [23585.751281] : clocks on: uart_clk
<6> [23585.751281] : [R] suspend end
<6> [23585.751281] : [R] resume start
<6> [23585.751678] : PM: early resume of devices complete after 0.396 msecs
<6> [23585.757965] : wakeup wake lock: SMD_RPCCALL
<6> [23585.764862] : PM: resume of devices complete after 12.439 msecs
<4> [23585.766082] : Restarting tasks ... done.
<6> [23585.783905] : suspend: exit suspend, ret = 0 (2010-12-29 13:37:55.798841765 UTC)
<6> [23585.784912] : active wake lock ds2784-battery
<6> [23585.785339] : suspend: abort suspend
Could the freeze be the result of having apps installed on the SD when the error occurred?
The strange thing is that I got a new SD card for Christmas, and I have had (seemingly) the same freezes before. I never managed to get a log before, since i was never near a computer.
I already tried reformatting the card a few times, but that didn't seem to help.
Does anybody know a solution? Is it SD card related, or can it be caused by something else entirely?
Thanks
Does anyone have know if this is a problem with my SD card?
I find it odd that I also had the lockscreen freezing on my other SD card, I don't have it with me at the moment, so I can't compare the logs.
Is it also possible that the internal memory is corrupt? (Which would be a lot worse i guess )
Are you overclocking? If your min cpu speed is lower that 245mhz sometimes you get issues with the device waking.
Sent from my HTC Desire using Tapatalk
No, I'm not over/underclocking.
The second log was taken after several failed downloads of updates from the market. It showed the exact same error as the one were the lockscreen froze, but the phone functioned normally. Except for the downloads that failed of course.
I think the freezing is the result of an app or essential file on the SD card that can't be reached. Is that possible?
I have the same problem with the screen not waking. Did you find a solution?
Exact same problem..!!
Hey,
I have the exact same problem! I'm running a mildwild rom, with cm7r2 hboot, and 4ext recovery.. everything should be OK, but it's not..
I also think that it's the SD card that's dying.. gonna buy a new one tomorrow, and see if the problem goes away.. I'll post here, as soon as I find something out..!
- H
Is it a class 10 card? Also, maybe the I/O schedule may cause it.
What settings do u have set for it?
SaySayonara said:
Is it a class 10 card? Also, maybe the I/O schedule may cause it.
What settings do u have set for it?
Click to expand...
Click to collapse
Hey,
No I don't think it is.. but I don't think that should matter much, since I just got this phone, and had an old SD-card lying around.. so I rooted it, partitioned it, etc., but these malfunctions appeared almost immediately.. and I'm pretty sure the SD was OK when I put it in.. isn't class 10 usually only recommended for demanding a2sd setup-ups, that run over long periods of time..? I find it extremly suspicious that an SD card, even below class 6, would almost instantaneously die upon being put into use.. ?
However, now I've played around with it some more, and I'm almost certain now that it's the SD card that has gone broken.. because if I clear the data and cache of both google play and google framework services apks, and then boot into recovery and choose "tools" --> "check filesystem" --> sdcard --> repair sdcard (it doesn't work EVERY time, which also makes me suspect the Sd card...!!!!) , and then reboot, the SD card will work -- for a while... Like, I'll install 5-7 apps from google play, and then the same s**t all over again..
Gonna try it out with the same setup, but a brand new class 10 SD tomorrow, and report back..!
- H
I bought Sandisk Extreme 32GB
What partitioning tool did u use? I've seen many ppl saying that 4ext is the best. To be Frank I never had any issues with it.
SaySayonara said:
I bought Sandisk Extreme 32GB
What partitioning tool did u use? I've seen many ppl saying that 4ext is the best. To be Frank I never had any issues with it.
Click to expand...
Click to collapse
Yeah, I also used 4ext.. worked like a charm!
HAhaha, LOL - I was just looking at what card I'm gonna get tomorrow, and it looks like it's gonna be the same as yours..!!
- H
You're in for a treat my friend
I was very surprised by the difference.
All right!
The mystery is solved! Just tested it out with a new SanDisk class 10 16GB SD card.. everything works just fine.. partitioned it in 4ext, installed MildWild AOSP GB rom, installed a s**tload of apps, and everything works just fine.. the a2sd script is working as it should, both the rom install and apps install went smoothly. Besides changing the SD card, I changed nothing; same HBOOT, same 4ext, same everything.. So I guess it was the SD card that was fu***n things up..!
Cheers everybody!
- H
Hello, guys!
This morning I found my phone with black screen and not responding to power button. I pulled the battery out and tried to boot. The phone only showed the "Google" text on the black screen for several minutes (five, may be ten minutes) and did not respond to any buttons. At this point I pulled the battery for the second time and tried the recovery mode. The stock recovery booted after about a minute of "Google" screen. In stock recovery the only option I tried first time was "Wipe cache". It showed a static image of "work-in-progress" with static progress bar for several seconds and then returned to main recovery screen. I tried the "reboot" and received the black screen with no buttons working.
Pulled the battery and tried normal boot, which stuck on black "Google" stage.
Ok, I connected the phone to my laptop, and booted TWRP via fastboot, it took a little longer to boot, but at least I managed to "adb-shell" it and grab dmesg output. This is the relevant part (containing "mmc" word):
Code:
<6>[ 2.828399] mmc0: new high speed MMC card at address 0001
...
<6>[ 2.829101] mmcblk0: mmc0:0001 VYL00M 14.6 GiB
<6>[ 2.829345] mmcblk0boot0: mmc0:0001 VYL00M partition 1 512 KiB
<6>[ 2.829681] mmcblk0boot1: mmc0:0001 VYL00M partition 2 512 KiB
<6>[ 2.835021] Reprogramming LPDDR2 timings to 400000000 Hz
<3>[ 2.836090] Power Management for TI OMAP4.
<6>[ 2.836334] OMAP4 PM: Static dependency added between MPUSS and DUCATI <-> L4_PER/CFG and L3_1.
<6>[ 2.836517] mmcblk0: p1 p2 p3 p4 p5 p6 p7 p8 p9 p10 p11 p12 p13
<4>[ 2.837432] sr_init: No PMIC hook to init smartreflex
<6>[ 2.837799] smartreflex smartreflex.0: omap_sr_probe: SmartReflex driver initialized
<6>[ 2.838073] smartreflex smartreflex.1: omap_sr_probe: SmartReflex driver initialized
<6>[ 2.838317] smartreflex smartreflex.2: omap_sr_probe: SmartReflex driver initialized
<6>[ 2.838592] sr_class1p5_driver_init: OMAP4460: add 10mV margin for class 1.5
<6>[ 2.838928] SmartReflex class 1.5 driver: initialized (86400000ms)
<6>[ 2.839569] mmcblk0boot1: unknown partition table
<6>[ 2.840728] [MODEM_IF] PA EVENT : reset =0, pa=1
<6>[ 2.840972] mmcblk0boot0: unknown partition table
...
<4>[ 3.851135] mmc1: queuing unknown CIS tuple 0x80 (7 bytes)
<4>[ 3.899353] mmc1: queuing unknown CIS tuple 0x80 (3 bytes)
<6>[ 3.915679] mmc1: new high speed SDIO card at address 0001
<4>[ 3.917633] F1 signature read @0x18000000=0x16844330
<4>[ 3.927154] DHD: dongle ram size is set to 294912(orig 294912)
...
<3>[ 7.677093] mmcblk0: timed out sending r/w cmd command, card status 0xe00
<3>[ 7.677276] mmcblk0: not retrying timeout
<3>[ 7.677581] end_request: I/O error, dev mmcblk0, sector 1495040
<3>[ 7.677764] Buffer I/O error on device mmcblk0p11, logical block 0
<4>[ 7.678100] lost page write due to I/O error on mmcblk0p11
<6>[ 7.678802] EXT4-fs (mmcblk0p11): recovery complete
<6>[ 7.679138] EXT4-fs (mmcblk0p11): mounted filesystem with ordered data mode. Opts: (null)
<3>[ 8.737213] mmcblk0: timed out sending r/w cmd command, card status 0x400e00
<3>[ 8.737304] mmcblk0: command error, retrying timeout
<3>[ 8.737426] mmcblk0: timed out sending r/w cmd command, card status 0x400e00
<3>[ 8.737548] mmcblk0: command error, retrying timeout
<3>[ 8.737701] mmcblk0: timed out sending r/w cmd command, card status 0x400e00
<3>[ 8.737762] mmcblk0: command error, retrying timeout
<3>[ 8.737915] mmcblk0: timed out sending r/w cmd command, card status 0x400e00
...
and a lot of I/O errors with mmcblk0 block device
Reading from /dev/block/mmcblk0 constantly fails, even the first sectors (dd if=/dev/block/mmcblk0 of=/dev/null).
I pulled the battery out, left the phone and rushed to the work.
With my little knowledge it looks like broken sdcard itself or sdcard controller. Does it make any sense? Is it possible to repair it easily? I realize I cannot simply replace sdcard, as it most likely soldered in the board, but how hard is it to replace if I have the equipment and spare parts?
Another question: as I can boot TWRP recovery via fastboot, is it theoretically possible to find and boot a custom kernel, which does not require internal storage at all, like some stripped kernel which works only in RAM, but still provides the basic functions like phone calling, wifi browsing and something like this?
Any help would be greatly appreciated!
Try restoring your phone to stock using ODIN
http://forum.xda-developers.com/showthread.php?t=1827685
I think the PIT file should repair your partition table if it's just a software problem
Thanks for the tip. I guess I will try odin methods only as as a last resort since it may void my warranty. I am still positive about sending my unit to the service center in January.
At the moment fastboot methods do not work if they try to actually write something. fastboot boot works pretty good.
Looks like a bad partition, ODIN back to factory wont void your warranty. All it does is reset your phone to the stock image, that's probably what they'll do when you send it in for warranty repair. Save yourself the time and trouble.
Bad blocks is something software won't fix. This is a hardware problem with the flash memory and it needs replaced.
I had something like this happen when I was formatting my /data partition in TWRP. I did a factory reset and it was like "wiping /data without wiping /data/media" and just to be on the safe side I wiped /data and it froze and when I got control back it said that it couldn't format it or anything so I ended up restoring the factory image and that fixed everything.
varet tviengt
Once again, just to be on the safe side, I will not try ODIN factory reset just yet. As it may be the hardware problem and I may end up with phone-triangle-computer state, in which case my warranty might be rejected like I messed something up myself blah-blah-blah.
The problem with the warranty is that I should go to my home, and I am now several thousands kilometers away from it on a vacation. So I will just wait for it.
I'm having the exact same problems for the last few weeks. Did you fix it? If so, how?
Please read forum rules before posting
Questions and help issues go in Q&A
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
I have a GNexus 4.2.2 stock and I have reboot problem from the last week.
in the last_kmsg(attached) I read many references to mmc problems, for example
Code:
[ 5213.429595] mmcblk0: timed out sending r/w cmd command, card status 0x900
[ 5213.429779] mmcblk0: not retrying timeout
[ 5213.429901] end_request: I/O error, dev mmcblk0, sector 2450976
[ 5213.430084] end_request: I/O error, dev mmcblk0, sector 2450984
[ 5213.430175] end_request: I/O error, dev mmcblk0, sector 2450992
[ 5213.430328] end_request: I/O error, dev mmcblk0, sector 2451000
[ 5213.430450] end_request: I/O error, dev mmcblk0, sector 2451008
[ 5213.430603] end_request: I/O error, dev mmcblk0, sector 2451016
[ 5213.430694] end_request: I/O error, dev mmcblk0, sector 2451024
[ 5213.430847] end_request: I/O error, dev mmcblk0, sector 2451032
[ 5213.431091] Aborting journal on device mmcblk0p12-8.
I have already restore the Factory Images from Google developer, but I don't solve.
Is damage the memory or is a software problem?
up
Any news here? Since a few days I'm experiencing the same problem .
I have sane issue ! Any info for us ?
Inviato dal mio Galaxy Nexus usando Tapatalk 4
I am experiencing this problem too. Often apps crash when SQLite tries to write something to disk: Disk I/O error (code 1034).
I'm also getting random reboots and corrupted files.
This happens both with CM11-M2 and stock 4.3 ROM, so I don't think it's a software problem.
Do you think the internal storage is dying? Is there something I can do? Thanks!
I have had my refurbished HTC Vision for about three weeks and it hadn't had any problems. Then yesterday, I rebooted it and now the sdcard doesn't work. Not just that it doesn't mount, rather there is not even a /dev/block/mmcblk1 device.
Here is what I tried:
* Boot into ClockworkMod, and run adb shell. Still no /dev/block/mmcblk1.
* Boot into fastboot and run "fastboot oem enableqxdm 0" and "fastboot oem eraseconfig".
* Per some random instructions on the net, I held vol-up and power, then pulled the battery after the phone vibrated. Then I held vol-up, vol-down, power and did the same. Then the fastboot commands again.
* Bent the sdcard port's pins out a bit with tweezers.
* SDcard works in computer (Linux).
* Tried another card that has nothing but a vfat partition.
Nothing works! There are some errors in dmesg:
Code:
$ dmesg |grep mmc
<5>[ 0.000000] Kernel command line: board_vision.disable_uart2=0 board_vision.usb_h2w_sw=0 board_vision.disable_sdcard=0 diag.enabled=0 board_vision.debug_uart=0 smisize=0 userdata_sel=0 androidboot.emmc=true androidboot.baseband=26.02.01.15_M2 androidboot.cid=T-MOB010 androidboot.batt_poweron=good_battery androidboot.carrier=TMUS androidboot.mid=PC1010000 androidboot.keycaps=qwerty androidboot.mode=normal androidboot.serialno=HT09LR200858 androidboot.bootloader=0.76.2000 no_console_suspend=1 console=null
<6>[ 2.532989] vision: vision_init_mmc
<3>[ 3.267822] mmc0: No card detect facilities available
<6>[ 3.268341] mmc0: Qualcomm MSM SDCC at 0x00000000a0500000 irq 98,0 dma 7
<6>[ 3.268615] mmc0: Platform slot type: MMC
<6>[ 3.268737] mmc0: 4 bit data mode disabled
<6>[ 3.269012] mmc0: 8 bit data mode enabled
<6>[ 3.269134] mmc0: MMC clock 144000 -> 50000000 Hz, PCLK 96000000 Hz
<6>[ 3.269378] mmc0: Slot eject status = 0
<6>[ 3.269531] mmc0: Power save feature enable = 1
<6>[ 3.269653] mmc0: DM non-cached buffer at ffa0c000, dma_addr 0x2b774000
<6>[ 3.269927] mmc0: DM cmd busaddr 0x2b774000, cmdptr busaddr 0x2b774300
<6>[ 3.270751] mmc1: Qualcomm MSM SDCC at 0x00000000a3000000 irq 96,0 dma 8
<6>[ 3.270996] mmc1: Platform slot type: N/A
<6>[ 3.271148] mmc1: 4 bit data mode enabled
<6>[ 3.271392] mmc1: 8 bit data mode disabled
<6>[ 3.271514] mmc1: MMC clock 144000 -> 50000000 Hz, PCLK 96000000 Hz
<6>[ 3.271789] mmc1: Slot eject status = 1
<6>[ 3.271911] mmc1: Power save feature enable = 1
<6>[ 3.272064] mmc1: DM non-cached buffer at ffa0d000, dma_addr 0x2b777000
<6>[ 3.272308] mmc1: DM cmd busaddr 0x2b777000, cmdptr busaddr 0x2b777300
<6>[ 3.273468] mmc2: Qualcomm MSM SDCC at 0x00000000a3100000 irq 100,0 dma 8
<6>[ 3.273712] mmc2: Platform slot type: SD
<6>[ 3.273834] mmc2: 4 bit data mode enabled
<6>[ 3.273986] mmc2: 8 bit data mode disabled
<6>[ 3.274230] mmc2: MMC clock 144000 -> 50000000 Hz, PCLK 96000000 Hz
<6>[ 3.274353] mmc2: Slot eject status = 0
<6>[ 3.274658] mmc2: Power save feature enable = 1
<6>[ 3.274810] mmc2: DM non-cached buffer at ffa0e000, dma_addr 0x2b778000
<6>[ 3.275054] mmc2: DM cmd busaddr 0x2b778000, cmdptr busaddr 0x2b778300
<6>[ 3.275207] mmc2: Polling status mode enabled
<6>[ 3.425598] mmc0: new high speed MMC card at address 0001
<6>[ 3.427093] mmcblk0: mmc0:0001 SEM04G 2.09 GiB
<6>[ 3.428100] mmcblk0: p1 p2 p3 p4 < p5 p6 p7 p8 p9 p10 p11 p12 p13 p14 p15 p16 p17 p18 p19 p20 p21 p22 p23 p24 p25 p26 p27 p28 >
<6>[ 3.569030] EXT4-fs (mmcblk0p25): mounted filesystem with ordered data mode. Opts: barrier=1
<4>[ 3.703063] mmc2: high speed mode max_dtr = 50000000
<4>[ 3.703491] mmc2: host does not support reading read-only switch. assuming write-enable.
<6>[ 3.703643] mmc2: new high speed SDHC card at address 0001
<6>[ 3.704498] mmcblk1: mmc2:0001 00000 7.41 GiB
<6>[ 3.705291] mmcblk1: p1
<4>[ 4.648254] EXT4-fs (mmcblk0p26): warning: maximal mount count reached, running e2fsck is recommended
<7>[ 4.651062] EXT4-fs (mmcblk0p26): ext4_orphan_cleanup: deleting unreferenced inode 24790
<7>[ 4.655670] EXT4-fs (mmcblk0p26): ext4_orphan_cleanup: deleting unreferenced inode 24741
<6>[ 4.657012] EXT4-fs (mmcblk0p26): 2 orphan inodes deleted
<6>[ 4.657379] EXT4-fs (mmcblk0p26): recovery complete
<6>[ 4.703216] EXT4-fs (mmcblk0p26): mounted filesystem with ordered data mode. Opts: noauto_da_alloc
<4>[ 4.758331] EXT4-fs (mmcblk0p27): warning: maximal mount count reached, running e2fsck is recommended
<6>[ 4.760345] EXT4-fs (mmcblk0p27): recovery complete
<6>[ 4.762298] EXT4-fs (mmcblk0p27): mounted filesystem with ordered data mode. Opts: barrier=1
<4>[ 4.886474] EXT4-fs (mmcblk0p28): warning: maximal mount count reached, running e2fsck is recommended
<6>[ 4.888580] EXT4-fs (mmcblk0p28): recovery complete
<6>[ 4.890563] EXT4-fs (mmcblk0p28): mounted filesystem with ordered data mode. Opts: barrier=1
<7>[ 20.824981] mmc1: card_present 1
<6>[ 20.825134] mmc1: Slot status change detected (0 -> 1)
<7>[ 23.383300] mmc1: queuing CIS tuple 0x91 length 3
<6>[ 23.383331] mmc1: new high speed SDIO card at address 0001
<3>[ 38.746368] mmc2: Data CRC error
<6>[ 38.746978] mmc2: Controller has been reset
<3>[ 38.747467] mmcblk1: error -84 transferring data, sector 2080, nr 1, card status 0x900
<6>[ 38.747619] mmc2: reinit card
<4>[ 38.747863] mmc2: Starting deferred resume
<3>[ 38.814849] mmc2: Data CRC error
<6>[ 38.815521] mmc2: Controller has been reset
<3>[ 38.815856] mmc2: Re-init card rc = -84 (retries = 5)
<3>[ 38.997650] mmc2: Data CRC error
<6>[ 38.998291] mmc2: Controller has been reset
<3>[ 39.001403] mmc2: Re-init card rc = -84 (retries = 4)
<3>[ 39.200927] mmc2: Data CRC error
<6>[ 39.201507] mmc2: Controller has been reset
<3>[ 39.201721] mmc2: Re-init card rc = -84 (retries = 3)
<3>[ 39.384826] mmc2: Data CRC error
<6>[ 39.385406] mmc2: Controller has been reset
<3>[ 39.385650] mmc2: Re-init card rc = -84 (retries = 2)
<3>[ 39.583618] mmc2: Data CRC error
<6>[ 39.584228] mmc2: Controller has been reset
<3>[ 39.584472] mmc2: Re-init card rc = -84 (retries = 1)
<6>[ 39.666137] mmc2: Deferred resume failed
<6>[ 39.666412] mmc: reinit failed, remove card
<6>[ 39.666625] mmc2: remove card
<3>[ 39.666778] end_request: I/O error, dev mmcblk1, sector 2080
<3>[ 39.667053] Buffer I/O error on device mmcblk1p1, logical block 32
<4>[ 39.667205] lost page write due to I/O error on mmcblk1p1
<3>[ 39.667480] mmc_blk_issue_rq failed!!
<6>[ 39.667633] mmc2: mmc_remove_sd_card
<6>[ 39.667907] mmc2: card 0001 removed
<3>[ 39.670318] mmcblk1: error -123 sending status comand
<3>[ 39.670471] mmcblk1: error -123 sending read/write command, response 0x0, card status 0x0
<3>[ 39.670867] end_request: I/O error, dev mmcblk1, sector 2080
<3>[ 39.671783] mmc_blk_issue_rq failed!!
<3>[ 39.671966] mmcblk1: error -123 sending read command, response 0x0
<4>[ 39.672210] mmcblk1: retrying using single block read
<3>[ 39.672332] mmcblk1: error -123 sending status comand
<3>[ 39.672607] mmcblk1: error -123 sending read/write command, response 0x0, card status 0x0
<3>[ 39.672882] end_request: I/O error, dev mmcblk1, sector 32378
<3>[ 39.673126] end_request: I/O error, dev mmcblk1, sector 32379
<3>[ 39.673278] end_request: I/O error, dev mmcblk1, sector 32380
<3>[ 39.673522] end_request: I/O error, dev mmcblk1, sector 32381
<3>[ 39.673675] end_request: I/O error, dev mmcblk1, sector 32382
<3>[ 39.673919] end_request: I/O error, dev mmcblk1, sector 32383
<3>[ 39.674072] end_request: I/O error, dev mmcblk1, sector 32384
<3>[ 39.674316] end_request: I/O error, dev mmcblk1, sector 32385
<3>[ 39.674499] mmc_blk_issue_rq failed!!
<3>[ 39.674774] mmcblk1: error -123 sending status comand
<3>[ 39.674926] mmcblk1: error -123 sending read/write command, response 0x0, card status 0x0
<3>[ 39.675292] end_request: I/O error, dev mmcblk1, sector 32378
... and so on. In this run, I see that at least briefly the kernel could read the mmcblk1 partition table (although there still was not /dev/block/mmcblk1). However, most of the time it can't and just gives the CRC errors.
Is this a hardware or software problem. Any suggestions? Thanks.
Almost 100% hardware from what you have written, I would suggest disconnecting the ribbion cable, clean it, and put it back. If it still won't work a new sd card tray is about 10$ on ebay and a snap to put it
Sent from my HTC Vision using xda premium
worked!
demkantor said:
Almost 100% hardware from what you have written, I would suggest disconnecting the ribbion cable, clean it, and put it back. If it still won't work a new sd card tray is about 10$ on ebay and a snap to put it
Sent from my HTC Vision using xda premium
Click to expand...
Click to collapse
Worked, thanks!!! The CRC errors made me suspect hardware, but I wanted someone else to say it before I tore the thing open. I've always had bad luck tearing these things apart (only junk phones in the past), but I bought a cheapo disassembly kit a while back which has helped greatly with popping the case off. And thankfully I only had to get to about step three of the instructions before the ribbon cable was accessible!
Hi all,
I have a Galaxy Nexus with CyanogenMod 10.1 RC2.
Yesterday the battery discharged and the phone turned off.
When at home, I charged and booted it. Short after the phone turned on, it rebooted.
It continues to reboot a few seconds after I turn it on. I wiped everything, and I reinstalled Cyanogenmod, without any effect.
I tried to read the kmesg via ADB. It seems to be a filesysem corruption: pastebin.com/6J2NR4ne
The beginning of the errors is this:
Code:
<6>[ 56.475524] sr_class1p5_calib_work: iva: Calibration complete: Voltage:Nominal=950000,Calib=860920,margin=13000
<4>[ 66.156127] omap_hsi omap_hsi.0: Missed previous CAWAKE falling edge...
<3>[ 66.157775] mmcblk0: timed out sending r/w cmd command, card status 0x900
<3>[ 66.157958] mmcblk0: not retrying timeout
<3>[ 66.158111] end_request: I/O error, dev mmcblk0, sector 2398632
<3>[ 66.158233] end_request: I/O error, dev mmcblk0, sector 2398640
<3>[ 66.158416] end_request: I/O error, dev mmcblk0, sector 2398648
<3>[ 66.158630] end_request: I/O error, dev mmcblk0, sector 2398656
<3>[ 66.158782] Aborting journal on device mmcblk0p12-8.
<0>[ 66.164672] journal commit I/O error
<2>[ 66.170043] EXT4-fs error (device mmcblk0p12): ext4_journal_start_sb:296: Detected aborted journal
<2>[ 66.170715] EXT4-fs (mmcblk0p12): Remounting filesystem read-only
Can anyone help me?
I tried to run e2fsck on /dev/block/mmcblk0p12 while in recovery. It did not solve the problem.
Code:
~ # e2fsck /dev/block/mmcblk0p12
e2fsck 1.41.11 (14-Mar-2010)
/dev/block/mmcblk0p12: recovering journal
/dev/block/mmcblk0p12 contains a file system with errors, check forced.
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/block/mmcblk0p12: ***** FILE SYSTEM WAS MODIFIED *****
/dev/block/mmcblk0p12: 25726/887696 files (4.9% non-contiguous), 1129492/3549691 blocks
SOLVED.
Wiping the /data partition only deleted the files. I flashed userdata.img from the stock image (downloaded from google code), it rewrote /data and it worked
Please report the thread for closing.
Sent from my Nexus
Thread closed per OP's request.
Hi All,
Anybody could help me coz got a bit of problem here.
Rom: stock GB 2.3.5 I8150XXKI8
It seems that everything is read-only except the external SD. After reboot, revert back to previous state.
Unable to go to recovery mode.
Done many success flashing in download mode ( flash stock,recovery) though and nothing. it just revert back to the previous state
Reformat usb storage also does not work.
Alot of apps force close.
Long pause at the samsung w logo.
mmcblk0p17 and mmcblk0p27 seems to have an error from below dmesg output.
Needs to confirm with anyone.
Thanks.
<3>[ 3.161895] init: MOUNT NAME /dev/block/mmcblk0p15
<3>[ 3.161925] init: SEC_DEVENC ***[/dev/block/mmcblk0p15][0]
<6>[ 3.181334] EXT4-fs (mmcblk0p15): mounted filesystem with ordered data mode. Opts: barrier=1
<3>[ 3.181395] init: MOUNT NAME /dev/block/mmcblk0p12
<3>[ 3.181426] init: SEC_DEVENC ***[/dev/block/mmcblk0p12][0]
<6>[ 3.186003] EXT4-fs (mmcblk0p12): barriers disabled
<6>[ 3.202056] EXT4-fs (mmcblk0p12): recovery complete
<6>[ 3.202697] EXT4-fs (mmcblk0p12): mounted filesystem with ordered data mode. Opts: barrier=0
<3>[ 3.202758] init: MOUNT NAME /dev/block/mmcblk0p16
<3>[ 3.202758] init: SEC_DEVENC ***[/dev/block/mmcblk0p16][0]
<6>[ 3.205413] EXT4-fs (mmcblk0p16): barriers disabled
<3>[ 3.215056] init: [boot time] finish coldboot
<6>[ 3.216735] EXT4-fs (mmcblk0p16): recovery complete
<6>[ 3.217314] EXT4-fs (mmcblk0p16): mounted filesystem with ordered data mode. Opts: barrier=0
<4>[ 3.220519] EXT4-fs (mmcblk0p27): warning: mounting unchecked fs, running e2fsck is recommended
<6>[ 3.221129] EXT4-fs (mmcblk0p27): mounted filesystem without journal. Opts: (null)
<4>[ 3.238127] EXT4-fs (mmcblk0p27): warning: mounting unchecked fs, running e2fsck is recommended
<6>[ 3.238738] EXT4-fs (mmcblk0p27): mounted filesystem without journal. Opts: (null)
<4>[ 3.248168] EXT4-fs (mmcblk0p27): warning: mounting unchecked fs, running e2fsck is recommended
<6>[ 3.249205] EXT4-fs (mmcblk0p27): mounted filesystem without journal. Opts: (null)
<4>[ 3.258544] EXT4-fs (mmcblk0p27): warning: mounting unchecked fs, running e2fsck is recommended
<6>[ 3.259154] EXT4-fs (mmcblk0p27): mounted filesystem without journal. Opts: (null)
<4>[ 3.271483] mmc2: host does not support reading read-only switch. assuming write-enable.
<6>[ 3.271514] mmc2: new high speed SDHC card at address 1234
<6>[ 3.271605] sdio_al mmc2:1234: Probing..
<6>[ 3.271605] sdio_al mmc2:1234: Not an SDIO card
<6>[ 3.271941] mmcblk1: mmc2:1234 SA16G 14.6 GiB
<6>[ 3.272124] mmcblk1: p1
<4>[ 3.276579] EXT4-fs (mmcblk0p27): warning: mounting unchecked fs, running e2fsck is recommended
<6>[ 3.277220] EXT4-fs (mmcblk0p27): mounted filesystem without journal. Opts: (null)
<3>[ 3.278319] init: [disk_config] :::: /dev/block/mmcblk0p27 (ext4)(opt (null)):::::
<3>[ 3.278349] init: internal_storage : ext_identify open
<3>[ 3.278380] init: internal_storage : ext_identify lseek
<3>[ 3.279234] init: internal_storage : ext_identify open
<3>[ 3.279265] init: internal_storage : ext_identify lseek
<3>[ 3.279295] init: MOUNT NAME /dev/block/mmcblk0p27
<3>[ 3.279326] init: SEC_DEVENC ***[/dev/block/mmcblk0p27][0]
<3>[ 3.279357] init: failed that mount s:'/dev/block/mmcblk0p27', t:'/efs', f:ext4 ,op null) (Device or resource busy)
<3>[ 3.279418] init: [disk_config] :::: /dev/block/mmcblk0p17 (ext4)(opt (null)):::::
<3>[ 3.279448] init: internal_storage : ext_identify open
<3>[ 3.279479] init: internal_storage : ext_identify lseek
<3>[ 3.280852] init: internal_storage : ext_identify open
<3>[ 3.280882] init: internal_storage : ext_identify lseek
<3>[ 3.282439] init: [disk_config] :::: fsck -> /dev/block/mmcblk0p17 (ext4):::::
<3>[ 3.282836] init: [disk_config] DEVENC : not mormal [0]
<3>[ 3.282836] init: [disk_config] DEVENC : fs_check with original dev_path
<3>[ 3.644621] mmc1 data status (0x8)
<3>[ 3.644652] mmc1: Data timeout opcode = 0x12
<3>[ 3.644682] mmc1: DMA channel flushed (0x80000004)
<3>[ 3.644682] Flush data: 0000c003 4f713000 00000000 00200040 00290028 00002003
<4>[ 3.645018] mmcblk0: retrying using single block read
<3>[ 4.017912] init: SEC_DEVENC check crypt status
<3>[ 4.017973] init: MOUNT NAME /dev/block/mmcblk0p17
<3>[ 4.017973] init: SEC_DEVENC ***[/dev/block/mmcblk0p17][1]
<3>[ 4.017973] init: SEC_DEVENC checkCrypt main
<3>[ 4.316953] mmc1 data status (0x8)
<3>[ 4.316953] mmc1: Data timeout opcode = 0x12
<3>[ 4.316984] mmc1: DMA channel flushed (0x80000004)
<3>[ 4.316984] Flush data: 0000c003 4f713000 00000000 00200040 05b905b8 00002003
<4>[ 4.317320] mmcblk0: retrying using single block read
<3>[ 4.519804] mmc1 data status (0x8)
<3>[ 4.519834] mmc1: Data timeout opcode = 0x12
<3>[ 4.519865] mmc1: DMA channel flushed (0x80000004)
<3>[ 4.519865] Flush data: 0000c003 4f713000 00000000 00200040 05b905b8 00002003
<4>[ 4.520170] mmcblk0: retrying using single block read
<3>[ 4.727903] mmc1 data status (0x8)
<3>[ 4.727903] mmc1: Data timeout opcode = 0x12
<3>[ 4.727934] mmc1: DMA channel flushed (0x80000004)
<3>[ 4.727934] Flush data: 0000c003 4f713000 00000000 00200040 04690468 00002003
<4>[ 4.728300] mmcblk0: retrying using single block read
<3>[ 5.135984] mmc1 data status (0x8)
<3>[ 5.136015] mmc1: Data timeout opcode = 0x12
<3>[ 5.136045] mmc1: DMA channel flushed (0x80000004)
<3>[ 5.136045] Flush data: 0000c003 4f713000 00000000 00200040 00b900b8 00002003
<4>[ 5.136381] mmcblk0: retrying using single block read
<4>[ 5.233640] EXT4-fs (mmcblk0p17): warning: mounting fs with errors, running e2fsck is recommended
<6>[ 5.234983] EXT4-fs (mmcblk0p17): recovery complete
<6>[ 5.235959] EXT4-fs (mmcblk0p17): mounted filesystem with ordered data mode. Opts: errors=continue
<3>[ 5.236020] init: SEC_DEVENC uncrypted parition mounted
<4>[ 5.237577] param_init !
<3>[ 5.237729] init: [boot time] processing action 0x3b6d8 (post-fs)
<3>[ 5.237760] init: [disk_config] :::: /dev/block/mmcblk0p28 (vfat)(opt (null)):::::
<3>[ 5.240323] init: oem_name (android )
<3>[ 5.244382] init: oem_name (android )
<3>[ 5.244474] init: [disk_config] :::: fsck -> /dev/block/mmcblk0p28 (vfat):::::
<3>[ 5.244901] init: [disk_config] DEVENC : not mormal [0]
<3>[ 5.244932] init: [disk_config] DEVENC : fs_check with original dev_path
<3>[ 5.599302] mmc1 data status (0x8)
<3>[ 5.599302] mmc1: Data timeout opcode = 0x12
<3>[ 5.599332] mmc1: DMA channel flushed (0x80000004)
<3>[ 5.599332] Flush data: 0000c003 4f713000 00000000 00200040 02690268 00002003
<4>[ 5.599698] mmcblk0: retrying using single block read
<3>[ 6.010587] mmc1 data status (0x8)
<3>[ 6.010587] mmc1: Data timeout opcode = 0x12
<3>[ 6.010617] mmc1: DMA channel flushed (0x80000004)
<3>[ 6.010617] Flush data: 0000c003 4f713000 00000000 00200040 02790278 00002003
<4>[ 6.010984] mmcblk0: retrying using single block read
<3>[ 6.435544] mmc1 data status (0x8)
<3>[ 6.435544] mmc1: Data timeout opcode = 0x12
<3>[ 6.435574] mmc1: DMA channel flushed (0x80000004)
<3>[ 6.435574] Flush data: 0000c003 4f713000 00000000 00200040 01b901b8 00002003
<4>[ 6.435910] mmcblk0: retrying using single block read
<3>[ 6.638852] mmc1 data status (0x8)
<3>[ 6.638883] mmc1: Data timeout opcode = 0x12
<3>[ 6.638883] mmc1: DMA channel flushed (0x80000004)
<3>[ 6.638913] Flush data: 0000c003 4f713000 00000000 00200040 00b900b8 00002003
<4>[ 6.639249] mmcblk0: retrying using single block read
my internal memory was damaged. I flashed stock rom, entered it's recovery and formatted the internal memory. then installed cwm and installed custom rom. now everything is perfect.
ozgurakman said:
my internal memory was damaged. I flashed stock rom, entered it's recovery and formatted the internal memory. then installed cwm and installed custom rom. now everything is perfect.
Click to expand...
Click to collapse
Hi,
Thanks for the reply and good for you ozgurakman coz able to go to recovery mode. But I'm unable to go to recovery mode to repair the system though. Press the 3 recovery buttons. and just a screen flicker. It seem that my recovery corrupt also. Even after I reflash the recovery block only, still nada.
It seem that I'm running out options though. Anybody?
Did you tried to install cwm?
ozgurakman said:
Did you tried to install cwm?
Click to expand...
Click to collapse
yup also trying that one. also using the dd command in case the odin not working.
If dd command works, everything is fine. if dd command not working +Odin is not working, flashing via jtag is the only way.
ozgurakman said:
If dd command works, everything is fine. if dd command not working +Odin is not working, flashing via jtag is the only way.
Click to expand...
Click to collapse
the weird is that both dd and odin works. Also when i try to reboot it shutdown instead.
Will try to find shop that can do jtag. thanks
zaffrullah said:
the weird is that both dd and odin works. Also when i try to reboot it shutdown instead.
Will try to find shop that can do jtag. thanks
Click to expand...
Click to collapse
If I helped you, please press to thanks button
Last advise: try to different Odin version, different ops, different Rom.
Select to wipe everything.