[EDIT] I meant GAPPs. Damnit.
Hello,
I'm at a loss for what's happening and how to fix it. My GoogleFU is failing and nothing I try seems to work.
Basically, WiFi does not work for me in CM 10.1 RC2 and it's something to do with the GAAPs. Everything is initially fine on a fresh install [edit: I don't know if it matters, but when I flash the latest milestone of AOKP WiFi never works. At the initial set up it connects but fails to authenticate over and over] and it's all going swimmingly at first. When I open the Playstore in these first few moments, it's the last version. Eventually the Playstore updates itself and that's when WiFi stops working. Nothing can connect to anything. In the Playstore I just get a 'failed to connect' message and a 'retry' button that doesn't work. The browser doesn't pull anything up and I can't get any sort of connection until I turn WiFi off and go to data.
I'm really at a loss. If it helps, I'm on the Sasktel version, but it's still the I747 [i747m in the stock ROM] which is the same as Bell/AT&T, right? So that shouldn't matter. I'm flashing the 20130301 GAAPs and even tried the 4.1.2 ones (they didn't work at all). I'm using CWMR 6.0.1.2. I can't figure out what I'm doing wrong. Any advice at all would be greatly appreciated. I don't know why I'm having so much trouble with ROMs on my S3 when it was so much easier to root than my old One V (which is still running CM 10 like a champ with 0 errors - I gave that phone to my sister).
Sorry for the long post, but this has been melting my brain.
so what all are you wiping before these flashes? i would recommend data, cache, dalvik, format /system, format /data when changing ROMs and especially when changing android versions (4.1 to 4.2, etc). If you have a micro sd card, place your ROM, gapps and a backup on there and go through the above wipe procedures.
you should also consider updating your recovery. 6.0.3.1 is the latest. you can flash this in recovery, go to Advanced and reboot recovery for this to take effect.
Related
I've rooted my phone for the first time the other day and started venturing into the custom ROM's realm, but so far all I got were dramas and failures.
I started by downloading Cyanogen 6.1.1 and 7 RC1. I thought I'll try each to see how they perform. So I copied them to the sd-card, along with the radio update that was recommended on the Cyanogen 7 RC1 thread, and rebooted to Clockswork recovery. I wiped my data and cache and went on with the ROM installation followed by the radio update (notice that I skipped the backup stage. stupid, I know).
Upon booting, I immediately noticed that I have no signal, and a force close message that says: "the process com.android.phone has stopped unexpectedly. Please try again" pops up every 2 seconds. Nothing happens when the message is dismissed, mind you, but it still comes up constantly every couple of seconds. This, along with the 'no signal' thing, rendered the phone unusable.
At this point I'm thinking that maybe my phone is just not reacting well to the non-final build of the Cyanogen 7, so I gave the stable Cyanogen 6.1.1 a go. Lo and behold, same thing happens with it also. Now panic kicks in when I realize that I have no backup, and no stock ROM to go back to.
Eventually, I downloaded the latest rooted Desire 2.2 ROM, got it into my sd-card and installed it. Thankfully, everything was working properly again. After some asking around in the Cyanogen forum, it got to my attention that the update to the radio might have caused all of this trouble, and that the installation of the stock ROM brought the previous radio version with it, which solved the problem. But when I tried to install Cyanogen again, without tinkering with the radio, same thing happened. I then tried Oxygen 2, thinking that maybe my device just doesn't like Cyanogen, but the exact same problem persisted.
Anyone have any idea what's the deal here?
Did you wipe dalvik cache after flashing the roms?
Sent from my HTC Desire using Tapatalk
I wiped the cache partition before I flashed. It didn't say 'dalvik' specificaly, just 'cache partition'. I never wiped any type of cache *after* the flashing process.
You should wipe the dalvik cache after (or just before) flashing roms.
You can find it under the advanced menu in clockworkmod recovery.
Sent from my HTC Desire using Tapatalk
Alright, tried wiping the Dalvik Cache after flashing, problem still persists.
You could try downloading another radio and trying it. Even if it's not the recommended one, an older radio works better for some people. There is no such thing as 'the best radio to use', since result may have large variations for different people (in different locations, using different phones and ROMs). Just browse the radios post and pick one
Btw, since the dalvik cache is stored at /data/dalvik-cache, wiping the /data partition implies deleting the dalvik cache
Well, since the radio that I have installed now works, and since it stays the same one after installing a different ROM, it seems to me that the radio is not the problem here. I really would like to stay away from tinkering with the radio stuff...
Bump.
This really bugs me that it wont work. I feel like I'm missing out on the biggest feature of having a rooted phone...
Hmm... I've found that if I force the phone into Airplane mode, the FC messages stop. Of course, I still have no signal.
So, the reason for the FC messages is due to the failure to connect to my mobile network. Now, why would I be able to connect to my network fine on the official Desire ROM, but not on any other ROM?
If all else fails you could always trying flashing the RUU for your phone then start from the beginning and root again if you've tried everything else.
Sent from my HTC Desire using XDA App
Ok, I'll try that.
Just a quick question. After I run the RUU and the device is unrooted, will I be able to recover my nandroid backup fully after I re-root?
So I've seen other people that have this problem but the difference is usually they get the message when opening this or that, while I get the message constantly. As is, if I force close it, it pops right back up again leaving me no time to actually do anything on my phone.
Any help would be appreciated, I have CM7 installed and this just happened after a reboot.
Did you flash the latest gapps when you flashed CM7?
Yeah, and CM7 had been working great up till this point. Now it says I have no service and I can't do much of anything.
TheUnknowing said:
Yeah, and CM7 had been working great up till this point. Now it says I have no service and I can't do much of anything.
Click to expand...
Click to collapse
Did you flash anything without wiping data? if you did you might have to wipe data. Before you do that try to fix permissions in rom manager and clear the data for the phone app. If those things dont work wipe data. If a data wipe doesnt work you have a problem with the ROM you flashed. If its a nightly you should either flash a different nightly or flash the stable.
As for the service you can try to flash a new radio. If that doesnt work i recommend going back to a sense rom updating your profile, and then your PRL. I wouldnt imagine the radio is the problem, because ROM's shouldnt normally include radio files, but you might as well try to flash the newest radio anyways. Newest radio is 2.15.00.11.19.
flashing a new radio, updating your prl, and updating your profile are about the only things you can do to help your service. updating prl and profile can only be done on sense roms through settings, because those involve sprint code, which is not made public.
Update: I'm not sure how to do most of the things you mentioned but my radio is up to date. I discovered that this problem only occurs after I reboot the phone. It flashes fine, works normally, but once I reboot it the problem starts up.
Hello,
My Droid Incredible can not connect to 3G nor can it connect to 1X. Luckily, I can still receive calls and sms. A couple of days ago, I upgraded from CM 7.0.2 or 7.0.3 to CM 7.1 RC1. A couple of hours later, I installed Synergy, wiping the cache and dalvik and data in the process. After a day of having that rom restart every 30 minutes or so, I restored the backup I had made of CM 7.1, without wiping the cache, dalvik, and data. I then noticed that I could not connect to 3G and to 1X. I thought I might just be in a dead zone, even though I have never had connectivity issues, so I didn't worry about it. Then, I noticed the same thing at my work, and anywhere I went no connectivity. I tried flashing a different kernel, Chad's incredikernel, 2.6.38.8, but that didn't work either. Any suggestions?
You need to install either liberation or the rooted leaked ota, set it up, then do *228 option 1, reboot *228 option 2. Then go back and reinstall fresh your cm7. I would fully wipe both installs, which means going to mounts and storage and wiping boot, dara, system, and cache. You have remnents of synergy on your phone. You need a real good wipe.
Thanks for the quick reply. I'm going to try that right now.
Let me know if that works. You may want to download vr superwipe.zip and keep it on your sd card to flash right before the rom, its what i use everytime. If ive helped you please hit the thanks button! Gracias
I only installed up to the root leaked ota and it works fine now. I actually think that the phone is faster with the ota than any other rom I've tried so I'm going to stay with that at least until I get home from my work.
The ota is smoking, it is what i use also.
If ive helped you, please hit the damn thanks button!
This morning I found my battery dead. When I got it to boot, it was bootlooping. I tried flashing, wiping, everything. Bottom line is if I sync to google, my phone goes into bootloop. Full data wipe in recovery does nothing, all my apps are there and work fine, flashing works fine. Tried installing twrp, same thing.
Any ideas?
Anyone got any ideas? Could this be a hardware problem?
Guess I'll try going back to stock when I get home. Unfortunately I could never get mtp to work properly.
Sounds like a bad ROM you are using.
Does it use the CM GAPPS file?
You can try flashing CyanogenMOD's latest GAPPS and i bet that would fix it.
Galaxy Nexus GSM
Tried many different ROMs, that was not the problem. Wipe didn't work, even the native factory reset. Went fully back to stock and rerooted and it seems to be fixed. Still working on restoring things.
Hi All,
Having some issues with my Galaxy Note 10.1 which I've had for quite a while now. It's rooted but with Android 5.0 stock rom and a custom kernel.
Just now (like 20mins ago) I tried to enable Adblock plus app, the app said it can't automatically change the settings - even though SuperSU was installed and had no issues with it previously. So like all things thought I'd give it a reboot that ought to clear it out. That didn't work, so tried clearing cache (Dalvik/ART/Cache), Still no joy.
I'm a s/w engineer, but not and android/bootloader expert, so I've tried to grab the dmesg and boot logs which I've attached, I've got some stuff on the internal SD (app data) which I'd like to keep, hence I'm not going for the full wipe.
Please take a look at the logs and see if you can determine how to fix this issue, my initial thoughts were there are some issues with the flash storage (bad sectors/partition table?), if I could grab the image and dd the image again I'd be OK - but I don't know much about about android boot loader/kernel etc so can't say.
Ok it has been fixed by wiping data - but I've lost my data and installed apps!
Is there anyway to find out which file/app is causing the boot loop so I can restore data, delete the offending file?
Well, I shall give a bump to this topic, with a little more info. Though probably not really useful.
First I had stock 5.1.1 deodex pre root etc ROM that, after I tried to insert a nano sim card (mine is a 601 3G model) that got stuck, it entered on a bootloop, I had to open it, take the sim card out, and it was still on a boot loop. Tried to install another image, still bootloop, tried to reinstall the original one I had, still bootloop, wiped data, worked fine.
Then almost 2 weeks later, everything worked fine, went to watch a video, the sound was mute, tried to turn it on but everything looked fine, decided to restart because it would probably fix the problem. Got a bootloop. Wiped the data, everything was fine again.
Now, a little more than 2 weeks later, seems like the wifi is not working, thought all my other devices are, guess it's the same problem, decided to restart it, and bootloop again. I'm currently trying to update my TWRP, and gonna try a different ROM, and wait to see if something like that happens, until then, I wonder what could be happening... I remembered an Asus Device that I had that had different firmware versions for 4.4 and 4.1, so if I tried to flash a 4.4 on a 4.1 firmware it wouldn't work, and for downgrade, the same problem happened, and wondered if Samsung has some difference between versions 4 and 5.
ssj4maiko Let me know if you find a more stable rom - I went back to pretty much stock, but with root as I wanted to use all the Samsung apps, but this constant random bootloops are annoying!