I was running UnNamed v2.2.1 and flashed the Siyah Kernel. However, after flashing the new kernel, in Settings > About the kernel version doesn't display that its Siyah but the CWM does change. Does this mean the kernel is not installed?
I assumed it was installed so I flashed the Init.Doh script. After it installed, my status bar was missing.
Since everything was messed up, I ran the Init.Doh uninstaller and tried out a new rom.
Did a factory reset, wiped cache and Dalvik cache, then installed SHOstock. Within 5 minutes, I lost signal.
Flashed back to UnNamed, but the signal loss was consistently happening. So I formatted system, did a factory reset, wiped both caches and installed SHOstock again.
As of now, I constantly lose signal. Tried flashing compatible modems but nothing is working. Does anyone have any idea of what to do?
I use CPUspy to see whether or not a specific kernel flashed successfully. As far as he signal loss..no idea sorry. I would start from scratch and flash bts and go from there maybe..
Sent from my SGH-I777 using xda premium
I would say the signal loss has nothing to do with the phone but your area if it happens on multiple roms
And the cwm is supposed to be different on siyah, it flashed fine and the kernel version in about phone should not change, changing your rom was silly
Sent from my SGH-I777 using XDA App
Nick281051 said:
I would say the signal loss has nothing to do with the phone but your area if it happens on multiple roms
And the cwm is supposed to be different on siyah, it flashed fine and the kernel version in about phone should not change, changing your rom was silly
Sent from my SGH-I777 using XDA App
Click to expand...
Click to collapse
Thanks for your replies. I think my post is confusing so I'll try to clarify.
Signal was prefect on UnNamed. After flashing Siyah and the Init.Doh script, the status bar went missing.
So I did a factory reset and wiped everything before installing SHOstock. When it booted up, my phone kept losing signal. So I wiped again and went back to UnNamed but the problem persisted.
I'm wondering if the problem is caused because I was never sure if Siyah flashed properly. In Settings > About Phone, the kernel version never said it was Siyah. BUT my CWM changed to the Siyah version. However, even if this was the case, I don't know why the signal problem continued after wiping everything and formatting /system.
dngen said:
Thanks for your replies. I think my post is confusing so I'll try to clarify.
Signal was prefect on UnNamed. After flashing Siyah and the Init.Doh script, the status bar went missing.
So I did a factory reset and wiped everything before installing SHOstock. When it booted up, my phone kept losing signal. So I wiped again and went back to UnNamed but the problem persisted.
I'm wondering if the problem is caused because I was never sure if Siyah flashed properly. In Settings > About Phone, the kernel version never said it was Siyah. BUT my CWM changed to the Siyah version. However, even if this was the case, I don't know why the signal problem continued after wiping everything and formatting /system.
Click to expand...
Click to collapse
See below...
Coreym said:
I use CPUspy to see whether or not a specific kernel flashed successfully. As far as he signal loss..no idea sorry. I would start from scratch and flash bts and go from there maybe..
Sent from my SGH-I777 using xda premium
Click to expand...
Click to collapse
CPUSpy displays large amounts of information not displayed by Settings->About Phone.
Although I would've expected Siyah to cause a version bump to 2.6.35.14... odd
Time without signal is a known gingerbread bug, if that's what you're referring to signal loss. It doesn't affect your battery life, just the android battery stats is all around messed up.
The big solar flare has a lot of people blaming 33204803428 different things on signal loss... basically everything BUT the fact that we're experiencing one of the largest CMEs to hit Earth for a few years.
After multiple factory resets, cache wipes, system formatting, and flashing ROMs, everything seems to be running properly again. Thanks for the suggestions!
Related
So I flashed CM9 alpha 13(after wiping) but can't get service to activate on my phone. Same problem I'm having with alpha 9. I use the activate button when it starts and it tells me it failed. Under "About Phone" and "Status" I can see that the My Phone Number setting is wrong so is the MIN.
When I call my carrier to manually activate, the short codes they give me to manually input this info do not work.
Anybody else had this problem?
Go into Sprint Zone, and try to manually activate.
Sent from my MB855 using xda premium
Nevermind. That won't work. Sorry
Sent from my MB855 using xda premium
Flash cm9 and reboot dont install gapps till after it activates
Sent from my MB855 using XDA App
I will try this. Thank you sir!!
Ok, so I wiped... Flashed CM9. Rebooted. The activation call failed, so I called sprint to manually activate again. They asked me to punch in ##971912# which is supposed to pop up a dialog screen where I can manually input MIN etc but did not. Not sure what to do.
Flash back to a blur rom activate then reflash
tcf84 said:
Ok, so I wiped... Flashed CM9. Rebooted. The activation call failed, so I called sprint to manually activate again. They asked me to punch in ##971912# which is supposed to pop up a dialog screen where I can manually input MIN etc but did not. Not sure what to do.
Click to expand...
Click to collapse
Sent from my MB855 using XDA App
Ok, I've got my phone up and running on Rocko's ROM. I'm doing a nand backup now. So, to be clear... I need go to my recovery. Data Reset and wipe dalvik cache. Then I need to flash CM9. I then need to activate(or make sure I'm still activated), and once that is confirmed I need to flash Gapps?
Sorry. I'm just trying to figure out where I went wrong the first time...
Try that, you're the first person to have issues so its a new issues
tcf84 said:
Ok, I've got my phone up and running on Rocko's ROM. I'm doing a nand backup now. So, to be clear... I need go to my recovery. Data Reset and wipe dalvik cache. Then I need to flash CM9. I then need to activate(or make sure I'm still activated), and once that is confirmed I need to flash Gapps?
Sorry. I'm just trying to figure out where I went wrong the first time...
Click to expand...
Click to collapse
Sent from my MB855 using XDA App
tcf84 said:
So I flashed CM9 alpha 13(after wiping) but can't get service to activate on my phone. Same problem I'm having with alpha 9. I use the activate button when it starts and it tells me it failed. Under "About Phone" and "Status" I can see that the My Phone Number setting is wrong so is the MIN.
When I call my carrier to manually activate, the short codes they give me to manually input this info do not work.
Anybody else had this problem?
Click to expand...
Click to collapse
I had this problem as well. I've also bricked my phone flashing an electrify pudding by mistake on my photon. My fix after fixing my boot loader issues was: I reverted to completely stock. Then I called sprint and had to reactivate my phone. After getting everything working and having a secure connection for over a day I then flashed cm7 to make sure that would work. After it did I did a says wipe and wiped everything else. And flashed cm9 then went into recovery wiped and flashed again. Then I flashed gapps and boot up. After booting up I went back and wiped again. And then used the phone for about twenty minutes and wiped and flashed "all" again. It was a long drawn out process. But I have had none of the issues that people are having on the forum. Battery life is great after calibrating. 3G is almost as fast as the 4G I had. Never have a single reboot or battery pull. Wifi and Bluetooth bead on perfect. I'm new to xda but not development. I'd post my success in the forum, but I'm not yet at ten post.
Sent from my MB855 using XDA App
FanBoy_Hunter said:
I had this problem as well. I've also bricked my phone flashing an electrify pudding by mistake on my photon. My fix after fixing my boot loader issues was: I reverted to completely stock. Then I called sprint and had to reactivate my phone. After getting everything working and having a secure connection for over a day I then flashed cm7 to make sure that would work. After it did I did a says wipe and wiped everything else. And flashed cm9 then went into recovery wiped and flashed again. Then I flashed gapps and boot up. After booting up I went back and wiped again. And then used the phone for about twenty minutes and wiped and flashed "all" again. It was a long drawn out process. But I have had none of the issues that people are having on the forum. Battery life is great after calibrating. 3G is almost as fast as the 4G I had. Never have a single reboot or battery pull. Wifi and Bluetooth bead on perfect. I'm new to xda but not development. I'd post my success in the forum, but I'm not yet at ten post.
Sent from my MB855 using XDA App
Click to expand...
Click to collapse
I tried reverting to stock as outlined by qbking77 but every time I sbf'ed the file as instructed I lost my recovery. The 'Unlocked' notice disappeared as it was supposed to but once I did that I couldn't get any recoveries to stick, stock or CWM, until I "re-unlocked" the phone with that sbf. Even then I couldn't get the stock recovery to write properly.
I'm pretty new to all of this. I unlocked my Optimus S and tried a few ROMs on it before I settled on Reborn Rom, but that's about my only experience with these things. I'm not incompetent(I hope) when it comes to this stuff, but it's definitely a learning curve. I'd like to master the whole process though so I can delve into the dev side of things a bit.
Joker - Thanks for the help. I'm up and running with no problems.
What did you do?
tcf84 said:
Joker - Thanks for the help. I'm up and running with no problems.
Click to expand...
Click to collapse
Sent from my MB855 using XDA App
A combination of what you and FanBoy suggested. First I wiped and flashed Rocko ROM. Got the phone to activate. Then I wiped. Flashed CM9. Wiped again. Booted up and verified service was active. Wiped again, Flashed CM9 again, wiped again, and flashed gapps v3.
I really don't know what the problem was to start. I originally tried to flash CM7 and couldn't get signal at all. So I flashed MIUI with the same issue. Finally I flashed CM9 and had signal but couldn't activate. So the problem wasn't tied to CM9, but I honestly have no idea what I did to lose signal/activation or to gain either of those back, but my phone does work now and I've successfully flashed both CM9 and Rocko without the loss of signal or service and have nand backups of both since my biggest problem originally stemmed from not having a nand backup of my latest working set up.
I think I hear the ice cream man!
tcf84 said:
A combination of what you and FanBoy suggested. First I wiped and flashed Rocko ROM. Got the phone to activate. Then I wiped. Flashed CM9. Wiped again. Booted up and verified service was active. Wiped again, Flashed CM9 again, wiped again, and flashed gapps v3.
I really don't know what the problem was to start. I originally tried to flash CM7 and couldn't get signal at all. So I flashed MIUI with the same issue. Finally I flashed CM9 and had signal but couldn't activate. So the problem wasn't tied to CM9, but I honestly have no idea what I did to lose signal/activation or to gain either of those back, but my phone does work now and I've successfully flashed both CM9 and Rocko without the loss of signal or service and have nand backups of both since my biggest problem originally stemmed from not having a nand backup of my latest working set up.
Click to expand...
Click to collapse
Most custom roms disallow communication from what ever it is that allows you to activate with sprint. I noticed that porting in sprintzone.apk often doesn't work and you can't activate with the dialer because it requires communication with sprintzone. So you need to flash to a rom that allows activation and then work your way back up. Glad to hear you got it working.
Since a picture, and in this case a video, paints a thousand words -> http://www.youtube.com/watch?v=qCkKkkukujI
Here I present to you my dilemma.
Before you ask, the phone is rooted, running cm7.1 nightly.
At the time of recording my modem is KI3.
I have tried about 4 modems, in the K family and no luck yet.
I cant put my finger on exactly the time this happened, but somewhere in the past 3-4 days and nothing significant happened to spawn it. (ie I wasn't changing roms or anything of that sort.)
Every modem I put on does the exact same as the video.
However generally the first boot after a flash, the wifi tends to connect, next boot = no go.
I have also used 'gs2blitzer v1.6' which is a script to clean out old kernel files and temporary bits n pieces between flashes.
So any helpful suggestions you have will be appreciated.
Do a backup with ClockWorkMod and then flash another kernel. (siyah, for example).
Sent from my GT-I9100 using XDA
I just flashed siyah as you suggested, no luck.
Still does exactly that in the video I posted earlier.
kitchy88 said:
I just flashed siyah as you suggested, no luck.
Still does exactly that in the video I posted earlier.
Click to expand...
Click to collapse
Tried a full-wipe?
Sent from my GT-I9100 using XDA
are you using the i9100 or a t-mobile branded or other variant?
did you have the problem before you flashed the new rom?
im using wanamlite ics 9.1 rom using the XXLPH kernel and my wifi works fine. XXLPH is still beta i think btw
Yes it has been wiped numerous times.
Wiping individual partitions from cwm, wiping dalvik, using the cleaning script to clear old kernel stuff..
And yes it worked prior - if you read my first post, nothing happened for it to stop working. There was no flash involved to stop it working.
Oh and its an international I9100.
Some extra info on the subject.
Disconnecting and deleting the AP, restart phone, it will then connect.
If i disable wifi then re-enable it, it wont connect.
Stuck in the loop of Scanning, connecting, disconnecting, over and over...
hey guys i hope i put this in the right section... anyways, i was using cm7.1 stable on my fascinate with the stock kernel that came with it, which was awesome i must say. but recently i decided to try out the glitch kernel 13.1 as ive heard its even faster and overclocks better. and it is lol, its reallllll freakin fast but now my wifi wont work. worked perfectly on the other kernel but now when i hit the button to turn on the wifi, nothing happens, it kinda lights up and just stays there and wifi never turns on. does anyone have any work arounds for this? i really want to keep this kernel because its damn stable and fast but wifi is my only issue.
thanks guys
toggle airplaine mode off/on
Make a Nandroid, the wipe data. (restore the Nandroid if it doesn't work) I had this problem on my Iconia Tab after I did a dirty flash.
am I reflashing the kernel or cm7? I tried to airplane mode toggle and it just says error when I try to enable wifi in the settings menu
Don't reflash anything, just wipe data & dalvik.
did nandroid backup and cleared dalvik and did factory wipe, still no dice. am i missing something? did i get a corrupted kernel install file or something?
username8611 said:
did nandroid backup and cleared dalvik and did factory wipe, still no dice. am i missing something? did i get a corrupted kernel install file or something?
Click to expand...
Click to collapse
I've seen this before... I only have a minute to type this. There is a kernel cleaning script you can get.. by lippol I believe. Sorry to send you on the hunt. If that don't work, backup all your apps/data and do a full wipe (just wipe, not flash) on the phone and reflash kernel.
-Maniac
what does a kernel cleaning script do? theres an option to clean the kernel in the glitch kernel, is that the same? ive reflashed the glitch kernel too after reclearing dalvik and factory reset and still no wifi. would using a kernel cleaner do anything after reflashing?
ok i decided to go ahead and try the script, i was able to find it without a problem. cleared cache, ran it, and reflashed a redownloaded kernel and........ it works!! thanks so much guys!
username8611 said:
ok i decided to go ahead and try the script, i was able to find it without a problem. cleared cache, ran it, and reflashed a redownloaded kernel and........ it works!! thanks so much guys!
Click to expand...
Click to collapse
Sweet. You're welcome. That's my good deed for today!.
-Maniac
Solved
Hello everyone
Since a few days ago my S2's Wifi is not working
h.ttp://i.imgur.com/ojDOm.png
The icon stays like this, pressing it does nothing. it happened 3 - 4 times before, usually, I'd just reboot it and that would do the trick (I google'd a bit and saw this is a common glitch when trying to turn wifi on), but not anymore, it refuses to turn on no matter what I do, rebooting, shutting down and restarting, it's stuck.
h.ttp://i.imgur.com/KeMxb.png
I can't Scan, add a network nor switch the toggle on/off because pressing them does nothing, So... I thought I should do backup and factory reset it, nope. still stuck.
What's wrong with it? Any ideas? The phone is a year old, running 4.0.3 Stock
Sorry about the dots in the URL's, can't post links yet.
Edit: Forgot to mention it started doing this since I got ICS, maybe I should try flashing it to see if that fixes it, I'm kinda reluctant though, since the factory reset didn't seem to do anything and I haven't done it before.
Cathari said:
Hello everyone
Since a few days ago my S2's Wifi is not working
h.ttp://i.imgur.com/ojDOm.png
The icon stays like this, pressing it does nothing. it happened 3 - 4 times before, usually, I'd just reboot it and that would do the trick (I google'd a bit and saw this is a common glitch when trying to turn wifi on), but not anymore, it refuses to turn on no matter what I do, rebooting, shutting down and restarting, it's stuck.
h.ttp://i.imgur.com/KeMxb.png
I can't Scan, add a network nor switch the toggle on/off because pressing them does nothing, So... I thought I should do backup and factory reset it, nope. still stuck.
What's wrong with it? Any ideas? The phone is a year old, running 4.0.3 Stock
Sorry about the dots in the URL's, can't post links yet.
Edit: Forgot to mention it started doing this since I got ICS, maybe I should try flashing it to see if that fixes it, I'm kinda reluctant though, since the factory reset didn't seem to do anything and I haven't done it before.
Click to expand...
Click to collapse
Do the steps below
- Boot to CWM recovery
- wipe cache partition
- wipe dalvik cache (under advanced)
- fix permissions (under advanced)
- reboot system now
The above steps will not make you lose some files and data
If that does not help, then flash another kernel
Since putting a custom kernel on my phone my bluetooth does exactly the same as what your wife is doing. Only way to turn it on is to reboot the phone whilst it is trying to turn on (ie whilst it is a shade of green)
saywhatt said:
Do the steps below
- Boot to CWM recovery
- wipe cache partition
- wipe dalvik cache (under advanced)
- fix permissions (under advanced)
- reboot system now
The above steps will not make you lose some files and data
If that does not help, then flash another kernel
Click to expand...
Click to collapse
Gonna try that and flash CM9 while I'm at it, never done this before... Lets see how it goes following the steps on CM's wiki
Cathari said:
Gonna try that and flash CM9 while I'm at it, never done this before... Lets see how it goes following the steps on CM's wiki
Click to expand...
Click to collapse
you should be Ok its relativley straight forward
Well, Flashed in CWM Recovery and CM9, wiped cache, Dalvik cache and fixed permissions but the wifi is still not working... it's still stuck at "Turning Wi-Fi on"
I really have no idea about kernels and that stuff, I don't know how to flash 'em (unless it's the same as flashing CWM) or which one to get at all, since theres too many and I don't know what they do/know if they're compatible.
Flashing kernels are the same as flashing ROMs and modems..
There are 2 ways to flash kernels.. 1 is via odin (.tar file) and 2 is via CWM (.zip file)
Now, if your ROM is on JB then use a JB Kernel
If ICS = ICS Kernel
AOKP = AOKP Kernel
AOSP = AOSP Kernel
The thing with kernel is that you have to match it with the ROM's base..
Sent from my GT-I9300 using xda premium
Hm...Checked my phone 7 hours after flashing CM9 on it and suddenly the Wifi's back on
Any explanation for this? It doesn't make any sense, I didn't even touch the phone during that time and it fixed itself?
Edit: Thanks for clarifying that up saywhatt, since I already flashed if and thus, voided the warranty I might as well go ahead and try flashing a kernel to improve battery life and get into the scene.
Cathari said:
Hm...Checked my phone 7 hours after flashing CM9 on it and suddenly the Wifi's back on
Any explanation for this? It doesn't make any sense, I didn't even touch the phone during that time and it fixed itself?
Edit: Thanks for clarifying that up saywhatt, since I already flashed if and thus, voided the warranty I might as well go ahead and try flashing a kernel to improve battery life and get into the scene.
Click to expand...
Click to collapse
No problem.
Perhaps the ROM was "settling"? Lol i dunno.. but i'm glad to hear you got it sorted out. You can revert back to complete stock if you have some serious problems and it is needed to be sent to the service center..
1 download triangle away to clear the binary count
2 flash stock firmware
Voila! U no longer have a void warranty
Sent from my GT-I9300 using xda premium
First of all: I have had my S II water damaged some months ago. It works fine that far (exept that the sensor keys are dead). Not sure if there is some other hardware malfunctioning...
Currently im running on MIUI and everything is fine, but recently I found out that no other ROM will work on my Phone:
- Samsung stock ROM runs extreme (!) laggy. Took me about 5 Minutes to go through the menus and enable USB debugging.
- CM9/ AOKP will reset immediately after system startup
- CM10 shows laggy boot animation for few secs, then bootloops
Only other ROM that works is "cMIUI". Which is a CM10 based ROM only with a MIUI userinterface...
What can I do to find out whats the problem with my phone??
Thats weird. Have you tried wiping data before flashing each of these ROMs? Next time, try formatting /system, /data, cache and dalvik cache. Also, have you tried using those kernel cleaning scripts, etc?
Sent from my GT-I9100 using Tapatalk 2
Spiralzz said:
Thats weird.
Click to expand...
Click to collapse
YES :laugh:
Spiralzz said:
Have you tried wiping data before flashing each of these ROMs? Next time, try formatting /system, /data, cache and dalvik cache.
Click to expand...
Click to collapse
Wiped and formatted like hell. I've hit every single wipe/ clean/ format option in the recovery. Also I have installed a dualboot kernel and installed CM as "second rom", where no ROM has gone before.....
Spiralzz said:
Also, have you tried using those kernel cleaning scripts, etc?
Click to expand...
Click to collapse
I Have tried different Kernels, all with the same effect. What kernel cleanig scripts specifically?
Rottnroll said:
YES :laugh:
Wiped and formatted like hell. I've hit every single wipe/ clean/ format option in the recovery. Also I have installed a dualboot kernel and installed CM as "second rom", where no ROM has gone before.....
I Have tried different Kernels, all with the same effect. What kernel cleanig scripts specifically?
Click to expand...
Click to collapse
Only one option I can think of is to go back to stock samsung rom then claim your warranty if you have it. Or, make a logcat and paste it here (upload to Dropbox or somewhere then past a link over here) and someone experienced might take a look.
Since you've already wiped everything, I'm more inclined to think that it's a hardware problem now. However, let's hope someone more experienced pops in and helps. Good luck
Sent from my GT-I9100 using Tapatalk 2
See two logs below, trying to boot cm9. One with default kernel, one with Siyah. Would be great if anybody could find out whats the issue.
https://www.dropbox.com/s/z7q3wbz1h9uhhvg/logcat_cm9_s2.txt
https://www.dropbox.com/s/r1l9umovmxx7jpo/logcat_cm9_s2_siyah.txt
In both logs the phone booted and showed the Pin dialog, then after few seconds rebooted.
As the Phone had been waterdamaged Im pretty shure warranty is absolutely void Also I think that the problems are due to some Hardware malfunctioning. Just want to know what and if theres some way to workaround.