[Q] USB tethering for RoyalGinger 2.0 w/logcat - myTouch 4G Q&A, Help & Troubleshooting

I just flashed from royalginger 1.6 to 2.0. Also flashed the new radio 9.04.26 and added the engineering bootloader. lol I've been busy today. Anyways whenever i usb tether now mt4g reboots. I already wiped cache and dalvik cache and fixed permissions, did not work. i have saved a logcat via the app from the market, not sure if the logcat got the info so let me know. Wifi hotspot still works, but i prefer usb tethering. If anyone could help it would be greatly appreciated thanks.

i think i figured this out maybe? I flashed faux123's newest kernel and now my usb tethering works fine. here's the logcat from the working usb tether so anybody who's interested can compare the two logcats.
edit: also i changed some stuff in the service.jar file using cskigen's throttle "fix" so i don't know which one fixed my problem or if it was neither.

Related

WIFI Tether on stock EPE54B with root

Hey everyone, so up to yesterday I was running modaco N1 2.0 ROM but trying to install the updated google maps became a pain cause nothing was working. Tried all the solutions on the modaco forum but didn't work for me. Anyways, I decided to go back to stock with root cause I still wanted to be able to USB and wifi tether. Anyways, installed the tether packages and now it says I have an improperly configured kernel. I'm sure this is related to the kernel being stock but I Dont know how to fix the issue. I was hoping someone could guide me. Could I simply pull the kernel out of modaco's/Cyanogen's ROM and push it to my N1? If so, I'd like some help since this is past my knowledge.
Thanks
bump cause I'm hoping someone can help me. I tried following the instructions on google code for updating the kernel to do this but I'm getting this error when doing ismod
insmod: init_module '/sqlite_stmt_journals/bcm4329.ko' failed (Exec format error
hopefully someone can help.
Got it working, the Undervolted kernel will work on stock rom, using the insecure boot image and pushing the wireless module. in the undervolted zip.

Please help. GPS and WiFi not working... any ideas?

I'm having a problem. Hopefully someone can help. Im running the Epic Experience ROM with the newest mixup kernel.Ive been running this ROM flawlessly for a few days and now for some reason when I click wifi or gps I don't get the icons at the top and they do not run but 4G will kick in. I tried wiping data and cache and re flashing the ROM and nothing. I also tried re doing the one click root and nothing. Any ideas?
Ok I got my GPS running but WiFi is still not working.

Wifi Error

So after a search here and through Google I haven't been able to get this fixed. I was running CyanogenMod 5.0.8 without problems, but wanted to try out Chromatic 4.5. After flashing Chromatic, WiFi worked for a few hours, but then it just suddenly stopped working. From the "Power Widget" WiFi just shows the grey bar below it like it's turning on/off, but it's not doing anything. When I click it, it does nothing. If I go to Wireless and Networks from the Menu, WiFi shows "Error" up under it. The only possible solution I've found was for the Droid that said to try flashing the ROM using a GoldCard, but that was with the Droid 2.2 update. I gave it a shot anyways with no success. I tried flashing with and without the GoldCard, and in both scenarios I tried flashing with and without a wipe. I restored my CM backup and WiFi is working again, so it's not a hardware problem (which I didn't think it was in the first place). Any help would be greatly appreciated guys and gals.
Bump, just to get back to the top I'd really like to get this straightened out.
Sent using Tapatalk.
Read and search the posts in development. It is simple to fix that error. Your situation is an incompatible rom. Try using CM6.
Sent from my HTC Magic using XDA App
Incompatible ROM???? It's a ROM using the CM 6 kernel and WiFi worked initially, so that's out the window. Thanks for the input though.
I have had the same problem since 0825 nightlies (nightly prior to CM6 official). Wifi works on the 0825 nightly but EVERYTHING since I get the wifi error. Logcat reports wifi driver failed to load. I have manually tried starting the driver, but still this damn error. I did flash the TMUS Froyo cm6 remix and that rom my wifi worked perfectly. I have flashed both pershoot and dumfuqs kernels--still the error. I manually pushed all things wlan to my mytouch and still nothing. So, there is no doubt that the error lies in the cm roms (or at least where it is mapping the drivers on our phone). Very frustrating. The fact that there are only a few of us having this problem leads me to believe that it is indeed a hardware issue or we have corrupted memory on our phones.
Anyway, I have given up trying to fix it. If you find a way, please post.
But, try flashing the tmus froyo remix AFTER nandroiding your rom and see if wifi continues to work.
I just reverted back to CM 5.0.8 for the time being. I'll probably try the T-Mobile 2.2 for the 32B since I'm sure someone will port it to the 1.2 once they get their hands on it.
Sent from my HTC Magic using Tapatalk

