Hello everyone,
Lately I have been experiencing some interesting issue's with ICS based ROM'S(not leaks). Currently I am running .905 firmware with CWM 5.x.x.x as the primary method for flashing ROM's, so far I have tested Gummy 1.2, AOKP Milestone 6, and Cyanogen Mod yet the one major issue that seems to be popping it's little head up is a complete loss of DATA(Both 4g, and 3g) connectivity. I have attempted to force Auto CDMA/PRL using the command *#*#DATA#*#* from the dialer with no luck. The radio just does not want connect properly. Just for clarification I have two bionic's, and tested GB based(no issues with data), as well as ICS ROM's(data comes up initially, but drops out completely). Maybe I am flashing the device wrong, or need to flash the ICS leak(s)(do they contain a different radio version?), root the device then flash a alternate ROM over the leak? If anyone else is experiencing this issue or has a solution please give me the heads up. Thank again!!!
Related
Hi all,
I've been unable to find a post about this for quite some time so I decided to make a threat about it.
I have a recurring problem with my captivate. Usually after about 2 weeks of using a ROM my phone will have 2 issues pop up simultaneously. They seem to always happen together. It seems to happen after my phone shuts off and will not turn back on until I battery pull. Once I do that I am presented with these two issues:
1.) When I try and toggle Wifi it attempts to then simply says "error" underneath it. I have found a few threads about this but no answers
2.) Upon installation OR restoration of any app with Titanium Backup my phone does a soft reboot (goes to spinning CM logo or for ICS goes to the multicolored squares flying around).
Edit: On the newest MIUI it now says "insufficient storage available" instead of rebooting when I try to install an app after the issues crop up, wifi "error" is still the same
I've had these same 2 issues occur with CM7 Stable, RC, and many nightlies, MIUI, and TeamHacksung's ICS build. I believe it may have happened with cognition too but am not positive.
I do not restore any data with TB. Before each flash I wipe system, cache, dalvik, and do factory reset and still this issue occurs without fail after about 2 weeks on any ROM and the only fix I have is to flash a new one.
Nandroid backups DO fix the problem. If anyone is willing to look through logs or something and see what was different I would be eternally grateful and certainly send you something through PayPal
Any help is greatly appreciated and I am willing to try anything at this point. Thanks!
Sorry for the double post,
Is there a better forum to post this in?
spectralite said:
Sorry for the double post,
Is there a better forum to post this in?
Click to expand...
Click to collapse
Nah this is the right place. That's a very strange problem you're having though, and I don't know what the exact solution is, if there even is one for this. The only thing I can suggest is going back to stock, and then reinstalling CM7 or whatever you want
Sent from my lightning fast Glitched 1.3Ghz CM7 i897 Captivate
Thanks,
Well happened again on newest MIUI. Gonna go back to stock and start over. I'll update the thread if it does or does not happen again.
Unfortunately after using Odin to go back to stock and rerooting/flashing it happened again on the most current build of MIUI. I'm currently at a loss for what to do. Has anyone heard of or seen anything like this?
Thanks in advance
spectralite said:
Unfortunately after using Odin to go back to stock and rerooting/flashing it happened again on the most current build of MIUI. I'm currently at a loss for what to do. Has anyone heard of or seen anything like this?
Thanks in advance
Click to expand...
Click to collapse
Just curious, have you tried leaving it stock and seeing if it happens on a pure stock ROM? If so it could be a defect with the phone?
If you flash back to pure stock and the issue doesn't come back, maybe try a custom ROM that's closer to stock, not a CM or MIUI or ICS build. I haven't seen this issue, just trying to suggest some solutions.
I had this same problem with my fascinate. I flashed 1.10.21 MIUI follwed by glitch 13.1. This combination used to work, or so I thought. I flashed back to stock, 1.12.1 then a different package of glitch 13.1 and my wifi started working again. I know the captivates and fascinates are somewhat different, but try this out and see if it works.
bobbylx said:
Just curious, have you tried leaving it stock and seeing if it happens on a pure stock ROM? If so it could be a defect with the phone?
If you flash back to pure stock and the issue doesn't come back, maybe try a custom ROM that's closer to stock, not a CM or MIUI or ICS build. I haven't seen this issue, just trying to suggest some solutions.
Click to expand...
Click to collapse
I guess I could try that, I just like CM7/MIUI so much. Another thing that happens is many different applications start FCing after the problems all begin.
I tried to restore to a nandroid backup I had made before it happened this time and I received an MD5 mismatch which I believe happened last time I tried to restore...
New info:
I have not realized this before but it seems that I start getting a message that says, "Google Talk Authentication Failed", around the same time. Also FCs happen much more frequently. Is there anything I could be doing to cause this?
New Info
Just going to keep this updated with things I have tried in case anyone ever searches for this that has this issue:
Full format of SD card and odin back to stock did not prevent the issue from cropping up on the DarkKnight3 ROM with Icy Glitch. At this point I can only assume it is somehow hardware relatedl
i search whole vivid forum about this problem
some guys (like me ) have problem with wifi on custom Roms
in some kernel wifi stuck on "wifi is turning on ..." and some kernel wifi could be on but it's crazy (like couldn't off) and couldn't find any wifi signal.
phone go to s-off but problem not solved
phone like Velocity 4G x710s
any body have a suggestion or help
when you flash any kernel, after that you have to push these file (bcmdhd.ko) which is in the kernel you download - to system/lib/module
and you will have wifi working with every kernel
mohamed_moscow said:
when you flash any kernel, after that you have to push these file (bcmdhd.ko) which is in the kernel you download - to system/lib/module
and you will have wifi working with every kernel
Click to expand...
Click to collapse
i found some "bcmdhd.ko" in some kernel
which is best for me
Cant wait for release!!
Can you upload that file for us?
Sent from my HTC Raider 4G LTE running ICS.
ideaLduK said:
Can you upload that file for us?
Sent from my HTC Raider 4G LTE running ICS.
Click to expand...
Click to collapse
yes, upload that for us
Every kernel has it's own specific modules.
Thats why if you're S-ON you have to flash a CWM Zip and fastboot the img.
If you're S-OFF both are done in CWM.
This thread should be moved.
ok i find working file
tested with kozmik RC1 kernel and work well
Nottach said:
Cant wait for release!!
Click to expand...
Click to collapse
Hehe awesome.
I experienced the issue you described as a separate error from the common issue solved by a manual adb push for the wireless module.
Even though my phone is S-Off, I'd receive the error consistently when installing certain ROMs (but not all ROMs).
After multiple wipes (including formatting all SD drives, data and system partitions), I finally fixed the issue on my phone by fastboot flashing the kernel for the specific ROM I'm installing after doing a re-format/wipe and before starting the ROM installer through CWM.
It's a strange error, especially because everything seemed to be installed properly (including proper kernel info in the system) and my phone is S-Off, but this is the method I've found that works.
If anyone experiences the issue, I'd recommend doing a back-up, full wipe and re-format (including internal and external SD, basically everything you can wipe); and then fastboot flash the boot.img pulled from your ROM zip before going into CWM and installing (always be careful when fastboot flashing; if you're new to it, you definitely need to familiarize yourself and read a tutorial or two; don't blame me if you're new to flashing, don't read tutorials and end up accidentally flashing a kernel to the wrong partition or some other problem).
Hope this helps out some of the people experiencing this issue.
I can relate
First let me say that kernels and ROMs are two different things.
Kernels are the base on which the ROM operates, they do include important information that can impact phone interoperability. They are required for a ROM to function. And they and ROMs do inter operate extensively.
ROMS are the added features and functionality that make our phones work as an actual appliance. They include software applications and compatibility feature that enable us to make and receive calls, and do all the other crazy things that we want in our phone, work.
I was experiencing similar issues recently. It turned out for me that if I didn't reflash the correct kernel after updating to a ROM that my MAC address would be missing. When that happened you will get the "turning on wireless" message that never completes, or your Wireless Networking switch in extended menu will be "ghosted" out.
Thanks to some great guys in TWRP, I got enough help to figure out what the right combination of "this and that" was. Now I am able to try and troubleshot mine effectively if I do it again.
Just my 3 cents guys, your mileage may vary!
daspazz said:
First let me say that kernels and ROMs are two different things.
Kernels are the base on which the ROM operates, they do include important information that can impact phone interoperability. They are required for a ROM to function. And they and ROMs do inter operate extensively.
ROMS are the added features and functionality that make our phones work as an actual appliance. They include software applications and compatibility feature that enable us to make and receive calls, and do all the other crazy things that we want in our phone, work.
I was experiencing similar issues recently. It turned out for me that if I didn't reflash the correct kernel after updating to a ROM that my MAC address would be missing. When that happened you will get the "turning on wireless" message that never completes, or your Wireless Networking switch in extended menu will be "ghosted" out.
Thanks to some great guys in TWRP, I got enough help to figure out what the right combination of "this and that" was. Now I am able to try and troubleshot mine effectively if I do it again.
Just my 3 cents guys, your mileage may vary!
Click to expand...
Click to collapse
How did you get it working
Sent from my ADR6410LVW using xda premium
I've been through four roms and managed to try each one out successfully. I've had issues, but none too difficult to figure out. I tried this one:
http://forum.xda-developers.com/showthread.php?t=1867484
And am having the WiFi problem some of the other posters outlined. I can't post on the forum because I don't have enough posts. I'm coming from the lastest Helly Bean build (http://forum.xda-developers.com/showthread.php?t=1783064). I followed the instructions (as much as possible from my version of recovery). I wiped data 3 times, wiped cache, wiped dalvik cache, cleared init.d and NSTools then installed it. Wifi gets stuck on "turning on wifi" and remains there, even after restarting. I attempted to reinstall the rom 3 times, it had the same problem each time. Finally gave up and went back to Helly Bean.
Gonna check out a couple other JB roms in the meantime, but I was hoping that one would work since people attest to the speed!
UPDATE: Put RemICS JB v2.0 (http://forum.xda-developers.com/showthread.php?t=1625619) on it and it works like a charm now. Still wouldn't mind trying out LANIGHT, but did anyone ever figure out how to fix the wifi issue?
I have the same problem coming from the latest helly bean. I flashed LANIGHTv2 5 times already and still have problems with the wifi. I tried coming from X-bean, which the wifi works perfectly, but still no dice. I have not one clue on how to fix the wifi.
Blu3izzy said:
I have the same problem coming from the latest helly bean. I flashed LANIGHTv2 5 times already and still have problems with the wifi. I tried coming from X-bean, which the wifi works perfectly, but still no dice. I have not one clue on how to fix the wifi.
Click to expand...
Click to collapse
Spent very little time on LANIGHT but I was reading their thread earlier and they've done a different build with a different kernel. It seems the one persone with the wifi issue that stuck around the thread(or could post) had success with the new build using a different kernel.
Which kernel are you using? I flashed the devil kernel today and followed the 2nd set of instructions and flashed the Lanight v2 nodatadata version. Everything including wifi has worked for me.
I am having an issue with WIFI on my LANIGHT 6.0 NDD. Wifi works fine for me except when I use airplane mode. When using airplane mode wifi will not turn on unless I enable Bluetooth. This use to work correctly in 4.2 DD. Is this a known issue or is their a fix for this.
I am using the "stock" kernel which comes with 6.0 NDD.
Hoodlum7 said:
I am having an issue with WIFI on my LANIGHT 6.0 NDD. Wifi works fine for me except when I use airplane mode. When using airplane mode wifi will not turn on unless I enable Bluetooth. This use to work correctly in 4.2 DD. Is this a known issue or is their a fix for this.
I am using the "stock" kernel which comes with 6.0 NDD.
Click to expand...
Click to collapse
No wifi issues here on the latest v6.5_DATADATA. Using the Devil kernel.
Hey guys,
So I installed the Milestone 6 ICS onto my SGT7 following all the steps of the walkthrough. Everything worked great for about a month, then suddenly I tried to start up the tab and it reads "Encryption Unsuccessful" and says I need to hard reset. I do so, nothing changes. I've tried reflashing the kernel, recovery, and rom, even went back through the entire process of the walkthrough, but still getting the same message. Now the walkthrough does indicate that this error was caused by a faulty kernel before, but I cannot seem to locate a compatible kernel for the life of me no matter how much I search.
Could anyone please help me with a fix to this or set me up with a working replacement kernel? Again, the model is the SCH-I800, VZW model, (was) running AOKP Milestone 6 ICS.
Thanks all!
I'm just a novice at this but Milestone 6 was one of the builds I didn't have trouble with on my cdma p1c (sch-i800)
I did get that message with a couple 4.2.2 builds out there that don't seem to have proper cdma support compiled in yet.
One build I did find rock stable and had all features working was the official Cyanogenmod 9.1 for p1c
http://get.cm/?device=p1c&type=stable
But it of course that is ICS 4.0.4 and not JB 4.1/4.2 - once you go to JB, none of the builds have usb tether working yet and other issues like bluetooth, etc.
JB looks nicer and you can have a hybrid of tablet/phone but that CM 9.1 is super stable and everything just works.
BTW when everything goes horribly wrong, I just start over with volume down button and heimdall and reflash recovery and that has always solved it for me.
I'm okay with ICS, no need for JB. I already tried reflashing recovery and then install Cyanogen 9.1, still came up with the encryption error. I'm stumped on this one.
I have just recently restarted using this phone due to my uscellular S4 getting turned off. I am now back on my LG-P990 currently rooted and running CM10.1. BUT most importantly to me is the fact that I have all my wonderful apps on my s4, I want to be able to use them by using the LG phone as a tether and calls not much else BUT CM10.1 tethering does not work, so i find myself flashing rom after rom, avatar rom, older CM mods, none would turn on tethering, so i flashed a modded version of MIUI for this phone and it worked except for ONE thing no signal, tethering turned on just fine so i decided to look around for other roms and found Slimrom TRYED to flash it didnt work, try to flash actual MIUI roms off there site, didnt work, met with an error in CWM Recovery after some searching I found its because Im running the OLD Bootloader -_- THIS is the issue im having IF MIUI does NOT work is it possible to downgrade the bootloader again so i can restore my CM10.1 backup? I have been working at this for a week, if there is something here about this can someone please just point me at it? I would appreciate any help.
On a side note i DID soft brick the phone the other day and found a program called nvflash witch flashed an install of CM mod. Dont know if that will help any.
Jeffril said:
I have just recently restarted using this phone due to my uscellular S4 getting turned off. I am now back on my LG-P990 currently rooted and running CM10.1. BUT most importantly to me is the fact that I have all my wonderful apps on my s4, I want to be able to use them by using the LG phone as a tether and calls not much else BUT CM10.1 tethering does not work, so i find myself flashing rom after rom, avatar rom, older CM mods, none would turn on tethering, so i flashed a modded version of MIUI for this phone and it worked except for ONE thing no signal, tethering turned on just fine so i decided to look around for other roms and found Slimrom TRYED to flash it didnt work, try to flash actual MIUI roms off there site, didnt work, met with an error in CWM Recovery after some searching I found its because Im running the OLD Bootloader -_- THIS is the issue im having IF MIUI does NOT work is it possible to downgrade the bootloader again so i can restore my CM10.1 backup? I have been working at this for a week, if there is something here about this can someone please just point me at it? I would appreciate any help.
On a side note i DID soft brick the phone the other day and found a program called nvflash witch flashed an install of CM mod. Dont know if that will help any.
Click to expand...
Click to collapse
I really do not understand how other ROMs deny Tethering. Did you flash the latest 2.x kernel by pengus77 after installing the rom? Did you make a clean install(wipe everything then install)? On the other hand, yes you can switch bootloaders as much as you like, just remember that changing the bootloader wipes everything on your internal memory, so do a backup. Did you try just plain old stock 4.0.4? Should work there. Ask anything you want, if you're still having questions.
NoDze said:
I really do not understand how other ROMs deny Tethering. Did you flash the latest 2.x kernel by pengus77 after installing the rom? Did you make a clean install(wipe everything then install)? On the other hand, yes you can switch bootloaders as much as you like, just remember that changing the bootloader wipes everything on your internal memory, so do a backup. Did you try just plain old stock 4.0.4? Should work there. Ask anything you want, if you're still having questions.
Click to expand...
Click to collapse
As to the flashing to stock i lost the original rom backup i had made along time ago and cant find the original firmware anywhere online. When I flashed CM 10.1 I just ran with it, when i go to try tethering it says "Turning on portable wifi hotspot." and it stays on that no matter what untill i restart, left the phone running for 2 days once and that was still stuck on that before i restarted. As for flashing a 2.x kernel i had no idea about that. But yes when i did the installs i would do a clean wipe and install. Most of what i read online led me to believe that there was an error with CM 10.1 nightlys that was not being fixed for the tethering. So that is why i decided to go to another rom. Two questions one how do i go about finding the original firmware for this phone and two how would i go about updating or downgrading the bootloaders and could i be pointed to the files please?
Jeffril said:
As to the flashing to stock i lost the original rom backup i had made along time ago and cant find the original firmware anywhere online. When I flashed CM 10.1 I just ran with it, when i go to try tethering it says "Turning on portable wifi hotspot." and it stays on that no matter what untill i restart, left the phone running for 2 days once and that was still stuck on that before i restarted. As for flashing a 2.x kernel i had no idea about that. But yes when i did the installs i would do a clean wipe and install. Most of what i read online led me to believe that there was an error with CM 10.1 nightlys that was not being fixed for the tethering. So that is why i decided to go to another rom. Two questions one how do i go about finding the original firmware for this phone and two how would i go about updating or downgrading the bootloaders and could i be pointed to the files please?
Click to expand...
Click to collapse
Okay, This is SFSP by @sgspluss which is a pretty fast, stable and battery-friendly slimmed down version of stock ICS. It is available for both Old and NewBL, so you might want to try that first. This is AIO Toolkit. I know that you've used it and bricked your phone, but try again, and for the love of God install the nvflash drivers because most people skip that part. You have to do it manually and if you're running Windows 8 you need to disable Driver Signature Verification. But yeah, you switch bootloaders with this.