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.
Related
First post here but I have searched and read a lot since joining.
I bit the bullet and rooted my hero last night following this guide from regaw_leinadso I guess I can't post links...)
Everything went fine so I then wiped and loaded freshrom 2.1.2 followed by a damage710.zip overclocking file in that order. This also worked fine and I was enjoying the new setup.
The main reason I rooted was for wifi tethering so I tried it out and kept getting a "unable to start tethering, please try again" message. After more reading I found that there was a bug in 212 on superuser permissions. So, I loaded the 212 su fix file and went back to wifi tether. The su permission came up and I selected always allow, was able to connect and all was good. I then tried to stop, su permission came up again, always allow was selected...then the device froze on "stop tethering." The only way for me to get out of this was to pull the battery.
I tried it again, and again it freezes at stop tethering and I have to pull the battery. I tried updating wifi tether with the one that is currently on the market (202) and that version stops at "unable to start tethering" message.
My initial recovery image was 1.5.2. I then did the process again using 1.2.3 with the exact same results.
Am I missing something here?
Thanks
In the dev threads there is a kernel you need to flash to stop it from freezing. I couldn't tell you if it works with your rom though. just have to try it.
Thanks; any idea where or which one it is? I can't seem to find it.
Kcarpenter said:
In the dev threads there is a kernel you need to flash to stop it from freezing. I couldn't tell you if it works with your rom though. just have to try it.
Click to expand...
Click to collapse
Found it. Kernel is in the following thread:
"[KERNEL][OC]Darchstar's GoDmOdE-Darchshizz #15 for senseUI roms - UNDERVOLTED"
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
OK - this is my fault and I'm willing to put the work in to fix it myself but I'm hoping someone knows off the top of their head.
Transformer firmware all up to date. Rooted and on MagnuSupr3m3 ROM.
I had also pushed a modified WPA_Supplicant file to enable ad-hoc tether to my HD2 - that worked great.
I applied Sheshmaru's cool win phone7 theme to check it out. see link below
http://forum.xda-developers.com/showthread.php?t=1120525
Somewhere after applying the theme I found that wifi could no longer connect at all and showed error as it's status. This problem persisted even after I rolled back to a recovery backup of prime 1.4 I had made - using SolarNZ CWM R3.
Any suggestions? I'd rather learn how the wifi stack is working and apply fixes rather than just reinstall the whole thing
I had the same Wifi Error status on my TF, but that was after I got it rooted and flashed the newer CWM on it. Toggling Airplane mode fixed the Wifi for me, no idea why lol
SOLVED
If anyone else suffers this misfortune the fix for me was this:
Followed instructions to add an eraseData file in the Solarnz CWM thread - http://forum.xda-developers.com/showthread.php?t=1093818
Reloaded my recovery.
There is most likely a better way to do this by just pushing some wifi related files into the right folder but that goes beyond me and I couldn't drum up any instructions from a quick google.
Ok, here it goes. let me first say that I am just learning alot of this stuff. I'v had my DX for almost a year now and had it Z4rooted and the tether apk applied in no time at all then came the GB update which was actually pushed onto me. So be it.
I have been watching the forums and reading posts off and on since the update, waiting till another reliable tether patch came out. I have the radiocomm app but was always leery of using it with my limited knowledge in this field.
Today after alot of reading I decided to install Liberty3 v2.0 Gold and did so with no problem whatsoever. then I continued reading and then decided to continue on with 3GHotspot.zip and TBH_DX_Tether_Patch_1.0.zip in that order. I did it through the built in ROM mgr. in liberty3 in the rom toolbox. with reboots in between.
I then went into my apps list and clicked on the new 3G wi-fi tether icon and was immediately shot to my boot screen animation. Thinking this was a fluke I attempted it 2 more times with the same result, Reboot. After this I noticed that I was on 3g data and no longer connected to my home wi-fi router I went in and tried to turn that back on but it won't even try. I'm locked out of wi-fi now as well.
I then turned to my friend google and started looking around and found one post and only one posting listing at mydroidworld post# 35944 that had this link "3GHotspot Unpatch --- Download" but that link was broken because of it being a megaupload link (which we all know was seized by the feds)
I have no idea what to do to rectify this situation. I am all for re-flashing the ROM and plan on doing that but I would like some guidance on this before I start messing things up worse than they already are. are there uninstalls for both of thes zips? if so where? have either of these altered my radios NVM authentication strings with these hacks and patches? can they be undone? please help.
Nope, no uninstalls for those zips. At least not to my knowledge.
Ok, I ended up having to SBf back to .602 with RSDLite 5.4.4 and then take the OTA update to .605.
I then re-flashed the Liberty3 v2.0Gold and then through the built in ROM Mgr. I installed the WugPacked GB Tether Patch.zip and everything worked out great. working free Wi-Fi. Thanks to those that both helped and wanted to help but forgot to post anything in the space provided.
Issue solved.
Hi Folks,
I've been lurking and getting great advice form this forum for many years but have finally come up with something I can't fix myself.
I was running a few custom roms but somehow when trying out a few of them I have managed to do something so that I can't flash any custom roms any more.
TWRP which gives an error 7 message (which seems to suggest that my phone no longer thinks it is a moto x play). At present I can install stock roms using ADB but that seems to be about it. I have tried to roll back using a stock rom from the motorola website (LUX_RETLA_DS_LPD23.118-6.1_cid12_lux_retla_ds) but that didn't fix it.
I also can't seem to root my current stock rom (XT1562_LUX_RETEU_6.0.1_MPD24.107-52) but am sure I was able to before i had this problem.
I can't help but think I probably should be grateful that whatever i did didn't brick my phone but I've been trying every idea I can find that over the last few months and nothing has helped. I get the idea it might be some kind of low level partition issue but that is just a desperate hunch. From time to time I've got what seem to be partition errors when try various roms to fix this but they've usually worked their way out.
Any hints or suggestions on how to rectify this would be most welcome.
N