Database Users

Update SPL without SD Card

Something happened to my phone.. think its from updating the SPL, wifi and sd card will no longer work.
Anyone know of a way to downgrade SPL without SD Card access?

i do not know the exact steps but you should be able to flash it via fastboot since it does not use the sdcard. but you will need adb working on your computer

KHannel said:
Something happened to my phone.. think its from updating the SPL, wifi and sd card will no longer work.
Anyone know of a way to downgrade SPL without SD Card access?
Click to expand...
Click to collapse
I find it hard to believe that upgrading your spl would effect your wifi and sd card. You able to give more details.

More Details
Well here is what happened and where the phone is now.
I had installed Drizzy Touch Flo 2.8 had it up and running ( Haykuro's new SPL and yes, I upgraded Radio first ) , everything was working fine. Took the back off my phone and somehow the battery fell out. Put the battery back in and the phone was stuck in the htc boot loop. Went into recovery to see what was happening and the phone wasn't able to mount the SD Card. Went into /dev/block and there was no mmcblk0 showing at all.
I got home, I put the card into a reader on my computer and it read just fine, all partitions and everyhing intact. I figured maybe it messed up a sector and just wasn't being read, so just for the heck of it I wiped the partition table and repartitioned it. Put it back into the phone and still stuck at htc boot loop with no mmcblk0.
So I flashed the phone back to the 1.5 dev rom from the HTC web site ( using fastboot ). Got the phone up and running but now it shows an error on the notification bar "SD Card Removed". I've tried 3 different SD Cards, nothing. Here is the dmesg upon insertion of an SD Card:
<7>[ 77.724578] msmsdcc_platform_status_irq: 194
<6>[ 77.725433] mmc1: Slot status change detected (0 -> 1)
<4>[ 80.221893] trout_sdslot_switchvdd: Setting level to 2950
<3>[ 80.230895] mmc1: Command timeout
<3>[ 80.237640] mmc1: Command timeout
<3>[ 80.243896] mmc1: Command timeout
<3>[ 80.250183] mmc1: Command timeout
<3>[ 80.256835] mmc1: Command timeout
<3>[ 80.263549] mmc1: Command timeout
<3>[ 80.269775] mmc1: Command timeout
<3>[ 80.276214] mmc1: Command timeout
<3>[ 80.282623] mmc1: Command timeout
<3>[ 80.288909] mmc1: Command timeout
<4>[ 80.294464] trout_sdslot_switchvdd: Disabling SD slot power
#
Had taken a break from working the SD Card issue, and decided to check my email. Turned on wifi after about 60 seconds I get an error saying "Unable to start Wifi". After that error it won't even attempt to turn it on again. Here is dmesg while turning on wifi
<6>[ 181.843994] TIWLAN: Driver loading
<4>[ 181.844665] wifi_probe
<4>[ 181.844940] trout_wifi_power: 1
<4>[ 182.051116] trout_wifi_reset: 0
<4>[ 182.102478] trout_wifi_set_carddetect: 1
<7>[ 182.102783] mmc0: card_present 1
<6>[ 182.103057] mmc0: Slot status change detected (0 -> 1)
<3>[ 184.613708] mmc0: Command timeout
<4>[ 184.620727] mmc0: card claims to support voltages below the defined range. These will be ignored.
<4>[ 184.621582] mmc0: SDIO card claims to support the incompletely defined 'low voltage range'. This will be ignored.
<6>[ 184.629089] mmc0: new SDIO card at address 0001
<6>[ 184.635101] TIWLAN: Found SDIO controller (vendor 0x104c, device 0x9066)
<6>[ 184.641021] TIWLAN: Driver initialized (rc 0)
<3>[ 185.643066] mmc0: Data timeout
<3>[ 185.643524] SDIO_SyncRead: Read operation failed (-110) (retries = 5)
<3>[ 186.646179] mmc0: Data timeout
<3>[ 186.646789] SDIO_SyncRead: Read operation failed (-110) (retries = 4)
<3>[ 187.649719] mmc0: Data timeout
<3>[ 187.650329] SDIO_SyncRead: Read operation failed (-110) (retries = 3)
<3>[ 187.651336] SDIO_SyncRead: Retry succeeded
<4>[ 187.651794] TIWLAN: invalid chip id = 0x 0 0 0 0!
<6>[ 187.652221] TIWLAN: Driver loaded
<3>[ 189.092773] mmc0: Data timeout
<3>[ 189.093170] SDIO_SyncRead: Read operation failed (-110) (retries = 5)
<3>[ 190.095825] mmc0: Data timeout
<3>[ 190.096466] SDIO_SyncRead: Read operation failed (-110) (retries = 4)
<3>[ 191.098968] mmc0: Data timeout
<3>[ 191.099945] SDIO_SyncRead: Read operation failed (-110) (retries = 3)
<3>[ 191.100616] SDIO_SyncRead: Retry succeeded
<3>[ 192.101654] mmc0: Data timeout
<3>[ 192.102264] SDIO_SyncRead: Read operation failed (-110) (retries = 5)
<3>[ 193.104766] mmc0: Data timeout
<3>[ 193.105743] SDIO_SyncRead: Read operation failed (-110) (retries = 4)
<3>[ 194.106292] mmc0: Data timeout
<3>[ 194.107238] SDIO_SyncRead: Read operation failed (-110) (retries = 3)
<3>[ 194.107940] SDIO_SyncRead: Retry succeeded
<3>[ 195.125518] mmc0: Data timeout
<3>[ 195.126220] SDIO_SyncRead: Read operation failed (-110) (retries = 5)
<3>[ 196.128784] mmc0: Data timeout
<3>[ 196.129760] SDIO_SyncRead: Read operation failed (-110) (retries = 4)
<3>[ 197.132293] mmc0: Data timeout
<3>[ 197.132934] SDIO_SyncRead: Read operation failed (-110) (retries = 3)
<3>[ 197.133972] SDIO_SyncRead: Retry succeeded
<3>[ 198.136474] mmc0: Data timeout
<3>[ 198.137481] SDIO_SyncRead: Read operation failed (-110) (retries = 5)
<3>[ 199.140197] mmc0: Data timeout
<3>[ 199.140838] SDIO_SyncRead: Read operation failed (-110) (retries = 4)
<3>[ 200.143768] mmc0: Data timeout
<3>[ 200.144409] SDIO_SyncRead: Read operation failed (-110) (retries = 3)
<3>[ 200.145416] SDIO_SyncRead: Retry succeeded
<3>[ 201.148010] mmc0: Data timeout
<3>[ 201.148651] SDIO_SyncRead: Read operation failed (-110) (retries = 5)
<3>[ 202.151855] mmc0: Data timeout
<3>[ 202.152496] SDIO_SyncRead: Read operation failed (-110) (retries = 4)
<3>[ 203.155426] mmc0: Data timeout
<3>[ 203.156066] SDIO_SyncRead: Read operation failed (-110) (retries = 3)
<3>[ 203.157073] SDIO_SyncRead: Retry succeeded
<3>[ 204.161895] mmc0: Data timeout
<3>[ 204.162536] SDIO_SyncRead: Read operation failed (-110) (retries = 5)
<3>[ 205.165588] mmc0: Data timeout
<3>[ 205.166229] SDIO_SyncRead: Read operation failed (-110) (retries = 4)
<3>[ 206.169158] mmc0: Data timeout
<3>[ 206.169799] SDIO_SyncRead: Read operation failed (-110) (retries = 3)
<3>[ 206.170806] SDIO_SyncRead: Retry succeeded
<3>[ 207.173858] mmc0: Data timeout
<3>[ 207.174499] SDIO_SyncRead: Read operation failed (-110) (retries = 5)
<3>[ 208.177551] mmc0: Data timeout
<3>[ 208.178192] SDIO_SyncRead: Read operation failed (-110) (retries = 4)
<3>[ 209.181152] mmc0: Data timeout
<3>[ 209.181793] SDIO_SyncRead: Read operation failed (-110) (retries = 3)
<3>[ 209.182464] SDIO_SyncRead: Retry succeeded
<3>[ 210.188385] mmc0: Data timeout
<3>[ 210.189025] SDIO_SyncRead: Read operation failed (-110) (retries = 5)
<3>[ 211.192230] mmc0: Data timeout
<3>[ 211.192871] SDIO_SyncRead: Read operation failed (-110) (retries = 4)
<3>[ 212.195373] mmc0: Data timeout
<3>[ 212.196380] SDIO_SyncRead: Read operation failed (-110) (retries = 3)
<3>[ 212.197052] SDIO_SyncRead: Retry succeeded
<3>[ 213.276336] mmc0: Data timeout
<3>[ 213.277008] SDIO_SyncRead: Read operation failed (-110) (retries = 5)
<3>[ 214.279937] mmc0: Data timeout
<3>[ 214.280578] SDIO_SyncRead: Read operation failed (-110) (retries = 4)
<3>[ 215.283233] mmc0: Data timeout
<3>[ 215.284210] SDIO_SyncRead: Read operation failed (-110) (retries = 3)
<3>[ 215.284881] SDIO_SyncRead: Retry succeeded
<3>[ 216.287963] mmc0: Data timeout
<3>[ 216.288604] SDIO_SyncRead: Read operation failed (-110) (retries = 5)
<3>[ 217.291259] mmc0: Data timeout
<3>[ 217.292236] SDIO_SyncRead: Read operation failed (-110) (retries = 4)
<3>[ 218.295043] mmc0: Data timeout
<3>[ 218.295684] SDIO_SyncRead: Read operation failed (-110) (retries = 3)
<3>[ 218.296722] SDIO_SyncRead: Retry succeeded
<3>[ 219.299468] mmc0: Data timeout
<3>[ 219.300476] SDIO_SyncRead: Read operation failed (-110) (retries = 5)
<3>[ 220.303131] mmc0: Data timeout
<3>[ 220.304107] SDIO_SyncRead: Read operation failed (-110) (retries = 4)
<3>[ 221.306610] mmc0: Data timeout
<3>[ 221.307250] SDIO_SyncRead: Read operation failed (-110) (retries = 3)
<3>[ 221.308258] SDIO_SyncRead: Retry succeeded
<3>[ 222.310913] mmc0: Data timeout
<3>[ 222.311889] SDIO_SyncRead: Read operation failed (-110) (retries = 5)
<3>[ 223.314453] mmc0: Data timeout
<3>[ 223.315093] SDIO_SyncRead: Read operation failed (-110) (retries = 4)
#
I'm not exactly blaming the SPL, but its that and the Radio are the ONLY things left that has not been changed. I can't downgrade the radio without first changing the SPL because we know that will brick with Haykuro's SPL that I'm running.
Hmm, someone had suggested a short in the phone... startin to look more and more like that now that I'm looking at the Wifi dmesg output.
I've loaded every partition on the phone, boot, recovery, system, etc. However, I think SPL is the only thing I can't change without SD Card access. I've thought of maybe being able to re-write the recovery to have it read from another directory than the SD Card... anyone ever done this?
Thanks for the help,
Ken

[Q] Run 6.1.0-RC2-Aria ROM in SDK emulator ?

Hi all,
I have downloaded the 6.1.0-RC2-Aria ROM a couple of days ago, installed it on my phone and everything is working great - thanks again attn1!
Now I would like to do some testing/dev with it; instead of tampering with my device.
I created a NANdroid back-up and then tried running the ROM on the SDK emulator following threads instructions found over here and other forums, e.g. :
http://forum.xda-developers.com/archive/index.php/t-572497.html
http://forum.xda-developers.com/showthread.php?t=525930&page=2
http://android.modaco.com/content/g...p-and-running-a-full-rom-with-the-market-etc/
The emulator seems to be running OK, but the kernel gets stuck before it even gives me the boot animation. (- c.f. below for the parameters passed and the kernel boot log; adb logcat does not report anything at all -)
Anyone has been able to run this particular ROM on the SDK emulator or may give me pointers as to how to do so successfully?
Thank you.
+++++++++++++++++++++++++++++++++++++++++++++++++++++
C:\android-sdk-windows\tools>emulator -avd testing -show-kernel -sdcard mycard
Uncompressing Linux............................................................................................. done, booting the kernel.
Initializing cgroup subsys cpu
Linux version 2.6.29-00261-g0097074-dirty ([email protected]) (gcc version 4.4.0 (GCC) ) #20 Wed Mar 31 09:54:02 PDT 2010
CPU: ARM926EJ-S [41069265] revision 5 (ARMv5TEJ), cr=00093177
CPU: VIVT data cache, VIVT instruction cache
Machine: Goldfish
Memory policy: ECC disabled, Data cache writeback
Built 1 zonelists in Zone order, mobility grouping on. Total pages: 130048
Kernel command line: qemu=1 console=ttyS0 android.checkjni=1 android.qemud=ttyS1 android.ndns=1
Unknown boot option `android.checkjni=1': ignoring
Unknown boot option `android.qemud=ttyS1': ignoring
Unknown boot option `android.ndns=1': ignoring
PID hash table entries: 2048 (order: 11, 8192 bytes)
Console: colour dummy device 80x30
Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
Memory: 512MB = 512MB total
Memory: 515840KB available (2616K code, 681K data, 104K init)
Calibrating delay loop... 238.38 BogoMIPS (lpj=1191936)
Mount-cache hash table entries: 512
Initializing cgroup subsys debug
Initializing cgroup subsys cpuacct
Initializing cgroup subsys freezer
CPU: Testing write buffer coherency: ok
net_namespace: 520 bytes
NET: Registered protocol family 16
bio: create slab <bio-0> at 0
NET: Registered protocol family 2
IP route cache hash table entries: 16384 (order: 4, 65536 bytes)
TCP established hash table entries: 65536 (order: 7, 524288 bytes)
TCP bind hash table entries: 65536 (order: 6, 262144 bytes)
TCP: Hash tables configured (established 65536 bind 65536)
TCP reno registered
NET: Registered protocol family 1
checking if image is initramfs... it is
Freeing initrd memory: 160K
goldfish_new_pdev goldfish_interrupt_controller at ff000000 irq -1
goldfish_new_pdev goldfish_device_bus at ff001000 irq 1
goldfish_new_pdev goldfish_timer at ff003000 irq 3
goldfish_new_pdev goldfish_rtc at ff010000 irq 10
goldfish_new_pdev goldfish_tty at ff002000 irq 4
goldfish_new_pdev goldfish_tty at ff011000 irq 11
goldfish_new_pdev smc91x at ff012000 irq 12
goldfish_new_pdev goldfish_fb at ff013000 irq 13
goldfish_new_pdev goldfish_mmc at ff005000 irq 14
goldfish_new_pdev goldfish_memlog at ff006000 irq -1
goldfish_new_pdev goldfish_events at ff014000 irq 15
goldfish_new_pdev goldfish_nand at ff015000 irq -1
goldfish_new_pdev goldfish-switch at ff016000 irq 16
goldfish_new_pdev goldfish-switch at ff017000 irq 17
goldfish_pdev_worker registered goldfish_interrupt_controller
goldfish_pdev_worker registered goldfish_device_bus
goldfish_pdev_worker registered goldfish_timer
goldfish_pdev_worker registered goldfish_rtc
goldfish_pdev_worker registered goldfish_tty
goldfish_pdev_worker registered goldfish_tty
goldfish_pdev_worker registered smc91x
goldfish_pdev_worker registered goldfish_fb
goldfish_pdev_worker registered goldfish_mmc
goldfish_pdev_worker registered goldfish_memlog
goldfish_pdev_worker registered goldfish_events
goldfish_pdev_worker registered goldfish_nand
goldfish_pdev_worker registered goldfish-switch
goldfish_pdev_worker registered goldfish-switch
ashmem: initialized
Installing knfsd (copyright (C) 1996 [email protected]).
yaffs Mar 26 2010 13:38:48 Installing.
msgmni has been set to 1008
alg: No test for stdrng (krng)
io scheduler noop registered
io scheduler anticipatory registered (default)
io scheduler deadline registered
io scheduler cfq registered
allocating frame buffer 320 * 480, got ffa00000
Console: switching to colour frame buffer device 40x30
console [ttyS0] enabled
brd: module loaded
loop: module loaded
nbd: registered device at major 43
smc91x.c: v1.1, sep 22 2004 by Nicolas Pitre <[email protected]>
eth0 (smc91x): not using net_device_ops yet
eth0: SMC91C11xFD (rev 1) at e084c000 IRQ 12 [nowait]
eth0: Ethernet addr: 52:54:00:12:34:56
goldfish nand dev0: size 6ea0000, page 2048, extra 64, erase 131072
goldfish nand dev1: size 4000000, page 2048, extra 64, erase 131072
goldfish nand dev2: size 4000000, page 2048, extra 64, erase 131072
mice: PS/2 mouse device common for all mice
*** events probe ***
events_probe() addr=0xe0854000 irq=15
events_probe() keymap=qwerty2
input: qwerty2 as /devices/virtual/input/input0
goldfish_rtc goldfish_rtc: rtc core: registered goldfish_rtc as rtc0
device-mapper: uevent: version 1.0.3
device-mapper: ioctl: 4.14.0-ioctl (2008-04-23) initialised: [email protected]
logger: created 64K log 'log_main'
logger: created 256K log 'log_events'
logger: created 64K log 'log_radio'
IPv4 over IPv4 tunneling driver
GRE over IPv4 tunneling driver
TCP cubic registered
NET: Registered protocol family 17
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
802.1Q VLAN Support v1.8 Ben Greear <[email protected]>
All bugs added by David S. Miller <[email protected]>
VFP support v0.3: implementor 41 architecture 1 part 10 variant 9 rev 0
goldfish_rtc goldfish_rtc: setting system clock to 2010-12-05 03:32:33 UTC (1291
519953)
Freeing init memory: 104K
mmc0: new SD card at address e118
mmcblk0: mmc0:e118 SU02G 1.00 GiB
mmcblk0:
init: cannot open '/initlogo.rle'
yaffs: dev is 32505856 name is "mtdblock0"
yaffs: passed flags ""
yaffs: Attempting MTD mount on 31.0, "mtdblock0"
yaffs_read_super: isCheckpointed 0
save exit: isCheckpointed 0
yaffs: dev is 32505857 name is "mtdblock1"
yaffs: passed flags ""
yaffs: Attempting MTD mount on 31.1, "mtdblock1"
yaffs: restored from checkpoint
yaffs_read_super: isCheckpointed 1
yaffs: dev is 32505858 name is "mtdblock2"
yaffs: passed flags ""
yaffs: Attempting MTD mount on 31.2, "mtdblock2"
yaffs: restored from checkpoint
yaffs_read_super: isCheckpointed 1
init: cannot find '/system/etc/install-recovery.sh', disabling 'flash_recovery'
request_suspend_state: wakeup (3->0) at 4206070790 (2010-12-05 03:32:36.48957032
7 UTC)
init: untracked pid 34 exited
init: untracked pid 42 exited
request_suspend_state: wakeup (0->0) at 4256118986 (2010-12-05 03:32:36.53963374
7 UTC)
init: untracked pid 44 exited
init: untracked pid 53 exited
request_suspend_state: wakeup (0->0) at 9387505566 (2010-12-05 03:32:41.67101886
1 UTC)
init: untracked pid 54 exited
init: untracked pid 60 exited
init: untracked pid 68 exited
init: untracked pid 69 exited
request_suspend_state: wakeup (0->0) at 14518491192 (2010-12-05 03:32:46.8020076
30 UTC)
init: untracked pid 74 exited
init: untracked pid 82 exited
init: untracked pid 83 exited
request_suspend_state: wakeup (0->0) at 19655651551 (2010-12-05 03:32:51.9391665
92 UTC)
init: untracked pid 89 exited
request_suspend_state: wakeup (0->0) at 24731037643 (2010-12-05 03:32:57.0145514
97 UTC)
init: critical process 'servicemanager' exited 4 times in 4 minutes; rebooting i
nto recovery mode
save exit: isCheckpointed 1
save exit: isCheckpointed 1
Restarting system with command 'recovery'.
Reboot failed -- System halted
+++++++++++++++++++++++++++++++++++++++++++++++++++++

LOL, root the emulated device!

I would if I knew how to do so on the emulator itself
I have rooted my actual device, but I have no idea how to accomplish this on the emulator; could you elaborate or send links on how to do this please?
I have googled and nothing relevant has showed up other than the emulator is supposed to be already root-ed; by issuing adb root I get:
C:\android-sdk\android-sdk-windows\tools>adb root
adbd is already running as root
I also tried running the emulator with the '-shell' parameter, but got the same result and the boot process gets stuck as well...
A little bit of extra guidance would be great.
Thank you.

CM7 And A Case Of The Wonks With LOGCAT

Hi All,
I would have posted in the developer forum under one of the CM7 threads but this is my first post on xda so here it goes:
I've been following the developer forums for a while now and I too am plagued with the wonks on my N1 with CM7. For me the wonkiness = phone not being responsive with black screen and no audio when making a phone call, then after about 15 to 25 seconds the screen shows the call and audio is back on).
This is understandable since it's still in an alpha state not ready for production so I wanted to post my logcat (running build 27) snapshot (attached) to see if it will help some developer figure out how to fix the wonk of terror.
Here's how I reproduce the wonk:
I turn my N1 on and as soon as it boots up I press the power button to shut the screen off. After about 2 to 3 minutes I press the power button, unlock my phone and try to make a call. I am guaranteed a wonk every time.
My temporary fix is the CM7 Dewonkificator Add-on. It definitely fixes my N1's wonkiness problem for the time being.
Thanks for listening!

markhm1978 said:
Hi All,
I would have posted in the developer forum under one of the CM7 threads but this is my first post on xda so here it goes:
I've been following the developer forums for a while now and I too am plagued with the wonks on my N1 with CM7. For me the wonkiness = phone not being responsive with black screen and no audio when making a phone call, then after about 15 to 25 seconds the screen shows the call and audio is back on).
This is understandable since it's still in an alpha state not ready for production so I wanted to post my logcat (running build 27) snapshot (attached) to see if it will help some developer figure out how to fix the wonk of terror.
Here's how I reproduce the wonk:
I turn my N1 on and as soon as it boots up I press the power button to shut the screen off. After about 2 to 3 minutes I press the power button, unlock my phone and try to make a call. I am guaranteed a wonk every time.
My temporary fix is the CM7 Dewonkificator Add-on. It definitely fixes my N1's wonkiness problem for the time being.
Thanks for listening!
Click to expand...
Click to collapse
If I'm not mistaken, CM has noted the source of the error (mic) and they are conjuring up a fix. It should most likely be ready to go in one of the next few nightlies.

Thanks! Didn't happen to come across that piece of information in my travels on xda forums.

markhm1978 said:
Thanks! Didn't happen to come across that piece of information in my travels on xda forums.
Click to expand...
Click to collapse
You must've taken a right instead of a left...

rickytenzer said:
If I'm not mistaken, CM has noted the source of the error (mic) and they are conjuring up a fix. It should most likely be ready to go in one of the next few nightlies.
Click to expand...
Click to collapse
That first attempt fix was released in build 27 earlier today.
Unfortunately some peoples are still reporting the call wonkiness.

rickytenzer said:
You must've taken a right instead of a left...
Click to expand...
Click to collapse
Yeah, it's pretty easy to get lost in all of the chocolaty goodness here.

baseballfanz said:
That first attempt fix was released in build 27 earlier today.
Unfortunately some peoples are still reporting the call wonkiness.
Click to expand...
Click to collapse
Thanks for the info. I am one of the unfortunate ones.

Just tried Build 28 and the phone call still wonks out. logcat snapshot attached.

Call Wonks for me on Build 29. Dewonkificator is still working as a temporary fix.

It's been hit or miss with me - no wonks until I think build 17 and then twenty-something...
It's still worth it - you get wonks in brand new phones sometimes and the solution isn't likely contained in a flash update within another 24 hours!
I will suffer the pain of wonkiness until it is finally solved by those brilliant minds working away on polishing this gorgeous CM7 port. Thank you - your efforts are REALLY appreciated here

should post this on the cyan forums if u havent already, im sure they could use it if it actually works.

Basil 123 said:
It's been hit or miss with me - no wonks until I think build 17 and then twenty-something...
It's still worth it - you get wonks in brand new phones sometimes and the solution isn't likely contained in a flash update within another 24 hours!
I will suffer the pain of wonkiness until it is finally solved by those brilliant minds working away on polishing this gorgeous CM7 port. Thank you - your efforts are REALLY appreciated here
Click to expand...
Click to collapse
I too love the CM7 port! So much that I'm about to donate $20 to buy Cyanogen some beer.
I figured instead of *****ing about how my phone calls are wonking out, I'd post some info to try and help with the situation and keep track of any wonks per build in this thread.
Have you tried Dewonkificator yet? It works really well for me. Here's the link: http://forum.xda-developers.com/showthread.php?t=935250

Buck Shot said:
should post this on the cyan forums if u havent already, im sure they could use it if it actually works.
Click to expand...
Click to collapse
I am creating an account on the Cyan forums now and will post a link to this thread.
Thanks for the suggestion.

Build 30, Wonks for me. Dewonkificator still working as a temp fix.

rickytenzer said:
You must've taken a right instead of a left...
Click to expand...
Click to collapse
lol you should have said: Sorry, but our princess is in another castle.
logcats are only half, posting dmesg's would be more helpful if any dev was going to check out your logs.

fitsnugly said:
lol you should have said: Sorry, but our princess is in another castle.
logcats are only half, posting dmesg's would be more helpful if any dev was going to check out your logs.
Click to expand...
Click to collapse
Thanks! I will look in to how to capture the dmesg's. While I look, do you have any suggestions for capturing this info?

fitsnugly said:
lol you should have said: Sorry, but our princess is in another castle.
logcats are only half, posting dmesg's would be more helpful if any dev was going to check out your logs.
Click to expand...
Click to collapse
Okay, figured it out. Attached the dmesg of my Wonkiness for Build 30.

Hi. I am on #31. The wonky is still here. dmesg output attached.
View attachment 2011-02-04-04.txt
I suppose this is a log of the wonky call:
Code:
<6>[ 644.924621] request_suspend_state: wakeup (3->0) at 640894655059 (2011-02-04 07:41:27.847267217 UTC)
<6>[ 644.927429] lcdc_resume: resuming
<6>[ 644.951568] mahimahi_ts_power: power 1
<6>[ 644.989440] lcdc_unblank: ()
<6>[ 644.990478] samsung_oled_panel_unblank: +()
<6>[ 645.281188] samsung_oled_panel_unblank: -()
<6>[ 648.953430] pcm_out: open
<6>[ 648.953918] acdb: 588 bytes for device 607, rate 48000.
<6>[ 650.724761] a1026_set_config: change to mode 1
<6>[ 650.724975] a1026_set_config: block write start (size = 56)
<6>[ 650.730865] a1026_set_config: block write end
<6>[ 650.755981] a1026_set_config: CMD ACK block read start
<3>[ 653.738586] msm_i2c msm_i2c.0: Error waiting for notbusy (0)
<3>[ 653.739074] msm_i2c msm_i2c.0: Transaction timed out
<3>[ 653.739868] msm_i2c msm_i2c.0: Error during data xfer 3e (-110)
<4>[ 653.740448] msm_i2c msm_i2c.0: Still the bus master, status 9b00, intf 0
<4>[ 653.741271] msm_i2c msm_i2c.0: i2c_scl: 0, i2c_sda: 1
<4>[ 653.918853] msm_i2c msm_i2c.0: Bus still busy, status 9b01, intf 200
<3>[ 653.919738] a1026_i2c_read: transfer error -110
<3>[ 653.920166] a1026_set_config: CMD ACK block read error
<6>[ 653.920928] a1026_i2c_sw_reset: 80020000
<3>[ 655.900756] msm_i2c msm_i2c.0: Error waiting for notbusy (1)
<4>[ 655.901336] msm_i2c msm_i2c.0: Still the bus master, status 9b01, intf 0
<4>[ 655.902130] msm_i2c msm_i2c.0: i2c_scl: 0, i2c_sda: 0
<4>[ 656.080993] msm_i2c msm_i2c.0: Bus still busy, status 9b01, intf 200
<3>[ 656.081573] a1026_i2c_write: transfer error -16
<3>[ 656.082000] a1026_ioctl: A1026_SET_CONFIG (1) error -110!
<6>[ 656.082824] a1026_set_config: change to mode 1
<6>[ 656.083282] a1026_set_config: block write start (size = 56)
<3>[ 658.063629] msm_i2c msm_i2c.0: Error waiting for notbusy (1)
<4>[ 658.064239] msm_i2c msm_i2c.0: Still the bus master, status 9b01, intf 0
<4>[ 658.065032] msm_i2c msm_i2c.0: i2c_scl: 0, i2c_sda: 0
<4>[ 658.243072] msm_i2c msm_i2c.0: Bus still busy, status 9b01, intf 200
<3>[ 658.243927] a1026_i2c_write: transfer error -16
<3>[ 658.244384] A1026 CMD block write error!
<6>[ 658.245117] a1026_i2c_sw_reset: 80020000
<3>[ 660.224914] msm_i2c msm_i2c.0: Error waiting for notbusy (1)
<4>[ 660.225830] msm_i2c msm_i2c.0: Still the bus master, status 9b01, intf 0
<4>[ 660.226318] msm_i2c msm_i2c.0: i2c_scl: 0, i2c_sda: 0
<4>[ 660.405181] msm_i2c msm_i2c.0: Bus still busy, status 9b01, intf 200
<3>[ 660.405761] a1026_i2c_write: transfer error -16
<3>[ 660.406524] a1026_ioctl: A1026_SET_CONFIG (1) error -16!
<6>[ 660.407012] a1026_set_config: change to mode 1
<6>[ 660.407440] a1026_set_config: block write start (size = 56)
<3>[ 662.387023] msm_i2c msm_i2c.0: Error waiting for notbusy (1)
<4>[ 662.387634] msm_i2c msm_i2c.0: Still the bus master, status 9b01, intf 0
<4>[ 662.388427] msm_i2c msm_i2c.0: i2c_scl: 0, i2c_sda: 0
<4>[ 662.567291] msm_i2c msm_i2c.0: Bus still busy, status 9b01, intf 200
<3>[ 662.568206] a1026_i2c_write: transfer error -16
<3>[ 662.568634] A1026 CMD block write error!
<6>[ 662.569427] a1026_i2c_sw_reset: 80020000
<3>[ 664.549560] msm_i2c msm_i2c.0: Error waiting for notbusy (1)
<4>[ 664.550476] msm_i2c msm_i2c.0: Still the bus master, status 9b01, intf 0
<4>[ 664.550964] msm_i2c msm_i2c.0: i2c_scl: 0, i2c_sda: 0
<4>[ 664.729370] msm_i2c msm_i2c.0: Bus still busy, status 9b01, intf 200
<3>[ 664.729919] a1026_i2c_write: transfer error -16
<3>[ 664.730712] a1026_ioctl: A1026_SET_CONFIG (1) error -16!
<6>[ 664.731170] a1026_set_config: change to mode 1
<6>[ 664.731628] a1026_set_config: block write start (size = 56)
<3>[ 666.721221] msm_i2c msm_i2c.0: Error waiting for notbusy (1)
<4>[ 666.721801] msm_i2c msm_i2c.0: Still the bus master, status 9b01, intf 0
<4>[ 666.722625] msm_i2c msm_i2c.0: i2c_scl: 0, i2c_sda: 0
<4>[ 666.901550] msm_i2c msm_i2c.0: Bus still busy, status 9b01, intf 200
<3>[ 666.902435] a1026_i2c_write: transfer error -16
<3>[ 666.902862] A1026 CMD block write error!
<6>[ 666.903656] a1026_i2c_sw_reset: 80020000
<3>[ 668.883361] msm_i2c msm_i2c.0: Error waiting for notbusy (1)
<4>[ 668.884277] msm_i2c msm_i2c.0: Still the bus master, status 9b01, intf 0
<4>[ 668.884765] msm_i2c msm_i2c.0: i2c_scl: 0, i2c_sda: 0
<4>[ 669.063629] msm_i2c msm_i2c.0: Bus still busy, status 9b01, intf 200
<3>[ 669.064178] a1026_i2c_write: transfer error -16
<3>[ 669.064941] a1026_ioctl: A1026_SET_CONFIG (1) error -16!
<3>[ 669.067352] msm_i2c msm_i2c.0: IRQ but nothing to do!, status 8302
<4>[ 669.083496] msm_i2c msm_i2c.0: Warning bus was busy (102)
<4>[ 669.085998] msm_i2c msm_i2c.0: 1 unrequested bytes read
<6>[ 669.127288] a1026_bootup_init: starting to load image (863 passes)...
<6>[ 672.336761] a1026_bootup_init: firmware loaded successfully
<6>[ 672.341888] batt: 54%, 3791 mV, -277 mA (-246 avg), 30.3 C, 728 mAh
<6>[ 672.497192] a1026_bootup_init: initialized!
<6>[ 672.658020] a1026_set_config: change to mode 1
<6>[ 672.658477] a1026_set_config: block write start (size = 56)
<6>[ 672.664947] a1026_set_config: block write end
<6>[ 672.687408] a1026_set_config: CMD ACK block read start
<6>[ 672.693542] a1026_set_config: CMD ACK block read end
<6>[ 672.747741] acdb: 974 bytes for device 2, rate 48000.
<6>[ 672.909057] acdb: 819 bytes for device 1, rate 8000.
<6>[ 673.097686] capella_cm3602_open
<6>[ 673.097869] capella_cm3602_ioctl cmd 2
<6>[ 673.098022] capella_cm3602_enable
<6>[ 673.098175] proximity 1
<6>[ 673.121124] request_suspend_state: wakeup (0->0) at 669063729306 (2011-02-04 07:41:56.016341464 UTC)
<6>[ 682.863403] capella_cm3602_ioctl cmd 2
<6>[ 682.863739] capella_cm3602_disable
<6>[ 682.864044] capella_cm3602_release
<6>[ 682.864349] capella_cm3602_disable
<6>[ 682.864868] capella_cm3602_disable: already disabled
<6>[ 682.874908] a1026_set_config: change to mode 13
<6>[ 682.875457] a1026_set_config: block write start (size = 16)
<6>[ 682.877563] a1026_set_config: block write end
<6>[ 682.907012] a1026_set_config: CMD ACK block read start
<6>[ 682.908966] a1026_set_config: CMD ACK block read end
<6>[ 682.909271] acdb: 871 bytes for device 507, rate 8000.
<6>[ 685.739837] pcm_out: release
PS @markhm1978
Compared your dmesg output with mine. It is quite the same...

dolphin77 said:
Hi. I am on #31. The wonky is still here. dmesg output attached.
View attachment 508500
I suppose this is a log of the wonky call:
Code:
<6>[ 644.924621] request_suspend_state: wakeup (3->0) at 640894655059 (2011-02-04 07:41:27.847267217 UTC)
<6>[ 644.927429] lcdc_resume: resuming
<6>[ 644.951568] mahimahi_ts_power: power 1
<6>[ 644.989440] lcdc_unblank: ()
<6>[ 644.990478] samsung_oled_panel_unblank: +()
<6>[ 645.281188] samsung_oled_panel_unblank: -()
<6>[ 648.953430] pcm_out: open
<6>[ 648.953918] acdb: 588 bytes for device 607, rate 48000.
<6>[ 650.724761] a1026_set_config: change to mode 1
<6>[ 650.724975] a1026_set_config: block write start (size = 56)
<6>[ 650.730865] a1026_set_config: block write end
<6>[ 650.755981] a1026_set_config: CMD ACK block read start
<3>[ 653.738586] msm_i2c msm_i2c.0: Error waiting for notbusy (0)
<3>[ 653.739074] msm_i2c msm_i2c.0: Transaction timed out
<3>[ 653.739868] msm_i2c msm_i2c.0: Error during data xfer 3e (-110)
<4>[ 653.740448] msm_i2c msm_i2c.0: Still the bus master, status 9b00, intf 0
<4>[ 653.741271] msm_i2c msm_i2c.0: i2c_scl: 0, i2c_sda: 1
<4>[ 653.918853] msm_i2c msm_i2c.0: Bus still busy, status 9b01, intf 200
<3>[ 653.919738] a1026_i2c_read: transfer error -110
<3>[ 653.920166] a1026_set_config: CMD ACK block read error
<6>[ 653.920928] a1026_i2c_sw_reset: 80020000
<3>[ 655.900756] msm_i2c msm_i2c.0: Error waiting for notbusy (1)
<4>[ 655.901336] msm_i2c msm_i2c.0: Still the bus master, status 9b01, intf 0
<4>[ 655.902130] msm_i2c msm_i2c.0: i2c_scl: 0, i2c_sda: 0
<4>[ 656.080993] msm_i2c msm_i2c.0: Bus still busy, status 9b01, intf 200
<3>[ 656.081573] a1026_i2c_write: transfer error -16
<3>[ 656.082000] a1026_ioctl: A1026_SET_CONFIG (1) error -110!
<6>[ 656.082824] a1026_set_config: change to mode 1
<6>[ 656.083282] a1026_set_config: block write start (size = 56)
<3>[ 658.063629] msm_i2c msm_i2c.0: Error waiting for notbusy (1)
<4>[ 658.064239] msm_i2c msm_i2c.0: Still the bus master, status 9b01, intf 0
<4>[ 658.065032] msm_i2c msm_i2c.0: i2c_scl: 0, i2c_sda: 0
<4>[ 658.243072] msm_i2c msm_i2c.0: Bus still busy, status 9b01, intf 200
<3>[ 658.243927] a1026_i2c_write: transfer error -16
<3>[ 658.244384] A1026 CMD block write error!
<6>[ 658.245117] a1026_i2c_sw_reset: 80020000
<3>[ 660.224914] msm_i2c msm_i2c.0: Error waiting for notbusy (1)
<4>[ 660.225830] msm_i2c msm_i2c.0: Still the bus master, status 9b01, intf 0
<4>[ 660.226318] msm_i2c msm_i2c.0: i2c_scl: 0, i2c_sda: 0
<4>[ 660.405181] msm_i2c msm_i2c.0: Bus still busy, status 9b01, intf 200
<3>[ 660.405761] a1026_i2c_write: transfer error -16
<3>[ 660.406524] a1026_ioctl: A1026_SET_CONFIG (1) error -16!
<6>[ 660.407012] a1026_set_config: change to mode 1
<6>[ 660.407440] a1026_set_config: block write start (size = 56)
<3>[ 662.387023] msm_i2c msm_i2c.0: Error waiting for notbusy (1)
<4>[ 662.387634] msm_i2c msm_i2c.0: Still the bus master, status 9b01, intf 0
<4>[ 662.388427] msm_i2c msm_i2c.0: i2c_scl: 0, i2c_sda: 0
<4>[ 662.567291] msm_i2c msm_i2c.0: Bus still busy, status 9b01, intf 200
<3>[ 662.568206] a1026_i2c_write: transfer error -16
<3>[ 662.568634] A1026 CMD block write error!
<6>[ 662.569427] a1026_i2c_sw_reset: 80020000
<3>[ 664.549560] msm_i2c msm_i2c.0: Error waiting for notbusy (1)
<4>[ 664.550476] msm_i2c msm_i2c.0: Still the bus master, status 9b01, intf 0
<4>[ 664.550964] msm_i2c msm_i2c.0: i2c_scl: 0, i2c_sda: 0
<4>[ 664.729370] msm_i2c msm_i2c.0: Bus still busy, status 9b01, intf 200
<3>[ 664.729919] a1026_i2c_write: transfer error -16
<3>[ 664.730712] a1026_ioctl: A1026_SET_CONFIG (1) error -16!
<6>[ 664.731170] a1026_set_config: change to mode 1
<6>[ 664.731628] a1026_set_config: block write start (size = 56)
<3>[ 666.721221] msm_i2c msm_i2c.0: Error waiting for notbusy (1)
<4>[ 666.721801] msm_i2c msm_i2c.0: Still the bus master, status 9b01, intf 0
<4>[ 666.722625] msm_i2c msm_i2c.0: i2c_scl: 0, i2c_sda: 0
<4>[ 666.901550] msm_i2c msm_i2c.0: Bus still busy, status 9b01, intf 200
<3>[ 666.902435] a1026_i2c_write: transfer error -16
<3>[ 666.902862] A1026 CMD block write error!
<6>[ 666.903656] a1026_i2c_sw_reset: 80020000
<3>[ 668.883361] msm_i2c msm_i2c.0: Error waiting for notbusy (1)
<4>[ 668.884277] msm_i2c msm_i2c.0: Still the bus master, status 9b01, intf 0
<4>[ 668.884765] msm_i2c msm_i2c.0: i2c_scl: 0, i2c_sda: 0
<4>[ 669.063629] msm_i2c msm_i2c.0: Bus still busy, status 9b01, intf 200
<3>[ 669.064178] a1026_i2c_write: transfer error -16
<3>[ 669.064941] a1026_ioctl: A1026_SET_CONFIG (1) error -16!
<3>[ 669.067352] msm_i2c msm_i2c.0: IRQ but nothing to do!, status 8302
<4>[ 669.083496] msm_i2c msm_i2c.0: Warning bus was busy (102)
<4>[ 669.085998] msm_i2c msm_i2c.0: 1 unrequested bytes read
<6>[ 669.127288] a1026_bootup_init: starting to load image (863 passes)...
<6>[ 672.336761] a1026_bootup_init: firmware loaded successfully
<6>[ 672.341888] batt: 54%, 3791 mV, -277 mA (-246 avg), 30.3 C, 728 mAh
<6>[ 672.497192] a1026_bootup_init: initialized!
<6>[ 672.658020] a1026_set_config: change to mode 1
<6>[ 672.658477] a1026_set_config: block write start (size = 56)
<6>[ 672.664947] a1026_set_config: block write end
<6>[ 672.687408] a1026_set_config: CMD ACK block read start
<6>[ 672.693542] a1026_set_config: CMD ACK block read end
<6>[ 672.747741] acdb: 974 bytes for device 2, rate 48000.
<6>[ 672.909057] acdb: 819 bytes for device 1, rate 8000.
<6>[ 673.097686] capella_cm3602_open
<6>[ 673.097869] capella_cm3602_ioctl cmd 2
<6>[ 673.098022] capella_cm3602_enable
<6>[ 673.098175] proximity 1
<6>[ 673.121124] request_suspend_state: wakeup (0->0) at 669063729306 (2011-02-04 07:41:56.016341464 UTC)
<6>[ 682.863403] capella_cm3602_ioctl cmd 2
<6>[ 682.863739] capella_cm3602_disable
<6>[ 682.864044] capella_cm3602_release
<6>[ 682.864349] capella_cm3602_disable
<6>[ 682.864868] capella_cm3602_disable: already disabled
<6>[ 682.874908] a1026_set_config: change to mode 13
<6>[ 682.875457] a1026_set_config: block write start (size = 16)
<6>[ 682.877563] a1026_set_config: block write end
<6>[ 682.907012] a1026_set_config: CMD ACK block read start
<6>[ 682.908966] a1026_set_config: CMD ACK block read end
<6>[ 682.909271] acdb: 871 bytes for device 507, rate 8000.
<6>[ 685.739837] pcm_out: release
PS @markhm1978
Compared your dmesg output with mine. It is quite the same...
Click to expand...
Click to collapse
It is quite the same. I am on 31 also, still experiencing the Wonkiness. Will post more logs when 32 hits.

Wonks for me on Build 32. Dewonkificator still working as a temporary fix: http://forum.xda-developers.com/showthread.php?t=935250

Boot from external SD?

So my tablet has been out of commission for a few months.. The battery drained fully one day and after charging it back up, it wouldn't boot (stuck on cyanogen boot screen) or go into recovery so I tried to re-flash the rom and then it got stuck in APX... so long story short, and a lot of experimentation later, I was able to reflash a working recovery and upgrade to the v8 bootloader, but I think my emmc is shot. --> When I try to flash a rom now it tells me that it can't mount certain partitions and what not, so! since some partitions apparently work, is it possible to flash a custom kernel or boot or something that looks at the sd card for the actual rom?
Read through another thread earlier today about figuring out if your emmc is hosed and ran dmesg | grep mmc in fastboot >>
Code:
<5>[ 0.000000] Kernel command line: tegraid=20.1.4.0.0 [email protected] androidbo
ot.serialno=[omitted] video=tegrafb console=none debug_uartport=hsport us
bcore.old_scheme_first=1 [email protected] [email protected]
brand=acer target_product=a500_ww_gen1 tegraboot=sdmmc gpt gpt_sector=15628287 a
ndroidboot.carrier=wifi-only bootloader_ver=0.03.14-MUL
<4>[ 3.323447] mmc0: Invalid maximum block size, assuming 512 bytes
<7>[ 3.323892] Registered led device: mmc0::
<6>[ 3.324098] mmc0: SDHCI controller on tegra [sdhci-tegra.3] using ADMA
<4>[ 3.324377] mmc1: Invalid maximum block size, assuming 512 bytes
<6>[ 3.324540] mmc1: no vmmc regulator found
<7>[ 3.324684] Registered led device: mmc1::
<6>[ 3.324846] mmc1: SDHCI controller on tegra [sdhci-tegra.2] using ADMA
<4>[ 3.325308] mmc2: Invalid maximum block size, assuming 512 bytes
<6>[ 3.325401] mmc2: no vmmc regulator found
<7>[ 3.325613] Registered led device: mmc2::
<6>[ 3.325772] mmc2: SDHCI controller on tegra [sdhci-tegra.0] using ADMA
<6>[ 3.417646] mmc0: new high speed MMC card at address 0001
<6>[ 3.418071] mmcblk0: mmc0:0001 M8G2FA 7.45 GiB
<6>[ 3.420953] mmcblk0: p1 p2 p3 p4 p5 p6 p7
<6>[ 3.654402] mmc1: new high speed SDHC card at address aaaa
<6>[ 3.654751] mmcblk1: mmc1:aaaa SU32G 29.7 GiB
<6>[ 3.657460] mmcblk1: p1
<3>[ 4.159931] EXT4-fs (mmcblk0p4): VFS: Can't find ext4 filesystem
<3>[ 5.586322] EXT4-fs (mmcblk0p4): VFS: Can't find ext4 filesystem
<3>[ 5.963153] EXT4-fs (mmcblk0p4): VFS: Can't find ext4 filesystem
<3>[ 6.356707] EXT4-fs (mmcblk0p4): VFS: Can't find ext4 filesystem
<3>[ 145.099265] EXT4-fs (mmcblk0p4): VFS: Can't find ext4 filesystem
<3>[ 145.541972] EXT4-fs (mmcblk0p4): VFS: Can't find ext4 filesystem
<3>[ 145.968406] EXT4-fs (mmcblk0p4): VFS: Can't find ext4 filesystem

Internal memory not working: host doesn't support card's voltages

A friend of mine got a new tablet and gave me his older S7-105.
He tried to upgrade to android 4.2.2 and repartition internal sd to have more internal space, and somewhere in the process his internal sd card seems to be dead.
After a couple of days reading this and some other forums, I have finally been able to install PAC-man 23 JB 4.2.2 rom, but all without external sd card. I tried to access the internal sd card from all systems: 2.1-upd1, 2.2.2 and 4.2.2, but no success.
I have also tried downgrading and zeroing the mbr with dd if=/dev/zero of=/dev/block/mmcblk0
but it just creates a 204mb file in /dev/block/mmcblk0 as /dev/block/mmcblk0 doesn't exist.
Now I have PAC-man 23 JB 4.2.2, and I have manually installed parted binaries.
This is what I get in dmesg related with mmc.
Code:
~/data/berserker.android.apps.sshdroid/home $ dmesg|grep -i mmc
[ 1.261768] [qsd8x50_init_mmc,4148] request GPIO 157 OK
[ 1.261927] [qsd8x50_init_mmc,4155] configure GPIO 157 OK
[ 4.133880] [vreg_mmc_control,3635] Switching ON vreg_mmc OK
[ 4.134412] [vreg_mmc_control,3641] vreg_mmc control status: vreg_sts=00000002 sdccid=1 on=1
[ 4.142679] mmc0: Qualcomm MSM SDCC at 0x00000000a0300000 irq 24,221 dma 8
[ 4.149306] mmc0: 8 bit data mode disabled
[ 4.153476] mmc0: 4 bit data mode enabled
[ 4.157375] mmc0: polling status mode disabled
[ 4.161794] mmc0: MMC clock 144000 -> 64000000 Hz, PCLK 64000000 Hz
[ 4.168154] mmc0: Slot eject status = 0
[ 4.171863] mmc0: Power save feature enable = 1
[ 4.176492] mmc0: DM non-cached buffer at ffd52000, dma_addr 0x3fb93000
[ 4.182975] mmc0: DM cmd busaddr 0x3fb93000, cmdptr busaddr 0x3fb93c00
[ 4.203892] [vreg_mmc_control,3641] vreg_mmc control status: vreg_sts=00000006 sdccid=2 on=1
[ 4.206968] mmc1: Qualcomm MSM SDCC at 0x00000000a0400000 irq 26,0 dma 8
[ 4.213593] mmc1: 8 bit data mode disabled
[ 4.217583] mmc1: 4 bit data mode enabled
[ 4.221663] mmc1: polling status mode disabled
[ 4.226000] mmc1: MMC clock 144000 -> 64000000 Hz, PCLK 64000000 Hz
[ 4.232341] mmc1: Slot eject status = 1
[ 4.236067] mmc1: Power save feature enable = 1
[ 4.240574] mmc1: DM non-cached buffer at ffd53000, dma_addr 0x3fb94000
[ 4.247282] mmc1: DM cmd busaddr 0x3fb94000, cmdptr busaddr 0x3fb94c00
[ 4.254142] mmc2: No card detect facilities available
[ 4.273889] [vreg_mmc_control,3641] vreg_mmc control status: vreg_sts=00000006 sdccid=1 on=1
[ 4.293982] [vreg_mmc_control,3641] vreg_mmc control status: vreg_sts=0000000e sdccid=3 on=1
[ 4.333879] [msm_sdcc3_setup_power,4077] Switching ON vreg_emmc in msm_sdcc3_setup_power OK
[ 4.336856] mmc2: Qualcomm MSM SDCC at 0x00000000a0500000 irq 10,0 dma 8
[ 4.343490] mmc2: 8 bit data mode enabled
[ 4.347392] mmc2: 4 bit data mode disabled
[ 4.351562] mmc2: polling status mode enabled
[ 4.355814] mmc2: MMC clock 144000 -> 64000000 Hz, PCLK 64000000 Hz
[ 4.362151] mmc2: Slot eject status = 0
[ 4.365882] mmc2: Power save feature enable = 1
[ 4.370387] mmc2: DM non-cached buffer at ffd54000, dma_addr 0x3fb96000
[ 4.377093] mmc2: DM cmd busaddr 0x3fb96000, cmdptr busaddr 0x3fb96c00
[ 5.093877] [vreg_mmc_control,3641] vreg_mmc control status: vreg_sts=0000000e sdccid=1 on=1
[ 5.113877] [vreg_mmc_control,3641] vreg_mmc control status: vreg_sts=0000000e sdccid=1 on=1
[ 5.129089] mmc0: new high speed SDHC card at address b72f
[ 5.137774] mmcblk1: mmc0:b72f SU08G 7.40 GiB
[ 5.142280] mmcblk1: p1 p2
[ 5.313958] [vreg_mmc_control,3641] vreg_mmc control status: vreg_sts=0000000e sdccid=2 on=1
[ 5.333916] [vreg_mmc_control,3641] vreg_mmc control status: vreg_sts=0000000e sdccid=2 on=1
[ 6.686815] mmc2: host doesn't support card's voltages
[ 6.708055] mmc2: error -22 whilst initialising SDIO card
[ 7.862767] mmc2: host doesn't support card's voltages
[ 7.871566] EXT4-fs (mmcblk1p2): mounted filesystem without journal
[ 7.884177] mmc2: error -22 whilst initialising SDIO card
[ 9.036666] mmc2: host doesn't support card's voltages
[ 9.054071] mmc2: error -22 whilst initialising SDIO card
[ 10.196824] mmc2: host doesn't support card's voltages
[ 24.154689] mmc2: error -22 whilst initialising SDIO card
[ 25.214152] mmc1: Slot status change detected (0 -> 1)
[ 25.309190] mmc2: host doesn't support card's voltages
[ 25.324092] mmc2: error -22 whilst initialising SDIO card
[ 25.494016] [vreg_mmc_control,3641] vreg_mmc control status: vreg_sts=0000000e sdccid=2 on=1
[ 25.514020] [vreg_mmc_control,3641] vreg_mmc control status: vreg_sts=0000000e sdccid=2 on=1
[ 25.569839] mmc1: queuing CIS tuple 0x80 length 50
[ 25.592533] mmc1: queuing CIS tuple 0x80 length 7
[ 25.602561] mmc1: queuing CIS tuple 0x80 length 9
[ 25.610713] mmc1: queuing CIS tuple 0x80 length 6
[ 25.675273] mmc1: queuing CIS tuple 0x02 length 1
[ 25.694244] [vreg_mmc_control,3641] vreg_mmc control status: vreg_sts=0000000e sdccid=2 on=1
[ 25.714010] [vreg_mmc_control,3641] vreg_mmc control status: vreg_sts=0000000e sdccid=2 on=1
[ 25.725996] mmc1: new SDIO card at address 0001
[ 26.469183] mmc2: host doesn't support card's voltages
[ 26.484220] mmc2: error -22 whilst initialising SDIO card
[ 27.659404] mmc2: host doesn't support card's voltages
[ 27.674591] mmc2: error -22 whilst initialising SDIO card
[ 28.817352] mmc2: host doesn't support card's voltages
"host doesn't support card's voltages" seems to be the main error... this looks as a kernel config error.
My external 8gb SD card is properly detected (mmcblk1).
It has two partitions, mmcblk1 and mmcblk1, but app2sd is not working. /sd-ext is mounted. I'll have to study a bit more.
Here is some system information:
Code:
# ls -la /dev/block/mm*
brw------- 1 root root 179, 16 Sep 20 11:38 /dev/block/mmcblk1
brw------- 1 root root 179, 17 Sep 20 11:38 /dev/block/mmcblk1p1
brw------- 1 root root 179, 18 Sep 20 11:38 /dev/block/mmcblk1p2
# mount
rootfs on / type rootfs (ro,relatime)
tmpfs on /dev type tmpfs (rw,nosuid,relatime,mode=755)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
/sys/kernel/debug on /sys/kernel/debug type debugfs (rw,relatime)
tmpfs on /storage type tmpfs (rw,relatime,mode=050,gid=1028)
tmpfs on /mnt/secure type tmpfs (rw,relatime,mode=700)
tmpfs on /mnt/asec type tmpfs (rw,relatime,mode=755,gid=1000)
tmpfs on /mnt/obb type tmpfs (rw,relatime,mode=755,gid=1000)
tmpfs on /mnt/fuse type tmpfs (rw,relatime,mode=775,gid=1000)
/dev/block/mtdblock2 on /system type yaffs2 (ro,relatime)
/dev/block/mtdblock4 on /data type yaffs2 (rw,nosuid,nodev,relatime)
/dev/block/mtdblock3 on /cache type yaffs2 (rw,nosuid,nodev,relatime)
/dev/block/mmcblk1p2 on /sd-ext type ext4 (rw,relatime,barrier=1,data=writeback)
/dev/block/vold/179:17 on /storage/sdcard0 type vfat (rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
tmpfs on /storage/sdcard0/.android_secure type tmpfs (ro,relatime,size=0k,mode=000)
# df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 204.2M 84.0K 204.1M 0% /dev
tmpfs 204.2M 0 204.2M 0% /storage
tmpfs 204.2M 0 204.2M 0% /mnt/secure
tmpfs 204.2M 0 204.2M 0% /mnt/asec
tmpfs 204.2M 0 204.2M 0% /mnt/obb
tmpfs 204.2M 0 204.2M 0% /mnt/fuse
/dev/block/mtdblock2 250.0M 216.5M 33.5M 87% /system
/dev/block/mtdblock4 160.0M 96.1M 63.9M 60% /data
/dev/block/mtdblock3 33.0M 1.2M 31.8M 4% /cache
/dev/block/mmcblk1p2 3.8G 52.0K 3.6G 0% /sd-ext
/dev/block/vold/179:17 3.6G 860.9M 2.7G 23% /storage/sdcard0
# cat /proc/mtd
dev: size erasesize name
mtd0: 00500000 00020000 "boot"
mtd1: 00500000 00020000 "recovery"
mtd2: 0fa00000 00020000 "system"
mtd3: 02100000 00020000 "cache"
mtd4: 0a000000 00020000 "userdata"
mtd5: 00200000 00020000 "logo"
mtd6: 000e0000 00020000 "splash"
mtd7: 00200000 00020000 "misc"
# fdisk -l /dev/block/mmcblk1
Disk /dev/block/mmcblk1: 7948 MB, 7948206080 bytes
4 heads, 16 sectors/track, 242560 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk1p1 1 117554 3761718+ c Win95 FAT32 (LBA)
Partition 1 does not end on cylinder boundary
/dev/block/mmcblk1p2 117554 242560 4000201 83 Linux
Partition 2 does not end on cylinder boundary
# fdisk -l /dev/block/mmcblk0
fdisk: can't open '/dev/block/mmcblk0': No such file or directory
# uname -a
Linux localhost 2.6.32.9-ideos #1 PREEMPT Thu Aug 15 15:06:53 FET 2013 armv7l GNU/Linux
# cat /system/etc/vold.fstab
# Mounts the first usable partition of the specified device s7-105
dev_mount sdcard /storage/sdcard0 auto /devices/platform/msm_sdcc.1/mmc_host/mmc0
dev_mount usbdisk /storage/usbdisk0 auto /devices/platform/msm_hsusb_host.0/usb1
Could someone help me revive my internal sd?
I'm not sure but it might be a hardware problem.
It could also be some kernel problem, as I didn't see those mmc errors in dmesg with 2.1 or 2.2.2. (I coudn't access internal mmc anyway)
what other kernels can I try?
Thanks just for reading this long post!!

I'll need to install or build a kernel with CONFIG_MMC_DEBUG enabled to see what might be going on with more detail.
Which kernel sources and .config do you (devs) recomend to use for s7-105 on 4.2.2?

I just installed 2.1-upd1 from dload in external sd card.
After getting root and installling busybox and sshdroid I see the same error in dmesg:
Code:
# dmesg|grep -i mmc
<6>[ 0.270488] [qsd8x50_init_mmc,3928] request GPIO 157 OK
<6>[ 0.270553] [qsd8x50_init_mmc,3935] configure GPIO 157 OK
<3>[ 4.071736] get_emmc_state(): msm_rpc_call_reply succeed! proc=23, emmc_state=0x4000000, g_emmc_state = 4
<6>[ 4.300377] [vreg_mmc_control,3408] Switching ON vreg_mmc OK
<6>[ 4.320455] mmc0: Qualcomm MSM SDCC at 0x00000000a0300000 irq 24,221 dma 8
<6>[ 4.325593] mmc0: 8 bit data mode disabled
<6>[ 4.329672] mmc0: 4 bit data mode enabled
<6>[ 4.333712] mmc0: polling status mode disabled
<6>[ 4.338120] mmc0: MMC clock 144000 -> 49152000 Hz, PCLK 64000000 Hz
<6>[ 4.344508] mmc0: Slot eject status = 0
<6>[ 4.348188] mmc0: Power save feature enable = 1
<6>[ 4.363768] mmc0: DM non-cached buffer at ffc09000, dma_addr 0x3ee05000
<6>[ 4.369093] mmc0: DM cmd busaddr 0x3ee05000, cmdptr busaddr 0x3ee05300
<6>[ 4.400529] mmc1: Qualcomm MSM SDCC at 0x00000000a0400000 irq 26,0 dma 8
<6>[ 4.401619] mmc1: 8 bit data mode disabled
<6>[ 4.405725] mmc1: 4 bit data mode enabled
<6>[ 4.409690] mmc1: polling status mode disabled
<6>[ 4.414191] mmc1: MMC clock 144000 -> 49152000 Hz, PCLK 64000000 Hz
<6>[ 4.421695] mmc1: Slot eject status = 1
<6>[ 4.424232] mmc1: Power save feature enable = 1
<4>[ 4.428740] mmc0: host doesn't support card's voltages
<6>[ 4.433849] mmc1: DM non-cached buffer at ffc0a000, dma_addr 0x3ee10000
<6>[ 4.440464] mmc1: DM cmd busaddr 0x3ee10000, cmdptr busaddr 0x3ee10300
<3>[ 4.447673] mmc2: No card detect facilities available
<3>[ 4.452126] mmc0: error -22 whilst initialising SDIO card
<6>[ 4.530392] [msm_sdcc3_setup_power,3865] Switching ON vreg_emmc in msm_sdcc3_setup_power OK
<6>[ 4.533203] mmc2: Qualcomm MSM SDCC at 0x00000000a0500000 irq 10,0 dma 8
<6>[ 4.539794] mmc2: 8 bit data mode disabled
<6>[ 4.546097] mmc2: 4 bit data mode enabled
<6>[ 4.547890] mmc2: polling status mode enabled
<6>[ 4.554118] mmc2: MMC clock 144000 -> 49152000 Hz, PCLK 64000000 Hz
<6>[ 4.558487] mmc2: Slot eject status = 0
<6>[ 4.565169] mmc2: Power save feature enable = 1
<6>[ 4.566816] mmc2: DM non-cached buffer at ffc0b000, dma_addr 0x3ecdd000
<6>[ 4.573473] mmc2: DM cmd busaddr 0x3ecdd000, cmdptr busaddr 0x3ecdd300
<6>[ 4.836918] mmc0: new high speed SDHC card at address b72f
<6>[ 4.843839] mmcblk0: mmc0:b72f SU08G 7.40 GiB
<6>[ 4.847051] mmcblk0:<6>android_bind
<7>[ 16.480324] mmc1: card_present 1
<7>[ 16.708405] mmc1: queuing CIS tuple 0x80 length 50
<7>[ 16.764824] mmc1: queuing CIS tuple 0x80 length 7
<7>[ 16.788457] mmc1: queuing CIS tuple 0x80 length 9
<7>[ 16.806202] mmc1: queuing CIS tuple 0x80 length 6
<7>[ 16.813065] mmc1: queuing CIS tuple 0x00 length 0
<7>[ 17.019966] mmc1: queuing CIS tuple 0x00 length 0
<7>[ 17.027365] mmc1: queuing CIS tuple 0x02 length 1
<6>[ 17.238124] mmc1: new SDIO card at address 0001
#
# dd if=/dev/zero of=/dev/block/mmcblk1
/dev/block/mmcblk1: write error: No space left on device
424601+0 records in
424600+0 records out
217395200 bytes transferred in 7.517 secs (28920473 bytes/sec)
# fdisk -l /dev/block/mmcblk1
Disk /dev/block/mmcblk1: 217 MB, 217395200 bytes
255 heads, 63 sectors/track, 26 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk /dev/block/mmcblk1 doesn't contain a valid partition table
# fdisk -l /dev/block/mmcblk0
Disk /dev/block/mmcblk0: 7948 MB, 7948206080 bytes
4 heads, 16 sectors/track, 242560 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 1 117554 3761718+ c Win95 FAT32 (LBA)
Partition 1 does not end on cylinder boundary
/dev/block/mmcblk0p2 117554 242560 4000201 83 Linux
Partition 2 does not end on cylinder boundary
host doesn't support card's voltages, same error than with 4.2.2
I have noticed that mmcblk0 and mmcblk1 are opposite than they were with 4.2.2!!!!

Maybe someone could post a full cwm backup of a clean 4.2.2 system with working internal and external sd?
I can create a ftp account to upload it to my cloud server, if needed.
I think there might be something wrong with some of my config files, which doesn't get overwritten when I flash a rom.
Some settings are kept, as language, so maybe the wrong partition information is passed from one installation to the other.

Contents of /system/etc/vold.conf are completely different in android 2.1, can someone post his /system/etc/vold.conf ?
This is mine:
Code:
# cat /system/etc/vold.conf | grep -v ^#
volume_sdcard {
media_path /devices/platform/msm_sdcc.1/mmc_host
media_type mmc
mount_point /sdcard2
ums_path /devices/platform/msm_hsusb/gadget/lun0
}
volume_sdcard3 {
media_path /devices/platform/msm_sdcc.3/mmc_host
media_type mmc
mount_point /sdcard
ums_path /devices/platform/msm_hsusb/gadget/lun1
}
volume_usb {
media_path /devices/platform/msm_hsusb_host.0/usb1
media_type usb
mount_point /data/disk/media/disk
}
volume_usb2 {
media_path /devices/platform/msm_hsusb_host.1/usb2
media_type usb
mount_point /data/disk/media/disk
}

ramoncio said:
...
Could someone help me revive my internal sd?
I'm not sure but it might be a hardware problem.
It could also be some kernel problem, as I didn't see those mmc errors in dmesg with 2.1 or 2.2.2. (I coudn't access internal mmc anyway)
what other kernels can I try?
Thanks just for reading this long post!!
Click to expand...
Click to collapse
It sure looks to be hardware related but hope I am wrong and you get your memory back!
Regards
J.