Related
I had used the amaze 4g all in one tool kit to unlock my bootloader, install a custom recovery, and then installed a custom rom (bullet proof 2.5) along with the provided kernel to go with it.
The phone worked great for a few days, then I noticed that it was acting like the wireless network radios were turned off in the software. They were still enabled so I rebooted and it fixed the problem for a little while.
Now my phone will only give me the com.android.phone has stopped working error and will not let me turn on the wireless network radios.
I have tried complete wipe of the phone and re-installation of the custom rom. I have tried different, yet still recommend, custom kernels, as well as different recoveries all with the same issue.
Any help would be greatly appreciated. I tried searching with out any good results.
Thanks.
Are you a Tmobile user?
Double0EK said:
Are you a Tmobile user?
Click to expand...
Click to collapse
Yeah. Even tried a new simcard even though I didnt think it would do any good.
toyoter91 said:
I had used the amaze 4g all in one tool kit to unlock my bootloader, install a custom recovery, and then installed a custom rom (bullet proof 2.5) along with the provided kernel to go with it.
The phone worked great for a few days, then I noticed that it was acting like the wireless network radios were turned off in the software. They were still enabled so I rebooted and it fixed the problem for a little while.
Now my phone will only give me the com.android.phone has stopped working error and will not let me turn on the wireless network radios.
I have tried complete wipe of the phone and re-installation of the custom rom. I have tried different, yet still recommend, custom kernels, as well as different recoveries all with the same issue.
Any help would be greatly appreciated. I tried searching with out any good results.
Thanks.
Click to expand...
Click to collapse
are you running joes "one good rom"? dude it says right in the op
Attention 2: on the first start "com.android.phone" process will FC, it is normal.
It's because of Toggle2G app. Just open that app and give it permission to run.
mrmako777 said:
are you running joes "one good rom"? dude it says right in the op
Attention 2: on the first start "com.android.phone" process will FC, it is normal.
It's because of Toggle2G app. Just open that app and give it permission to run.
Click to expand...
Click to collapse
I actually stated in my first post what rom I was running when all this happened.
I have tried Joes "one good rom" and followed all his kernel and set up instructions with no luck. On his rom I don't get the error message, but all of the wireless network options are grayed out. I am starting to think it might be something hardware.
toyoter91 said:
I actually stated in my first post what rom I was running when all this happened.
I have tried Joes "one good rom" and followed all his kernel and set up instructions with no luck. On his rom I don't get the error message, but all of the wireless network options are grayed out. I am starting to think it might be something hardware.
Click to expand...
Click to collapse
doh! shame on me for not seeing that i would say if worse comes to worse, reflash the stock rom and see if youre up and running. if its still not working, then id say maybe send it in for warranty
mrmako777 said:
doh! shame on me for not seeing that i would say if worse comes to worse, reflash the stock rom and see if youre up and running. if its still not working, then id say maybe send it in for warranty
Click to expand...
Click to collapse
No worries. I am actually in the process of finding and flashing the stock rom back onto it, going to try and put everything back to stock and see what happens.
Having a similar problem
toyoter91 said:
No worries. I am actually in the process of finding and flashing the stock rom back onto it, going to try and put everything back to stock and see what happens.
Click to expand...
Click to collapse
Hi. I decided to add to this thread instead of starting a new one since i am having a similar problem. The originator never said if he was able to solve the problem. I was using the Energy ROM (http://forum.xda-developers.com/showthread.php?t=1362759) (ICS, S-ON) and everything was fine. I decided to try the Speed ROM (project "butter" http://forum.xda-developers.com/showthread.php?t=1623184) which is Jellybean based. I did a full wipe, and after installing it I got the same com.android.phone error. I got it to stop, but then started having other issues like Superuser, BusyBox, and Titanium Backup unable to get root access. Unable to find any other solutions, I decided to restore to stock, which went fine (well I had to try a few times as I haven't done it before). After that, and having the phone working fine back at stock ICS I reflashed the Speed ROM. I ended up with the same issue. I wiped again and returned to the Energy ROM and it seems to be working fine. My quesiton is, why is the Speed ROM not working on my phone? When it flashed there were no issues, and I followed the instrucitons exactly.
I would post in the Speed ROM forum but I don't have enough posts yet since I am usually able to find answers by searching.
BillyD325 said:
Hi. I decided to add to this thread instead of starting a new one since i am having a similar problem. The originator never said if he was able to solve the problem. I was using the Energy ROM (http://forum.xda-developers.com/showthread.php?t=1362759) (ICS, S-ON) and everything was fine. I decided to try the Speed ROM (project "butter" http://forum.xda-developers.com/showthread.php?t=1623184) which is Jellybean based. I did a full wipe, and after installing it I got the same com.android.phone error. I got it to stop, but then started having other issues like Superuser, BusyBox, and Titanium Backup unable to get root access. Unable to find any other solutions, I decided to restore to stock, which went fine (well I had to try a few times as I haven't done it before). After that, and having the phone working fine back at stock ICS I reflashed the Speed ROM. I ended up with the same issue. I wiped again and returned to the Energy ROM and it seems to be working fine. My quesiton is, why is the Speed ROM not working on my phone? When it flashed there were no issues, and I followed the instrucitons exactly.
I would post in the Speed ROM forum but I don't have enough posts yet since I am usually able to find answers by searching.
Click to expand...
Click to collapse
That's a common problem with SpeedRom and some other as well. Re-flash the SpeedRom, after it boot-up, go to Google Play store and download SuperSU -not Superuser -, open SuperSU and update binary. After that you can install busy box and run Titanium ....
antiquezip said:
That's a common problem with SpeedRom and some other as well. Re-flash the SpeedRom, after it boot-up, go to Google Play store and download SuperSU -not Superuser -, open SuperSU and update binary. After that you can install busy box and run Titanium ....
Click to expand...
Click to collapse
Thank you! After I posted I ran across somehting in the speed rom thread that made me go back to the original post. Sure enough, there is a download link for SuperSU which it says you need to flash to gain root after installng the ROM. I guess I read the instructions above, scrolled down to the rom download link, and then stopped. I will try this again with what you suggested when I have time in the next day or two.
BillyD325 said:
Thank you! After I posted I ran across somehting in the speed rom thread that made me go back to the original post. Sure enough, there is a download link for SuperSU which it says you need to flash to gain root after installng the ROM. I guess I read the instructions above, scrolled down to the rom download link, and then stopped. I will try this again with what you suggested when I have time in the next day or two.
Click to expand...
Click to collapse
I had this error factory reset stop the error.
This belongs in Q&A.
Thread Moved.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
"If you choose not to decide, you still have made a choice"
Sent from my Galaxy Note (i717), using XDA Premium.
I am coming from a Galaxy Nexus. I have flashed many roms in the past, but when I flash roms on the Note the phone portion seems to stop working. Data works fine, its just when I try to make a call it just sits there for a long time and then the call terminates. Happens every time a flash a new rom. With my old Droid 1 on Verizon you could dial up a number to reactivate the phone, on the Nexus this seems to not be an issue at all. Is there some trick to getting AT&T to reinitialize the cell phone after a new rom flash? I tried pulling the battery for like 5 minutes figuring that would force it to resync or something...
Any one else running into this?
Never heard of this problem. Which roms are you loading, I would suggest asking the dev of the ROM, including all of the steps you use to install it.
Sent from my SAMSUNG-SGH-I717 using XDA
I completely agree with you and same thing is happening to my note as well...I thought i was in bad signal area....now i am running into problems with google market....cant load apps...always showing error 492....i installed saurom rom rc7 and also i dont see what kernel i have on my phone....i also installed the kernel fix and flashed it....still nothing...i am myself trying to get some help here
busybeebusy said:
I completely agree with you and same thing is happening to my note as well...I thought i was in bad signal area....now i am running into problems with google market....cant load apps...always showing error 492....i installed saurom rom rc7 and also i dont see what kernel i have on my phone....i also installed the kernel fix and flashed it....still nothing...i am myself trying to get some help here
Click to expand...
Click to collapse
To fix the market you need to reboot to clockworkmod and clear the cache. The issue with the kernel is normal, it is the HoloKernel, it just has bad information in the about screen, that's normal too.
To fix the phone issue I usually pull the battery for like 5 minutes and then toggle the network from auto to manual a couple of times and then it seems to finally pick it up. Just seems odd...
omniphil said:
I am coming from a Galaxy Nexus. I have flashed many roms in the past, but when I flash roms on the Note the phone portion seems to stop working. Data works fine, its just when I try to make a call it just sits there for a long time and then the call terminates. Happens every time a flash a new rom. With my old Droid 1 on Verizon you could dial up a number to reactivate the phone, on the Nexus this seems to not be an issue at all. Is there some trick to getting AT&T to reinitialize the cell phone after a new rom flash? I tried pulling the battery for like 5 minutes figuring that would force it to resync or something...
Any one else running into this?
Click to expand...
Click to collapse
Did you flash the ATT fix after flashing RC7? If not, download ATT fix, flash Saurom RC7, wipe cache and d cache, flash ATT fix and then reboot system...
Update.....yesterday i opened the cwm and just cleared the wipe cache and then rebooted the phone and everything came back to normal...error code 492 disappeared and i was able to download all my apps.. I hope it will help somebody. Running saurom rc7. Everything looks fine so far....only data speed needs to go up some more but it could be the area....
Sent from my SGH-I717R using XDA
omniphil said:
To fix the market you need to reboot to clockworkmod and clear the cache. The issue with the kernel is normal, it is the HoloKernel, it just has bad information in the about screen, that's normal too.
To fix the phone issue I usually pull the battery for like 5 minutes and then toggle the network from auto to manual a couple of times and then it seems to finally pick it up. Just seems odd...
Click to expand...
Click to collapse
What is the problem with the kernel that you need to flash the kernel fix? Is that only if you use holo kernel?
I've been having this issue for a few days now and I haven't been able to solve it myself. I've been using a GB rom for the past few months (this one and it's always been working fine. Still, I wanted to try ICS so I got myself to install CM9 on the device, and while I was at it, updated the baseband to 72. However, since then, I've been unable to connect to Wifi. I can see Wifi networks, but as soon as I try to connect it gets stuck on "Connecting". I tried flashing other ICS roms and restoring the baseband, nothing works. Yesterday I put the rom back that I've been using succesfully over the past months but still no difference.
When I scan for networks, they appear fine. Reception is good, but as soon as it tries to connect the icon changes to the icon for poor reception. It doesn't matter what network I pick. Other devices running Android have no problem connecting.
Does anyone have an idea what might cause this issue? Is there any way to get a logging of the Wifi to see what exactly goes wrong? Any troubleshooting steps I could take? Your help would be very much appreciated
edit: forgot to mention, with CM9 I used the CM9 kernel, with other roms I use Rage kernel
in exactly the same situation as above, except it was all working just fine until a couple of hours ago. now suddenly the router that's sitting right in front of me, giving full signals has turned into a "poor connection"!!!
i'm on CM9 with CM9 kernel and the recommended baseband
especially suspicious is the facebook application that just got updated when it was working fine a couple of hours or so back. hasn't worked since that update
Backup and try this https://www.dropbox.com/s/s587q1udg2ya2s1/Xperia Mini,LWW,Active_wifi_modules.zip flash in cmw and perform factory reset after that..
If it doesn't work then flash this stock ics ftf http://www.4shared.com/rar/du68FPM-/SK17i_41B0431__1249-7380ftf.html?refurl=d1url via flashtool...
Sent from my WT19i using xda app-developers app
rachit.rc96 said:
Backup and try this https://www.dropbox.com/s/s587q1udg2ya2s1/Xperia Mini,LWW,Active_wifi_modules.zip flash in cmw and perform factory reset after that..
If it doesn't work then flash this stock ics ftf http://www.4shared.com/rar/du68FPM-/SK17i_41B0431__1249-7380ftf.html?refurl=d1url via flashtool...
Sent from my WT19i using xda app-developers app
Click to expand...
Click to collapse
Flashed the Wifi module, did a factory reset and it's connected! Thank you so much :laugh:
my problem solved as well. i didn't read rachit.rc96's reply so i solved it the hard way
was previously on baseband 72, flashed baseband 64 then 72 back again, no luck, went back to gingerbread, rooted then was able to connect to only one of my routers, the other one wasn't even showing up then flashed stock ics rooted that, now able to connect to both routers.
was that a problem with cm9 i wonder. or what?
Ok I hate starting a new thread but I have a problem that I can not seem to find any information on it,
I have had my S2 for 1.5 years and have run many many custom roms. Been using Paranoid lately. Today I tried flashing the newest Wanam Lite as my second rom keeping Paranoid as primary. (using dorimanx kernel)
Wanam failed to install. After boot the screen goes black. No problem... I will just go back to my Primary rom. Tried, Tested and True, Paranoid Android.
What's this? My phone is asking for SIM unlock code. I unlocked this phone 1 and a half years ago. Ok so I unlock it the same way i had done in the past for my S2 and many friends S2. I installed "Galaxy S Unlock" from the market and ran it. Ok phone is unlocked and I can use it like normal, as I have network signal.
But as soon as I reboot it is locked again. So now I have to unlock the SIM every time I reboot my phone.
Does anyone know why this is happening?
This is what I have tried so far.
- reinstalled ROM
- wiped dalvic
- wiped data
- wiped cache
- fixed permissions
Nothing I try solves the problem. Every time I reboot I lose my sim unlock.
Any help is appreciated.
Thanks.
anyone have any insight into this??
has this happened to anyone else?
kevjef420 said:
Ok I hate starting a new thread but I have a problem that I can not seem to find any information on it,
I have had my S2 for 1.5 years and have run many many custom roms. Been using Paranoid lately. Today I tried flashing the newest Wanam Lite as my second rom keeping Paranoid as primary. (using dorimanx kernel)
Wanam failed to install. After boot the screen goes black. No problem... I will just go back to my Primary rom. Tried, Tested and True, Paranoid Android.
What's this? My phone is asking for SIM unlock code. I unlocked this phone 1 and a half years ago. Ok so I unlock it the same way i had done in the past for my S2 and many friends S2. I installed "Galaxy S Unlock" from the market and ran it. Ok phone is unlocked and I can use it like normal, as I have network signal.
But as soon as I reboot it is locked again. So now I have to unlock the SIM every time I reboot my phone.
Does anyone know why this is happening?
This is what I have tried so far.
- reinstalled ROM
- wiped dalvic
- wiped data
- wiped cache
- fixed permissions
Nothing I try solves the problem. Every time I reboot I lose my sim unlock.
Any help is appreciated.
Thanks.
Click to expand...
Click to collapse
First of all , use the following to unlock your phone, if it works for you that would be gud otherwise flash the rom again (Fresh Install)
https://dl.dropbox.com/u/21618136/GalaxSimUnlock.apk
You cannot dual boot Leaked JB based roms as of yet ..
Exatley same things happend with me at this afternoon. My sgs 2 was unlocked nearly a year ago, and I'v been tryed a new "leaked - out" rom which I've found on the Sammobile forum. I9100XXLSJ - Offical, beta... or alpha.. dunno, but 4.1.2
Few minutes later I also tried an another rom... http://forum.xda-developers.com/showthread.php?t=2037363 XXLSJ tweeked by Alliance.
I've wiped everything before every install, and I'm not sure where I've lost my "unlocked" status... Lol.. First time I was thinking its a PIN code only. Obviously I never seen this before. In the last few year I installed, and tried many roms without any issue. Mostly Darky's, CM 7-9.
But long story short: your tool solved my problem under a minute. Thank you so much MR.Killer
Ps: maybe I also tried a CM10 nighty build today.. I cant bear in my mind everything
jstonehun said:
Exatley same things happend with me at this afternoon. My sgs 2 was unlocked nearly a year ago, and I'v been tryed a new "leaked - out" rom which I've found on the Sammobile forum. I9100XXLSJ - Offical, beta... or alpha.. dunno, but 4.1.2
Few minutes later I also tried an another rom... http://forum.xda-developers.com/showthread.php?t=2037363 XXLSJ tweeked by Alliance.
I've wiped everything before every install, and I'm not sure where I've lost my "unlocked" status... Lol.. First time I was thinking its a PIN code only. Obviously I never seen this before. In the last few year I installed, and tried many roms without any issue. Mostly Darky's, CM 7-9.
But long story short: your tool solved my problem under a minute. Thank you so much MR.Killer
Ps: maybe I also tried a CM10 nighty build today.. I cant bear in my mind everything
Click to expand...
Click to collapse
Glad i helped and you never clicked the thanks button
Please CLICK THANKS IF I HELP
Mr.KiLLeR said:
First of all , use the following to unlock your phone, if it works for you that would be gud otherwise flash the rom again (Fresh Install)
https://dl.dropbox.com/u/21618136/GalaxSimUnlock.apk
You cannot dual boot Leaked JB based roms as of yet ..
Click to expand...
Click to collapse
THANK YOU VERY MUCH. This app solved my problem with the sim unlock. Saw it on the market but it wanted me to pay
I didn't know that the leaked JB could not be dual booted. That would explain the black screen. I think I will back up my primary to SD and try installing that rom again. Does this work on any kernel or just the one it is supplied with?
Anyways. Thanks again. You solved my BIG problem.
kevjef420 said:
THANK YOU VERY MUCH. This app solved my problem with the sim unlock. Saw it on the market but it wanted me to pay
I didn't know that the leaked JB could not be dual booted. That would explain the black screen. I think I will back up my primary to SD and try installing that rom again. Does this work on any kernel or just the one it is supplied with?
Anyways. Thanks again. You solved my BIG problem.
Click to expand...
Click to collapse
only 'Philz' kernel does support the leaked Jb rom or one based on it for know
The app is free to use if you get it from Spockys thread.
I believe you have to pay if you get it through play store.
Hey all,
I downloaded and flashed MM this past week. I *did* root my phone using the latest supersu 2.74 from chainfire. Now, I am random reboots. I did use odin for the firmware flash.
I have a G900t1.
Thoughts?
Having exactly the same issue, phone will work fine for a day or two , them I will get as many as 5 reboots in a day....
sameog said:
Hey all,
I downloaded and flashed MM this past week. I *did* root my phone using the latest supersu 2.74 from chainfire. Now, I am random reboots. I did use odin for the firmware flash.
I have a G900t1.
Thoughts?
Click to expand...
Click to collapse
After all the random reboots, I downgraded back to kitkat because it's stable.
im wanting do go back to lolipop because i made a complete nandroid backup not entirely sure how to go about it, since ive switched to marshmallow my call quality and network connections have been crappy. like having make a call several times before it goes through with full LTE signal strength etc.
darthmalus said:
im wanting do go back to lolipop because i made a complete nandroid backup not entirely sure how to go about it, since ive switched to marshmallow my call quality and network connections have been crappy. like having make a call several times before it goes through with full LTE signal strength etc.
Click to expand...
Click to collapse
Just a thought.. double check your modem and boot loader are correct. But if your sure you want to go back, there is a couple threads with the roms, bl and modem for download.
http://forum.xda-developers.com/tmo.../compilation-s5-g900t-stock-firmware-t3042400
I've found this release very stable and solid.