Alright, as you guys may have already noticed, I've attempted to port Kali NetHunter to the S7.
While this normally comes without any issues, the S7 has turned out with more than its fair share of kernel problems.
So far, this is what we have learned:
CONFIG_TIMA_RKP must be disabled in order to not use prebuilt "secure" vmm.elf and boot.
CONFIG_SEC_RESTRICT_ROOTING does not necessarily need to be disabled for root to work, but is safe to disable nonetheless.
We can't use O= in the make command to set an output directory until one of you decides to fix Samsung's silly Makefiles.
All variants Exynos seem to have the same hardware, so we don't need to compile for specific variants, ex. F/FD/X/W8
SELinux can be forced to permissive to avoid init resetting it using this patch.
Booting with f2fs in the fstab is possible with this patch.
A working dtb.img can be generated using dtbgen.sh in this patch.
S7 and S7 Edge share the same kernel source.
Building for the S7 Edge instead of S7 requires only a few small changes in the kernel config -> diffchecker
pstore filesystem support seems unfinished, as enabling CONFIG_EXYNOS_SNAPSHOT_PSTORE results in an unbootable kernel.
We can maybe use cat /proc/kmsg > /sdcard/kmsg to live write kmsg to a file on sdcard, but it truncates too early when a panic/reboot happens.
So far it seems that disabling TIMA results in random reboots, or reboots any time that something secure is requested such as fingerprint or lock screen entry.
As it is, I think I'll wait for a newer kernel source release from Samsung OSRC.
If you guys are willing to try and get things working (it's very hard for me, not having an S7 myself), then my current work is available at:
https://github.com/jcadduono/nethunter_kernel_herolte
There are multiple branches:
twrp-6.0 is the kernel source used in TWRP
touchwiz-6.0 is my attempted NetHunter kernel
stock-6.0 builds a stock equivalent kernel with a few build issues fixed and scripts added (a good place to start)
testing-6.0 is my branch for attempting to get a permissive kernel to boot
If there's any information you guys can contribute to getting us a working custom kernel, feel free to contribute here with that information.
TL;DR
We can build the kernel, we can boot the kernel, but it panics and reboots all the time and we have no reliable way to debug it.
Could you please explain "CONFIG_TIMA must be disabled in order to not use prebuilt vmm.elf and boot." for more detail?
As I know on exynos 7420 we can disable tima in default.prop
Devries said:
Could you please explain "CONFIG_TIMA must be disabled in order to not use prebuilt vmm.elf and boot." for more detail?
As I know on exynos 7420 we can disable tima in default.prop
Click to expand...
Click to collapse
My test user said that the pure stock kernel with CONFIG_TIMA=y would not boot past the bootloader screen (with KERNEL IS NOT SEANDROID ENFORCING), but when I disabled that, they said they were able to boot but it reboot whenever they reached the lock screen.
I know one of the TIMA options disables building vmm.elf and uses a proprietary prebuilt vmm.elf in the kernel boot sequence. I'm not knowledgeable enough to know how this works.
Adding ro.config.tima=0 does not fix the reboot.
jcadduono said:
My test user said that the pure stock kernel with CONFIG_TIMA=y would not boot past the bootloader screen (with KERNEL IS NOT SEANDROID ENFORCING), but when I disabled that, they said they were able to boot but it reboot whenever they reached the lock screen.
I know one of the TIMA options disables building vmm.elf and uses a proprietary prebuilt vmm.elf in the kernel boot sequence. I'm not knowledgeable enough to know how this works.
Click to expand...
Click to collapse
He means you should change it in /system/build.prop or in the ramdisk /default.prop.
Just add ro.config.tima=0 into the default.prop and see if that fixes the reboots.
AndreiLux said:
He means you should change it in /system/build.prop or in the ramdisk /default.prop.
Just add ro.config.tima=0 into the default.prop and see if that fixes the reboots.
Click to expand...
Click to collapse
I tried many methods but still reboot,do you have any good suggestion?
AndreiLux said:
He means you should change it in /system/build.prop or in the ramdisk /default.prop.
Just add ro.config.tima=0 into the default.prop and see if that fixes the reboots.
Click to expand...
Click to collapse
Had this problem also in tab s kernel, once i disabled it I've got reboots when using fingerprints /pin/etc..
Sent from my Galaxy S5 SM-G900F boosted by PhoeniX ROM using Tapatalk
Good News for us developers.
I noticed Samsung just add last_kmsg support in latest G930KKKU1APCF source.
Jesse Chan said:
Good News for us developers.
I noticed Samsung just add last_kmsg support in latest G930KKKU1APCF source.
Click to expand...
Click to collapse
Finally
Sent with my Nova powered SM-G901F
Anyone get a kernel to boot up? I tried all variants of CONFIG_TIMA_RKP and CONFIG_TIMA, also different toolchains and stock dtb.img and the dtb.img generator, the kernel didn't boot up one single time!
jcadduono said:
[*]CONFIG_TIMA_RKP must be disabled in order to not use prebuilt "secure" vmm.elf and boot.
Click to expand...
Click to collapse
vmm.elf is not the reason of not boot.
I tried to compile pre-built vmm.elf into kernel while RKP is set to false and it booted.
Devries said:
I tried many methods but still reboot,do you have any good suggestion?
Click to expand...
Click to collapse
ro.securestorage.support=false
no reboots...
I'm not too concerned with the reboots however did any of you manage to build any image which recognizes the SIM card and boots up the modem?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
i'm not sure even samsung is taking exynos seriously
can you guys see everything wrong with this picture lol
jcadduono said:
http://puu.sh/owbIT/0745e59f30.png
i'm not sure even samsung is taking exynos seriously
can you guys see everything wrong with this picture lol
Click to expand...
Click to collapse
You're just nitpicking about trivial stuff.
The cause of the current issues is that when you're compiling a custom image this doesn't pass the EL3 image verification of some sort. Disabling RKP seems to make the basic things work but the TEE remains non-functional. Android's KeyStore relies on the TEE and the reboots are caused by a timeout in the kernel TEE drivers trying to get a response from the TZ side which of course isn't running because it saw that the kernel image isn't a valid Samsung kernel image.
The fingerprint sensor, pin lock, account management (Google, Skype, etc) also use the TEE KeyStore so that's why things like YouTube are crashing the phone because they're trying to access it. You can also crash the device by simply adding a new Google account. In a way things are working as intended as the chain of trust is broken by us flashing a custom image.
The issue lies more on the user-space side where it doesn't allow for a non-hardware backed fallback KeyStore like in previous Android versions. As far as I see it the kernel sources are completely fine and Samsung isn't in the wrong here, but to be able to get a workable daily kernel we need a workaround in the way Android treats TEE. Maybe some people will be able to do something via Xposed or maybe even backport some of the framework from the S6 but ultimately this isn't a technical issue but more of a design/security constraint caused by Google new Android 6.0 CDD requirements.
9.11. Keys and Credentials
The Android Keystore System [Resources, 133] allows app developers to store cryptographic keys in
a container and use them in cryptographic operations through the KeyChain API [Resources, 134] or
the Keystore API [Resources, 135].
All Android device implementations MUST meet the following requirements:
When the device implementation supports a secure lock screen and has a secure
hardware such as a Secure Element (SE) where a Trusted Execution Environment (TEE)
can be implemented, then it:
Is STRONGLY RECOMMENDED to back up the keystore implementation with
the secure hardware. The upstream Android Open Source Project provides the
Keymaster Hardware Abstraction Layer (HAL) implementation that can be used
to satisfy this requirement.
MUST perform the lock screen authentication in the secure hardware if the
device has a hardware-backed keystore implementation and only when
successful allow the authentication-bound keys to be used. The upstream
Android Open Source Project provides the Gatekeeper Hardware Abstraction
Layer (HAL) that can be used to satisfy this requirement [Resources, 136].
Click to expand...
Click to collapse
Custom kernels will run fine without issues as long as nothing tries to access the TEE. Unfortunately that's not reasonable for daily drivers making use of accounts and apps using it for authentication, so until this is somehow bypassed custom kernels seem to be a thing of the past for most users.
@AndreiLux so the short story is that we can't built kernel until Samsung gives us this key , right? Do you think they will release it? Or we are lost?
Sent from my Galaxy S5 SM-G900F boosted by PhoeniX ROM using Tapatalk
tamirda said:
@AndreiLux so the short story is that we can't built kernel until Samsung gives us this key , right? Do you think they will release it? Or we are lost?
Click to expand...
Click to collapse
As said before, the kernel works absolutely fine as long as it doesn't access TEE. Samsung will absolutely never give anybody their signing mechanisms for us to do kernel images that work with it since it's a huge security risk.
IMHO the best possibility is for somebody to figure out a way via Xposed to change the ROM's KeyStore mechanism so it avoids using the TEE.
AndreiLux said:
As said before, the kernel works absolutely fine as long as it doesn't access TEE. Samsung will absolutely never give anybody their signing mechanisms for us to do kernel images that work with it since it's a huge security risk.
IMHO the best possibility is for somebody to figure out a way via Xposed to change the ROM's KeyStore mechanism so it avoids using the TEE.
Click to expand...
Click to collapse
Interesting. Is this thing only on new devices? Because s5 got 6.0.1 and my kernel works great on it.
I think one of the libs must be patched for those checks. Just don't know which one. ...
But as for now it's a temp end of custom kernels ..
Sent from my Galaxy S5 SM-G900F boosted by PhoeniX ROM using Tapatalk
AndreiLux said:
As said before, the kernel works absolutely fine as long as it doesn't access TEE. Samsung will absolutely never give anybody their signing mechanisms for us to do kernel images that work with it since it's a huge security risk.
IMHO the best possibility is for somebody to figure out a way via Xposed to change the ROM's KeyStore mechanism so it avoids using the TEE.
Click to expand...
Click to collapse
What will happen if we directly disable TEE from kernel's defconfig?
Devries said:
What will happen if we directly disable TEE from kernel's defconfig?
Click to expand...
Click to collapse
Android doesn't boot.
AndreiLux said:
Android doesn't boot.
Click to expand...
Click to collapse
In fact,it will boot but fingerprint,lock screen will not work.
---------- Post added at 02:36 PM ---------- Previous post was at 02:35 PM ----------
<3>[ 42.038368] [5: POSIX timer 0: 7102] Trustonic TEE: wait_mcp_notification: No answer after 10s
<3>[ 42.038603] [5: POSIX timer 0: 7102] Trustonic TEE: mcp_dump_mobicore_status: TEE halted. Status dump:Trustonic TEE: mcp_dump_mobicore_status: flags = 0x80000401
<3>[ 42.039004] [5: POSIX timer 0: 7102] Trustonic TEE: mcp_dump_mobicore_status: haltCode = 0x00000002
<3>[ 42.039213] [5: POSIX timer 0: 7102] Trustonic TEE: mcp_dump_mobicore_status: haltIp = 0x07f02948
<3>[ 42.039420] [5: POSIX timer 0: 7102] Trustonic TEE: mcp_dump_mobicore_status: faultRec.cnt = 0x00000003
<3>[ 42.039634] [5: POSIX timer 0: 7102] Trustonic TEE: mcp_dump_mobicore_status: faultRec.cause = 0x00000002
<3>[ 42.039756] [5: POSIX timer 0: 7102] Trustonic TEE: mcp_dump_mobicore_status: faultRec.meta = 0x00000000
<3>[ 42.039815] [5: POSIX timer 0: 7102] Trustonic TEE: mcp_dump_mobicore_status: faultRec.thread = 0x00010001
<3>[ 42.039871] [5: POSIX timer 0: 7102] Trustonic TEE: mcp_dump_mobicore_status: faultRec.ip = 0x00001a84
<3>[ 42.039928] [5: POSIX timer 0: 7102] Trustonic TEE: mcp_dump_mobicore_status: faultRec.sp = 0x0001d280
<3>[ 42.039984] [5: POSIX timer 0: 7102] Trustonic TEE: mcp_dump_mobicore_status: faultRec.arch.dfsr = 0x00000a11
<3>[ 42.040039] [5: POSIX timer 0: 7102] Trustonic TEE: mcp_dump_mobicore_status: faultRec.arch.adfsr = 0x00000000
<3>[ 42.040096] [5: POSIX timer 0: 7102] Trustonic TEE: mcp_dump_mobicore_status: faultRec.arch.dfar = 0x00000000
<3>[ 42.040151] [5: POSIX timer 0: 7102] Trustonic TEE: mcp_dump_mobicore_status: faultRec.arch.ifsr = 0x00000205
<3>[ 42.040205] [5: POSIX timer 0: 7102] Trustonic TEE: mcp_dump_mobicore_status: faultRec.arch.aifsr = 0x00000000
<3>[ 42.040263] [5: POSIX timer 0: 7102] Trustonic TEE: mcp_dump_mobicore_status: faultRec.arch.ifar = 0xfe500f08
<3>[ 42.040321] [5: POSIX timer 0: 7102] Trustonic TEE: mcp_dump_mobicore_status: mcData.flags = 0x00000001
<3>[ 42.040375] [5: POSIX timer 0: 7102] Trustonic TEE: mcp_dump_mobicore_status: mcExcep.partner = 0xffffffff
<3>[ 42.040430] [5: POSIX timer 0: 7102] Trustonic TEE: mcp_dump_mobicore_status: mcExcep.peer = 0x00000009
<3>[ 42.040484] [5: POSIX timer 0: 7102] Trustonic TEE: mcp_dump_mobicore_status: mcExcep.cause = 0x00000012
<3>[ 42.040541] [5: POSIX timer 0: 7102] Trustonic TEE: mcp_dump_mobicore_status: mcExcep.meta = 0xfffffffe
<3>[ 42.040715] [5: POSIX timer 0: 7102] Trustonic TEE: mcp_dump_mobicore_status: mcExcep.uuid = 0xffffffffd0000000000000000000000e
<0>[ 42.042245] [5: POSIX timer 0: 7102] Kernel panic - not syncing: tbase halt
* That's the reason why kernel will random reboot.
Related
Hi everyone,
I'm having a problem with my G1.
Each time i try to turn the Wi-Fi on, i follow this steps (spoil !!) :
- Settings -> Wireless controls -> and the i click on Wi-Fi,
wich changes the lower text to "Turning on..."
Ok, but this step take something like 1 minute and after all this time, i can read : "Unable to stop Wi-Fi" (or sometimes "Unable to start Wi-Fi"),
I got this problem 5 days ago, and this is really a pain in the arse, because the only way i can download applications is using Wi-Fi (I'm french) and i can't !
I have tried everything :
- Turn Off/On G1
- Remove/Replace battery
- Reset to factory data
- Back to RC29 (thx to you )
- Root my G1 with JF1.41 mod (Thx so much !!)
But the problem is still there,
And i can't get it back to T-Mobile, because i bought it on eBay and i live in France...
So... can anybody help ?
Thx
Hi,
Same problem here. Edit: It does this 4 times on 5. And even if if finally starts, it hangs some time after.
Additionally I've googled (almost) all night long to find some clues but nothing concrete
First, an issue is open here: http://code.google.com/p/android/issues/detail?id=1124
I get this line in logcat:
Code:
D/wlan_loader( 574): ConfigMge start rc = -1
that shows a problem. Normally it should be "rc = 0".
I've digged into the code but it is very complicated (state machine, etc...) so I could not figure where the problem resides.
I also have this in dmesg:
Code:
<4>[ 1425.145012] mmc0: card claims to support voltages below the defined range. These will be ignored.
<4>[ 1425.145867] mmc0: SDIO card claims to support the incompletely defined 'low voltage range'. This will be ignored.
I don't know if this means a hardware problem.
I also suspect a bug in the proprietary file "/system/etc/wifi/Fw1251r1c.bin" but I've not found any other version on the net, even in "not so clean ways".
The size of the file on my G1 is 194188 bytes.
I have installed RC33 ADP1 by Jesus Freke but it did not solved the problem.
Can anyone look at the size of this file on his G1 and tell me if it is different? And if it is the case possibly send it to me?
The only solution I've seen on the net is to send back the phone to T-Mobile for a replacement but unfortunately I live in France and I got it from US by unusual ways so it is not a possibility for me .
Any clue / advice will be gladly accepted
Thanks in advance.
Mid'.
I have the same problem...
I was wondering if either of you figured out what to do to get around this. I'm in the US and am having the same problem. I was also working for about a week before this behavior started ("Unable to start Wi-Fi", "Unable to stop Wi-Fi").
I have seen other posts where this is intermittent. It isn't with me. Once it quit working, I haven't been able to get anything but the error messages.
If someone has found a way around this, I would appreciate any help you can provide.
Regards
Steve
You three should post what third party apps you have installed.
I am having this same issue after flashing the new google ION R2
I'm also having this issue after flashing Ion.
Same Issue
I started having this issue before the Ion rom. It wasn't intermittent, just stopped working.
Same problem here
Code:
<4>[ 1425.145012] mmc0: card claims to support voltages below the defined range. These will be ignored.
<4>[ 1425.145867] mmc0: SDIO card claims to support the incompletely defined 'low voltage range'. This will be ignored.
CRB43, factory reset, nothing works.
Does anybody have an idea on how to solve this? It seems to be a known problem bij T-Mobile.
I'm running JF1.51 and WiFi is horribly flaky. It will work great for a few seconds then go deaf.
If I toggle it off and on it will work for a little bit again.
EDIT: I'm also getting the "low voltage" error message.
I've looked at this a little bit, and it looks like a ring buffer problem.
As I said before, my WiFi will work great for a while then go deaf.
Disabling/enabling through the Settings GUI will restore operation for a couple of minutes, tops.
Here's what I think might be relevant dmesgs:
Code:
<6>[88157.446136] request_suspend_state: sleep (0->3) at 88153591964926 (2009-06-27 20:57:10.146884034 UTC)
<4>[88157.467956] deinit sharp panel
<4>[88157.996398] select 4913 (app_process), adj 15, size 3053, to kill
<4>[88157.996734] send sigkill to 4913 (app_process), adj 15, size 3053
<4>[88158.236358] save exit: isCheckpointed 1
<6>[88282.505401] request_suspend_state: wakeup (3->0) at 88278651260580 (2009-06-27 20:59:15.206149170 UTC)
<6>[88282.615966] rev_crc_err_count 1, INT 23a001
<6>[88282.616332] rev: unknown reverse packet: len=0009 type=0049 CURR_REV_PTR=1617500b
<6>[88282.616851]
<6>[88282.617126] 09<6> 00<6> 49<6> 00<6> 00<6> 80<6> 00<6> 60<6> 00<6> 80<6> 0a<6>
<6>[88282.620574] mddi: resetting rev ptr
<6>[88282.621154] mddi_remote_read: failed, sent MDDI_CMD_SEND_RTD: int 23a001, stat 808063, rtd val e curr_rev_ptr 1617500b
<4>[88282.666717] init sharp panel
<4>[88287.779876] select 4943 (app_process), adj 15, size 2991, to kill
<4>[88287.780731] send sigkill to 4943 (app_process), adj 15, size 2991
<4>[88295.748840] select 4951 (app_process), adj 15, size 2992, to kill
<4>[88295.749694] send sigkill to 4951 (app_process), adj 15, size 2992
<6>[88298.065185] TIWLAN: Driver unloading
<4>[88298.066314] sdio_reset_comm():
<7>[88298.154388] TIWLAN: Releasing SDIO resources
<7>[88298.158172] TIWLAN: SDIO resources released
<4>[88298.160217] wifi_remove
<4>[88298.160552] trout_wifi_set_carddetect: 0
<7>[88298.160827] mmc0: card_present 0
<6>[88298.161346] mmc0: Slot status change detected (1 -> 0)
<4>[88298.161712] trout_wifi_reset: 1
<6>[88298.172302] mmc0: card 0002 removed
<4>[88298.233215] trout_wifi_power: 0
<6>[88298.996520] TIWLAN: Driver unloaded
Here's a little more that I'm getting when the WiFi stops. Is this driver OSS or a proprietary blob?
Code:
<3>[ 1097.459899] init: untracked pid 364 exited
<4>[ 1101.746643] wds: 0020 @ 01
<6>[ 1101.747192] qmi: wds: got handle 0x17aaafb0
<4>[ 1101.747711] wds: 0022 @ ff
<6>[ 1101.748168] qmi: wds: CONNECTED
<4>[ 1101.750244] wds: 002d @ 01
<4>[ 1101.750701] qmi: got network profile
<6>[ 1101.752502] rmnet_open()
<6>[ 1685.105285] request_suspend_state: wakeup (3->0) at 1679298966064 (2009-06-27 21:55:33.740494873 UTC)
<6>[ 1685.217498] rev_crc_err_count 1, INT 23a001
<6>[ 1685.218078] rev: unknown reverse packet: len=0009 type=0049 CURR_REV_PTR=1617500b
<6>[ 1685.218383]
<6>[ 1685.218658] 09<6> 00<6> 49<6> 00<6> 00<6> 80<6> 00<6> 60<6> 00<6> 80<6> 0a<6>
<6>[ 1685.222137] mddi: resetting rev ptr
<6>[ 1685.222595] mddi_remote_read: failed, sent MDDI_CMD_SEND_RTD: int 23a001, stat 808063, rtd val e curr_rev_ptr 1617500b
<4>[ 1685.288696] init sharp panel
<4>[ 1692.515502] wds: 0021 @ 01
<6>[ 1692.515838] qmi: wds: network stopped
<6>[ 1692.546508] rmnet_stop()
<4>[ 1693.342254] wds: 0022 @ ff
<6>[ 1693.342864] qmi: wds: DISCONNECTED
<6>[ 1704.187591] TIWLAN: Driver unloading
<4>[ 1704.188781] sdio_reset_comm():
<7>[ 1704.266632] TIWLAN: Releasing SDIO resources
<7>[ 1704.267944] TIWLAN: SDIO resources released
<4>[ 1704.270568] wifi_remove
<4>[ 1704.271057] trout_wifi_set_carddetect: 0
<7>[ 1704.272521] mmc0: card_present 0
<6>[ 1704.272979] mmc0: Slot status change detected (1 -> 0)
<6>[ 1704.276489] mmc0: card 0002 removed
<4>[ 1704.280487] trout_wifi_reset: 1
<4>[ 1704.332305] trout_wifi_power: 0
<6>[ 1704.543151] TIWLAN: Driver unloaded
<4>[ 1705.308166] wds: 0020 @ 01
<6>[ 1705.308715] qmi: wds: got handle 0x17aaafb0
<4>[ 1705.309234] wds: 0022 @ ff
<6>[ 1705.309661] qmi: wds: CONNECTED
<4>[ 1705.311370] wds: 002d @ 01
<4>[ 1705.311798] qmi: got network profile
<6>[ 1705.313690] rmnet_open()
<6>[ 1709.503326] TIWLAN: Driver loading
<4>[ 1709.504211] wifi_probe
<4>[ 1709.504486] trout_wifi_power: 1
<4>[ 1709.714965] trout_wifi_reset: 0
<4>[ 1709.766632] trout_wifi_set_carddetect: 1
<7>[ 1709.767303] mmc0: card_present 1
<6>[ 1709.767608] mmc0: Slot status change detected (0 -> 1)
<3>[ 1712.275085] mmc0: Command timeout
<4>[ 1712.282226] mmc0: card claims to support voltages below the defined range. These will be ignored.
<4>[ 1712.283081] mmc0: SDIO card claims to support the incompletely defined 'low voltage range'. This will be ignored.
<6>[ 1712.290405] mmc0: new SDIO card at address 0001
<6>[ 1712.296447] TIWLAN: Found SDIO controller (vendor 0x104c, device 0x9066)
<6>[ 1712.302520] TIWLAN: Driver initialized (rc 0)
<4>[ 1712.303436] TIWLAN: 1251 PG 1.2
<6>[ 1712.303863] TIWLAN: Driver loaded
<4>[ 1721.950164] wds: 0021 @ 01
<6>[ 1721.950500] qmi: wds: network stopped
<6>[ 1721.976440] rmnet_stop()
<4>[ 1726.546569] select 151 (app_process), adj 15, size 3009, to kill
<4>[ 1726.547149] select 158 (app_process), adj 15, size 3081, to kill
<4>[ 1726.547454] select 311 (app_process), adj 15, size 3246, to kill
<4>[ 1726.547973] send sigkill to 311 (app_process), adj 15, size 3246
<4>[ 1730.936798] wds: 0022 @ ff
<6>[ 1730.937652] qmi: wds: DISCONNECTED
I had the problem, i redid everything. just flashing the phone didn't help. downloaded the jf1.51 and did it again. logs would say wifi drivers not found. and guess what i checked and there were not there... I don't know 'who' or 'what' deleted them...
The only thing II suspect is the Backup program available on market for root users...or the "Privacy for rooted phones" prog
Same problem
Experiencing the same problem with my UK T-Mobile G1 (JF v1.51). Tried wiping, reseting, turning device off and on and removing battery, nothing has worked.
Is there any solution yet? I don't have any new apps installed and it is a fresh update, the problem was there prior to updating to jf v1.51
Any help will be appreciated
Did anyone manage to fix this? could it be related to the SDCard you are using?
Does everyone with non-working wifi on a G1 have this?
3 days ago, after I apply a chinese character sorting patch, i met this problem. So I wiped my phone, repartitioned my sdcard, reflashed the CM404 rom. And finnally got my wifi back.
But today I had this problem back again. I'm thinking is it because the sdcard I'm using is taking up to much battery power, so that the wifi module could not acquire enough power? This recalls me that I changed my sdcard exactly 3 days ago, right before I met this problem for the first time.
I am from India and G1 is very expensive over here. So, a friend bought me G1 from US and it reached in my hand yesterday . It is a T-Mobile G1. Was having same issue with Wifi and was showing "WiFi unable to start" . I tried rooting it and flashing with various ROM - issue remained. Lastly I downloaded a application from Market and installed. Named : WiFi Fixer by Zanshin-g1 .that software is written for completely different reason.
Code:
Does your wifi "hang" while still connected? Wifi Fixer keeps wifi working automatically, with optional wifi lock.
0.3.1 Cupcake, Disable function, warning if Wifi Notification is on
0.2.9 Added support for Landscape
*Wifi Fixer Classic also available*
But somehow it fixed my issue
Thanks Zanshin-g1.
bidhata said:
I am from India and G1 is very expensive over here. So, a friend bought me G1 from US and it reached in my hand yesterday . It is a T-Mobile G1. Was having same issue with Wifi and was showing "WiFi unable to start" . I tried rooting it and flashing with various ROM - issue remained. Lastly I downloaded a application from Market and installed. Named : WiFi Fixer by Zanshin-g1 .that software is written for completely different reason.
Code:
Does your wifi "hang" while still connected? Wifi Fixer keeps wifi working automatically, with optional wifi lock.
0.3.1 Cupcake, Disable function, warning if Wifi Notification is on
0.2.9 Added support for Landscape
*Wifi Fixer Classic also available*
But somehow it fixed my issue
Thanks Zanshin-g1.
Click to expand...
Click to collapse
Thanks Bidhata ,
but it tried that application and initially at first run it worked . but then once i got dc , the problem came back. since then i am not able to have the wifi truned on .
so the issue remains ..
Did you check the permission of this file: /data/misc/wifi/wpa_supplicant.conf
osoft said:
Did you check the permission of this file: /data/misc/wifi/wpa_supplicant.conf
Click to expand...
Click to collapse
This gave me the idea of how to fix, and its relativley simple... please correct me if I have made a grave error, but it seems to work so meh:
enter your terminal emulator and type the following:
su
(allow the request when asked)
chmod 777 /data/misc/wifi/wpa_supplicant.conf
exit the terminal
try powering up your wifi, it seems to be pretty stable as of now. This began occuring after I left my home's wireless range without turning wifi off and having the Wireless Helper app installed from the market...needless to say I have uninstalled said app and done this mod.
Whats funny about my situation is that if i use the DREAIMG.nbh file to flash back to rc29 my wifi works fine if i then upgrade to jf 1.5 still works fine upgrade to the latest cyanogen stable still works fine. Then a couple of days later poof "Unable to start wifi" intermittently and then a few days later permanently. Even if i downgrade to jf again still no wifi until i re-flash rc29 again. Weird thing is before i downgrade to jf 1.5 i run a fastboot erase on all the pertinent partitions. The only one that doesn't get flashed or erased in the downgrade to 1.5 is the radio rom. This leads me to believe that either my hardware is on it's way out or something that gets set in the radio rom from cyanogen 4.0.4 gets carried over no matter what rom you flash until the radio is erased and re-flashed. Mind you the second one is a totally just a guess with no proof to back it up. I also tried to chmod 777 /data/misc/wifi/wpa_supplicant.conf like said in the last post but to no avail.
I think the most common problem we are seeing is people not clearing the old files. Before you download a new kernel and extract it, delete the old files from your SDK directory on your computer. Everyone that has had a problem so far, either screwed up a step or flashed a combo of new files and old files (ie the wifi not working after). So again BEFORE you extract the new kernel, REMOVE all old kernel files from the SDK directory on your computer.
List of files:
boot.img
/system/lib/modules/bcm4329.ko
/system/lib/modules/tun.ko
/system/lib/modules/scsi_wait_scan.ko
/system/lib/modules/cifs.ko
/system/etc/vold.fstab
You may ask why i didn't post this in the development forum, cause i'm not developing anything.
upgrading from Tiaman 1.1.6 to 1.3.1 just overwrites them ... you mean changing kernels completely right?
MitchRapp said:
upgrading from Tiaman 1.1.6 to 1.3.1 just overwrites them ... you mean changing kernels completely right?
Click to expand...
Click to collapse
No i mean the files on your computer, not the xoom. People are extracting the files into the SDK directory. Then leaving them there to mix with the new files. The xoom will overwrite what it needs to.
bwcorvus said:
I think the most common problem we are seeing is people not clearing the old files. Before you download a new kernel and extract it, delete the old files from your SDK directory on your computer. Everyone that has had a problem so far, either screwed up a step or flashed a combo of new files and old files (ie the wifi not working after). So again BEFORE you extract the new kernel, REMOVE all old kernel files from the SDK directory on your computer.
List of files:
boot.img
/system/lib/modules/bcm4329.ko
/system/lib/modules/tun.ko
/system/lib/modules/scsi_wait_scan.ko
/system/lib/modules/cifs.ko
/system/etc/vold.fstab
You may ask why i didn't post this in the development forum, cause i'm not developing anything.
Click to expand...
Click to collapse
This is why I always copy my files into a temp directory as shown in this post
Or just use a different folder for each version, and cd to the directory before you flash.
Also, you can do adb push system /system, and it'll put them in the right folders if you have it mirrored in your PC's folders.
Mine doesn't power up after following the procedure, it stays in the Motorola Dual Core logo..
I guess no XOOM for me until tomorrow
dmesg output:
Code:
<4>[ 18.182391] Primary GPT is invalid, using alternate GPT.
<6>[ 18.182577] mmcblk1: p1 (ebb) p2 (pdsb) p3 (misc) p4 (logo.bin) p5 (kpanic) p6 (recovery) p7 (boot) p8 (system) p9 (cache) p10 (userdata)
<6>[ 18.567134] android_usb gadget: high speed config #1: android
<6>[ 18.572291] EXT4-fs (mmcblk1p8): INFO: recovery required on readonly filesystem
<6>[ 18.572602] EXT4-fs (mmcblk1p8): write access will be enabled during recovery
<6>[ 18.603790] EXT4-fs (mmcblk1p8): recovery complete
<6>[ 18.606421] EXT4-fs (mmcblk1p8): mounted filesystem with ordered data mode. Opts: (null)
<6>[ 18.682391] EXT4-fs (mmcblk1p10): recovery complete
<6>[ 18.683460] EXT4-fs (mmcblk1p10): mounted filesystem with ordered data mode. Opts: (null)
<6>[ 18.701587] EXT4-fs (mmcblk1p9): recovery complete
<6>[ 18.702643] EXT4-fs (mmcblk1p9): mounted filesystem with ordered data mode. Opts: (null)
<4>[ 18.740397] init (1): /proc/1/oom_adj is deprecated, please use /proc/1/oom_score_adj instead.
<3>[ 18.745288] init: cannot find '/system/etc/install-recovery.sh', disabling 'flash_recovery'
<6>[ 18.844887] enabling adb
<6>[ 18.861463] adb_open
<6>[ 18.924122] warning: `rild' uses 32-bit capabilities (legacy support in use)
<6>[ 18.928677] gps_brcm4750_ioctl: Setting gps gpio reset pin: 0
<6>[ 18.928769] stingray_gps_reset_gpio: setting GPS Reset GPIO to 0
<6>[ 18.928937] gps_brcm4750_ioctl: Setting gps gpio standby pin to: 0
<6>[ 18.929026] stingray_gps_standby_gpio: setting GPS standby GPIO to 0
<6>[ 18.930479] gps_brcm4750_ioctl: Setting gps gpio reset pin: 1
<6>[ 18.930572] stingray_gps_reset_gpio: setting GPS Reset GPIO to 1
<6>[ 19.003124] adb_release
<6>[ 19.003397] adb_open
<6>[ 19.028708] gps_brcm4750_ioctl: Setting gps gpio standby pin to: 1
<6>[ 19.029017] stingray_gps_standby_gpio: setting GPS standby GPIO to 1
<6>[ 19.261164] android_usb gadget: high speed config #1: android
<6>[ 19.577060] tear_down_dma
<6>[ 19.577183] setup_dma
<6>[ 37.780346] gps_brcm4750_ioctl: Setting gps gpio standby pin to: 0
<6>[ 37.780512] stingray_gps_standby_gpio: setting GPS standby GPIO to 0
Hi,
I have tested all possible ROMS (Beast, Utopian, NI, CyanogemMod, EdenX,...) and I encounter the same problem: the interface goes in Error after some time. When I flash and start using it, it's woking fine, but after some time (counted in minutes, not in days), network is down and in the Network settings panel, I get the message "error". Sometimes the interface comes back up, but at some point, it stays in error and in logcat I have
E/WifiService( 1242): Failed to load Wi-Fi driver.
Dmesg gives:
Code:
[<4>[ 1190.039532] Dongle Host Driver, version 4.218.223.1
<4>[ 1198.044261] __ratelimit: 17 callbacks suppressed
<4>[ 1198.048915] dhd_module_init: sdio_register_driver timeout
I also see other errors in the dmesg output:
Code:
<4>[ 1180.754089] dhdsdio_dpc: FAILEDnewstatusREAD, LINE 4092
<4>[ 1180.836536] dhdsdio_dpc: failed backplane access over SDIO, halting operation 1
<4>[ 1180.844034] dhdsdio_dpc: failed backplane access over SDIO, halting operation 1
<4>[ 1180.851469] dhdcdc_query_ioctl: dhdcdc_msg failed w/status -5
<4>[ 1180.871027] dhd_ioctl_entry DONGLE_DOWN,__FUNCTION__
<4>[ 1180.954228] dhd_start_xmit: xmit rejected pub.up=1 busstate=0
<4>[ 1180.960068] dhd_start_xmit: Event RELOAD send up
<4>[ 1180.964706] BUG wlan0 code -19 qlen 0
<4>[ 1186.978451] dhd_ioctl_entry DONGLE_DOWN,__FUNCTION__
<4>[ 1190.019110] bcmsdh_sdmmc: probe of mmc0:0001:1 failed with error -5
I attached logcat and dmesg files.
Before I send my unit to repair, anyone having seen the same problem? Is this really a hardware problem, and if yes, how comes it works fine for some time before breaking?
I've just seen in the dmesg that there are badblocks on mtdblock4. Could that be the reason?
Code:
<4>[ 35.143702] yaffs: Attempting MTD mount on 31.4, "mtdblock4"
<6>[ 35.163593] tegra_nand tegra_nand: Block 0x92d is bad [chip=0,offset=0x125a0000]
<3>[ 35.170984] tegra_nand tegra_nand: Reading OOB data of bad block
I hope someone can help me as I'd rather not send my adam back for repair!
Thanks
Raph
Try the unbricking procedure (not sure it will actually help though). A fresh flash with NVFlash might get you up and running again though the bad sectors do concern me.
It seems there is little information on the internet regarding how to compile the kernel and how to convert to the correct image format so the boot loader will recognise and how to transfer it over to the touchpad. I ended up spent a few hours and finally figured out. I hope this will be useful for someone. I will try to make it concise as this is mainly aimed for developers.
What you will need
A linux development machine with uboot mkimage tool installed.
Sourcery G++ Lite 2010q1-188 for ARM EABI cross compile tool chain
https://sourcery.mentor.com/sgpp/lite/arm/portal/release1294
Touchpad kernel source
https://github.com/CyanogenMod/hp-kernel-tenderloin
CM7 Alpha 3 image (zip file)
http://goo-inside.me/roms/cmtouchpad/alpha3/update-cm-7.1.0-tenderloin-a3-fullofbugs-signed.zip
Prepare
Download CM7 Alpha 3 image and extract the boot.img to a temporary place.
Download Sourcery G++ Lite and install it. Add the G++ Lite tool chain binaray path to the PATH env variable. Get the kernel source from git hub and extract to local disk and change directory to the kernel source.
Compile the kernel
Still in the kernel source directory run
Code:
make ARCH=arm CROSS_COMPILE=arm-none-eabi- tenderloin_android_defconfig
make ARCH=arm CROSS_COMPILE=arm-none-eabi- uImage
Prepare the initramfs U-boot image
Extract the initramfs from the boot.img saved in temporary folder and convert it to uboot-image format
Code:
dd if=boot.img bs=1 skip=3577748 of=img.gz
mkimage -A arm -O linux -T ramdisk -C none -a 0x60000000 -e 0x60000000 -n "Image" -d ./img.gz arch/arm/boot/uRamdisk
(The dd offset for alpha 2.1 image is 3561152)
Combine the kernel and initramfs into a single U-boot image
Create a combined U-boot image (kernel and initramfs)
Code:
mkimage -A arm -O linux -T multi -a 0x40208000 -e 0x40208000 -C none -n "multi image" -d arch/arm/boot/uImage:arch/arm/boot/uRamdisk uImage.CyanogenMod.new
Transfer it to the device
Boot your touchpad into recovery mode and run
Code:
adb shell mount /dev/block/mmcblk0p13 /boot
adb push uImage.CyanogenMod.new /boot/uImage.CyanogenMod.new
adb shell umount /boot
adb shell reboot
After it reboot you should be able to see a new CyanogenMod.new item from the boot menu.
That's it!
Optimisation
For those who wants to experiment with GCC build options you can update the entry "arch-$(CONFIG_CPU_32v7" in file arch/arm/Makefile and I set mine to
Code:
arch-$(CONFIG_CPU_32v7) :=-D__LINUX_ARM_ARCH__=7 -mtune=cortex-a8 -mfpu=neon -ftree-vectorize -mfloat-abi=softfp -O2 $(call cc-option,-march=armv7-a,-march=armv5t -Wa$(comma)-march=armv7-a)
Warning
Please be aware you are working on the bleeding edge kernel for touchpad and there is no guarantee that the latest git version will work for you. Please try an earlier version if that's the case.
As of 2011-11-23 you will need the latest kernel source to build kernel for alpha 3. Please do not mix the kernel with an initramfs from a different version, i.e. don't use initramfs extracted from alpha 2.1 and use it with alpha3.
Thanks for this. Last weekend spent a while trying to figure this out.
Sent from my HP Touchpad using Tapatalk
x2. Huge thanks
Thank you soooooo much for this guide. Quick question if you don't mind though.. I am using an mkimage that goes back to my nook kernel days. Is there anything newer out, or would this still be ok,?
Divine_Madcat said:
Thank you soooooo much for this guide. Quick question if you don't mind though.. I am using an mkimage that goes back to my nook kernel days. Is there anything newer out, or would this still be ok,?
Click to expand...
Click to collapse
As long as the mkimage can generate a standard U-boot image it should be fine.
You can always try it yourself. In worst case you have to hard reboot the touchpad by pressing the power button and home button at the same time for more than 10 minutes. As long as you keep the original image files (UImage.*) untouched I don't think you can brick it even if you want to.
S7
I have been trying to compile the kernel for some time now, and was hopeful reading your guide (and this last post) However, still following the steps to merge the ramdisk, i cannot make a booting kernel. I can get it flashed, as i am using the update.zip method, but moboot always gives me a crc error when booting it.
Though, before i totally go nuts, i think i need to try the source forgery toolchain, as i am using the Android ndk r6b...
Divine_Madcat said:
S7
I have been trying to compile the kernel for some time now, and was hopeful reading your guide (and this last post) However, still following the steps to merge the ramdisk, i cannot make a booting kernel. I can get it flashed, as i am using the update.zip method, but moboot always gives me a crc error when booting it.
Though, before i totally go nuts, i think i need to try the source forgery toolchain, as i am using the Android ndk r6b...
Click to expand...
Click to collapse
Could you check the md5sum of the u-boot image crated on disk and the one installed by update.zip file? Do they match? If they do then you probably will need to upgrade your mkimage tool.
s7mx1 said:
Could you check the md5sum of the u-boot image crated on disk and the one installed by update.zip file? Do they match? If they do then you probably will need to upgrade your mkimage tool.
Click to expand...
Click to collapse
I will give it a check; just in case, know where to get a newer mkimage?
Thanks so much for this guide
s7mx1 said:
You can always try it yourself. In worst case you have to hard reboot the touchpad by pressing the power button and home button at the same time for more than 10 minutes.
Click to expand...
Click to collapse
It feels like 10 mins.. doesn't it
WEll, i checked the MD5 sums, and it looks good. So, i guess it is time to try again with the toolchain listed here, and perhaps a new mkimage (if there is a "modern" one i should using, please point me to it...)
edit: Never mind.. in all my looking, i never saw that ubuntu had a nice one waiting for me.... doh
edit2: Woo! After getting the probably correct mkimage, and the CS toolchain, looks like i finally got it to pass the crc check. Now, lets see if it finishes booting. Thanks again for the guide!
Nope.. no boot. I get a dmesg with this:
<3>[ 69.978716] init: untracked pid 224 exited
<6>[ 70.086076] android_usb gadget: high speed config #1: android
<6>[ 70.086209] gadget_event: schedule host_connected
<6>[ 70.096953] max8903b_current_setup: CURRENT_500MA
<6>[ 70.097040] gadget_event: source=bus mA=500 (no change)
<4>[ 70.910953] UDC-CHG (2-2-2): usb_multi_chg_detect (591) : USB host Adaptor
(500mA)!
<6>[ 70.912805] gadget_event: schedule host_disconnected
<6>[ 70.925482] max8903b_current_setup: CURRENT_ZERO
<6>[ 71.164066] android_usb gadget: high speed config #1: android
<6>[ 71.164220] gadget_event: schedule host_connected
<6>[ 71.173640] max8903b_current_setup: CURRENT_500MA
<6>[ 71.178212] gadget_event: source=bus mA=500 (no change)
<6>[ 72.160955] gadget_event: host_connected=1 (no change)
<6>[ 74.142224] request_suspend_state: wakeup (0->0) at 74121495501 (2011-11-1
1 22:49:33.378031648 UTC)
<3>[ 74.143675] init: untracked pid 266 exited
<3>[ 74.155217] init: untracked pid 273 exited
<6>[ 79.285016] request_suspend_state: wakeup (0->0) at 79264287462 (2011-11-1
1 22:49:38.520824942 UTC)
The last three lines repeat alot, with different pid's .
Alrighty.. figured this one out - You cannot use the latest repository commits with the 2.1 alpha build. However, i was able to build commit fd70bb7aae, and it builds and actually boots. Now, i can actually play around and tweak it. Thank you again for the guide, and sorry for the edit spamming.. heh.
myn said:
x2. Huge thanks
Click to expand...
Click to collapse
Myn, do you have a touchpad???!!!? God I hope so!
vinscuzzy said:
Myn, do you have a touchpad???!!!? God I hope so!
Click to expand...
Click to collapse
He does
Sent from my PG86100 using Tapatalk
Divine_Madcat said:
WEll, i checked the MD5 sums, and it looks good. So, i guess it is time to try again with the toolchain listed here, and perhaps a new mkimage (if there is a "modern" one i should using, please point me to it...)
edit: Never mind.. in all my looking, i never saw that ubuntu had a nice one waiting for me.... doh
edit2: Woo! After getting the probably correct mkimage, and the CS toolchain, looks like i finally got it to pass the crc check. Now, lets see if it finishes booting. Thanks again for the guide!
Nope.. no boot. I get a dmesg with this:
<3>[ 69.978716] init: untracked pid 224 exited
<6>[ 70.086076] android_usb gadget: high speed config #1: android
<6>[ 70.086209] gadget_event: schedule host_connected
<6>[ 70.096953] max8903b_current_setup: CURRENT_500MA
<6>[ 70.097040] gadget_event: source=bus mA=500 (no change)
<4>[ 70.910953] UDC-CHG (2-2-2): usb_multi_chg_detect (591) : USB host Adaptor
(500mA)!
<6>[ 70.912805] gadget_event: schedule host_disconnected
<6>[ 70.925482] max8903b_current_setup: CURRENT_ZERO
<6>[ 71.164066] android_usb gadget: high speed config #1: android
<6>[ 71.164220] gadget_event: schedule host_connected
<6>[ 71.173640] max8903b_current_setup: CURRENT_500MA
<6>[ 71.178212] gadget_event: source=bus mA=500 (no change)
<6>[ 72.160955] gadget_event: host_connected=1 (no change)
<6>[ 74.142224] request_suspend_state: wakeup (0->0) at 74121495501 (2011-11-1
1 22:49:33.378031648 UTC)
<3>[ 74.143675] init: untracked pid 266 exited
<3>[ 74.155217] init: untracked pid 273 exited
<6>[ 79.285016] request_suspend_state: wakeup (0->0) at 79264287462 (2011-11-1
1 22:49:38.520824942 UTC)
The last three lines repeat alot, with different pid's .
Alrighty.. figured this one out - You cannot use the latest repository commits with the 2.1 alpha build. However, i was able to build commit fd70bb7aae, and it builds and actually boots. Now, i can actually play around and tweak it. Thank you again for the guide, and sorry for the edit spamming.. heh.
Click to expand...
Click to collapse
That's because dalingrin has updated the default configuration to use the HIGHMEM which seems to kill all the apps. The latest git actually works if you disable all the HIGHMEM related stuff.
decalex said:
Thanks so much for this guide
It feels like 10 mins.. doesn't it
Click to expand...
Click to collapse
Absolutely
I just hope there is a rest button as the touchscreen occasionally will not respond at all after wake up and I have to reboot to webos and then reboot back to get the touchscreen back.
Great guide and I got the kernel all built, but how do you change the kernel arguments for booting? e.g. where does moboot get its whole root=/dev/ram0 ro fb...stuff, and how does the CyanogenMod kernel know where to look for the rootfs partition?
crimsonredmk said:
Great guide and I got the kernel all built, but how do you change the kernel arguments for booting? e.g. where does moboot get its whole root=/dev/ram0 ro fb...stuff, and how does the CyanogenMod kernel know where to look for the rootfs partition?
Click to expand...
Click to collapse
The root parameter (root=/dev/ram0) that passed to kernel is not useful to you. The root / is mere extracted initramfs in memory. I assume you are looking for system, data partitions etc. With TP we have LVM partitions which you can do really fancy stuff with. The actual mount device and mount point is defined (hard coded) in file init.tenderloin.rc which you can find in the initramfs (i.e. the img.gz which is a gzipped cpio file). You can extract all the contents out from img.gz and modify init.tenderloin.rc to suit your need and then create an updated initramfs file to go with the kernel.
Since Android (at least CM7 on TP) does not use pivot_root any changes made to the initramfs will appear automatically when you boot up the device.
You can google if you are not sure how to work with initramfs file.
Hi,
I bought a second hand i9505, which i used for several days with the standard Samsung stuff.
After a few day's i installed CM11, but after a day my wifi stopped working.
Then i started googling, found several other treads with the same problem, tried those solutions.
But at the this point none of them worked for me.
Things that i tried:
-Different modems
-Stock Samsung rom
-Factory reset
-Format /system , and reflash stock rom with Odin
-Pull the battery out for 30mins
-Reconnected the Wifi antenna
-Deleted the WPA_Supplicant file
-Disable the powersaving mode under *#0011#
Al of them did not work for me.
Is there anybody who has an idea?
Thanks in advance!
sven93 said:
Hi,
I bought a second hand i9505, which i used for several days with the standard Samsung stuff.
After a few day's i installed CM11, but after a day my wifi stopped working.
Then i started googling, found several other treads with the same problem, tried those solutions.
But at the this point none of them worked for me.
Things that i tried:
-Different modems
-Stock Samsung rom
-Factory reset
-Format /system , and reflash stock rom with Odin
-Pull the battery out for 30mins
-Reconnected the Wifi antenna
-Deleted the WPA_Supplicant file
-Disable the powersaving mode under *#0011#
Al of them did not work for me.
Is there anybody who has an idea?
Thanks in advance!
Click to expand...
Click to collapse
Hi,
Maybe is hardware related did you check if the WIFI Antenna Signal Flex Cable is well connected?
https://www.ifixit.com/Teardown/Samsung+Galaxy+S4+Teardown/13947
MAX 404 said:
Hi,
Maybe is hardware related did you check if the WIFI Antenna Signal Flex Cable is well connected?
Click to expand...
Click to collapse
Thanks, but i already tried this.
Reconnected both connections, and made sure both were aligned flat on the connector.
Unfortunately without any result.
sven93 said:
Thanks, but i already tried this.
Reconnected both connections, and made sure both were aligned flat on the connector.
Unfortunately without any result.
Click to expand...
Click to collapse
Maybe is the chip....can you scan , do you see wifi networks or did you try the option wifi direct , between your phone and another unit?
MAX 404 said:
Maybe is the chip....can you scan , do you see wifi networks or did you try the option wifi direct , between your phone and another unit?
Click to expand...
Click to collapse
Well, lets hope its not the chip.
I can't turn on the wifi, if i tap the wifi button (either in settings or at the notifications area) it goes green for 0.5 sec and goes to grey right after.
Haven't tried wifi-direct as i don't have any compatible devices.
Just tried to turn on the tether service, there is states "Error" when i try to turn it on.
Is there any logfile that i can use to determine the cause?
sven93 said:
Well, lets hope its not the chip.
I can't turn on the wifi, if i tap the wifi button (either in settings or at the notifications area) it goes green for 0.5 sec and goes to grey right after.
Haven't tried wifi-direct as i don't have any compatible devices.
Just tried to turn on the tether service, there is states "Error" when i try to turn it on.
Is there any logfile that i can use to determine the cause?
Click to expand...
Click to collapse
Not sure about the log file ...
Here i found a thread , it talks about a solution but they use a SPT box, for what i see the problem is efs related, do you have an EFS backup?
http://forum.gsmhosting.com/vbb/f45...nlock-default-efs-imei-solution-here-1788263/
Nope, unfortunately i didn't backup the EFS folder.
Flashed my S2 a thousand times, with backup, never happened anything. I flash my S4 1 time without,...
Compared the content with the S2, and for me is looks like everything needed is still there. (not an expert though)
Any other ideas?
sven93 said:
Nope, unfortunately i didn't backup the EFS folder.
Flashed my S2 a thousand times, with backup, never happened anything. I flash my S4 1 time without,...
Compared the content with the S2, and for me is looks like everything needed is still there. (not an expert though)
Any other ideas?
Click to expand...
Click to collapse
1. Dial *#1234# in Stock Rom and check if your Csc is correct.
2. Reflash 2 times the stock rom.
Joku1981 said:
1. Dial *#1234# in Stock Rom and check if your Csc is correct.
2. Reflash 2 times the stock rom.
Click to expand...
Click to collapse
CSC Seems to match.
Tried flashing it 3 times in a row with the same (stock) ROM, still nothing.
sven93 said:
Hi,
I bought a second hand i9505, which i used for several days with the standard Samsung stuff.
After a few day's i installed CM11, but after a day my wifi stopped working.
Then i started googling, found several other treads with the same problem, tried those solutions.
But at the this point none of them worked for me.
Things that i tried:
-Different modems
-Stock Samsung rom
-Factory reset
-Format /system , and reflash stock rom with Odin
-Pull the battery out for 30mins
-Reconnected the Wifi antenna
-Deleted the WPA_Supplicant file
-Disable the powersaving mode under *#0011#
Al of them did not work for me.
Is there anybody who has an idea?
Thanks in advance!
Click to expand...
Click to collapse
I have the same problem. Wifi won't turn on no matter what I do. I was on cm-11-20140627-NIGHTLY-jflte and then decided to upgrade to cm-11-20140908-NIGHTLY-jflte. With that upgrade I lost wifi. I tried every possible thing that I found on forums and nothing helped. I also tried to upgrade to latest stock. I was on old bootloader until then, now I have the KNOX sh...t.
I have a feeling that something is wrong with wifi firmware. Is there a way to somehow check or reflash wifi firmware only?
regards.
ajax505 said:
I have the same problem. Wifi won't turn on no matter what I do. I was on cm-11-20140627-NIGHTLY-jflte and then decided to upgrade to cm-11-20140908-NIGHTLY-jflte. With that upgrade I lost wifi. I tried every possible thing that I found on forums and nothing helped. I also tried to upgrade to latest stock. I was on old bootloader until then, now I have the KNOX sh...t.
I have a feeling that something is wrong with wifi firmware. Is there a way to somehow check or reflash wifi firmware only?
regards.
Click to expand...
Click to collapse
Sad to hear you have the same.
Pretty strange, i haven't used the S4 since Wednesday, but the phone was still turned on, ten minutes ago i wanted to check something, turns out wifi is working again, until i decided to reboot, now its doing the same as before...
It does indeed smells software/firmware related.
Just made a dumpfile of the logs (bugreport > /mnt/sdcard/dump.txt) , and saw some interesting stuff in the kernel log:
<4>[ 9.717163] failed to power up wifi chip, retry again (5 left) **
<4>[ 9.717163]
<4>[ 9.733306] ## wifi_remove
<4>[ 9.733612] wifi_set_power = 1
<4>[ 9.733612] WiFi: trying to acquire BT lock
<4>[ 9.733612] ####btlock acquired cookie: WiFi
<4>[ 9.733642] wifi_set_power: btlock acquired
<6>[ 9.733642] ------------------------------------------------
<6>[ 9.733642] ------------------------------------------------
<6>[ 9.733642] brcm_wlan_power Enter: power on
<3>[ 9.733642] brcm_wlan_power: WL_REG_ON failed to pull up
<4>[ 9.733734] wifi_probe: set_power failed. err=-5
<4>[ 9.733734] wifi_set_power = 0
<4>[ 9.733734] ####btlock released, cookie: WiFi
<6>[ 9.733734] ------------------------------------------------
<6>[ 9.733795] ------------------------------------------------
<6>[ 9.733825] brcm_wlan_power Enter: power off
<3>[ 9.733825] brcm_wlan_power: WL_REG_ON failed to pull down
Click to expand...
Click to collapse
Then after a bit:
<4>[ 11.727294]
<4>[ 11.727294] failed to power up wifi chip, retry again (4 left) **
<4>[ 11.727294]
<4>[ 11.743499] ## wifi_remove
<4>[ 11.743835] wifi_set_power = 1
<4>[ 11.743835] WiFi: trying to acquire BT lock
<4>[ 11.743835] ####btlock acquired cookie: WiFi
<4>[ 11.743835] wifi_set_power: btlock acquired
<6>[ 11.743835] ------------------------------------------------
<6>[ 11.743865] ------------------------------------------------
<6>[ 11.743865] brcm_wlan_power Enter: power on
<6>[ 11.743865] barcode_emul_ice4: ice_gpiox_set : num = 3 , val = 1
<6>[ 11.754608] [email protected]: Start PackageManagerService
<6>[ 11.775604] [SSP] Updated 73599 bytes / 139282 bytes
<4>[ 11.977172] wifi_set_carddetect = 1
<4>[ 11.977172] brcm_wifi_status:267 status 1
Click to expand...
Click to collapse
For people who want to view the log: https://dl.dropboxusercontent.com/u/15503253/dumpfile.txt
I also get those kind of messages in my system logs:
<4>[ 1837.921936] failed to power up wifi chip, retry again (1 left) **
<4>[ 1837.921966]
<4>[ 1837.941497] ## wifi_remove
<4>[ 1837.941497] wifi_set_power = 0
<4>[ 1837.941528] ####btlock released, cookie: WiFi
<6>[ 1837.941558] ------------------------------------------------
<6>[ 1837.941558] ------------------------------------------------
<6>[ 1837.941589] brcm_wlan_power Enter: power off
<6>[ 1837.941619] barcode_emul_ice4: ice_gpiox_set : num = 3 , val = 0
<4>[ 1838.182006] wifi_set_carddetect = 0
<4>[ 1838.182037] brcm_wifi_status:267 status 0
<6>[ 1838.182067] mmc1: Slot status change detected (1 -> 0)
<4>[ 1838.187591]
<4>[ 1838.187622] failed to power up wifi chip, max retry reached, exits **
Click to expand...
Click to collapse
I also get a lot of "mmc1: Data CRC error":
<3>[ 1826.574645] mmc1: Data CRC error
<3>[ 1826.577178] msmsdcc_data_err: opcode 0x00000035
<3>[ 1826.581542] msmsdcc_data_err: blksz 4, blocks 1
<6>[ 1826.586883] sps:BAM 0x12182000 enabled: ver:0x5, number of pipes:6dhd_detach(): thread:dhd_sysioc:392 terminated OK
<4>[ 1826.651245] dhd_detach(): thread:dhd_watchdog_thread:38f terminated OK
<4>[ 1826.651336] dhd_dpc_thread: Unexpected up_cnt 0
<4>[ 1826.651428] dhd_detach(): thread:dhd_dpc:390 terminated OK
<4>[ 1826.651733] dhd_detach(): thread:dhd_rxf:391 terminated OK
<6>[ 1826.670593] CFG80211-INFO2) wl_event_handler : was terminated
<4>[ 1826.670898] wl_destroy_event_handler(): thread:wl_event_handler:38e terminated OK
<4>[ 1826.682250] dhdsdio_disconnect : the lock is released.
<4>[ 1826.683807] ## wifi_remove
<4>[ 1826.683837] wifi_set_power = 0
<4>[ 1826.683868] ####ignore lock release, cookie mismatch: WiFi owner ˙˙˙˙
<6>[ 1826.683898] ------------------------------------------------
<6>[ 1826.683898] ------------------------------------------------
<6>[ 1826.683929] brcm_wlan_power Enter: power off
<6>[ 1826.683959] barcode_emul_ice4: ice_gpiox_set : num = 3 , val = 0
<4>[ 1826.920593] wifi_set_carddetect = 0
<4>[ 1826.920623] brcm_wifi_status:267 status 0
<6>[ 1826.920654] mmc1: Slot status change detected (1 -> 0)
<6>[ 1826.928405] mmc1: card 0001 removed
<6>[ 1828.083618] synaptics_rmi4_i2c 3-0020: [0][P] 0x01
<6>[ 1828.142578] synaptics_rmi4_i2c 3-0020: [0][R] 0x00 M[4] V[5c]
<4>[ 1828.178527] wifi_set_power = 1
<4>[ 1828.178558] WiFi: trying to acquire BT lock
<4>[ 1828.178558] ####btlock acquired cookie: WiFi
<4>[ 1828.178558] wifi_set_power: btlock acquired
<6>[ 1828.178558] ------------------------------------------------
<6>[ 1828.178588] ------------------------------------------------
<6>[ 1828.178588] brcm_wlan_power Enter: power on
<6>[ 1828.178588] barcode_emul_ice4: ice_gpiox_set : num = 3 , val = 1
<4>[ 1828.411895] wifi_set_carddetect = 1
<4>[ 1828.411926] brcm_wifi_status:267 status 1
<6>[ 1828.411956] mmc1: Slot status change detected (0 -> 1)
<3>[ 1828.473205] mmc1: msmsdcc_switch_io_voltage: MCIDATIN_3_0 is still not all zeros
<3>[ 1828.480651] mmc1: CMD7: Command CRC error
<3>[ 1828.484039] mmc1: SDCC PWR is ON
<3>[ 1828.487426] mmc1: SDCC clks are ON, MCLK rate=400000
<3>[ 1828.492217] mmc1: SDCC irq is enabled
<3>[ 1828.495849] ===== SDCC-CORE: Register Dumps @phys_base=0x12180000, @virt_base=0xe337a000 =====
<3>[ 1828.504608] Reg=0x00: 0x00000001, 0x01209300, 0x00000000, 0x00000447
<3>[ 1828.510955] Reg=0x10: 0x00000000, 0x00000000, 0x00000000, 0x00000000
<3>[ 1828.517120] Reg=0x20: 0x00000000, 0x00000000, 0x00000000, 0x00000000
<3>[ 1828.523620] Reg=0x30: 0x00000000, 0x004c0000, 0x00000000, 0x408001ff
<3>[ 1828.529785] Reg=0x40: 0x00000000, 0x00000000, 0x00000000, 0x00000000
<3>[ 1828.536285] Reg=0x50: 0x06000018, 0x00000000, 0x00000000, 0x00000000
<3>[ 1828.542633] Reg=0x60: 0x67356400, 0x00000000, 0x00000018, 0x00000000
<3>[ 1828.548797] ===== SDCC-DML: Register Dumps @phys_base=0x12180800, @virt_base=0xe3534800 =====
<3>[ 1828.557495] Reg=0x00: 0x00000000, 0x00010001, 0x00000000, 0x00000000
<3>[ 1828.563629] Reg=0x10: 0x00000000, 0x00001000, 0x00001000, 0x00020001
<3>[ 1828.570159] Reg=0x20: 0x00000000, 0x00000000, 0x00000000, 0x00000000
<3>[ 1828.576477] Reg=0x30: 0x00000000, 0x00000000, 0x00000000, 0x00000000
<3>[ 1828.582641] Reg=0x40: 0x00000000, 0x00000000, 0x00000000, 0x00000000
<3>[ 1828.589172] ===== SDCC-BAM: Register Dumps @phys_base=0x12182000, @virt_base=0xe33d8000 =====
<3>[ 1828.597503] Reg=0x00: 0x00000000, 0x00000000, 0x00000000, 0x00000000
<3>[ 1828.604003] Reg=0x10: 0x00000000, 0x00000000, 0x00000000, 0x00000000
<3>[ 1828.610351] Reg=0x20: 0x00000000, 0x00000000, 0x00000000, 0x00000000
<3>[ 1828.616516] Reg=0x30: 0x00000000, 0x00000000, 0x00000000, 0x00000000
<3>[ 1828.623016] Reg=0x40: 0x00000000, 0x00000000, 0x00000000, 0x00000000
<3>[ 1828.629180] mmc1: MCI_TEST_INPUT = 0x0000003e
<3>[ 1828.633697] mmc1: got_dataend=0, prog_enable=0, wait_for_auto_prog_done=0, got_auto_prog_done=0, req_tout_ms=10000
<3>[ 1828.644012] mmc1: PM: sdcc_suspended=0, pending_resume=0, sdcc_suspending=0
<3>[ 1828.650817] mmc1: RPM: runtime_status=0, usage_count=2, is_suspended=0, disable_depth=0, runtime_error=0, request_pending=0, request=0
<4>[ 1828.663024] mmc1: Skipped tuning.
<3>[ 1828.686431] mmc1: error -110 whilst initialising SDIO card
<4>[ 1830.421936]
<4>[ 1830.421966] failed to power up wifi chip, retry again (4 left) **
Click to expand...
Click to collapse
As long as I know mmc0 is internal memory and mmc2 is external sd card. Can anyone explain what mmc1 device is?
Bump...