Related
"Wi-Fi unable to start" error appeared couple weeks ago.
I have tried everything - reflashing different images, radio, formatting ... etc.
Nothing helped.
In a desperate moment I tried something.
Here are the steps:
I made some progress and it seams that is pure software problem.
Currently I'm with G1/black Cyanogen 3.6.8.1, Recovery 1.4 and 8GB SD/class 4.
What I did is reformatting the SD card in 2 partitions 1st FAT32 and 2nd ext2 ~ 460MB.
Wiped before flashing cyanogen build and also I made sure that there is nothing on the ext2 partition.
When flashing finished I waited the phone to fully set up itself on the first boot ~5-7 min.
Then I tried the WiFi - it didn't start
The important and desperate thing I did was to go to su console in /system/lib/modules and tried to load wlan.ko manually (insmod wlan.ko) - it failed the 1st time.
Then I tried 2 times more and it loaded itself successfully (of course wifi connection is not established in that moment, because loading the module is just one step of the process).
I unloaded successfully (rmmod wlan) the module and tried to start WiFi again - gues what - It worked!
That is just partial solution of the problem, but shows that it is just a software problem.
I guess some timeouts appear and WiFi starting procedure is not so patient to wait for the module to start up and it's not retrying to unload and load again the module.
Good luck
Hope it will work on yours G1.
Cheers
this has been up on a google code bug report page for a while now. I had the same result when trying to start the module in the terminal
cyanogen's new 3.9.1 scary experimental build shows that he used a new wifi driver in the changelog but that hasn't helped me with this issue at all. I thought it might be a software conflict so I used a clean sd card, flashed my update.zip, and still had the same problem
I have tried Cyanogen 3.9.1 with the same result - it doesn't work for me.
I can't explain why it started to work again in 3.6.8.1
Anyway, try to copy all your important files (not system/applications created like thumbnails folder) to your PC, put the SD card to card reader connected to a PC and then do a full reformat to FAT32.
Partition the newly formatted SD card to FAT32 and EXT2 partitions.
Reformat partitions again, copy update.zip to your SD card.
Start up your G1 holding home button and do wipe ( I wiped 2-3 times just to be sure )
Do ext2 system repair from the repair menu.
Do not convert it to ext3.
Apply the update.zip and continue to the next steps I wrote above.
Hope that's info is useful for you.
Post the output of "dmesg" after you try to install the module. It will tell us whats going wrong. This is not normal at all and might be hardware related.
cssvb94 said:
but shows that it is just a software problem.
Click to expand...
Click to collapse
I don't see how you come to the conclusion that it is a software problem. Intermittence is typically a sign of a HARDWARE problem.
lbcoder said:
I don't see how you come to the conclusion that it is a software problem. Intermittence is typically a sign of a HARDWARE problem.
Click to expand...
Click to collapse
Simple, it works somethimes on some builds and it doesn't at all on others - same hardware, different software.
Anyway, I realy hope it's not hardware related ...
cyanogen said:
Post the output of "dmesg" after you try to install the module. It will tell us whats going wrong. This is not normal at all and might be hardware related.
Click to expand...
Click to collapse
Is that request for me or airmaxx?
I really don't want to reflash now when it's working.
In the moment when something goes wrong I'll post dmesg.
I've noticed "D/wlan_loader( 228): ConfigMge start rc = -1" couple times in dmesg output when it wasn't working and "D/wlan_loader( 228): ConfigMge start rc = 0" when it works.
after a clean install of cyanogen 3.9.1, i tried to start with in the gui, through settings menu. after it reported "unable to start wifi" this is my dmesg output....
Code:
<6>[ 695.675048] TIWLAN: Driver loading
<4>[ 695.679168] wifi_probe
<4>[ 695.681762] trout_wifi_power: 1
<4>[ 695.888366] trout_wifi_reset: 0
<4>[ 695.943084] trout_wifi_set_carddetect: 1
<7>[ 695.947265] mmc0: card_present 1
<6>[ 695.950744] mmc0: Slot status change detected (0 -> 1)
<3>[ 698.464202] mmc0: Command timeout
<4>[ 698.474548] mmc0: card claims to support voltages below the defined range. These will be ignored.
<4>[ 698.484191] mmc0: SDIO card claims to support the incompletely defined 'low voltage range'. This will be ignored.
<6>[ 698.497955] mmc0: new SDIO card at address 0001
<6>[ 698.508758] TIWLAN: Found SDIO controller (vendor 0x104c, device 0x9066)
<6>[ 698.517639] tiwlan0 (): not using net_device_ops yet
<6>[ 698.530426] TIWLAN: Driver initialized (rc 0)
<3>[ 698.535705] mmc0: Data CRC error
<3>[ 698.539276] msmsdcc_data_err: opcode 0x00000035
<3>[ 698.544128] msmsdcc_data_err: blksz 4, blocks 1
<3>[ 698.549621] SDIO_SyncWrite: failed (-84)
<3>[ 698.554016] mmc0: Data CRC error
<3>[ 698.557586] msmsdcc_data_err: opcode 0x00000035
<3>[ 698.562713] msmsdcc_data_err: blksz 4, blocks 1
<3>[ 698.567718] SDIO_SyncWrite: failed (-84)
<3>[ 701.399383] mmc0: Data timeout
<3>[ 701.403289] SDIO_SyncRead: failed (-110)
<4>[ 701.407623] TIWLAN: invalid chip id = 0x 0 0 0 0!
<6>[ 701.412933] TIWLAN: Driver loaded
<4>[ 701.820495] select 226 (app_process), adj 15, size 3301, to kill
<4>[ 701.826873] send sigkill to 226 (app_process), adj 15, size 3301
<3>[ 704.165802] mmc0: Data timeout
<3>[ 704.169311] SDIO_SyncRead: failed (-110)
<3>[ 704.174041] TIWLAN: TIWLAN: Failed to start config manager
<6>[ 710.698730] RPC_TIME_TOD_SET_APPS_BASES:
<6>[ 710.698760] tick = 38620607
<6>[ 710.698760] stamp = 48907518449025024
<4>[ 735.120178] select 480 (app_process), adj 15, size 4338, to kill
<4>[ 735.126464] send sigkill to 480 (app_process), adj 15, size 4338
something i remembered earlier was that long ago, many roms and flashes prior (when I was still chasing after Hero and Rosie) i saw a wpa supplicant file had been installed on my fat32 partition, no system folder or anything just on the root of the card. i remember thinking at the time how odd this was and manually deleting the file prior to my next flash.
My problem may have started shortly thereafter but honestly don't remember, just grasping for straws here
cssvb94 said:
Simple, it works somethimes on some builds and it doesn't at all on others - same hardware, different software.
Anyway, I realy hope it's not hardware related ...
Click to expand...
Click to collapse
Really? That's not what you said before...
cssvb94 said:
I have tried everything - reflashing different images, radio, formatting ... etc.
Nothing helped.
Click to expand...
Click to collapse
Clearly, it is NOT related to the software since you TRIED CHANGING the software and it didn't help, and the SAME SOFTWARE works fine for everybody else, which means that it MUST be either USER ERROR, or HARDWARE DEFECT.
lbcoder said:
Really? That's not what you said before...
Clearly, it is NOT related to the software since you TRIED CHANGING the software and it didn't help, and the SAME SOFTWARE works fine for everybody else, which means that it MUST be either USER ERROR, or HARDWARE DEFECT.
Click to expand...
Click to collapse
Listen, I'm not here to argue and I don't have anything against you.
Why you are so catchy about that simple details?
I'm trying to help and share what I've been through.
If you are offended of something I said then - sorry.
Don't be such arrogant, capital letters don't work on me. =)
----------------------------------------------------------------------
This is cut from my dmesg :
WiFi starting OK
--- cut ---
<6>[ 268.613555] TIWLAN: Driver loading
<4>[ 268.617797] wifi_probe
<4>[ 268.620758] trout_wifi_power: 1
<4>[ 268.830261] trout_wifi_reset: 0
<4>[ 268.884521] trout_wifi_set_carddetect: 1
<7>[ 268.888824] mmc0: card_present 1
<6>[ 268.892303] mmc0: Slot status change detected (0 -> 1)
<3>[ 271.400268] mmc0: Command timeout
<4>[ 271.410339] mmc0: card claims to support voltages below the defined range. These will be ignored.
<4>[ 271.419982] mmc0: SDIO card claims to support the incompletely defined 'low voltage range'. This will be ignored.
<6>[ 271.436584] mmc0: new SDIO card at address 0001
<6>[ 271.446960] TIWLAN: Found SDIO controller (vendor 0x104c, device 0x9066)
<6>[ 271.455352] tiwlan0 (): not using net_device_ops yet
<6>[ 271.464538] TIWLAN: Driver initialized (rc 0)
<4>[ 271.469909] TIWLAN: 1251 PG 1.2
<6>[ 271.473693] TIWLAN: Driver loaded
<3>[ 271.863403] mmc0: Data CRC error
<3>[ 271.866851] msmsdcc_data_err: opcode 0x00000035
<3>[ 271.871551] msmsdcc_data_err: blksz 512, blocks 1
<4>[ 271.877441] SDIO Write failure (-84)
<3>[ 271.883209] TIWLAN: TIWLAN: Failed to start config manager
--- cut ---
<6>[ 689.787445] TIWLAN: Found SDIO controller (vendor 0x104c, device 0x9066)
<6>[ 689.795745] tiwlan0 (): not using net_device_ops yet
<6>[ 689.804901] TIWLAN: Driver initialized (rc 0)
<4>[ 689.810150] TIWLAN: 1251 PG 1.2
<6>[ 689.813690] TIWLAN: Driver loaded
<3>[ 690.153045] mmc0: Data CRC error
<3>[ 690.156463] msmsdcc_data_err: opcode 0x00000035
<3>[ 690.161163] msmsdcc_data_err: blksz 4, blocks 1
<4>[ 690.168182] SDIO Write failure (-84)
<3>[ 690.173889] TIWLAN: TIWLAN: Failed to start config manager
--- cut ---
Now new case: "Unable to stop Wi-Fi"
rmmod wlan throws back: "rmmod: delete_module 'wlan' failed (errno 11)"
lsmod returns: "wlan 566844 1 - Live 0xbf480000"
lbcoder, was there anything in my dmesg that confirmed it is indeed hardware, or anything useful at all in there?
after reading the reports on googlecode pages, i was leaning to hardware issue only because the problem is so rare and those people sent their g1's back in. I was really hoping this wasn't the case though.
I'd be happy with intermittent at this point, my wifi has not turned on in like 2 months my phone was purchased used (wifi worked fine at the time though) on craigslist so I can't return it to TMO
The CRC errors on mmc0 means that your sdcard is dying. It might seem unrelated but because how the way the G1 hardware works, this could be the problem. Yank your card and try it again.
No more WiFi
"Unable to stop" or "Unable to start" after reboot.
Tried with different SD card - no CRC errors and still no WiFi
for me the wifi turned on but it cant connect with a router... just write obtain ip address.. and after.. no connection
this is my log
<6>[ 175.583831] ept #2 out max:512 head:ffc0c100 bit:2
<6>[ 175.584289] ept #0 in max:64 head:ffc0c040 bit:16
<6>[ 175.585083] ept #1 in max:512 head:ffc0c0c0 bit:17
<6>[ 175.585510] ept #2 in max:512 head:ffc0c140 bit:18
<6>[ 175.586059] usb: notify offline
<6>[ 175.594207] usb: suspend
<6>[ 175.813262] usb: reset
<6>[ 175.815673] usb: portchange USB_SPEED_HIGH
<6>[ 175.967803] usb: reset
<6>[ 175.970092] usb: portchange USB_SPEED_HIGH
<6>[ 176.164825] usb_mass_storage usb_mass_storage: config #1
<6>[ 187.209259] request_suspend_state: wakeup (3->0) at 180968491210 (2009-07-
29 16:16:01.570098877 UTC)
<6>[ 188.333618] TIWLAN: Driver loading
<4>[ 188.334503] wifi_probe
<4>[ 188.334777] trout_wifi_power: 1
<4>[ 188.536346] trout_wifi_reset: 0
<4>[ 188.586914] trout_wifi_set_carddetect: 1
<7>[ 188.587432] mmc0: card_present 1
<6>[ 188.587738] mmc0: Slot status change detected (0 -> 1)
<3>[ 191.095031] mmc0: Command timeout
<4>[ 191.102386] mmc0: card claims to support voltages below the defined range.
These will be ignored.
<4>[ 191.103210] mmc0: SDIO card claims to support the incompletely defined 'lo
w voltage range'. This will be ignored.
<6>[ 191.112518] mmc0: new SDIO card at address 0001
<6>[ 191.118377] TIWLAN: Found SDIO controller (vendor 0x104c, device 0x9066)
<6>[ 191.123901] TIWLAN: Driver initialized (rc 0)
<4>[ 191.125244] TIWLAN: 1251 PG 1.2
<6>[ 191.125701] TIWLAN: Driver loaded
<6>[ 192.657897] snd_set_volume 256 0 5
<6>[ 192.747344] snd_set_volume 256 0 5
<3>[ 198.871185] init: sys_prop: permission denied uid:1000 name:ro.config.noc
heckin
<6>[ 244.551879] TIWLAN: Driver unloading
<4>[ 244.553070] sdio_reset_comm():
<7>[ 244.631011] TIWLAN: Releasing SDIO resources
<7>[ 244.632324] TIWLAN: SDIO resources released
<4>[ 244.634918] wifi_remove
<4>[ 244.635406] trout_wifi_set_carddetect: 0
<7>[ 244.636199] mmc0: card_present 0
<6>[ 244.636627] mmc0: Slot status change detected (1 -> 0)
<6>[ 244.639465] mmc0: card 0002 removed
<4>[ 244.643585] trout_wifi_reset: 1
<4>[ 244.699401] trout_wifi_power: 0
<6>[ 244.905883] TIWLAN: Driver unloaded
<6>[ 246.548492] TIWLAN: Driver loading
<4>[ 246.549377] wifi_probe
<4>[ 246.549652] trout_wifi_power: 1
<4>[ 246.754119] trout_wifi_reset: 0
<4>[ 246.805236] trout_wifi_set_carddetect: 1
<7>[ 246.805786] mmc0: card_present 1
<6>[ 246.806060] mmc0: Slot status change detected (0 -> 1)
<3>[ 249.310638] mmc0: Command timeout
<4>[ 249.318481] mmc0: card claims to support voltages below the defined range.
These will be ignored.
<4>[ 249.319335] mmc0: SDIO card claims to support the incompletely defined 'lo
w voltage range'. This will be ignored.
<6>[ 249.326782] mmc0: new SDIO card at address 0001
<6>[ 249.332794] TIWLAN: Found SDIO controller (vendor 0x104c, device 0x9066)
<6>[ 249.338226] TIWLAN: Driver initialized (rc 0)
<4>[ 249.339141] TIWLAN: 1251 PG 1.2
<6>[ 249.339599] TIWLAN: Driver loaded
<6>[ 994.061614] request_suspend_state: sleep (0->3) at 987820816650 (2009-07-2
9 16:29:28.422424317 UTC)
<4>[ 994.083801] deinit sharp panel
<4>[ 994.762908] save exit: isCheckpointed 1
<4>[ 994.765380] save exit: isCheckpointed 1
If you want help, get your details straight! If you contradict yourself all over the place, then nobody can possibly know what is going on and you won't get anywhere.
cssvb94 said:
Listen, I'm not here to argue and I don't have anything against you.
Why you are so catchy about that simple details?
Click to expand...
Click to collapse
You mention having tried flashing different software...
Have you tried flashing IMAGES (fastboot) or just update scripts (i.e. update.zip)?
If you haven't tried already, I suggest flashing the stock *engineering* bootloader 0.95.3000, ADP1-CRC1 images from www.htc.com -- the one that's labeled as "system image" (not the one labeled "recovery image", which is just an update.zip), and radio v2_22_19_26I (also from htc.com), write everything to the phone using fastboot, pull the battery, wait 10 minutes, and see what happens. IF it is a software problem, then this will *definitely* fix it. If it is a HARDWARE problem, then this will *definitely NOT* fix it. If the wifi starts working right after you write these things, *do not* conclude that it was a software problem since it could simply have gone intermittent-on. Keep the software like that and run it for at least a week to make sure the problem doesn't come back before making your conclusions.
Went back to stock 1.0 RC29 with original SPL, radio and bootloader and started from scratch.
Also formated SD card - only one partition FAT32.
Now I'm with ADP1.5 JF and WiFi is working most of the time.
So angry lbcoder what's your great verdict now? SOFTWARE or HARDWARE?
lbcoder said:
You mention having tried flashing different software...
Have you tried flashing IMAGES (fastboot) or just update scripts (i.e. update.zip)?
If you haven't tried already, I suggest flashing the stock *engineering* bootloader 0.95.3000, ADP1-CRC1 images from www.htc.com -- the one that's labeled as "system image" (not the one labeled "recovery image", which is just an update.zip), and radio v2_22_19_26I (also from htc.com), write everything to the phone using fastboot, pull the battery, wait 10 minutes, and see what happens. IF it is a software problem, then this will *definitely* fix it. If it is a HARDWARE problem, then this will *definitely NOT* fix it. If the wifi starts working right after you write these things, *do not* conclude that it was a software problem since it could simply have gone intermittent-on. Keep the software like that and run it for at least a week to make sure the problem doesn't come back before making your conclusions.
Click to expand...
Click to collapse
which is the commands for push the radio and the the adp1-crc1 image via fastboot?
i can t find ADP1-CRC1 images can you give me a url please?
success!!!!!!
the problem was the radio... i flashed 2 times the radio and now work!!!!!
thanks guyssss i love you aahahah
rock187 said:
the problem was the radio... i flashed 2 times the radio and now work!!!!!
thanks guyssss i love you aahahah
Click to expand...
Click to collapse
Great =)
Would you please post full step-by-step what you did.
10x in advance
It didn't work for me. I'm going to return my G1 back to the store I bought it, it's still under warranty.
My sensation keeps restarting randomly.
I've tried:
- Reflashing firmware 3.33, 3.32
- Other roms: Miui v4, cm10, cm9, Darksense, ARDHD, stock, gingerbread cm7.
- New battery
- Battery card trick
Sometimes it turns off completely and I can't turn it back on without pulling the battery out and putting it back in.
Moon2 said:
My sensation keeps restarting randomly.
I've tried:
- Reflashing firmware 3.33, 3.32
- Other roms: Miui v4, cm10, cm9, Darksense, ARDHD, stock, gingerbread cm7.
- New battery
- Battery card trick
Sometimes it turns off completely and I can't turn it back on without pulling the battery out and putting it back in.
Click to expand...
Click to collapse
I need more information, so I ask you do these things.
OK. First:
Code:
adb shell
dmesg > /sdcard/DMESG.txt
Attach the DMESG.txt file from your SDCard.
Code:
adb logcat > Logcat.txt
Wait for phone to randomly restart (sorry) and attach the logcat file.
Secondly:
Current HBOOT version? Kernel if flashing manually?
DennisBold said:
I need more information, so I ask you do these things.
OK. First:
Code:
adb shell
dmesg > /sdcard/DMESG.txt
Attach the DMESG.txt file from your SDCard.
Code:
adb logcat > Logcat.txt
Wait for phone to randomly restart (sorry) and attach the logcat file.
Secondly:
Current HBOOT version? Kernel if flashing manually?
Click to expand...
Click to collapse
I'd previously logged the logcat twice before it restarted and also have a last_kmsg of when it happened. It doesn't seem to reboot when I'm in recovery.
HBoot: 1.29.0000, S-off
Kernel: Stock, faux, sebastian (happens on all of them)
I'm having the same problem with my sensation with alternative battery!!! Please help!!!
It just happened again and I've got another logcat, I'll try and do the dmesg now.
I've tried letting the phone sleep without wifi/3g, taking sd card out, formatting it.
Moon2 said:
I'd previously logged the logcat twice before it restarted and also have a last_kmsg of when it happened. It doesn't seem to reboot when I'm in recovery.
HBoot: 1.29.0000, S-off
Kernel: Stock, faux, sebastian (happens on all of them)
Click to expand...
Click to collapse
I thought the pyramid had Adreno 220?
Code:
D/libEGL ( 1113): loaded /system/lib/egl/libGLESv2_adreno200.so
What ROM do you currently have installed?
DennisBold said:
I thought the pyramid had Adreno 220?
Code:
D/libEGL ( 1113): loaded /system/lib/egl/libGLESv2_adreno200.so
What ROM do you currently have installed?
Click to expand...
Click to collapse
Miui v4
I've seen that library used on different phones with adreno on them, I don't think the 200 has a bearing on the type found on the phone.
Moon2 said:
Miui v4
Click to expand...
Click to collapse
Is your GPS enabled, and does this happen when your GPS is disabled?
Moon2 said:
Miui v4
I've seen that library used on different phones with adreno on them, I don't think the 200 has a bearing on the type found on the phone.
Click to expand...
Click to collapse
Never really looked at that, well, the only thing I can connect it with is GPS.
DennisBold said:
Is your GPS enabled, and does this happen when your GPS is disabled?
Click to expand...
Click to collapse
I've tried it with wifi, 3g, bluetooth, gps, auto-sync all turned off and it still happens.
Moon2 said:
I've tried it with wifi, 3g, bluetooth, gps, auto-sync all turned off and it still happens.
Click to expand...
Click to collapse
(From First Logcat)
Code:
D/GpsLocationProvider( 241): [handleMessage] message :7
D/GpsLocationProvider( 241): [handleMessage] UPDATE_LOCATION
D/GpsLocationProvider( 241): handleUpdateLocation
D/lib_locapi( 241): loc_eng_inject_location, accuracy = 48.0
(Second Logcat)
Code:
D/GpsLocationProvider( 242): [handleMessage] message :7
D/GpsLocationProvider( 242): [handleMessage] UPDATE_LOCATION
D/GpsLocationProvider( 242): handleUpdateLocation
D/lib_locapi( 242): loc_eng_inject_location, accuracy = 52.0
Logcat ends a minute not long after that.
On a side note, do you have AdFree installed?
DennisBold said:
(From First Logcat)
Code:
D/GpsLocationProvider( 241): [handleMessage] message :7
D/GpsLocationProvider( 241): [handleMessage] UPDATE_LOCATION
D/GpsLocationProvider( 241): handleUpdateLocation
D/lib_locapi( 241): loc_eng_inject_location, accuracy = 48.0
(Second Logcat)
Code:
D/GpsLocationProvider( 242): [handleMessage] message :7
D/GpsLocationProvider( 242): [handleMessage] UPDATE_LOCATION
D/GpsLocationProvider( 242): handleUpdateLocation
D/lib_locapi( 242): loc_eng_inject_location, accuracy = 52.0
Logcat ends a minute not long after that.
On a side note, do you have AdFree installed?
Click to expand...
Click to collapse
No, I've tried all of the roms with & without adding any apps.
Moon2 said:
No, I've tried all of the roms with & without adding any apps.
Click to expand...
Click to collapse
There's not exactly any errors other than this on dmesg.
Code:
<3>[ 475.735900] init: cannot execve('/system/bin/DxDrmServerIpc'): Permission denied
That isn't really a problem. Neither are these:
Code:
E/MobileDataStateTracker( 242): Error mapping networkType 23 to apnType.
Code:
D/MobileDataStateTracker( 242): internet: mMobileDataState=DISCONNECTED mTeardownRequested=false got [AnyDataCSC] : type=internet state=DISCONNECTED reason=dataDetached apn=null roaming=false unavailable=true NetworkType=0 NetworkTypeName=UNKNOWN entitleError=0 apnCarrier=null
I've just installed cm9 and run the logcat to just before it rebooted.
Moon2 said:
I've just installed cm9 and run the logcat to just before it rebooted.
Click to expand...
Click to collapse
Run Fix Permissions in recovery.
Also, send me another DMESG. Not during/while the phone is crashing.
DennisBold said:
Run Fix Permissions in recovery.
Also, send me another DMESG. Not during/while the phone is crashing.
Click to expand...
Click to collapse
It seems to reboot more frequently on a non-sense rom like cm9/10 than sense based roms like Miui or arhd and I don't think its rebooted or shutdown yet if it's been plugged in to charger/computer.
Moon2 said:
It seems to reboot more frequently on a non-sense rom like cm9/10 than sense based roms like Miui or arhd and I don't think its rebooted or shutdown yet if it's been plugged in to charger/computer.
Click to expand...
Click to collapse
Thanks.
Can you try:
Code:
adb shell
dmesg | grep mmc
And copy and paste the results?
You should see:
Code:
[email protected]:/ # dmesg | grep mmc
dmesg | grep mmc
[email protected]:/ #
---------- Post added at 08:04 PM ---------- Previous post was at 07:33 PM ----------
Could you run?
Code:
cat /sys/class/block/mmcblk0/device/name
Code:
[email protected]:/ $ dmesg | grep mmc
dmesg | grep mmc
1|[email protected]:/ $ cat /sys/class/block/mmcblk0/device/name
cat /sys/class/block/mmcblk0/device/name
MLL00M
Moon2 said:
Code:
[email protected]:/ $ dmesg | grep mmc
dmesg | grep mmc
1|[email protected]:/ $ cat /sys/class/block/mmcblk0/device/name
cat /sys/class/block/mmcblk0/device/name
MLL00M
Click to expand...
Click to collapse
Flash an RUU (preferably Gingerbread) and see if it makes any difference?
Run this from stock and see if you still have errors
Code:
adb shell
dmesg | grep mmc
logcat | grep mmc
DennisBold said:
Flash an RUU (preferably Gingerbread) and see if it makes any difference?
Run this from stock and see if you still have errors
Code:
adb shell
dmesg | grep mmc
logcat | grep mmc
Click to expand...
Click to collapse
Code:
dmesg | grep mmc
Code:
<5>[ 0.000000] Kernel command line: poweron_status=1 board_pyramid.disable_ua
rt3=0 diag.enabled=0 board_pyramid.debug_uart=0 userdata_sel=0 androidboot.emmc=
true androidboot.pagesize=2048 androidboot.baseband=10.14.9035.01_M androidboo
t.cid=11111111 androidboot.batt_poweron=good_battery androidboot.carrier=ALL and
roidboot.mid=PG5813000 androidboot.keycaps=qwerty androidboot.dq=FAIL androidboo
t.mode=normal androidboot.serialno=SH191V463715 androidboot.bootloader=1.17.1111
zygote_oneshot=off msm_watchdog.enable=1 console=ttyHSL0 androidboot.hardware=p
yramid no_console_suspend=1
<6>[ 0.335052] pyramid: pyramid_init_mmc
<6>[ 0.907806] Create /proc/emmc OK.
<3>[ 2.389921] mmc0: No card detect facilities available
<6>[ 2.390287] mmc0: Qualcomm MSM SDCC at 0x0000000012400000 irq 136,0 dma 18
<6>[ 2.390379] mmc0: Platform slot type: MMC
<6>[ 2.390562] mmc0: 8 bit data mode enabled
<6>[ 2.390654] mmc0: 4 bit data mode disabled
<6>[ 2.390745] mmc0: polling status mode disabled
<6>[ 2.390928] mmc0: MMC clock 400000 -> 48000000 Hz, PCLK 0 Hz
<6>[ 2.391020] mmc0: Slot eject status = 0
<6>[ 2.391203] mmc0: Power save feature enable = 1
<6>[ 2.391294] mmc0: DM non-cached buffer at ff007000, dma_addr 0x5751b000
<6>[ 2.391386] mmc0: DM cmd busaddr 0x5751b000, cmdptr busaddr 0x5751b300
<6>[ 2.391966] mmc1: Qualcomm MSM SDCC at 0x0000000012180000 irq 134,654 dma
20
<6>[ 2.392149] mmc1: Platform slot type: SD
<6>[ 2.392240] mmc1: 8 bit data mode disabled
<6>[ 2.392332] mmc1: 4 bit data mode enabled
<6>[ 2.392515] mmc1: polling status mode disabled
<6>[ 2.392607] mmc1: MMC clock 144000 -> 48000000 Hz, PCLK 0 Hz
<6>[ 2.392790] mmc1: Slot eject status = 0
<6>[ 2.392881] mmc1: Power save feature enable = 1
<6>[ 2.392973] mmc1: DM non-cached buffer at ff008000, dma_addr 0x5751c000
<6>[ 2.393156] mmc1: DM cmd busaddr 0x5751c000, cmdptr busaddr 0x5751c300
<6>[ 2.393644] mmc2: Qualcomm MSM SDCC at 0x00000000121c0000 irq 133,0 dma 21
<6>[ 2.393736] mmc2: Platform slot type: N/A
<6>[ 2.393919] mmc2: 8 bit data mode disabled
<6>[ 2.394010] mmc2: 4 bit data mode enabled
<6>[ 2.394102] mmc2: polling status mode disabled
<6>[ 2.394285] mmc2: MMC clock 400000 -> 48000000 Hz, PCLK 0 Hz
<6>[ 2.394377] mmc2: Slot eject status = 1
<6>[ 2.394468] mmc2: Power save feature enable = 1
<6>[ 2.394651] mmc2: DM non-cached buffer at ff009000, dma_addr 0x5751d000
<6>[ 2.394743] mmc2: DM cmd busaddr 0x5751d000, cmdptr busaddr 0x5751d300
<6>[ 2.513761] mmc0: new high speed MMC card at address 0001
<6>[ 2.526975] mmcblk0: mmc0:0001 MLL00M 2.25 GiB
<6>[ 2.527555] mmcblk0: p1 p2 p3 p4 < p5 p6
<6>[ 2.568296] EXT4-fs (mmcblk0p22): INFO: recovery required on readonly file
system
<6>[ 2.568662] EXT4-fs (mmcblk0p22): write access will be enabled during reco
very
<4>[ 2.666654] mmc1: high speed mode max_dtr = 50000000
<4>[ 2.667081] mmc1: host does not support reading read-only switch. assuming
write-enable.
<6>[ 2.667264] mmc1: new high speed SD card at address 1234
<6>[ 2.667753] mmcblk1: mmc1:1234 SA02G 1.83 GiB
<6>[ 2.668149] mmcblk1: p1
<6>[ 2.697813] EXT4-fs (mmcblk0p22): recovery complete
<6>[ 2.705625] EXT4-fs (mmcblk0p22): mounted filesystem with ordered data mod
e. Opts: (null)
<7>[ 3.291562] EXT4-fs (mmcblk0p23): ext4_orphan_cleanup: deleting unreferenc
ed inode 22945
<7>[ 3.292050] EXT4-fs (mmcblk0p23): ext4_orphan_cleanup: deleting unreferenc
ed inode 22946
<6>[ 3.292416] EXT4-fs (mmcblk0p23): 2 orphan inodes deleted
<6>[ 3.292691] EXT4-fs (mmcblk0p23): recovery complete
<6>[ 3.334836] EXT4-fs (mmcblk0p23): mounted filesystem with ordered data mod
e. Opts: nodelalloc
<6>[ 3.389493] EXT4-fs (mmcblk0p24): recovery complete
<6>[ 3.397031] EXT4-fs (mmcblk0p24): mounted filesystem with ordered data mod
e. Opts: nodelalloc
<6>[ 3.516964] EXT4-fs (mmcblk0p27): recovery complete
<6>[ 3.521115] EXT4-fs (mmcblk0p27): mounted filesystem with writeback data m
ode. Opts: nodelalloc
<6>[ 20.862468] mmc2: Slot status change detected (0 -> 1)
<7>[ 20.915202] mmc2: queuing CIS tuple 0x91 length 3
<6>[ 20.915446] mmc2: new high speed SDIO card at address 0001
Code:
logcat | grep mmc
I've left it running for a few mins but nothings showing up.
Its still not showing anything, but I'm attaching a logcat on stock gb upto the point it restarted.
I have TF700 Infinity with Cromi-X 4.6.9 installed, running hundsbuah's 3.0.6 kernel with Data2SD enabled. I use SanDisk 32GB Mobile Ultra Micro SDHC card, formatted using gparted on Parted Magic linux. Fsync is enabled.
I noticed that my experience with Data2SD is deteriorating. Fresh after formatting Micro SD it works perfectly fine, but after week or two some random freezes start to occur (most often when running app's but sometimes even at lockscreen) forcing me to reboot. With more number of reboots freezes get more often after I'm desperate enough to format Micro SD again and reinstall. I've been trying with _that kernel, but it was no difference. Is that a problem of my SD Card or with Infinity? How can I fix it?
Here is the part of content of last_kmsg
Code:
[ 1789.970823] Switched to NOHz mode on CPU #1
[ 1792.498820] tegradc tegradc.0: Using mode 1920x1200 pclk=154012000 href=0 vref=1
[ 1792.971434] cpu_down(3)+
[ 1792.973679] CPU3: shutdown
[ 1792.975627] edp_update_limit: Limiting cpu speed from 1500000 to 1500000 during boot!
[ 1792.976218] cpu_down(3)-
[ 1794.117317] tegradc tegradc.0: Using mode 1920x1200 pclk=154012000 href=0 vref=1
[ 1794.841849] cpu ext_temperature=37
[ 1795.971717] cpu_down(2)+
[ 1795.975049] CPU2: shutdown
[ 1795.977786] edp_update_limit: Limiting cpu speed from 1500000 to 1500000 during boot!
[ 1795.978965] cpu_down(2)-
[ 1797.990758] mmcblk1: error -110 transferring data, sector 36657736, nr 344, cmd response 0x900, card status 0xb00
[ 1797.991805] mmcblk1: retrying using single block read
[ 1798.981523] cpu_down(1)+
[ 1798.982526] CPU1: shutdown
[ 1798.983655] edp_update_limit: Limiting cpu speed from 1600000 to 1500000 during boot!
[ 1798.984118] cpu_down(1)-
[ 1799.638992] mmcblk1: error -110 transferring data, sector 36657736, nr 344, cmd response 0x900, card status 0x0
[ 1799.639284] [mmc]:mmc_blk_issue_rw_rq:1101 SD freq. down to UHS_SDR12_MAX_DTR
[ 1799.642246] mmcblk1: timed out sending r/w cmd command, card status 0x400b00
[ 1799.642518] mmcblk1: command error, retrying timeout
[ 1800.322357] tegradc tegradc.0: Using mode 1920x1200 pclk=154012000 href=0 vref=1
[ 1802.446926] mmcblk1: error -110 transferring data, sector 36657737, nr 343, cmd response 0x900, card status 0xb00
[ 1802.449065] mmcblk1: retrying using single block read
[ 1804.863463] cpu ext_temperature=34
[ 1805.248817] mmcblk1: error -110 transferring data, sector 36657737, nr 343, cmd response 0x900, card status 0x0
[ 1805.251672] mmcblk1: timed out sending r/w cmd command, card status 0x400b00
[ 1805.251929] mmcblk1: command error, retrying timeout
[ 1808.053001] mmcblk1: error -110 transferring data, sector 36657738, nr 342, cmd response 0x900, card status 0xb00
[ 1808.053064] mmcblk1: retrying using single block read
[ 1810.851446] mmcblk1: error -110 transferring data, sector 36657738, nr 342, cmd response 0x900, card status 0x0
[ 1810.853818] mmcblk1: timed out sending r/w cmd command, card status 0x400b00
[ 1810.853875] mmcblk1: command error, retrying timeout
[ 1813.657813] mmcblk1: error -110 transferring data, sector 36657739, nr 341, cmd response 0x900, card status 0xb00
[ 1813.659954] mmcblk1: retrying using single block read
[ 1814.883548] cpu ext_temperature=32
[ 1816.459651] mmcblk1: error -110 transferring data, sector 36657739, nr 341, cmd response 0x900, card status 0x0
[ 1816.462061] mmcblk1: timed out sending r/w cmd command, card status 0x400b00
[ 1816.462161] mmcblk1: command error, retrying timeout
[ 1818.411499] gpio_keys: Pressed KEY_POWER
[ 1819.262896] mmcblk1: error -110 transferring data, sector 36657740, nr 340, cmd response 0x900, card status 0xb00
[ 1819.263004] mmcblk1: retrying using single block read
[ 1822.059974] mmcblk1: error -110 transferring data, sector 36657740, nr 340, cmd response 0x900, card status 0x0
[ 1822.067079] mmcblk1: timed out sending r/w cmd command, card status 0x400b00
[ 1822.069317] mmcblk1: command error, retrying timeout
[ 1824.877483] mmcblk1: error -110 transferring data, sector 36657741, nr 339, cmd response 0x900, card status 0xb00
[ 1824.879788] mmcblk1: retrying using single block read
[ 1824.902545] cpu ext_temperature=31
13422 Corrected bytes, 16 unrecoverable blocks
Also after last reinstall I noticed that I can't access ext4 partition of my sdcard. In /storage I see emulated, sdcard0 and sdcard1. Emulated and sdcard0 lead to data that are on my internal sdcard, sdcard1 is empty. However, data2SD is working, because i tested with androbench and the random write speed is 0.3-0.4Mbps and when I removed the Micro SD card from a slot the system booted with all my apps gone, so it made me sure, that my regular installation is on external sd.
"error -110 transferring data" and "timed out sending r/w cmd" indicates problems with your card. The TF700 is known to have troubles with fast microSD cards - some work reliably, some don't.
_that said:
"error -110 transferring data" and "timed out sending r/w cmd" indicates problems with your card. The TF700 is known to have troubles with fast microSD cards - some work reliably, some don't.
Click to expand...
Click to collapse
Well, the card is SanDisk Mobile Ultra, which worked nice for many people from what I've read. Anyway, I think I managed to solve the problem. I've read in one of threads that formatting to ext2 instead of ext4 might work better, so I tried it and so far so good.
Just if someone has simmilar problem - try ext2.
Arquiteto said:
Well, the card is SanDisk Mobile Ultra, which worked nice for many people from what I've read. Anyway, I think I managed to solve the problem. I've read in one of threads that formatting to ext2 instead of ext4 might work better, so I tried it and so far so good.
Just if someone has simmilar problem - try ext2.
Click to expand...
Click to collapse
I had a similar problem with crashing and freezing using Data2SD but I think it was because of a defective card. Since then, I tried using the CROMI-X without data2sd and I was surprised I was still satisfied with the response and speed of the tablet. Data2SD still might be a little bit faster but in my opinion the differences are not that noticeable anymore.
lasallegreen said:
I had a similar problem with crashing and freezing using Data2SD but I think it was because of a defective card. Since then, I tried using the CROMI-X without data2sd and I was surprised I was still satisfied with the response and speed of the tablet. Data2SD still might be a little bit faster but in my opinion the differences are not that noticeable anymore.
Click to expand...
Click to collapse
I think that all the advances made in kernel development and rom tweaks that data2sd is not as beneficial as it used to be
Arquiteto said:
Just if someone has simmilar problem - try ext2.
Click to expand...
Click to collapse
Thanks for the advice. Could you do us all a favor and report back in a week or so? This seems like a useful thing to document.
B00T_Sp0rk said:
Thanks for the advice. Could you do us all a favor and report back in a week or so? This seems like a useful thing to document.
Click to expand...
Click to collapse
Reporting back:
It looked like the problem was solved, as it worked fine... for a few days. And then it was all over again, so I guess the problem is the MicroSD Card after all. However it was a little better with ext2 the freezes returned so I dumped data2sd. My Infinity is now a bit slower, but at least it's stable. I got the freeze one more time without data2sd (checked the last_kmsg it was -110 error) but I'm using it for few days and it was the only time it happened.
You think that I might get a replacement MicroSD from SanDisk if I sent it back?
Arquiteto said:
Reporting back:
It looked like the problem was solved, as it worked fine... for a few days. And then it was all over again, so I guess the problem is the MicroSD Card after all. However it was a little better with ext2 the freezes returned so I dumped data2sd. My Infinity is now a bit slower, but at least it's stable. I got the freeze one more time without data2sd (checked the last_kmsg it was -110 error) but I'm using it for few days and it was the only time it happened.
You think that I might get a replacement MicroSD from SanDisk if I sent it back?
Click to expand...
Click to collapse
You may have a system problem rather than the external SD. Without data2sd, your system still caused the same problem. If you don't have any other solution, you may want to format your internal SD and start out fresh. I use 64G Samsung class 10 and it works fine with data2sd. Good luck.
LetMeKnow said:
You may have a system problem rather than the external SD. Without data2sd, your system still caused the same problem. If you don't have any other solution, you may want to format your internal SD and start out fresh. I use 64G Samsung class 10 and it works fine with data2sd. Good luck.
Click to expand...
Click to collapse
The problem looked the same, as it was -110, but might have been for different reason. And it havn't occured ever again so far, while with data2sd I had it few times a day after a while, so I guess it is the external SD fault after all.
I wonder why the manufacturers and users doesn't bother about the speed of internal memory. OFC most people look at the CPU, GPU and resolution when they buy tablets, but the speed of memory is also important parameter, especially in high-end devices.
Arquiteto said:
The problem looked the same, as it was -110, but might have been for different reason. And it havn't occured ever again so far, while with data2sd I had it few times a day after a while, so I guess it is the external SD fault after all.
I wonder why the manufacturers and users doesn't bother about the speed of internal memory. OFC most people look at the CPU, GPU and resolution when they buy tablets, but the speed of memory is also important parameter, especially in high-end devices.
Click to expand...
Click to collapse
I thought that you still have the same problem without the data2sd but it only happened once then you probably right about the defected external sd. I totally agree with you about the overall design of this tablet if it is intended for a high performance device but one year ago the technical specification was very impressive comparing with other product lines on the market. So to answer your question, I use it for an entertainment when I travel to kill time at the airport and check my personal email at the hotel. I don't expect much out of it and so far it does what it is supposed to do except for the slow internet. I found a solution with a custom rom...:good: I don't know what other users use it for and why manufacturer came up with that designed concept. I am guessing that they want more profit out of this product maybe.
Folks,
Just got my Moto G Gen3. Everything appears to be working perfectly fine, but I get the below backtrace in dmesg if I reboot the phone with the USB cable plugged in. This is on stock, unrooted, Lollipop 5.1. Could you guys possibly check if you get the same message in your kernel ring buffers when you reboot with the cable in? It's probably a software issue so nothing to worry about, but since this is on the stock ROM - which I expect to be QA'd for bugs - the backtrace does have me a bit worried that I might have received a defective unit.
Code:
<3>[ 0.742295,0] i2c-msm-v2 78b5000.i2c: msm_bus_scale_register_client(mstr-id:86):0xb (ok)
<3>[ 0.743063,0] power_supply max170xx_battery: driver failed to report `present' property: -11
<4>[ 0.743170,0] thermal thermal_zone0: failed to read out thermal zone 0
<3>[ 0.743357,0] power_supply max170xx_battery: driver failed to report `present' property: -11
<4>[ 0.744315,0] Battery Temp State = 1
<3>[ 0.744347,0] power_supply max170xx_battery: driver failed to report `present' property: -11
<3>[ 0.748545,0] BMS: bms_get_adc: vadc not found - defer probe rc=-517
<3>[ 0.748551,0] BMS: qpnp_vm_bms_probe: Failed to get adc rc=-517
<6>[ 0.748565,0] spmi qpnp-vm-bms-ebfb6a00: Driver qcom,qpnp-vm-bms requests probe deferral
<3>[ 0.748706,0] CHG: qpnp_lbc_probe: Failed to read DT properties rc=-517
<6>[ 0.748718,0] spmi qpnp-linear-charger-ebfb6800: Driver qcom,qpnp-linear-charger requests probe deferral
<6>[ 0.749148,0] CBL: qpnp_cbldet_probe: Probe usb=1
<3>[ 0.749707,0] unable to find DT imem DLOAD mode node
<3>[ 0.749980,0] unable to find DT imem EDLOAD mode node
<3>[ 0.752453,0] qpnp_adc_tm_channel_measure: chip not valid
<3>[ 0.752463,0] fan5404x-charger 1-006b: tm disable failed: -19
<6>[ 0.753984,0] fan54046_otg_vreg: no parameters
<3>[ 0.754294,0] fan5404x_charger_probe: vadc not ready, defer probe
<4>[ 0.855673,0] ------------[ cut here ]------------
<4>[ 0.855688,0] WARNING: at ../../../../../../kernel/drivers/regulator/core.c:4144 regulator_unregister+0xb4/0xb8()
<4>[ 0.855694,0] Modules linked in:
<4>[ 0.855727,0] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 3.10.49-g5fbdf50 #1
<4>[ 0.855747,0] [<c010be5c>] (unwind_backtrace+0x0/0xec) from [<c01099cc>] (show_stack+0x10/0x14)
<4>[ 0.855760,0] [<c01099cc>] (show_stack+0x10/0x14) from [<c011bf5c>] (warn_slowpath_common+0x54/0x6c)
<4>[ 0.855772,0] [<c011bf5c>] (warn_slowpath_common+0x54/0x6c) from [<c011c140>] (warn_slowpath_null+0x1c/0x24)
<4>[ 0.855783,0] [<c011c140>] (warn_slowpath_null+0x1c/0x24) from [<c0436848>] (regulator_unregister+0xb4/0xb8)
<4>[ 0.855795,0] [<c0436848>] (regulator_unregister+0xb4/0xb8) from [<c06d6474>] (fan5404x_charger_probe+0x814/0xb58)
<4>[ 0.855808,0] [<c06d6474>] (fan5404x_charger_probe+0x814/0xb58) from [<c05eebd0>] (i2c_device_probe+0xa4/0xec)
<4>[ 0.855821,0] [<c05eebd0>] (i2c_device_probe+0xa4/0xec) from [<c04bab00>] (driver_probe_device+0x104/0x23c)
<4>[ 0.855832,0] [<c04bab00>] (driver_probe_device+0x104/0x23c) from [<c04bad08>] (__driver_attach+0x8c/0x90)
<4>[ 0.855844,0] [<c04bad08>] (__driver_attach+0x8c/0x90) from [<c04b8ff0>] (bus_for_each_dev+0x60/0x94)
<4>[ 0.855855,0] [<c04b8ff0>] (bus_for_each_dev+0x60/0x94) from [<c04ba27c>] (bus_add_driver+0x1c4/0x250)
<4>[ 0.855866,0] [<c04ba27c>] (bus_add_driver+0x1c4/0x250) from [<c04bb2e4>] (driver_register+0x78/0x140)
<4>[ 0.855876,0] [<c04bb2e4>] (driver_register+0x78/0x140) from [<c05eea78>] (i2c_register_driver+0x30/0xb8)
<4>[ 0.855886,0] [<c05eea78>] (i2c_register_driver+0x30/0xb8) from [<c010064c>] (do_one_initcall+0x108/0x158)
<4>[ 0.855899,0] [<c010064c>] (do_one_initcall+0x108/0x158) from [<c1000c14>] (kernel_init_freeable+0x138/0x1d8)
<4>[ 0.855911,0] [<c1000c14>] (kernel_init_freeable+0x138/0x1d8) from [<c0a35e40>] (kernel_init+0x8/0x14c)
<4>[ 0.855922,0] [<c0a35e40>] (kernel_init+0x8/0x14c) from [<c0105c38>] (ret_from_fork+0x14/0x3c)
<4>[ 0.855959,0] ---[ end trace 86e3ab8c74ad6457 ]---
<6>[ 0.925770,0] i2c 1-006b: Driver fan5404x-charger requests probe deferral
Thanks a ton! :fingers-crossed:
I know it's a dead platform pretty much but here goes... I have a mangled GT-N8010. It's been fine for years, I even rooted it and installed nerdyblonde's blissrom image middle of last year. All of a sudden out of nowhere I get bootloop.
It's got TWRP on it and I notice that most of the partitions mount ro even though I have selected for them to be rw. Then I realise that they mount rw to start with then transition to ro due to filesystem errors. From dmesg:
Code:
<6>[ 806.261839] c0 binder: 1803:1803 transaction failed 29189, size 0-0
<6>[ 806.455283] c0 Atmel MXT1664S 3-004a: P: id[0]
<6>[ 806.519815] c0 Atmel MXT1664S 3-004a: R: id[0] M[0]
<3>[ 806.527889] c2 mmc0: mshci_check_sbc_status cmd response crc error
<3>[ 806.527925] c2 mmc0: it occurs a critical error on eMMC it'll try to recover eMMC to normal state
<6>[ 806.712682] c2 mmc0: recovering eMMC has been done
<3>[ 806.712698] c2 brq->sbc.opcode=23,brq->cmd.opcode=18.
<3>[ 806.712706] c2 brq->sbc.error=-110,brq->cmd.error=0, brq->stop.error=0,brq->data.error=0.
<3>[ 806.712747] c2 mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x900
<3>[ 806.712755] c2 mmcblk0: not retrying timeout
<3>[ 806.712813] c2 end_request: I/O error, dev mmcblk0, sector 6008856
<3>[ 806.712908] c2 CMD aborting case in MMC's block layer ret 0.
<3>[ 806.712916] c2 mmcblk0: CMD18, ARG=0x5bb018.
<3>[ 806.712921] c2 packed CMD type = 0.
<3>[ 806.712926] c2 mmc0, request returns 4.
<2>[ 806.713152] c1 EXT4-fs error (device mmcblk0p12): ext4_find_entry:934: inode #2: comm ls: reading directory lblock 0
<3>[ 806.713166] c1 Aborting journal on device mmcblk0p12-8.
<2>[ 806.713176] c1 EXT4-fs (mmcblk0p12): Remounting filesystem read-only
<6>[ 807.261975] c0 binder: 1803:1803 transaction failed 29189, size 0-0
<6>[ 808.262113] c0 binder: 1803:1803 transaction failed 29189, size 0-0
<6>[ 809.262253] c0 binder: 1803:1803 transaction failed 29189, size 0-0
<6>[ 810.262394] c0 binder: 1803:1803 transaction failed 29189, size 0-0
So my internal eMMC is broken. The broken sectors are all over the place too so I don't think I can partition around them with a custom PIT:
Code:
end_request: I/O error, dev mmcblk0, sector 180224
end_request: I/O error, dev mmcblk0, sector 209968
end_request: I/O error, dev mmcblk0, sector 1818496
end_request: I/O error, dev mmcblk0, sector 4685696
end_request: I/O error, dev mmcblk0, sector 5709696
end_request: I/O error, dev mmcblk0, sector 5726210
end_request: I/O error, dev mmcblk0, sector 6008856
end_request: I/O error, dev mmcblk0, sector 30769024
I think I have the latest 4.4.2 Samsung bootloader so what I can do from the bootloader is limited (basically just boot into odin/download mode or into TWRP - no fastboot. Obviously due to failed eMMC I get loads of NAND failures trying to do things with odin.
I would like to make use of the tablet for another 6 months or so, so has anyone ever had any success booting one of these from SD card?
Damn, sorry this should have gone in the Q&A forum. Could someone move it please? Sorry!
Use the report button .