Related
I was running a stock ROM, rooted, with the original radios. All was operating properly.
Flashed the leaked radio update. Everything still okay.
Flashed Das BAMF 1.6. It boots up fine (and looks gorgeous, btw), but my SIM card is not recognized at all. Symptoms:
When making a call, I see text in the upper-right corner saying: "SIM Card not found. Please \n the phone."
Settings > Call > Voicemail Service... tapping on this dropdown results in "Voicemail number change unsuccessful. Please contact your carrier if this..."
I tried turning the phone off, booting it once without the SIM card, then rebooting with it back in place. That didn't help.
Out of frustration, I restored my tbolt to the backup I made before attempting das BAMF. Magically, my SIM card is recognized and everything back to normal. ...I tried das bamf one more time, only to have the same crappy results... FYI, I was sure to wipe data/cache/dalvik before flashing the rom in recovery.
HELP!
EDIT: I've also just noticed that despite this being das bamf 1.6 remix, I don't see the 4-in-1 restart menu, nor a 6-bar signal indicator. I'm absolutely positive that I downloaded 1.6 remix... Am I in the twilight zone?
did you wipe data before installing the ROM?
nevermind i missed it. i dont know then sorry.
try redownloading and check md5
I verified the md5 before flashing.
i actually received the same errors but it did not impede functions of the phone. My data has been dropping, but that is not because of the ROM, it has been doing it since the 4G outage.
EDIT: Actuallly my voicemail says:
"We have a problem
Your voicemail settings could not be loaded. Please try again."
Never seen that before.
The more I look into it, I'm missing things that are pictured in the 1.6 Remix screenshots... all of this has me very confused. I'm going back to the stock ROM until someone else finds and resolves the SIM card issue.
I am experiencing the same issues here. I see 'no Sim Card Detected' at the top, I have none of the Reboot Options, no 6 bar signal, etc.
Seems to be kind of a big issue and yet noone has really offered solutions. I have done the full wipe aswell.
Thank you for everyone's time involved with making such a Great ROM....Plus this Community of Users is awesome...Take that IPhone!
Did you happen to download 1.6.1 or 1.6.2 and install just those first? Those two are just patches that required 1.6 as a base.
So, you would have to flash 1.6, then 1.6.1 or 1.6.2 over it as a patch - you can't just flash 1.6.1 or 1.6.2 by themselves. With 1.6.3, I think they went back to a full rom release.
Install via cwr, not Rom manager.
Sent from my ADR6400L using XDA App
I had the same problem with the SD card running Bamf Remix. What solved it for me was formatting the SD card. Obviously backup the SD card on your computer first.
Download 1.6.3 and do a flash. It's a complete download too, id give that a go. I didn't run into any of those problems. Are you flashing through rom manager or cwm?
Sent from my ADR6400L using XDA App
Dont manually mount data. For some reason when i did that the same exact this happened to me. No 6 bar signal and no 4 in 1 reboot menu.
Sent from my ADR6400L using XDA App
Thanks for all the suggestions, everyone. I solved the problem by using recovery rather than ROM Manager, and wiping data/dalvik/cache twice each (doing them only once wasn't sufficient, although idk how to explain it). I've been running 1.6.2 without issues for a day now. I'll move on to 1.6.3 after I see how well it's holding up for everyone else.
I ended up wiping everything and installing 1.6.3 and that fixed everything. Thank You all Gentlemen for helping!
You guys are genius!
Well I thought the issues was over after the install, But now Every time i receive a call ...Call Recorder Crashes. Also I am experiencing random reboots.
I was in the middle of a call and it rebooted on me.
Any Ideas?
Kodiax said:
Well I thought the issues was over after the install, But now Every time i receive a call ...Call Recorder Crashes. Also I am experiencing random reboots.
I was in the middle of a call and it rebooted on me.
Any Ideas?
Click to expand...
Click to collapse
For the Call Recorder, it sounds like you're running a custom kernel. Most kernels don't support the things that Call Recorder needs. For the reboots, well, can't help you there.
mcore09 said:
Thanks for all the suggestions, everyone. I solved the problem by using recovery rather than ROM Manager, and wiping data/dalvik/cache twice each (doing them only once wasn't sufficient, although idk how to explain it). I've been running 1.6.2 without issues for a day now. I'll move on to 1.6.3 after I see how well it's holding up for everyone else.
Click to expand...
Click to collapse
Other than wiping twice (???), what you said you did should be standard procedure. Flashing via ROM Manager and Kernel Manager are no-no's unless you get lucky. In an ideal world, they work. And in many cases, they do work. However, in many cases, they cause nasty issues. For example, if you flash some kernels via Kernel Manager, the device drivers don't get flashed properly and you have some pretty nasty problems. And when you flash via ROM Manager, well, you learned what happens. From now on, only flash via CWM and CWM only.
Thank you for your responses. I am only using the 4.4.7 kernel. Which come s with dad band 1.6.3. I think that it is this new kernel (4.4.7). I never had these issues with 1.6.2.
Sent from my ADR6400L using XDA Premium App
Try down grading your kernel to a slightly older version.
Sent from my ADR6400L using XDA App
I reflashed my kernel to the same 4.4.7 but downloaded the kernel from his standalone post regarding kernels. My call rcorder is working now. Hasn't restarted since then either. Crossing my fingers ...
Sent from my ADR6400L using XDA Premium App
Well it restarted randomly while I had it connected to my Laptop and set to charge. I was in the middle of a Call with someone.
Very interesting why its Randomly rebooting. Could be the new radio. May be that why verizon held out on releasing it yet.
Been looking for a solution for the past 12 hours and have not found any.
Bought a stock i777 with 2.3.4, flashed with SGH-I777_ClockworkMod-Recovery_5.0.2.3 and a stock 2.3.5 AT&T ROM. After ANY kernel is flashed, I seem to lose WiFi capability. I have 5 wireless points near my house and it just gets stuck on "Scanning" and then the WiFi turns off. No points are even listed!
Currently running CW 5.0.2.3 kernel, 2.3.5 AT&T stock ROM, UCKJ1 baseband, kernel 2.6.35.7.
TL-DR - Flashed and lost wifi ability.
Which 2.3.5 ATT stock rom is this that you're referring to? Have a link to where you got it from?
I believe I got it from here: androidadvices.com/update-samsung-galaxy-s2-i777-gingerbread-235-firmware/
Did it work initially when you went to 2.3.5? You said you've tried some different kernels, at what point did you notice the wifi broke?
I even reflashed using kernel + non-rooted system package located in this thread: http://forum.xda-developers.com/showthread.php?t=1286432
Still no WiFi showing. Just says "scanning" then the wifi shuts off.
Update: Flashed Entropy512's stock package + nonrooted with no luck. No wifi. Flashed zetamax kernel after. Still no wifi.
Showed at that time: version 2.3.4, 1777UCKH7 baseband, 2.6.35.7_ZedomaxStockKernel.
Flashed again with a I777UCKJ1 2.3.5 ODIN package that I know will fix the WiFi. It shows version 2.3.5, 1777UCKJ1 baseband, 2.6.35.7 kernel.
Seems like if I flash ANYTHING else besides this the wifi stops working on me.
Solved problems for myself.
Completely unrooted, reflashed ATTGalaxyS2Unroot_SGH-i777.tar. This brought me back to the original AT&T firmware that came with the phone. I then flashed SGH-I777_ClockworkMod-Recovery_5.0.2.3.tar and subsequently used SuperOneClick 2.2 to root.
WiFi seems to be working fine now. I am now running a stock 2.3.4 ROM, UCKJ1, kernel 2.6.35.7...Clockworks version.
If anyone else is having the same issue this should help.
Thanks for the updates. Sounds like a frustrating battle. Glad all is well.
Sent from my páhhōniē
rpesta said:
Solved problems for myself.
Completely unrooted, reflashed ATTGalaxyS2Unroot_SGH-i777.tar. This brought me back to the original AT&T firmware that came with the phone. I then flashed SGH-I777_ClockworkMod-Recovery_5.0.2.3.tar and subsequently used SuperOneClick 2.2 to root.
WiFi seems to be working fine now. I am now running a stock 2.3.4 ROM, UCKJ1, kernel 2.6.35.7...Clockworks version.
If anyone else is having the same issue this should help.
Click to expand...
Click to collapse
Hrrrrm Having the same issues and the only way I could manage wifi to get back on was going to 2.3.5 which had it's own set of issues. I tried following your steps but one thing I noticed you said you were running UCKJ1 but isn't that 2.3.5? When I flash the exact same files I am still stuck without working wifi
Still noobing it up here - hopefully I can either stumble upon a fix like you did or spot someone else's that matches my issues...
Avoid that androidadvices.com **** - Half the time they link to firmware that isn't even for the device it claims it is, carrying a high risk of a hardbrick.
I only experienced this when I was trying to upgrade kernels using the SHOstock ROM. I get no wifi with siyah and can't send MMS with Entropy's kernel. That's the only time I've had those issues. Maybe you had a bad download? Glad you got it fixed though.
Just to clarify, those kernels work great with most other ROMS I've tried them on.
Sent from my SAMSUNG-SGH-I777 using XDA App
Had the same problem
I had this problem (with wifi, not mms) after rooting from 2.3.6. I eventually flashed Zedomax's kernel using mobile odin and wifi functionality was restored.
I still haven't moved on from there, but probably will sometime this week.
Jank4AU said:
I only experienced this when I was trying to upgrade kernels using the SHOstock ROM. I get no wifi with siyah and can't send MMS with Entropy's kernel. That's the only time I've had those issues. Maybe you had a bad download? Glad you got it fixed though.
Just to clarify, those kernels work great with most other ROMS I've tried them on.
Sent from my SAMSUNG-SGH-I777 using XDA App
Click to expand...
Click to collapse
Weird, I cannot think of anything that would cause MMS to fail - what sort of errors?
It's happened to me several times after I flash a kernel. when I attempt to send an mms it just hangs and says sending but it never goes out. Could it be a conflict as I have Chomp set as my primary messaging app? Although if that were the case it should be able to send from one or the other but it doesn't. Can't remember for sure but I believe that I may have flashed the kernel cleaning script beforehand in each instance. The only way I've been able to fix it is to reinstall everything starting with the ROM. I'm sure it's user error.
As info, steps I took to try to fix before I restored:
1) reflash kernel
2) flash radio again
3) tried all 5 radios released (not a radio problem I'm guessing)
4) wipe dalvik and reflash kernel
5) run kernel cleaning script and reflash kernel
No dice, it was bizarre. Is this even the sort of event that you could get an error log from? There was no FC or any error message, you know? If it happens again what can I provide you that would help...can I do a logcat or whatever? ;-)
By the way,I could receive mms, just not send.
Sent from my SAMSUNG-SGH-I777 using XDA App
I have no wifi but I'm looking for the ATTGalaxyS2Unroot_SGH-i777.tar and I can't find any link, can you point me there? thanks
AMATHEU said:
I have no wifi but I'm looking for the ATTGalaxyS2Unroot_SGH-i777.tar and I can't find any link, can you point me there? thanks
Click to expand...
Click to collapse
Here you go. It is a sticky in the development threads
http://forum.xda-developers.com/showthread.php?t=1286432
AMATHEU said:
I have no wifi but I'm looking for the ATTGalaxyS2Unroot_SGH-i777.tar and I can't find any link, can you point me there? thanks
Click to expand...
Click to collapse
galaxys2root.com's kangs are not supported here...
A proper supported package was linked in the post above.
Factory Data Reset restored wi-fi
I was on UCKK6 (2.3.6) and rooted by flashing Entropy512's Return/Unbrick to Stock (2c)
http://forum.xda-developers.com/showthread.php?p=18576627
and lost wi-fi (scanning then wi-fi shuts off).
Since I was reverting from UCKK6 back to UCKH7, I had to do a factory data reset
(Menu > Settings > Privacy > Factory Data Reset)
based on the info in this thread:
http://forum.xda-developers.com/showthread.php?t=1286432
I got wi-fi back once I did the Factory Data Reset.
I'm having the same problem
Giant noob here =(
Could someone post step by step instructions on how to unroot so that I can restore my wifi?
For example, if in fact doing the factory data reset as described in the post above me is the correct course of action... is there a way to do a backup before so that I do not lose all my apps and stuff?
Thanks
RocketOptics said:
I was on UCKK6 (2.3.6) and rooted by flashing Entropy512's Return/Unbrick to Stock (2c)
http://forum.xda-developers.com/showthread.php?p=18576627
and lost wi-fi (scanning then wi-fi shuts off).
Since I was reverting from UCKK6 back to UCKH7, I had to do a factory data reset
(Menu > Settings > Privacy > Factory Data Reset)
based on the info in this thread:
http://forum.xda-developers.com/showthread.php?t=1286432
I got wi-fi back once I did the Factory Data Reset.
Click to expand...
Click to collapse
Was having problem with WiFi on my T-Mobile SGS2 where it was seem like it was turning on, then try to start scanning for networks then would automatically turn off...I was pulling me hair out reflashing it with different ROMs, and Radios, and doing a "Factory Data Reset" from inside the main Settings screen fixed the problem...thanks a lot guy!
I posted a couple days ago about some issues with rooting my phone, which I solved, but now I have some new issues. When I went to turn on bluetooth, it wouldn't turn on, just try to turn on for a couple seconds and then nothing. I tried turning on wifi, and it would go straight to showing 'error' under wifi. So, I tried a different rom beast 2.3, and being at work, I can't connect the phone to my comp (encryption issues) so I only had a copy of the rom, not a kernel. Once I had beast installed I lost my network too! so I couldn't connect to my provider's network. I wiped everything, brought back AR 1.1, and am currently without bluetooth, wifi, and network. When I scan for networks my telus network shows up, as well as bell, rogers etc.
Is this a kernel issue? As soon as I get home that's the first thing I'll be trying out
andy55 said:
I posted a couple days ago about some issues with rooting my phone, which I solved, but now I have some new issues. When I went to turn on bluetooth, it wouldn't turn on, just try to turn on for a couple seconds and then nothing. I tried turning on wifi, and it would go straight to showing 'error' under wifi. So, I tried a different rom beast 2.3, and being at work, I can't connect the phone to my comp (encryption issues) so I only had a copy of the rom, not a kernel. Once I had beast installed I lost my network too! so I couldn't connect to my provider's network. I wiped everything, brought back AR 1.1, and am currently without bluetooth, wifi, and network. When I scan for networks my telus network shows up, as well as bell, rogers etc.
Is this a kernel issue? As soon as I get home that's the first thing I'll be trying out
Click to expand...
Click to collapse
yes its a kernel issue. what version of software are you running?
I had the wifi error issue, and i flashed the kernel on top of the rom and it works now
Depending on the ROM you flashed, it may or may not display "Flash Kernel after." In which then you flash it. This'll take care of all Bluetooth and Wi-Fi Issues!
If you're having issues let me know.
I had the same issue I was using stock kernel for tmobile version 1.36.531.6 on mine which I had over the air updated to 1.43.531.3. This created the wifi error and bluetooth issue, I had to try different kernels to try to figure this thing out...It will posted in my read me page when I get a chance
It's a kernel issue, there are actually three different kernels, not two, I posted this in xboarders thread, but He hasn't updated his page.
kernels
1: for tmobile software stock 1.43.531.3, this is not available anywhere on the amaze forums, i had to personally extract this from the rooted stock rom that xboarder provided
2: for tmobile software stock 1.36.531.6 and 1.36.531.5 and lower, this stock i believe is the one xboarder has up as the original boot.img
3: faux's custom kernel, this kernel will work with all versions i believe
no luck, flashed faux kernel 3x's and still same problem.
Any other ideas on what it could be?
I get a signal for the phone, no 4g icon, same error with wifi, and nothing with bluetooth or network.
andy55 said:
no luck, flashed faux kernel 3x's and still same problem.
Any other ideas on what it could be?
I get a signal for the phone, no 4g icon, same error with wifi, and nothing with bluetooth or network.
Click to expand...
Click to collapse
you need to help me help you. I ask you again what software version are you on???? go to settings>about phone>software information and look at software version, let me know which you're on.
second: what rom are you running?
you have to answer these two questions
andy55 said:
I posted a couple days ago about some issues with rooting my phone, which I solved, but now I have some new issues. When I went to turn on bluetooth, it wouldn't turn on, just try to turn on for a couple seconds and then nothing. I tried turning on wifi, and it would go straight to showing 'error' under wifi. So, I tried a different rom beast 2.3, and being at work, I can't connect the phone to my comp (encryption issues) so I only had a copy of the rom, not a kernel. Once I had beast installed I lost my network too! so I couldn't connect to my provider's network. I wiped everything, brought back AR 1.1, and am currently without bluetooth, wifi, and network. When I scan for networks my telus network shows up, as well as bell, rogers etc.
Is this a kernel issue? As soon as I get home that's the first thing I'll be trying out
Click to expand...
Click to collapse
I told you rooting is not for you but you thought I was attacking you. But seriously if you do not know what you are doing you will mess up the phone. you still havent because there still is no s-off so pretty much your phone is kinda locked
seansk said:
you need to help me help you. I ask you again what software version are you on???? go to settings>about phone>software information and look at software version, let me know which you're on.
second: what rom are you running?
you have to answer these two questions
Click to expand...
Click to collapse
Aren't your 2 questions the same? Just asking because when you go into software information there is no listing for software version, only software number which displays the name of the Rom you are running. Which would make it answer to both of your questions.
To the Op, are you sure the kernel flashed correctly when you flashed fauxs kernel? Did you use the EFK to flash it or did you try and flash it through CWM? Go into software information and tell us what it says under kernel
sent from my Bulletproof Amaze w/faux .008 kernel
aj_2423 said:
Aren't your 2 questions the same? Just asking because when you go into software information there is no listing for software version, only software number which displays the name of the Rom you are running. Which would make it answer to both of your questions.
To the Op, are you sure the kernel flashed correctly when you flashed fauxs kernel? Did you use the EFK to flash it or did you try and flash it through CWM? Go into software information and tell us what it says under kernel
sent from my Bulletproof Amaze w/faux .008 kernel
Click to expand...
Click to collapse
Yes you are correct I'm just trying to make sure what he's running so I can provide him the right kernel file to flash!
seansk said:
Yes you are correct I'm just trying to make sure what he's running so I can provide him the right kernel file to flash!
Click to expand...
Click to collapse
lol ok. but the thing is, is that he said he flashed faux's kernel and the stuff still didn't work, which it should no matter what rom hes running, unless of course he was running a sense 3.5 rom which im sure hes not from reading his posts. this is why i'm assuming he did not flash the kernel correctly... wouldnt u agree? we'll see when he finally posts what it says in his software information for what Rom hes running and what it says his Kernel is.
sent from my Bulletproof Amaze w/faux .008 kernel
aj_2423 said:
lol ok. but the thing is, is that he said he flashed faux's kernel and the stuff still didn't work, which it should no matter what rom hes running, unless of course he was running a sense 3.5 rom which im sure hes not from reading his posts. this is why i'm assuming he did not flash the kernel correctly... wouldnt u agree? we'll see when he finally posts what it says in his software information for what Rom hes running and what it says his Kernel is.
sent from my Bulletproof Amaze w/faux .008 kernel
Click to expand...
Click to collapse
yes lets wait, with people with lets experience, I tend to dumb things down when asking questions...I am not doing it to demean them, but It's the only way to get any real good answers and being able to help them. Then over time they'll learn
sean, I was running the android revolution 1.1, and tried a couple different kernels and nothing
But I ended up fixing the issue finally. The super wipe zip file I downloaded with AR 1.1 was corrupt, and wouldn't load properly, so I was installing a rom without doing a wipe every time. So, I put a working copy of the zip on the sd card, and did a manual wipe of the caches, re-installed AR 1.1 and all is well.
So, even though I was following all necessary steps, I failed to realize that the wipe zip was faulty, and really messed everything up, and when I changed the rom again to beastmod, I didn't install the correct kernel with it, so yet more issues.
Happy to say that it's all over, and I have a much faster phone with alot less bloat on it. Thanks to everyone!
aj_2423 said:
lol ok. but the thing is, is that he said he flashed faux's kernel and the stuff still didn't work, which it should no matter what rom hes running, unless of course he was running a sense 3.5 rom which im sure hes not from reading his posts. this is why i'm assuming he did not flash the kernel correctly... wouldnt u agree? we'll see when he finally posts what it says in his software information for what Rom hes running and what it says his Kernel is.
sent from my Bulletproof Amaze w/faux .008 kernel
Click to expand...
Click to collapse
Flashed the kernel as xboarder showed in his thread and video.
Have a VZW DNA, currently on Hatka 3.0.3. S-Off, latest radio, stock 2.04 kernel. Twrp
Shortly before I flashed the new radios, I had a problem that whenever I tried to connect a call, whether incoming or outgoing, com.android.phone or.. process.acore?? would force close. I can't remember what the exact name of the acore force close was. Anyway.
I was pretty sure I fixed the problem before I flashed the new radios, but either way, I have the problem again. And, I have noticed that after the force close, the SIM seems to reset. Get a toast message for preparing the SIM card.
It makes no difference whether its the stock dialer, or a third party like Go Contacts. Third party apps don't force close, just go back to whatever I was doing before I tried to connect the call.
I tried flashing the viper with both dsb's stock and cubed kernel with viper to no avail. I haven't tried RUU, or old radios simply because I haven't had time to back up.
Any ideas before I do RUU?
Sent from my HTC6435LVW using xda premium
cappiez said:
Have a VZW DNA, currently on Hatka 3.0.3. S-Off, latest radio, stock 2.04 kernel. Twrp
Shortly before I flashed the new radios, I had a problem that whenever I tried to connect a call, whether incoming or outgoing, com.android.phone or.. process.acore?? would force close. I can't remember what the exact name of the acore force close was. Anyway.
I was pretty sure I fixed the problem before I flashed the new radios, but either way, I have the problem again. And, I have noticed that after the force close, the SIM seems to reset. Get a toast message for preparing the SIM card.
It makes no difference whether its the stock dialer, or a third party like Go Contacts. Third party apps don't force close, just go back to whatever I was doing before I tried to connect the call.
I tried flashing the viper with both dsb's stock and cubed kernel with viper to no avail. I haven't tried RUU, or old radios simply because I haven't had time to back up.
Any ideas before I do RUU?
Sent from my HTC6435LVW using xda premium
Click to expand...
Click to collapse
I had the same issue today between 2 and 3, but it wasn't letting me send texts even though I could receive them. Maybe a network hiccup?
I am on stock radios, didn't know new ones came out. It is working for me now.
in the same boat
looks like we're in the same situation. I looked through the threads and this is another case of call errors. I found this thread and one other, not sure if it was droid dna related.
cappiez said:
Have a VZW DNA, currently on Hatka 3.0.3. S-Off, latest radio, stock 2.04 kernel. Twrp
Shortly before I flashed the new radios, I had a problem that whenever I tried to connect a call, whether incoming or outgoing, com.android.phone or.. process.acore?? would force close. I can't remember what the exact name of the acore force close was. Anyway.
I was pretty sure I fixed the problem before I flashed the new radios, but either way, I have the problem again. And, I have noticed that after the force close, the SIM seems to reset. Get a toast message for preparing the SIM card.
It makes no difference whether its the stock dialer, or a third party like Go Contacts. Third party apps don't force close, just go back to whatever I was doing before I tried to connect the call.
I tried flashing the viper with both dsb's stock and cubed kernel with viper to no avail. I haven't tried RUU, or old radios simply because I haven't had time to back up.
Any ideas before I do RUU?
Sent from my HTC6435LVW using xda premium
Click to expand...
Click to collapse
sjhanson Today, 12:20 AM #1035
Junior Member
Thanks Meter 1
Posts: 11
Join Date: Jan 2011
I am running 3.0.3 now. I was running Viper until the big man published 3.0.3, then i switched back. But even on Viper I was getting the same COM.PHONE.ANDROID has stopped error.
Cheers!
http://forum.xda-developers.com/showthread.php?t=2126386&page=2
borkborkbork! said:
looks like we're in the same situation. I looked through the threads and this is another case of call errors. I found this thread and one other, not sure if it was droid dna related.
Click to expand...
Click to collapse
Link to any of the other threads?
http://forum.xda-developers.com/showthread.php?t=2157855
xDexter said:
Link to any of the other threads?
Click to expand...
Click to collapse
I had the same issue, actually was getting soft reboots upon receipt of an incoming call, happened to me after s-off. It took a bit of fiddling, but I finally got back up and running 100% by flashing stock kernel and a clean ROM install.
TheJ0hnman said:
I had the same issue, actually was getting soft reboots upon receipt of an incoming call, happened to me after s-off. It took a bit of fiddling, but I finally got back up and running 100% by flashing stock kernel and a clean ROM install.
Click to expand...
Click to collapse
You went back to S-ON or just a different kernel?
TheJ0hnman said:
I had the same issue, actually was getting soft reboots upon receipt of an incoming call, happened to me after s-off. It took a bit of fiddling, but I finally got back up and running 100% by flashing stock kernel and a clean ROM install.
Click to expand...
Click to collapse
I also tried going back to stock ruu , nothing worked for me
borkborkbork! said:
I also tried going back to stock ruu , nothing worked for me
Click to expand...
Click to collapse
I am having 0 issues anymore with S-OFF and .torrented's rom and suggested R/W kernel: http://forum.xda-developers.com/showthread.php?t=2150262
xDexter said:
I am having 0 issues anymore with S-OFF and .torrented's rom and suggested R/W kernel: http://forum.xda-developers.com/showthread.php?t=2150262
Click to expand...
Click to collapse
com.android.phone .. but I still get my txt messages, go figure. I think my partitions may be in rare shape from rom's, kernals, and all the other numerous changes. Never been the same after I got error 7 on schatka 3.0.2, I switched back and forth from viper/hatka and twrp/cwmr
I took my phone into Verizon yesterday, explained the situation. Told them it started after ota, and I had done a factory reset already. They tried a new SIM card to no avail, overnighting a new phone.
Sent from my HTC6435LVW using xda premium
xDexter said:
You went back to S-ON or just a different kernel?
Click to expand...
Click to collapse
Forgot about this post, sorry. Did not go back to s-on, just flashed stock kernel from here: http://d-h.st/Ma1, boot.img via fastboot and then the modules zip contained within in recovery, and everything was good.
This didnt work for me . Any other suggestions?
cappiez said:
I took my phone into Verizon yesterday, explained the situation. Told them it started after ota, and I had done a factory reset already. They tried a new SIM card to no avail, overnighting a new phone.
Sent from my HTC6435LVW using xda premium
Click to expand...
Click to collapse
Basically I hd the same situation happen to myself, no calls or data but wifi was good. Mine started to fail slowly , firs \t it was showing a 1X connection but dl were about 3G speeds. Next I lost signals in areas I never had signal issues with. Then total loss. New sim card and spent hours on the support line and a replacement unit.
Got a PM request for assistance, and thought I don't have a lot of tips to offer other than what I provided before, I'm going to post a more detailed overview (as I remember it, it's been awhile...) in case it's helpful for any other who may come across it later. The bottom line for me was that once things broke, it didn't work again until I flashed stock kernel via fastboot +modules in recovery and did a clean install of Hatka 3.03 w/ Sense launcher. That said, because of my flashing compulsion and failure to fully test things once installed, I can't pinpoint the exact step at which things broke.
Initially, I: Bought phone and factory reset, did not take Verizon OTA. Fiddled around, hated Sense, unlocked, flashed recovery, flashed Viper 1.1.0 (?, whatever the base was), booted and setup, fiddled around, hated Sense, wiped data, flashed 3 subsequent Viper updates (1.1.1,2,3 maybe?), booted and setup, fiddled around, hated Sense. Wiped and reinstalled de-Sensed Viper a few times in an attempt to get rid of Sense as much as possible.
Then things get murky. I did s-off, and at some point flashed (recovery) a kernel, Cubed I think. Wifi or something was borked (as I understand is the case with Cubed/Viper), and I flashed stock kernel back via recovery (no modules, I didn't catch that part at the time) and restored my backup for good measure, leaving me on fully functional Viper 1.1.3. Everything worked for a few days, but I continued to hate Sense, and began searching for something more sensible. At some point I flashed Hatka 3.03 w/ de-Sensed options, went to 320 DPI, and thought everything was fine for about 18 hours until I realized my phone was warm, and figured out it was rebooting every time I received (or placed) an incoming call (boss was pissed and kept trying to call me, already gives me a hard time about being an Android fanboy so I'm never going to hear the end of that). After a few hours of fiddling and various recovery attempts including restores and full wipe/clean installs of Viper, I finally managed to get things up and running with A. flashing stock kernel via fastboot + modules in recovery and a full wipe/clean install of Hatka 3.03 w/ Sense + Xperia launchers and eventually a 380 DPI.
One of or some combination of the s-off/custom kernel/failure to reinstall stock kernel modules/de-Sensed/low DPI/pin lock/Widget Locker/Viper combo I had going fouled something up, which I know is not entirely helpful. If I found myself in this situation again, I would flash stock boot.img via fastboot + modules in recovery, and probably flash a stock ROM to rule out anything else, then wipe and flash things from there until I got where I wanted or it broke.
For the record, I'm now back on my Galaxy Nexus until stable-ish CM 10.1 is within sight or I get tired of waiting and sell the thing, I just can't tolerate Sense.
same issue
I've been reading wherever I see this topic and haven't found the answer that I'm looking for. Have tried everything said but nothing has fixed my problem can't make or receive calls. This problem happened after I turned s-off have relocked boot loader, flashed RUU, reset factory, re-unlocked bootloader, re-flashed different roms, and flashed radios still not working. No doubt it is a software issue. Does anyone know how to format internal storage on this phone. My thinking is if that can be done problem should go away and then can re-flash to stock. Any help would be most appreciated.
jimmydee62 said:
I've been reading wherever I see this topic and haven't found the answer that I'm looking for. Have tried everything said but nothing has fixed my problem can't make or receive calls. This problem happened after I turned s-off have relocked boot loader, flashed RUU, reset factory, re-unlocked bootloader, re-flashed different roms, and flashed radios still not working. No doubt it is a software issue. Does anyone know how to format internal storage on this phone. My thinking is if that can be done problem should go away and then can re-flash to stock. Any help would be most appreciated.
Click to expand...
Click to collapse
Have you tried fixing permissions? In some other post I read phone process force closing was just a matter of wrong permissions.
In other hand I think if you format system, data and cache the phone storage would just keep hboot and recovery; at that point you could only run RUU to stock or adb sideload from recovery if your CWM version has the feature.
Sent from my HTC6435LVW using xda app-developers app
still problem
Yes have fixed permissions. Also have formatted everything I could in CWM still have problem. Is there a way to format with ADB commands?
This is my first post on this forum and I am nowhere near as tech savvy as most people on here, so I apologise in advance if anything I post sounds daft or if I have broken any forum rules which I have tried to follow.
I have a Galaxy S2 GT-I9100 which was on Android 4.1.2 and which I am trying to flash to Kitkat with limited success using Slim Sabre.
If I unzip Slim Sabre by itself the phone "works" - I can make calls use internet, text etc, but when I install gapps all I get is messages stating "the android process (name of process) has stopped" - the processes include keyboard, location, calendar and a couple of others. I've tried flashing different versions of gapps, as well as Slimkat but keep getting the same thing.
I would really appreciate it if someone can point me in the right direction as to what I need to do to get kitkat working on my phone.
Again, my apologies if I have forgotten to include information or breached any rules, and thanks in anticipation for any assistance.
The following is currently what I have on "about phone"
Android version: 4.4.2
Kernel version: 3.0.80+ [email protected] #1
Slim version: Slim-4.2.2.build.5-OFFICIAL-4068
Build number : slim_i9100-userdebug 4.4.2 KVT49L 4068 test-keys
Update
Just to update, after switching my phone off and on again, the only message now appearing is "android keyboard (AOSP) has stopped". I am not getting any of the other messages for some reason.
I've tried clearing data from Keyboard app as well as dictionary and also tried clearing the cache on both. The cache for the dictionary was at 12 kb and when I pressed the clear cache button nothing happened (though I did get haptic feedback so I know it was pressed).
I've also tried installing LatinIME.APK but it fails to install (I have allowed unknown sources).
Also tried fixin permissions.
I would really appeciate any help and guidance on this - I am very new to all this flashing and rom business as you might guess!
Many thanks
rk001 said:
Just to update, after switching my phone off and on again, the only message now appearing is "android keyboard (AOSP) has stopped". I am not getting any of the other messages for some reason.
I've tried clearing data from Keyboard app as well as dictionary and also tried clearing the cache on both. The cache for the dictionary was at 12 kb and when I pressed the clear cache button nothing happened (though I did get haptic feedback so I know it was pressed).
I've also tried installing LatinIME.APK but it fails to install (I have allowed unknown sources).
Also tried fixin permissions.
I would really appeciate any help and guidance on this - I am very new to all this flashing and rom business as you might guess!
Many thanks
Click to expand...
Click to collapse
Reboot to recovery and then Simply reflash the rom zip file once again without any wipe and see
Thanks for responding. Ive done as you said but still get the same thing.
Boot into recovery - wipe/factory reset.
Still no joy. Ive read that another cause is flashing the wrong version of android. Does the info ive put in my first post suggest this?
Really do appreciate the help being provided.
Just tried iWnn IME but get the same problem if that sheds any light
Umm... Gone quiet on here! Will it be worthwhile trying a new rom, kernel etc and see if that works or is the problem indicative that nothing will work?
Turns out I was using wrong version of gapps. Got the correct one now and all seems to be running OK. However Play is now telling me that Candy Crush is not compatible with my device but it was before. Any ideas what that is all about? I need it to keep me sane at work!!