Hi,
Awhile ago, when I was reviewing dmesg on my Gtab, I noticed that I was consistently getting two "bad block" messages. The Gtab itself had been running ok, so I had kind of ignored those.
In parallel with that, I've been trying to get a complete nvflash backup of the Gtab, using "nvflash -r --read X partX.img", to pull all of the partitions.
When doing this, I was able to retrieve all of the partitions from the Gtab, except for partition 11, which as I understand it, is, unfortunately the "system" partition.
I've tried this nvflash a number of times, and get the same error, "read failure". The error occurs near the end of the nvflash command, always with the same (byte?) count.
That got me started to thinking about the bad block messages I had seen in dmesg, and when I went to review dmesg again, sure enough, one of the bad blocks was in the "system" partition.
I am still on stock TNT on this Gtab. The "history" of it is:
Got/installed OTA 3389 after I powered up 1st time
Download 3452, and installed using stock recovery
Had a situation where things were FC'ing, a couple of weeks ago, so I had to install CWM, clear system/swap (2048/0), and then re-install 3452 using CWM. 3452 replaces CWM with stock recovery, so I then used stock recovery to re-install 3452 again (so, at that time, I installed 3452 twice, first with CWM, then using stock recovery).
At this point, I'm not 100% sure if the bad blocks displayed in dmesg have anything to do with not being able to "nvflash -r --read" partition 11, but I'd still like to be able to do the nvflash to backup the Gtab, so I'm hoping that someone here might have some information about these problems, and also some idea of how I could possibly eliminate the bad blocks.
Thanks,
Jim
Hi,
There're the dmesg lines:
<6>[ 6.509581] tegra_nand tegra_nand: tegra_nand_probe: probing (c053bc30)
<6>[ 6.516993] tegra_nand tegra_nand: tegra_nand_scan: found NAND chip (Vendor = 0xad, DevId = 0xdc)
<6>[ 6.576725] tegra_nand tegra_nand: Block 0x186 is bad [chip=0,offset=0x30c0000]
<6>[ 6.673896] tegra_nand tegra_nand: Block 0x43b is bad [chip=0,offset=0x8760000]
<5>[ 7.109313] 7 cmdlinepart partitions found on MTD device tegra_nand
<5>[ 7.115570] Creating 7 MTD partitions on "tegra_nand":
<5>[ 7.120711] 0x000000740000-0x000001740000 : "misc"
<5>[ 7.126240] 0x000003ce0000-0x000004ce0000 : "recovery"
<5>[ 7.131927] 0x000004d60000-0x000005d60000 : "boot"
<5>[ 7.137257] 0x000005de0000-0x0000125e0000 : "system"
<6>[ 7.142361] tegra_nand tegra_nand: Block 0x43b is bad [chip=0,offset=0x8760000]
<5>[ 7.150517] 0x000012680000-0x00001ff80000 : "cache"
<5>[ 7.156331] 0x0000017c0000-0x000001bc0000 : "bootbmp"
<5>[ 7.161933] 0x000001c40000-0x000003c40000 : "logodata"
<6>[ 7.167158] tegra_nand tegra_nand: Block 0x186 is bad [chip=0,offset=0x30c0000]
I guess what I'm worried about is that if I can't nvflash read, then if I ever have to use nvflash to flash, that won't work, I.e. won't be able to recover using nvflash ...
Jim
Hi,
I've been using nvflash on Windows, so I figured I'd try the Linux version, but (sigh), I just did that, using the bootloader.bin and nvflash from Bekit's dropbox, and got exactly the same error when trying to do the --read for partition 11:
Code:
[email protected]:/nvflash# ./nvflash -r --read 11 jl-part11.img
Nvflash started
[resume mode]
receiving file: jl-part11.img, expected size: 209715200 bytes
/ 209584128/209715200 bytes receiveddata receive failure NvError 0x120000
command failure: read failed
Double sigh ...
FYI, it stops with the read failed at exactly the same place that the Windows nvflash.exe did for that --read...
Since I went through the trouble of installing Ubuntu to try this, I also tried --getpartitiontable, to see if output text or binary (on Windows, the nvflash.exe in Bekit's dropbox outputs binary), and found that the Linux nvflash (from Bekit's dropbox) DOES output a text file, so at least that's ONE mystery that was solved, i.e.:
Bekit Linux nvflash - outputs text for --getpartitiontable
Bekit Windows nvflash.exe - outputs binary for --getpartitiontable
Nvidia SDK Windows nvflash.exe - outputs text for --getpartitiontable
Jim
maybe run badblocks on that partition assuming you can access it from the shell. read only of course
muqali said:
maybe run badblocks on that partition assuming you can access it from the shell. read only of course
Click to expand...
Click to collapse
What is badblocks? Is it a tool already on the Gtab?
Jim
Hi,
One other thing I've noticed, and been wondering about is that the size if partition 11 in the partition table is about 209mb, and the nvflash --read fails just before reading the full size. But, the actual amount of space that's used in /system is only about 113mb. Finally, the partition 11 IMG file in Bekit's recovery is also about 113mb.
So I'm wondering if maybe nvflash has some kind of Max filesize, and that's why the --read fails.
If that's the case, then the question is how Bekit pulled the partition 11 that he has in his recovery files?
Does anyone know?
Jim
I've been continuing to research this, and I've some discussions mentioning that formatting /system *MIGHT* eliminate the bad block.
I tried adb'ing into the Gtab while CWM was running, but it looks like the .8 version doesn't have a format command, but I notice that CWM does have a menu item for 'format system' under mounts.
So I'm thinking:
- in CWM, format system, then
- use CWM Advanced restore to restore ONLY system
Looking for comments as to whether (1) this would be safe and (2) might get rid of the bad block?
Jim
badblocks is a badblocks checking/recording program. I'm not 100% sure what ADB is, my understanding is it is basically like a serial tty into the OS running on the tab. Correct me if I'm wrong.
The format commands under linux would be something like
mkfs.ext2
mkfs.ext3
mkfs.msdos
et cetera.
They might also be mke2fs -options
Again, I'm not sure, I'm not familiar with Android shells and what is available under them. Try some of those though and see if you get joy.
muqali said:
badblocks is a badblocks checking/recording program. I'm not 100% sure what ADB is, my understanding is it is basically like a serial tty into the OS running on the tab. Correct me if I'm wrong.
The format commands under linux would be something like
mkfs.ext2
mkfs.ext3
mkfs.msdos
et cetera.
They might also be mke2fs -options
Again, I'm not sure, I'm not familiar with Android shells and what is available under them. Try some of those though and see if you get joy.
Click to expand...
Click to collapse
Yes, adb gives you a connection from workstation to device, you can do stuff like push/pull files and shell into the device.
When you boot into CWM (vs. TNT), there's a different set of commands avail. I'll check about what you suggested, but (1) the /system is yaffs and (2) per the post I just made, CWM already has menu item for formatting system.
Thanks,
Jim
Hi,
I just tried what I was thinking of a couple of posts above:
- in CWM, format system, then
- use CWM Advanced restore to restore ONLY system
I was checking dmesg throughout, while adb'ing into CWM, and it still kept showing the bad block, so I tried it a couple of times, but the bad block persisted, so it must be a "hard" bad block that format doesn't clear ...
Not sure where to go with this at this point. The bottom line is that:
- It appears that the bad block in the /system partition is preventing the nvflash --read from working on partition 11.
- Doing format SYSTEM in CWM doesn't clear the bad block
I'm not so much concerned about the --read problem, but more concerned about if this will result in some as-yet unforeseen problem in the future, i.e., if I do an update later, and then bad block prevents the update from working.
I'm also wondering if something like these bad blocks may be the reason for some of the "mysterious" problems I've seen posted at various times, e.g., the acore FCs and FCs appearing out of nowhere, having to re-partition, etc.? If so, these almost seem like they might be categorized as a "latent defect" type of thing?
Jim
Hi,
I've posted an inquiry on VS's support website about the bad blocks. We'll see if/when they respond....
Jim
Is there not tab completion when you're at an ADB shell?
muqali said:
Is there not tab completion when you're at an ADB shell?
Click to expand...
Click to collapse
I noticed that also ... It's kind of weird, because you can access command history using up/down arrows, ala bash, but doesn't look like it does command/tab completion. I think it's because of some kind of key mapping or something.
However, what you can do is go into "ash" (similar to bash) instead. Then tab completion works, I think. On the regular (not adb) terminal, you have to do "busybox ash" to go into ash. Not sure whether there's a native ash or if you also have to use the busybox ash in adb.
Jim
jimcpl said:
Hi,
I've posted an inquiry on VS's support website about the bad blocks. We'll see if/when they respond....
Jim
Click to expand...
Click to collapse
FYI, I got a response to my inquiry:
"Thank you for contacting ViewSonic Technical Support. I understand that you have concerns with our ViewSonic G-Tablet. I care about your concern and I am glad you took the time to contact us.
I do apologize but we have dedicated department that supports our G-Tablets. You can contact them direct at 866-501-6405 between 9AM-9PM CST, Monday through Friday."
Is that 866 # "US merchants"?
Jim
Dmesg
<6>[ 7.333176] tegra_nand tegra_nand: tegra_nand_probe: probing (c06bfc90)
<6>[ 7.340674] tegra_nand tegra_nand: tegra_nand_scan: found NAND chip (Vendor = 0xad, DevId = 0xdc)
<6>[ 7.590637] tegra_nand tegra_nand: Block 0x706 is bad [chip=0,offset=0xe0c0000]
<6>[ 7.603285] tegra_nand tegra_nand: Block 0x72c is bad [chip=0,offset=0xe580000]
<6>[ 7.610782] tegra_nand tegra_nand: Block 0x72e is bad [chip=0,offset=0xe5c0000]
<6>[ 7.618292] tegra_nand tegra_nand: Block 0x730 is bad [chip=0,offset=0xe600000]
<6>[ 7.625800] tegra_nand tegra_nand: Block 0x732 is bad [chip=0,offset=0xe640000]
<6>[ 7.633305] tegra_nand tegra_nand: Block 0x734 is bad [chip=0,offset=0xe680000]
<6>[ 7.640808] tegra_nand tegra_nand: Block 0x736 is bad [chip=0,offset=0xe6c0000]
<6>[ 7.648320] tegra_nand tegra_nand: Block 0x738 is bad [chip=0,offset=0xe700000]
<6>[ 7.655823] tegra_nand tegra_nand: Block 0x73a is bad [chip=0,offset=0xe740000]
<6>[ 7.663338] tegra_nand tegra_nand: Block 0x73c is bad [chip=0,offset=0xe780000]
<6>[ 7.670839] tegra_nand tegra_nand: Block 0x73e is bad [chip=0,offset=0xe7c0000]
<6>[ 7.678330] tegra_nand tegra_nand: Block 0x740 is bad [chip=0,offset=0xe800000]
<6>[ 7.685848] tegra_nand tegra_nand: Block 0x742 is bad [chip=0,offset=0xe840000]
<6>[ 7.714226] tegra_nand tegra_nand: Block 0x7d7 is bad [chip=0,offset=0xfae0000]
<6>[ 7.722450] tegra_nand tegra_nand: Block 0x7de is bad [chip=0,offset=0xfbc0000]
<6>[ 7.867189] tegra_nand tegra_nand: Block 0xbab is bad [chip=0,offset=0x17560000]
<6>[ 7.935604] tegra_nand tegra_nand: Block 0xd5f is bad [chip=0,offset=0x1abe0000]
<6>[ 7.943348] tegra_nand tegra_nand: Block 0xd62 is bad [chip=0,offset=0x1ac40000]
<6>[ 8.024165] tegra_nand tegra_nand: Block 0xf67 is bad [chip=0,offset=0x1ece0000]
<5>[ 8.053153] 7 cmdlinepart partitions found on MTD device tegra_nand
<5>[ 8.059414] Creating 7 MTD partitions on "tegra_nand":
<5>[ 8.064556] 0x000000bc0000-0x000001bc0000 : "misc"
<5>[ 8.070089] 0x000003cc0000-0x000004cc0000 : "recovery"
<5>[ 8.075777] 0x000004d40000-0x000005d40000 : "boot"
<5>[ 8.081123] 0x000005dc0000-0x0000125c0000 : "system"
<6>[ 8.086407] tegra_nand tegra_nand: Block 0x706 is bad [chip=0,offset=0xe0c0000]
<6>[ 8.093786] tegra_nand tegra_nand: Block 0x72c is bad [chip=0,offset=0xe580000]
<6>[ 8.101148] tegra_nand tegra_nand: Block 0x72e is bad [chip=0,offset=0xe5c0000]
<6>[ 8.108515] tegra_nand tegra_nand: Block 0x730 is bad [chip=0,offset=0xe600000]
<6>[ 8.115880] tegra_nand tegra_nand: Block 0x732 is bad [chip=0,offset=0xe640000]
<6>[ 8.123248] tegra_nand tegra_nand: Block 0x734 is bad [chip=0,offset=0xe680000]
<6>[ 8.130604] tegra_nand tegra_nand: Block 0x736 is bad [chip=0,offset=0xe6c0000]
<6>[ 8.137969] tegra_nand tegra_nand: Block 0x738 is bad [chip=0,offset=0xe700000]
<6>[ 8.145336] tegra_nand tegra_nand: Block 0x73a is bad [chip=0,offset=0xe740000]
<6>[ 8.152702] tegra_nand tegra_nand: Block 0x73c is bad [chip=0,offset=0xe780000]
<6>[ 8.160058] tegra_nand tegra_nand: Block 0x73e is bad [chip=0,offset=0xe7c0000]
<6>[ 8.167426] tegra_nand tegra_nand: Block 0x740 is bad [chip=0,offset=0xe800000]
<6>[ 8.174793] tegra_nand tegra_nand: Block 0x742 is bad [chip=0,offset=0xe840000]
<6>[ 8.182184] tegra_nand tegra_nand: Block 0x7d7 is bad [chip=0,offset=0xfae0000]
<6>[ 8.189555] tegra_nand tegra_nand: Block 0x7de is bad [chip=0,offset=0xfbc0000]
<5>[ 8.197497] 0x000012640000-0x00001ff80000 : "cache"
<6>[ 8.202585] tegra_nand tegra_nand: Block 0xbab is bad [chip=0,offset=0x17560000]
<6>[ 8.210142] tegra_nand tegra_nand: Block 0xd5f is bad [chip=0,offset=0x1abe0000]
<6>[ 8.217595] tegra_nand tegra_nand: Block 0xd62 is bad [chip=0,offset=0x1ac40000]
<6>[ 8.225172] tegra_nand tegra_nand: Block 0xf67 is bad [chip=0,offset=0x1ece0000]
<4>[ 19.428515] Failed Ddk Rd. Bad block Error code=0xb0010 at chip=0,block=2683
<3>[ 19.437234] tegra_nand tegra_nand: Failed to read OOB 0x14f68800
Nosunshine said:
<6>[ 7.333176] tegra_nand tegra_nand: tegra_nand_probe: probing (c06bfc90)
<6>[ 7.340674] tegra_nand tegra_nand: tegra_nand_scan: found NAND chip (Vendor = 0xad, DevId = 0xdc)
<6>[ 7.590637] tegra_nand tegra_nand: Block 0x706 is bad [chip=0,offset=0xe0c0000]
<6>[ 7.603285] tegra_nand tegra_nand: Block 0x72c is bad [chip=0,offset=0xe580000]
<6>[ 7.610782] tegra_nand tegra_nand: Block 0x72e is bad [chip=0,offset=0xe5c0000]
<6>[ 7.618292] tegra_nand tegra_nand: Block 0x730 is bad [chip=0,offset=0xe600000]
<6>[ 7.625800] tegra_nand tegra_nand: Block 0x732 is bad [chip=0,offset=0xe640000]
<6>[ 7.633305] tegra_nand tegra_nand: Block 0x734 is bad [chip=0,offset=0xe680000]
<6>[ 7.640808] tegra_nand tegra_nand: Block 0x736 is bad [chip=0,offset=0xe6c0000]
<6>[ 7.648320] tegra_nand tegra_nand: Block 0x738 is bad [chip=0,offset=0xe700000]
<6>[ 7.655823] tegra_nand tegra_nand: Block 0x73a is bad [chip=0,offset=0xe740000]
<6>[ 7.663338] tegra_nand tegra_nand: Block 0x73c is bad [chip=0,offset=0xe780000]
<6>[ 7.670839] tegra_nand tegra_nand: Block 0x73e is bad [chip=0,offset=0xe7c0000]
<6>[ 7.678330] tegra_nand tegra_nand: Block 0x740 is bad [chip=0,offset=0xe800000]
<6>[ 7.685848] tegra_nand tegra_nand: Block 0x742 is bad [chip=0,offset=0xe840000]
<6>[ 7.714226] tegra_nand tegra_nand: Block 0x7d7 is bad [chip=0,offset=0xfae0000]
<6>[ 7.722450] tegra_nand tegra_nand: Block 0x7de is bad [chip=0,offset=0xfbc0000]
<6>[ 7.867189] tegra_nand tegra_nand: Block 0xbab is bad [chip=0,offset=0x17560000]
<6>[ 7.935604] tegra_nand tegra_nand: Block 0xd5f is bad [chip=0,offset=0x1abe0000]
<6>[ 7.943348] tegra_nand tegra_nand: Block 0xd62 is bad [chip=0,offset=0x1ac40000]
<6>[ 8.024165] tegra_nand tegra_nand: Block 0xf67 is bad [chip=0,offset=0x1ece0000]
<5>[ 8.053153] 7 cmdlinepart partitions found on MTD device tegra_nand
<5>[ 8.059414] Creating 7 MTD partitions on "tegra_nand":
<5>[ 8.064556] 0x000000bc0000-0x000001bc0000 : "misc"
<5>[ 8.070089] 0x000003cc0000-0x000004cc0000 : "recovery"
<5>[ 8.075777] 0x000004d40000-0x000005d40000 : "boot"
<5>[ 8.081123] 0x000005dc0000-0x0000125c0000 : "system"
<6>[ 8.086407] tegra_nand tegra_nand: Block 0x706 is bad [chip=0,offset=0xe0c0000]
<6>[ 8.093786] tegra_nand tegra_nand: Block 0x72c is bad [chip=0,offset=0xe580000]
<6>[ 8.101148] tegra_nand tegra_nand: Block 0x72e is bad [chip=0,offset=0xe5c0000]
<6>[ 8.108515] tegra_nand tegra_nand: Block 0x730 is bad [chip=0,offset=0xe600000]
<6>[ 8.115880] tegra_nand tegra_nand: Block 0x732 is bad [chip=0,offset=0xe640000]
<6>[ 8.123248] tegra_nand tegra_nand: Block 0x734 is bad [chip=0,offset=0xe680000]
<6>[ 8.130604] tegra_nand tegra_nand: Block 0x736 is bad [chip=0,offset=0xe6c0000]
<6>[ 8.137969] tegra_nand tegra_nand: Block 0x738 is bad [chip=0,offset=0xe700000]
<6>[ 8.145336] tegra_nand tegra_nand: Block 0x73a is bad [chip=0,offset=0xe740000]
<6>[ 8.152702] tegra_nand tegra_nand: Block 0x73c is bad [chip=0,offset=0xe780000]
<6>[ 8.160058] tegra_nand tegra_nand: Block 0x73e is bad [chip=0,offset=0xe7c0000]
<6>[ 8.167426] tegra_nand tegra_nand: Block 0x740 is bad [chip=0,offset=0xe800000]
<6>[ 8.174793] tegra_nand tegra_nand: Block 0x742 is bad [chip=0,offset=0xe840000]
<6>[ 8.182184] tegra_nand tegra_nand: Block 0x7d7 is bad [chip=0,offset=0xfae0000]
<6>[ 8.189555] tegra_nand tegra_nand: Block 0x7de is bad [chip=0,offset=0xfbc0000]
<5>[ 8.197497] 0x000012640000-0x00001ff80000 : "cache"
<6>[ 8.202585] tegra_nand tegra_nand: Block 0xbab is bad [chip=0,offset=0x17560000]
<6>[ 8.210142] tegra_nand tegra_nand: Block 0xd5f is bad [chip=0,offset=0x1abe0000]
<6>[ 8.217595] tegra_nand tegra_nand: Block 0xd62 is bad [chip=0,offset=0x1ac40000]
<6>[ 8.225172] tegra_nand tegra_nand: Block 0xf67 is bad [chip=0,offset=0x1ece0000]
<4>[ 19.428515] Failed Ddk Rd. Bad block Error code=0xb0010 at chip=0,block=2683
<3>[ 19.437234] tegra_nand tegra_nand: Failed to read OOB 0x14f68800
Click to expand...
Click to collapse
Hi,
Oh my!
Did you try the nvflash yet? It looks like the bad blocks are in both system and cache?
Jim
I'll try to get that up by tomorrow, I just reloaded Win7 and have yet to force feed it the usb drivers to get adb/nvflash working again.
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.
Hi folks,
I'm hoping someone can help me get my head around loading drivers in android.
I'm very familiar with Linux, so I understand drivers compiled into the kernel vs loading modular drivers. I also understand module versions in that they should match the installed kernel.
I have a cyanogenmod ROM that was built for a device similar to mine except that the wifi/bt drivers do not work. I have a ROM where these DO work.
I have extracted the boot.img from each ROM and I'm trying to combine the kernel that works with the cyanogenmod boot.img to get a working device. But the drivers have me a bit stumped.
On the device that works, here is what I see during boot in dmesg:
Code:
<6>[ 2.273829] Bluetooth: HCI UART driver ver 2.2
<6>[ 2.278272] Bluetooth: HCI H4 protocol initialized
<6>[ 2.283084] Bluetooth: HCI BCSP protocol initialized
<6>[ 2.288045] Bluetooth: HCILL protocol initialized
<7>[ 2.292983] [wifi]: Select sdio wifi: bcm40183 !!
<7>[ 2.297878] [mmc_pm]: SDIO card gpio init is OK !!
<7>[ 2.302753] [mmc]: sunximmc_init
<7>[ 2.306208] [mmc]: sunxi mmc controller using config : 0xb
<7>[ 2.311762] [mmc]: sunxi-mmc.0: pdev->name: sunxi-mmc, pdev->id: 0
<7>[ 2.318190] [mmc]: mmc 0 power off !!
<7>[ 2.321978] [mmc]: mmc0 Probe: base:0xe8916000 irq:32 dma:0 pdes:0xe704c000, ret 0.
<7>[ 2.329650] [mmc]: sunxi-mmc.1: pdev->name: sunxi-mmc, pdev->id: 1
<7>[ 2.336069] [mmc]: mmc 1 power off !!
<7>[ 2.339801] [mmc]: mmc1 Probe: base:0xe8918000 irq:33 dma:0 pdes:0xe7050000, ret 0.
<7>[ 2.347496] [mmc]: sunxi-mmc.3: pdev->name: sunxi-mmc, pdev->id: 3
<7>[ 2.353876] [mmc]: mmc 3 power off !!
<7>[ 2.357601] [mmc]: mmc3 Probe: base:0xe891a000 irq:35 dma:0 pdes:0xe7054000, ret 0.
This is below the line that says
Code:
<7>[ 2.081010] insmod_device_driver
So I'm assuming this is a module that is being loaded. I have however compared the init.sun4i.rc on both and made sure I'm loading the same drivers. I'm also loading the kernel from the working ROM.
This is what I see in the broken setup:
Code:
<6>[ 2.261673] Bluetooth: HCI UART driver ver 2.2
<6>[ 2.266116] Bluetooth: HCI H4 protocol initialized
<6>[ 2.270928] Bluetooth: HCI BCSP protocol initialized
<6>[ 2.275891] Bluetooth: HCILL protocol initialized
<7>[ 2.280811] [mmc_pm]: no sdio card used in configuration
<7>[ 2.286118] [mmc]: sunximmc_init
<7>[ 2.289602] [mmc]: sunxi mmc controller using config : 0xb
<7>[ 2.295210] [mmc]: sunxi-mmc.0: pdev->name: sunxi-mmc, pdev->id: 0
<7>[ 2.301688] [mmc]: mmc 0 power off !!
<7>[ 2.305451] [mmc]: mmc0 Probe: base:0xe8916000 irq:32 dma:0 pdes:0xe704c000, ret 0.
<7>[ 2.313150] [mmc]: sunxi-mmc.1: pdev->name: sunxi-mmc, pdev->id: 1
<7>[ 2.319533] [mmc]: mmc 1 power off !!
<7>[ 2.323293] [mmc]: mmc1 Probe: base:0xe8918000 irq:33 dma:0 pdes:0xe7050000, ret 0.
<7>[ 2.330984] [mmc]: sunxi-mmc.3: pdev->name: sunxi-mmc, pdev->id: 3
<7>[ 2.337351] [mmc]: mmc 3 power off !!
<7>[ 2.341106] [mmc]: mmc3 Probe: base:0xe891a000 irq:35 dma:0 pdes:0xe7054000, ret 0.
So this seems to be complaining about no SD card being available - is this a correct assumption?
I also assume this is a card used for storage, and wifi/bt using the SDIO standard.
Would the wifi driver be being loaded from the SD card? If so, where? It may just be something else I need to add to the zip file for the new ROM.
When I compare dmesg between the two, I don't see anything obvious that loads differently, so it's got me stumped as to what's happening.
Can anyone shed some light on how the working ROM might be loading the bcm40183 driver?
in my android tablet I noticed how the /system folder is actually stored in nandd partition, and refered to by the main nand partition via a symlink. Since /system/vendor/modules (where my bcm40183 module is stored) is a symlink path to a location on a nand partition, I assume the OS reaches that location using a mmc device (maybe because it is flash memory after all). So your problem isn't about a missing SD card, but about a missing nand partition...or a broken link. Apparently, from one android version to the next, the number of partitions varies. On mine, there are 9 partitions!
Since you know about modules and versions, do you know how I could get that bcm40183 module working in linux? I can't find a kernel with that module on offer and I dont know how to add modules on already compiled kernels. I'd love to be able to insmod this bcm40183 version 3.0.8 in my sunxi-3.4 kernel...
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 .