Related
Hey guys, I'm not new to rooting or flashing ROM's but I've encountered some issues. Basically, I was on an early JB Rom and everything was working fine but it mostly was in roaming and would go from 2-4 signal bars.
I backed up and have attempted to flash:
PACman
MIUI 2.11.23
As well as CM10 by joker and AOKP CM 10.
Every flash I end up with no signal bars and no roaming, also following all install instructions in the threads.
I have tried flashing with and without prop tweak, i have even restored the backup all with the same results:
Empty signal bars, occasional R for roaming, every call says mobile network unavailable.
I have also fixed permissions, and have tried to flash via TH3Bill CWM and TWRP recovery... what am I doing wrong? The backup isin't even working!
I wouldn't know off hand, but here's something you can try while waiting for a more professional member to come to the rescue.
System Settings> More>Mobile Networks>System select>Home only
What's your current PRL, APNs?
if it was me I'd sbf back to stock and see if I had signal then go back and try a custom rom again
foxsdaddy67 said:
if it was me I'd sbf back to stock and see if I had signal then go back and try a custom rom again
Click to expand...
Click to collapse
Before sbf'ing if you have a back up of your stock ROM or any ROM that has the update profile/prl setting in it, restore that back up and try updating your profile/prl then wipe/flash your new ROM.
I usually have this problem when I switch back to my Photon from my ET4G, but updating the profile usually does the trick.
When I restored my old backup, I had the same problem. The only fix I could find was on MIUI and selecting automatic netowrk before flashing options chooser. Any other rom would make no changes on automatic or home only. I am going to try a fresh install and if no luck will sbf today. I'll keep you guys posted.
Thanks!
**EDIT** Does it matter if I use Th3Bill's CWM recovery or TWRP? I have tried both with similar results. I jut noticed CWM is usually posted with the ROM builds... does it makes a difference? If so, what should I use?
Normally both work just fine, as long as you're using one of those two
I spent too much time flashing roms and wondering why they wouldn't work right, when I was using the stock CWM
I think It's just my opinion but I have preference for bill's cwm
Having this exact same problem. Did anyone figure it out?
No Radio/Signal
I recently flashed the latest MIUI.US V5 3.4.5 for the Photon provided by Th3Bill. I am familiar with the process of applying ROMs. I tried to go back to Beanstalk, JB, and ICS and could not recover the radio signal. I even restored a few backups with the same result, no signal. I flashed the MIUI V5 3.4.5 ROM back to the Photon and it worked flawlessly. Can anyone please help? I would really like to get off the MIUI ROM, it does not appeal to me like the standard versions of Jelly Bean that Th3Bill has produced.
Everyone,
I have been running the latest CM10 nightlies for a couple days and love it on my EVO. However, I am having consistent issues with the navigation. I am S-OFF running the latest firmware. I have been flashing the latest CM10 nightly, although I have also tried deck's latest version as well. When flashing, I wipe everything in sight, trying both the superwipe zip and manual wiping, but everytime I install CM10 the Google navigation crashes on me and has weird screen artifacts. I have also tried using the GPS Status app to clear my GPS data to no avail. Does anyone have any other tricks to get nav to work on CM10?
Thanks!
Brian
Well, all I can say is to make sure you have a half decent kernel, and make sure you're using the right gapps. No reason it should crash on you.
actually im in the same boat. had to use waze (not bad at all), just wish it works.
Misterblc said:
Everyone,
I have been running the latest CM10 nightlies for a couple days and love it on my EVO. However, I am having consistent issues with the navigation. I am S-OFF running the latest firmware. I have been flashing the latest CM10 nightly, although I have also tried deck's latest version as well. When flashing, I wipe everything in sight, trying both the superwipe zip and manual wiping, but everytime I install CM10 the Google navigation crashes on me and has weird screen artifacts. I have also tried using the GPS Status app to clear my GPS data to no avail. Does anyone have any other tricks to get nav to work on CM10?
Thanks!
Brian
Click to expand...
Click to collapse
I have the same issue. Eventually I was going to get around to trying a different kernel.
I am running the Kernel from the CM10 build:
3.0.53-dc2c1ebb
[email protected] #1
Mon Dec 3 21:32:25 PST 2012
As for the GAPPS I just installed the latest I could find with the ROM and then downloaded the latest Maps from the market.
Any recommendations on a good kernel to try?
This is a widespread issue for unrooted, stock users. It is documented in several forums, so it does not only affect you or other rooted users.
I am running CM10 12/05 build from IRC and used my Navigation with G maps for 2 straight hours today with no problems.
I am on the kernel it comes with. Before flashing CM10 I update prl, profile and make sure I have a GPS lock on a Sense rom. Then go into TWRP and wipe cache, dalvick, factory reset, and system a couple times each, flash CM10, I'm using the Captain's Gapps from IRC and it works fine for me.
I've never wiped the GPS data stuff or anything like that either.
YMMV though I guess
Naters
Naters,
I haven't tried using the IRC build...do you have a link / instructions on how to get that (and the GAPPS). I will try loading up MeanROM, getting a sense lock, and then switching to that build.
Thanks!
Brian
NaterTots said:
I am running CM10 12/05 build from IRC and used my Navigation with G maps for 2 straight hours today with no problems.
I am on the kernel it comes with. Before flashing CM10 I update prl, profile and make sure I have a GPS lock on a Sense rom. Then go into TWRP and wipe cache, dalvick, factory reset, and system a couple times each, flash CM10, I'm using the Captain's Gapps from IRC and it works fine for me.
I've never wiped the GPS data stuff or anything like that either.
YMMV though I guess
Naters
Click to expand...
Click to collapse
This is the link to get into the IRC channels.
Once you are in the DL link for the rom and Gapps will be at the top of the page.
http://forum.xda-developers.com/showthread.php?t=1643396
Let me know how it works for you.
Naters
Tried it, some problem unfortunately...I guess this is a YMMV type thing.
BTW, is that IRC channel a good place to get support for CM10? I was hoping to talk with the developers and try to help out with kernel logs or whatever may be useful.
Brian
NaterTots said:
This is the link to get into the IRC channels.
Once you are in the DL link for the rom and Gapps will be at the top of the page.
http://forum.xda-developers.com/showthread.php?t=1643396
Let me know how it works for you.
Naters
Click to expand...
Click to collapse
Sorry it didn't work.
No clue why it works for some and not others.
Sent from my PC36100 using xda app-developers app
Working now
I was having a lot of problems with the navigation until looked in the location access menu and selected the GPS source as "Use Internal GPS." It has been running smooth since then. :fingers-crossed: Hopes this helps.
Hi,
We have 2 Vibrant phones. 1 is on Paranoid Android 2.54 (via stock eclair, ICS Passion, Slim Bean 2.9 & 3.0) and works perfectly.
The second one was on ICS Passion for a long time and I have finally got around to (trying LOL) to update it.
Here is where the weirdness begins - Flashed PA 2.54 no problems, flashed and booted up, but no wi-fi, well no wi-fi icon, and it can find a couple of wi-fi networks belonging to my neighbours, but won't find my network, 2 rooms away. The network is obviously all good, I am sending this from my laptop through said network.
Obviously I need an internet connection to get through the phone setup, so I power down, throw the SIM back in and boot up only to find no cell data either.
Skip the google account setup and get to the home screen to check things further and I find:
Calls in/out work, and most things are running, but wi-fi won't co-operate, and nothing in the APN list? Baseband and IMEI all look normal, too.
Try to flash Slim Bean 2.9 as I put the zip on the phone at the same time as a fallback and I get EXACTLY the same thing...
Anyone able to shed any light on what would cause this? Anything else worth trying? I'd like to avoid Odin as it honestly scares me reading all the problems people on here have with it...
At this point I've tried flashing both ROMs a few times with exactly the same results, I also can't go back to the ICS nandroid as the partition setup has changed and the restore doesn't work...
Thanks in advance for any help anyone can give.
Cheers...
I ended up flashing a 4.2 ROM (slim 4.2 beta 1) and it made the problem go away, I'm guessing something in the 4.1 base was broken and not getting overwritten on new installs?
ROM seems pretty sorted for a beta, few minor things not working, but hopefully it gives us a clean upgrade path...
Thanks.
I had the same issue with Slim 4.2 Beta 2. If anyone has a solution other than flashing the modem, please post.
Weird. The phone I was having this problem with now has that ROM on it and is working 100%.
I have a suspicion that flashing a ROM that uses a different kernel is what fixed it for us. I guess it just overwrites/replaces more stuff?
Maybe try hellybean 4.2 and see if it makes a difference, and if it does flash back to slim 4.2 and see if the problem comes back?
I have installed slim and other ROMs but not had this issue. Currently on jellybam
Sent from my GT-I9300 using xda premium
wendleburger said:
Weird. The phone I was having this problem with now has that ROM on it and is working 100%.
I have a suspicion that flashing a ROM that uses a different kernel is what fixed it for us. I guess it just overwrites/replaces more stuff?
Maybe try hellybean 4.2 and see if it makes a difference, and if it does flash back to slim 4.2 and see if the problem comes back?
Click to expand...
Click to collapse
The weird part is that every other Slim Bean has worked great. I'll keep my fingers crossed for beta 3.
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?
Due to instability issues in the latest nightlies, I clean flashed and reverted back to CM11 milestone 5. After doing this, I haven't been able to get mobile data. Voice and sms work fine, just "mobile network state disconnected" and no data connectivity. Also after flashing back to M5, "Phone" seems to prevent the device from sleeping. In battery stats, the device is always awake, with "Phone" using the majority of the batter.
I've tried re-flashing CM11 M5 multiple times, I've also flashed different modems, and I've also called AT&T to reset my internet connectivity. Nothing has worked thus far. Any suggestions? :good:
UPDATE/SOLUTION:
I got mobile data back by going back to stock, clean flashing AOKP (which works with mobile data), then dirty flash to CM11. Quite unorthodox, probably not the best solution, but it's the only 'fix' that has worked!!
I've tried many other suggestions, such as the "patched" modems & kernels, to no avail. Finally this works, dreams do come true
UPDATE: I tried ODINing back to stop 4.3 ROM, on which data was working again. However, upon flashing back to CM11, data stopped working once again. I tried flashing AOKP, which *did* get data back, so I'm assuming this is a CM11-exclusive problem.
I really don't know how the CM11 data problem persisted even after flashing back to stock and then re-flashing CM11. What could've gone wrong? Anyways, I guess I'm sticking to AOKP for the time being.
n0stalgia said:
UPDATE: I tried ODINing back to stop 4.3 ROM, on which data was working again. However, upon flashing back to CM11, data stopped working once again. I tried flashing AOKP, which *did* get data back, so I'm assuming this is a CM11-exclusive problem.
I really don't know how the CM11 data problem persisted even after flashing back to stock and then re-flashing CM11. What could've gone wrong? Anyways, I guess I'm sticking to AOKP for the time being.
Click to expand...
Click to collapse
Which AOKP rom you using? Is it for Kit Kat 4.4.2?
LAD2012 said:
Which AOKP rom you using? Is it for Kit Kat 4.4.2?
Click to expand...
Click to collapse
yep, latest AOKP nightly
check out this thread
http://forum.xda-developers.com/galaxy-s3/help/major-problem-s3-network-t2748246/page2
and this one too
http://forum.xda-developers.com/galaxy-s3/general/ref-imei-efs-stuff-i9300-including-t2393289
n0stalgia said:
yep, latest AOKP nightly
Click to expand...
Click to collapse
Have you got a link to the rom - any issues with Wi-Fi or 3G/Mobile Data? This CM 11 rom I have is awesome but it's a pain that the 3G/Mobile data just doesn't work at all.
LAD2012 said:
Have you got a link to the rom - any issues with Wi-Fi or 3G/Mobile Data? This CM 11 rom I have is awesome but it's a pain that the 3G/Mobile data just doesn't work at all.
Click to expand...
Click to collapse
http://forum.xda-developers.com/galaxy-s3/orig-development/rom-aokp-kitkat-i9300-t2597838
I had a problem connecting to the network with all ROMs
http://forum.xda-developers.com/galaxy-s3/help/emergency-calls-t2748393
If you look on that thread, try installing the specified modem and kernel. Hope this helps.
lukeg26 said:
I had a problem connecting to the network with all ROMs
http://forum.xda-developers.com/galaxy-s3/help/emergency-calls-t2748393
If you look on that thread, try installing the specified modem and kernel. Hope this helps.
Click to expand...
Click to collapse
Did you install the patched kernel/modem while on stock ROM or on a custom ROM?
n0stalgia said:
Did you install the patched kernel/modem while on stock ROM or on a custom ROM?
Click to expand...
Click to collapse
Got the 4.3 stock ROM from sammobile then installed the kernel and modem from TWRP recovery - haven't tried a custom ROM yet but I presume it'd work in the same way
UPDATE:
I got mobile data back by going back to stock, clean flashing AOKP (which works with mobile data), then dirty flash to CM11. Quite unorthodox, probably not the best solution, but it works!
I've tried many other suggestions, such as the "patched" modems & kernels, to no avail. Finally this works, dreams do come true