I'm Running Das Bamf 1.6 remix and I flashed leankernel extreme from Kernel Manager and now when I turn on wifi it just says error. I tried flashing two other kernels but I'm still getting a wifi error. I've restarted a few times and nothing has worked. Any suggestions? Thanks everybody
I would suggest downloading the kernel outside of kernel manager and flash it in recovery to see if that works. I prefer using recovery to flash things instead of Rom Manager of Kernel Manager. I have heard using something besides recovery could cause errors.
I would agree. Wipe Dalvik cache. I first flashed kernels through rom manager but it never worked great. Did it through recovery and things are very good. One small bug but hopefully that gets resolved soon. Im on Imoseyons lean kernel on normal mode. The battery saver mode did not work at all for me. Drained the battery like I drain a bottle of beer.
Its not just you, and at least my error has nothing to do with flashing it in through rom manager or kernel manager since I use neither. No matter the kernel I use, Ive not had wifi unless I had the stock kernel or for one day on Ziggys 5/3. Ive been having this issue for MONTHS now and Ive seen a lot of others have it with no resolution. I just tried nuking the Dav, restarting and nothing. Still getting the "Unable to scan for Networks" toast notification.
Related
Hi,
I was trying to flash a Ultimate Honeycomb v3.1.1 theme on my VZN Fascinate using CWM, but after flashing and rebooting, it just sits there on the booting screen (flashing honeycomb) while the phone vibrates occasionally. Can someone tell me how to fix this or why it's happening? I didn't have problem flashing gingerbread theme by nitsuj17.
I have SC2.9.2 voodoo/EB01
many thanks,
kim2rock said:
Hi,
I was trying to flash a Ultimate Honeycomb v3.1.1 theme on my VZN Fascinate using CWM, but after flashing and rebooting, it just sits there on the booting screen (flashing honeycomb) while the phone vibrates occasionally. Can someone tell me how to fix this or why it's happening? I didn't have problem flashing gingerbread theme by nitsuj17.
I have SC2.9.2 voodoo/EB01
many thanks,
Click to expand...
Click to collapse
Download might have been corrupted or you flashed SC and then flashed the theme without rebooting in between.
Thanks jonesya13!
I'm pretty sure I rebooted in between, but I will try to re-download the file and then flash the theme again as you suggested.
This happened to me on both the 3.1 & 3.1.2 with superclean 2.9.2. I booted fully into superclean as well before flashing the theme after a cache/dalvik wipe. Battery pull worked both times. Rebooted normally after that.
Thanks garywojdan81!
I tried to flash with a newer ultimate honeycomb (3.1.2), it flashed without a hitch but I found out that menu & home button didn't work. So I went back to SC2.9.2... I will try battery pull & wiping cache/dalvik then reflash the 3.1.2 theme.
kim2rock said:
Thanks garywojdan81!
I tried to flash with a newer ultimate honeycomb (3.1.2), it flashed without a hitch but I found out that menu & home button didn't work. So I went back to SC2.9.2... I will try battery pull & wiping cache/dalvik then reflash the 3.1.2 theme.
Click to expand...
Click to collapse
I had the menu and home button problem as well, ended up flashing, I think the EC10 kernal, and it fixed that problem for me.
Thanks jonesya13 and garywojdan81!
I tried reflashing the theme after wiping cache/dalvik - that did the trick!
I have not tried the EC10 kernel yet. So far, I'm satisfied with EB01, so I'll try sticking with it until it causes problems.
kim2rock said:
Thanks jonesya13 and garywojdan81!
I tried reflashing the theme after wiping cache/dalvik - that did the trick!
I have not tried the EC10 kernel yet. So far, I'm satisfied with EB01, so I'll try sticking with it until it causes problems.
Click to expand...
Click to collapse
You might as well as update to jt's ec10. BLN + Sound + Color.. Epiiiic
Just wipe cache/dalvik
Rocking Frankenclean 2.9.2 Voodoo/EC10+Sound+BLN+Color/Nitro Ultra Honeycomb v3.1/XDA Premium
xHoLyx,
What might be some advantages of jt's EC10 over regular EB01, in your opinion? I'm not too familiar with kernel replacement, so reading relevant posts might take some time. thx!
I tried 2.2 out a few weeks ago and decided I couldn't live without Voodoo Sound and BLN so I decided to wait it out. Obviously we have these enhancements available for Froyo now, so I made the jump to JT's initial EC10 release.
Everything worked fine, I just didn't feel that "snappiness" I had before. I thought maybe it had something to do with being undervolted (even though only slightly.) I saw that there were some problems with imnuts initial kernals he posted and waited to flash the updated (fixed) link for 0328_imnuts_sv_voodoo.zip. I flashed last night, booted up, and played around for a little bit and everything was working great. I had it plugged in to charge overnight. That brings me to my issue...
I woke up this morning, reached over to turn my phone on and I got NOTHING. No boot, samsung, lights, nada...I thought "****, I really bricked my phone now." I tried booting into recovery using the 3-button combo, plugging it in my computer to try download mode, plugging my charger in different outlets,etc...The phone seemed like there was no sign of life. I was ready to head to Verizon before work then decided to plug in my car charger for ****s and giggles and sure enough...IT WORKED! It started charging and I turned the phone on. Now I am at work and the phone seems to be working just fine...I even have the usb plugged in my computer and it is charging now (The same one that didn't work this morning.) This has never happened to me before and it was pretty scary. I have had to ODIN before, but I was worried that wasn't even an option. Thanks god everything SEEMS to be working fine right now, though that made me a little concerned.
Do anyone have ANY idea what might have happened!? Thanks in advance.
EDIT: After a couple hours, I saw my battery start to wig out. It went from being at like 34% to flashing the "low battery" warning. It then turned off and did the exact same thing. I had to go out to use my car charger to get into recovery. I wiped cache/dalvik cach, and re-installed SC. Not sure if it's kernal/ROM/Theme with 3rd party battery supprt...
Voodoo'd Samsung Fascinate
Kernal: 0328_imnuts_sv_voodoo
ROM: Superclean 2.9.2
Theme: Nitro's Ultimate Honeycomb v3.1.2
I found the solution to the problem described below. It was ROM Manager that was sabotaging me, for whatever reason. I went into CWM manually, wiped everything obsessively 3 times like I've seen other people describe, installed 1.6, and it worked perfectly. Too early to say how it actually runs for me but I least I've got it fully installed!
PROBLEM:
I started from stock rooted S-off ROM and installed Das BAMF 1.5, wiping everything as recommended. Under Settings/About Phone/Software information, the baseband, kernel, build number etc were all correct. Things ran OK, although battery life was pretty bad. But there were a number of anomalies. The Verizon bloatware still seems to be present. The location reticule is still present in the notification area. Etc.
Today I installed 1.6 over 1.5, again wiping everything even though it is said not to be essential. I did the install through ROM Manager. Everything proceeded as expected, the boot animation screen shows BAMF 1.6, all the About Phone information is correct for 1.6. But again, the location reticule is still present; signal strength indicator is 4 bars instead of 6, Verizon bloatware still present.
I know the real action is in the development thread but I still need a few more posts before reaching that exalted status. Anybody else seen/solved an issue like this? Any help is appreciated and if some kind moderator feels led to move this to the other thread, all the better!
[EDIT] A couple other anomalies are the extended Power Options and Reboot menu options shown in the 3rd and 4th screenshots at the beginning of the Das BAMF 1.6.1 development thread-- I don't have those. On the other hand, I do have BAMF Toolbox, Call Recorder, and other expected apps included with the ROM.
Thanks very much.
I'm having the exact same results. Frustrating!
Are you installing with ROM Manager, or directly from CWM?
Having the exact same issue and I installed with ROM manager. Should I reinstall 1.6 manually in CWR? I JUST rooted my phone a week ago and I think I may have flashed it 20X already, lol! I also have weird caller ID issues, it says CDMA call waiting when I miss a call, and Call waiting when I have a voicmail. If flashing it manually will fix these issues, I'll do it again!
Here's the thing I don't get. What's the fricking point of wiping 3 times?
If wiping == formatting a partition, then what good does it do to do it 3 times? None that I can imagine.
If wiping == deleting everything in a directory tree, then again, what point is it to wipe 3 times? What is accomplished on the second and third time that isn't on the first?
Just my opinion. I've never had a problem with wiping just once.
johnkc1975 said:
Having the exact same issue and I installed with ROM manager. Should I reinstall 1.6 manually in CWR? I JUST rooted my phone a week ago and I think I may have flashed it 20X already, lol! I also have weird caller ID issues, it says CDMA call waiting when I miss a call, and Call waiting when I have a voicmail. If flashing it manually will fix these issues, I'll do it again!
Click to expand...
Click to collapse
I would try hbooting the unsigned stock RUU. Then try flashing the rom of your choice through Cwm not rom manager. This should start you back at scratch with s off along with clearing up any bugs you can't seem to get rid of.
I had the same problem. Don't use Rom Manager for this Rom. Do it manually and everything will be like it should.
Ditto to that. All my unfruitful efforts were due to initiating the process via ROM Manager. Doing it all via CWR did the trick.
Alright, so I have a problem where my bluetooth and wifi don't work at all. Wifi status shows up as error and when I try to enable it, it just puts the phone in a reboot cycle where it starts up for a bit then restarts unless I can catch it fast enough to put it into airplane mode. From what I've been reading after doing some looking around on the net, it's most likely a kernel issue.
How can I figure out exactly what is causing this issue so I can flash over the corrupt kernel and try to get it to work? I've tried flashing 3 different roms but none of them fix the problem so I'd like to try to find a way to figure out which individual kernel is causing it.
Post what you've installed and what you're running. Usually using a ROM that does a full wipe will usually solve any issues. Are you using ROM manager to do your installs or CWM?
Originally I was having this issue on 1.83. When I used rsdlite to flash the stock 2.3.4 sbf, it fixed the issue for me. I later tried to install the new androidmarket apk and the issue came back.
Since then, I've used Tenfar's CWM to flash Ninja SF, Alien, the CWM stock 2.3.4 and am now running piCrust but I haven't been able to fix it again.
Hey, My wi-fi/hotspot shows up as error when i go to settongs and wireless networks. i had the problem with alien#4 so i decided to switch to cynanogen 7.1 and still nothing :/ is it a hardware problem or i need to flash a different baseband/kernel or what? thanks for the help in advance if anyone reples. it would mean alot haha
I had that issue when I installed one of faux123 kernels.I re-flashed the kernel wipped cache and dalvik and rebooted.I didn'tn have the issue afterwards,hope this helps out.
thanks. I tried flashing a 1.30 ghz kernel by faux123 and i have a bootloop :/
try flashing a different kernel.I notice the 1.3 works better than 1.45 for me no bootloops.try going into cwm and clear cache dalvik and fix permissions.
ok,im using tenfars recovery. should i be using clockwork mod?
i don't know what the problem is :/ i still have error for wi-fi.. but i flashed 145 cause that's all that would work
Atrixn00b said:
i don't know what the problem is :/ i still have error for wi-fi.. but i flashed 145 cause that's all that would work
Click to expand...
Click to collapse
Tenfa'rs recovery is outdated. Use romracer's instead (he just updated today).
*Edit* I ran into this same problem early on when I started flashing customs mods. Ended up having to go back to my "stock" backup before wi-fi started working again. After that, I haven't had it re-occur. That might be your best bet to get it functioning again. If not, it may be a hardware issue.
haha I just got this thing 3 months ago...hopefully it's not a hardware issue. but i'll try that
MY phone is completely effed right now..like the "soft keys" on the bottom don't work and the screen sensitivity is really low..it's like my phone is destroying itself or something.
Sounds like a hardware issue. I had the same exact issue.
Wifi error, some random reboots especially after trying to turn it on.
after much testing, reading, and playing around i started getting constant reboots. You could get too the lock screen, then it would reboot.
Before jumping to conclusions about hardware go back to your stock backup.Also use RomRacers newest recovery.then start flashing kernels again and see if the problem persists.Its easy to blame everything on hardware issues but often that's not the problem.
I want to give my wife's rezound more options that she is looking for out of her phone. Mainly wifi hot spotting. I installed RLS 4.0 two days ago and everything worked great except for her wifi would not turn on. Though maybe it was the kernel I used. So last night flashed the RLS 5.0 and the recomended "S-on" stock boot.img afterwards. Still the same thing. Everything seems to work great except for her wifi trys to work but will not. I've toggled the settings, turn on and off airplane mode many times etc etc. still nothing will get her wifi to run. I clean system, dalvic, cache etc each time as well. Is there something I am missing? I seen in the developers forum that a few others are having the same issue but not many. Any way to get this to work? Or is there another ROM to try? She really likes the latest sense in this ROM.
Try flashing the kernel using adb from your computer. Either that or flash a different kernel like dsb's kernel then flash the one xxx kernel over it
Sent from my ADR6425LVW using xda app-developers app