[Q] Wi-fi 'Error'

Hey guys, did some searches and can't find any help here and I wonder what I could try to get my wifi working again.
CM7.03
2.6.32.39-CM-GB-Faux123-v2.5.2-CFS
I was on CM7.03 and had been using the 2.6.5 until I realized the thread said it was only compatible with 2.3.4 ROMs. I had been having some freezing issues here and there and decided to look around.
I wiped cache and dalvik cache and moved to the correct kernel so now my wifi will not toggle and stays with just "Error".
Any thoughts? Reboot / battery pull is no good.
breakaway87 said:
Hey guys, did some searches and can't find any help here and I wonder what I could try to get my wifi working again.
CM7.03
2.6.32.39-CM-GB-Faux123-v2.5.2-CFS
I was on CM7.03 and had been using the 2.6.5 until I realized the thread said it was only compatible with 2.3.4 ROMs. I had been having some freezing issues here and there and decided to look around.
I wiped cache and dalvik cache and moved to the correct kernel so now my wifi will not toggle and stays with just "Error".
Any thoughts? Reboot / battery pull is no good.
Click to expand...
Click to collapse
I would recommend asking this in the rom thread. Your wifi issue might be rom specific and the other users in that rom thread or the dev should be able to assist you better.
Thanks, I'll try that
How did you flash the kernel? The issue is from a wrong wifi driver, which should have been updated with the kernel change.
Reboot into recovery, wipe cache and dalvik then install zip from sdcard
Fixed, turns out it was a bad wifi driver install and was noted in the original kernel post.. ouch lol. Just pushed the file over and rewrote it and it works now.

wifi issue

Is there any way i can extract wifi component from one ROM and use it another?
i've installed cyanogenmod 7.2 but can't connect to hidden wifi at work. I don't have access to access point to enable broadcast.
I've tried different ROMs and was able to finally get it to work with DARKSIDE SENSE v4.0 ROM with thederekjay's Kernel. But my phone keeps randomly booting and is really slow compared to cyanogenmod (200 vs 400 free mem).
So I flashed back to cyanogenmod and tried wifi module (bcm4329.ko) from DARKSIDE SENSE v4.0 ROM. But wifi doesn't work, I can't even enable wifi connection.
Any help would be greatly appreciated.
Thanks
That module is compiled for a very particular kernel, i.e. the one it came with. To regain some RAM you could de-sense the ROM and maybe run v6 supercharger to make the OS more aggressive about closing apps.
so I switched back to Darkside snese but my phone keeps randomly rebooting. I've tried flashing the ROM multiple times, clearing cache and formatting partitions. nothing seems to work. I was able to get 3 (of approx 30+ reboots) kernel panic logs: (/proc/last_kmsg )
h**ps://dropbox.com/s/u44a6eccgl257pd/1364486847908.txt
h**ps://dropbox.com/s/1mzy7a1l30vc74p/1364503975830.txt
h**ps://dropbox.com/s/mmpyv4ouowwclg0/1364746269337.txt
Can some one look at these logs and see what's causing the reboots.
thanks for the help

Resources