Database Info

Flashed CM7, now i dont have internet (mez)

Last night i flashed CM7 on my us cellular samsung mesmerize and today when i go to use anything with interent it does not work. Not the browser, not facebook. I am kinda a noob so any help to fix it would be appreciated.

super74nova said:
Last night i flashed CM7 on my us cellular samsung mesmerize and today when i go to use anything with interent it does not work. Not the browser, not facebook. I am kinda a noob so any help to fix it would be appreciated.
Click to expand...
Click to collapse
try rebooting? if that doesn't work try reflashing, maybe try a data wipe as well.
Sent from my CM7 SCH-i500

I'm currently having the same issue, talkin to the devs atm. Will get back to you.

jpaulwaite said:
I'm currently having the same issue, talkin to the devs atm. Will get back to you.
Click to expand...
Click to collapse
Thanks man. Let me know what you find. I am dying without internet. I have tried reflashing both the rom and the kernel, wiping cache and davlik, and tried fixing permissions. Nothing works

super74nova said:
Thanks man. Let me know what you find. I am dying without internet. I have tried reflashing both the rom and the kernel, wiping cache and davlik, and tried fixing permissions. Nothing works
Click to expand...
Click to collapse
did you try a data wipe? that often fixes issues like this.
Sent from my CM7 SCH-i500

sageDieu said:
did you try a data wipe? that often fixes issues like this.
Sent from my CM7 SCH-i500
Click to expand...
Click to collapse
I did, but when i do it it comes up with an error cant mount/ datadata or something to that affect. Any idea what i could do to fix that?

Um. Try going to mounts and storage, then mount everything.
Sent from my CM7 SCH-i500

This issue has been addressed with lmartin92, and I'm in the process of testing a new build of his to see if it will fix the 3g issues for some mesmerize users. As soon as I know something I'll post it.

If you're losing 3g connection, copy ect/ppp/ from Heinz57 and reboot, a complete wipe may be needed also.

KillKount said:
If you're losing 3g connection, copy ect/ppp/ from Heinz57 and reboot, a complete wipe may be needed also.
Click to expand...
Click to collapse
I just tried that. It didnt seem to work, i even flashed it multiple times.

ok kids, we got it resolved, it was a kernel issue.
You can copy the redbend_ua from any mesmerize rom into the cm7 kernel_update folder and change any references in the updater.script from "bmlwrite" to "redbend_ua"
Then enjoy gingerbread with 3g.
Of course, I'm sure lmartin92 will repost the fixed cm7 soon if you aren't savvy enough to get those instructions done.
This thread can be closed now.

jpaulwaite said:
ok kids, we got it resolved, it was a kernel issue.
You can copy the redbend_ua from any mesmerize rom into the cm7 kernel_update folder and change any references in the updater.script from "bmlwrite" to "redbend_ua"
Then enjoy gingerbread with 3g.
Of course, I'm sure lmartin92 will repost the fixed cm7 soon if you aren't savvy enough to get those instructions done.
This thread can be closed now.
Click to expand...
Click to collapse
I copied the redbend_ua from Heinz 57, went into the updater.script and replaced all blmwrite's to redbend_ua and i still got nothing. Hopefully he will post the updated version soon.

removed for sillyness

[Q] About to throw this XOOM into the wall

Hi there,
I have a UK WiFI xoom, and everything was working fine. I installed the ICS AOSP rom, and no issues.
The problem started when I updated the AOSP ICS rom, and the gapps, Now I DONT HAVE MARKET access. The loading circle just goes round and round till it says 'connection timed out - retry'. The GTALK doesnt connect either, it just says 'signing in' till it goes 'offline'.
Right now, I am on the EOS Wifi ICS rom.
Here's what I HAVE done so far to fix it based on ideas in this forum and others (trust me, I search before I post:
- Factory reset, wipe cache, dalvik before every rom install
- Installed every single ICS rom there is, with the recommended google apps
- wiped data on the google services framework
- Installed different version of gapps
- Shut down the firewall on the HOME NETWORK.
It just doesnt work anymore. It used to connect fine to the home Wifi earlier but something just went wrong somewhere and i cant track it down.
Any help would be appreciated.

you have any more info like does your xoom show you are connected to your wifi? do you have any other wireless devices and are they accessing the internet fine? are you flashing the right gapps package?

yea, Wifi is connected fine. Alternate markets like 'slideme', and browser, gmail, maps app etc work fine without problems.
I have flashed the latest gapps package as recommended by EOS rom makers (v. 10 i believe)

after installing the eos mod, did u restart before installing the gaps?

load a stock backup then reinstall your current flavor and gapps

pr1vate piles said:
after installing the eos mod, did u restart before installing the gaps?
Click to expand...
Click to collapse
No I Didn't restart.
load a stock backup then reinstall your current flavor and gapps
Unfortunately, I didnt make a backup. I am an idiot I know!

Just quickly, 10.4 is the latest Gapps to use with EOS.

TheStickMan said:
Just quickly, 10.4 is the latest Gapps to use with EOS.
Click to expand...
Click to collapse
Yes, sorry for not clarifying. 10.4 (the latest as of yesterday) is the one I used

inshadesofgrey said:
Yes, sorry for not clarifying. 10.4 (the latest as of yesterday) is the one I used
Click to expand...
Click to collapse
First, take a deep breath. It's probably something small that's causing the problem, no doubt.
Some of the EOS Nightly are more stable than others. I would recommend wingray nightly build #56 (very smooth and stable) with the 10.4 GAPPS flashed immediately afterward. First wipe cache partitions, then dalvik cache (in advanced) then flash the rom and the GAPPS, then reboot. This should work very well for you. If you feel the need to do another data wipe, do that before anything else.
IMHO, no need to flash stock images 1st. Just flash on top of your current rom.
Good luck!

ok- will try and respond with results. thanks for the patience/

okantomi said:
First, take a deep breath. It's probably something small that's causing the problem, no doubt.
Some of the EOS Nightly are more stable than others. I would recommend wingray nightly build #56 (very smooth and stable) with the 10.4 GAPPS flashed immediately afterward. First wipe cache partitions, then dalvik cache (in advanced) then flash the rom and the GAPPS, then reboot. This should work very well for you. If you feel the need to do another data wipe, do that before anything else.
IMHO, no need to flash stock images 1st. Just flash on top of your current rom.
Good luck!
Click to expand...
Click to collapse
Hi - I did the steps exactly as you said (with a full data wipe). Still getting nowhere?
Any more ideas?

Go back to stock US recovery ROM. Start again.
Also no idea how to fix it (as nothing previously worked), but the symptoms seem similar to when you haven't accepted the agreement that pops up on new google framework (?) version. Won't let you use market or gtalk.. has happened to me before.

Before flashing, try an extra wipe: wipe system (in some recoveries also called "format system" ). I have been saved by this more than once.
Tapatalking

I always wipe dalvick and cache partition. Install ROM from SD card, followed by latest Gapps and then use the fix permissions in advanced settings before rebooting. I have never had a single problem and have been using EOS Wingray nightly since release 11. I am sure the fix permissions is the key to this. No need to do a full wipe if you are on the same ROM!
Sent from my ZTE-BLADE using Tapatalk

Krypt2Nyte said:
I always wipe dalvick and cache partition. Install ROM from SD card, followed by latest Gapps and then use the fix permissions in advanced settings before rebooting. I have never had a single problem and have been using EOS Wingray nightly since release 11. I am sure the fix permissions is the key to this. No need to do a full wipe if you are on the same ROM!
Sent from my ZTE-BLADE using Tapatalk
Click to expand...
Click to collapse
i will try that now.
Also, if i should move back to stock - which rom should I go to? HC or ICS? any links would help. thx guys, for the patience.
j

You can only go back to 3.0 or whatever it is. t will update to 3.2, and then hopefully ICS.
On tablet, so can't quickly find original motorola dev website - try Googling. Here is link to post with hosted firmwares anyway..
http://forum.xda-developers.com/showthread.php?t=1049485
Also check second post there, for using fast boot to install.

inshadesofgrey said:
i will try that now.
Also, if i should move back to stock - which rom should I go to? HC or ICS? any links would help. thx guys, for the patience.
j
Click to expand...
Click to collapse
yea it didnt work. I guess i have to flash back honeycomb. Funny thing is, after I tried this - the GTALK staed working!!! just not the market. Its just hat i can't get to the user agreement page the first time we open the market.

inshadesofgrey said:
yea it didnt work. I guess i have to flash back honeycomb. Funny thing is, after I tried this - the GTALK staed working!!! just not the market. Its just hat i can't get to the user agreement page the first time we open the market.
Click to expand...
Click to collapse
Have you tried accessing the market through the browser? You will need to sign in...that may reestablish your link. I can't see why you need to go back to stock Honeycomb. It gets complicated getting cwm recovery back on (to stick).

I had a similar issue on my DHD. It turned out that your language needs to be US English.
Hope this helps

okantomi said:
Have you tried accessing the market through the browser? You will need to sign in...that may reestablish your link. I can't see why you need to go back to stock Honeycomb. It gets complicated getting cwm recovery back on (to stick).
Click to expand...
Click to collapse
this is very very strange. I can open all other google services and sign in from the browser but not the market.android.com, its just NOT opening the signin page

[Q] NewSENSE RC2 ControlPanel Issues.

I have been having issues, with my control panel ( NewSENSE CP ), I get to my Modifications tab and i try to change my mods Lockscreens or Overscroll rosie mods or system UI Settings And it right away Forcecloses on me with a quickness..... Any Suggestions help and or Solutions ? ive tried to superwipe Everything over 5 times and reinstall Rom . and it still FC's on me ....

Did you download the Rom over WiFi, Hardline, or the Network ? Did you Restore any Data ? Did you verify the MD5 sum before Flashing ?

prboy1969 said:
Did you download the Rom over WiFi, Hardline, or the Network ? Did you Restore any Data ? Did you verify the MD5 sum before Flashing ?
Click to expand...
Click to collapse
Ive Downloaded Via Wifi. On laptop. Ive also Redownloaded Via Hardline Ive Checked the MD5, Restoring Data No all Was Fresh Wiped.

Try reflashing the Rom. Only this time manually wipe everything. There's a how to link in my Sig if your on a PC.
TEAM MiK
MikROMs Since 3/13/11

Ive tired your tut and its still a no go Ive Wiped Everything x3 Fully and Manually.... Ive waited the 10 minutes to settle everything into the rom. and Still its a no go. still getting the FC In the Modifications Selections. :crying:

Have you tried fixing permissions in Recovery ?

Have you tried flashing rc1 and doing the upgrade to rc2?

prboy1969 said:
Have you tried fixing permissions in Recovery ?
Click to expand...
Click to collapse
Yes i have tried fixing permissions in Rom and Outside of rom within Recovery still it was still a no go. But i may take the shot of Downgrading to RC1 The Re upping to RC 2 I may have some chance with that. Other then that, I will keep you all posted if its a go or no go.

Ianonymous said:
Yes i have tried fixing permissions in Rom and Outside of rom within Recovery still it was still a no go. But i may take the shot of Downgrading to RC1 The Re upping to RC 2 I may have some chance with that. Other then that, I will keep you all posted if its a go or no go.
Click to expand...
Click to collapse
If RC1 to RC2 doesn't work I think you're out of luck, unless drob releases an update

bilgerryan said:
If RC1 to RC2 doesn't work I think you're out of luck, unless drob releases an update
Click to expand...
Click to collapse
Well, Ive tried the RC1 going to RC2, IT was a no go. It told me it could not even Download. So im thinking an update maybe. it was a good run while it lasted hopefully i can get some news about it to see where i stand with newsence.

Ianonymous said:
Well, Ive tried the RC1 going to RC2, IT was a no go. It told me it could not even Download. So im thinking an update maybe. it was a good run while it lasted hopefully i can get some news about it to see where i stand with newsence.
Click to expand...
Click to collapse
Sorry to hear that, it is a GREAT ROM. Although there is not a lot of difference between RC1 & RC2, if you can live without some of the mods, RC1 is still AMAZING!

Yes RC1 is Amazing, so is RC2 . Hmmm....What Recovery are you using ? Still trying to figure out why your having this issue.
EDIT: just saw your post on the thread, and read about it maybe being a server issue

I'm having this same issue; I've also done everything suggested in this thread but it keeps force closing on any of the Modifications options. I guess it's not a huge deal because I don't even know what I'm really missing but it would be nice to have some more stuff to tinker with. Other than that, love the rom!!!

klund29078 said:
I'm having this same issue; I've also done everything suggested in this thread but it keeps force closing on any of the Modifications options. I guess it's not a huge deal because I don't even know what I'm really missing but it would be nice to have some more stuff to tinker with. Other than that, love the rom!!!
Click to expand...
Click to collapse
It's a server issue... tommytomatoe was hosting them and I'm guessing they got moved or something.

bilgerryan said:
It's a server issue... tommytomatoe was hosting them and I'm guessing they got moved or something.
Click to expand...
Click to collapse
Well somebody needs to get it fixed. Like right damn now.
Jussssst foolin'. It's all good. Thanks for the clarification.

klund29078 said:
Well somebody needs to get it fixed. Like right damn now.
Jussssst foolin'. It's all good. Thanks for the clarification.
Click to expand...
Click to collapse
Get ahold of Dread7us if you really want it fixed.. He was gonna check on it and probably forgot.

bilgerryan said:
Get ahold of Dread7us if you really want it fixed.. He was gonna check on it and probably forgot.
Click to expand...
Click to collapse
Nah it's not a huge deal. Like I said, I don't even know what I'm missing

[Q] Unable to Enable Wifi in Cyanogenmod 10

I have the 01/20/2013 nightly build currently installed and can't seem to enable wifi. Have looked up any info from Google and can't seem to find much. Any suggestions?

The same happened for me and if you look around you will probably see a few more comments about the same thing. If you go back to the 1/13 nightly it should work fine.

Try clearing cache and dalvik and then reflashing the rom. Worked for me.

Jevid said:
The same happened for me and if you look around you will probably see a few more comments about the same thing. If you go back to the 1/13 nightly it should work fine.
Click to expand...
Click to collapse
I did this and it works perfect. Thanks.

For the latest nightly, flash boot.img then reinstall the zip. The same thing happened to me and that worked fine.

[Q] Can't install any 4.2 ROM

I was hoping to try out one of the 4.2 builds tonight, but every time I try to flash one through TWRP it just says "Failed"; I've tried CM10.1 and Eclipse ROM and they both had the same result. Also tried redownloading ROMs and re-copying them to my SD card, still no change. Can anyone tell me what I'm doing wrong here? I've never had a problem flashing any ROM before.

Devilicus said:
I was hoping to try out one of the 4.2 builds tonight, but every time I try to flash one through TWRP it just says "Failed"; I've tried CM10.1 and Eclipse ROM and they both had the same result. Also tried redownloading ROMs and re-copying them to my SD card, still no change. Can anyone tell me what I'm doing wrong here? I've never had a problem flashing any ROM before.
Click to expand...
Click to collapse
What version of TWRP are you running?
If you haven't done it lately, I would suggest updating your twrp to the latest and trying again.

I'm running the newest TWRP (I think), version 2.4.1.0

Devilicus said:
I'm running the newest TWRP (I think), version 2.4.1.0
Click to expand...
Click to collapse
Weird. I am on that same version and have been flashing 4.2 roms for the last few weeks without any issues.
A few things I would try:
-Double check the md5 of the rom you are flashing
-Make sure it is a d2vzw rom
-Wipe caches, delete user data and wipe system
-Put the rom on the internal sdcard before flashing.
Other than that, I got nothing

Relentless D said:
Weird. I am on that same version and have been flashing 4.2 roms for the last few weeks without any issues.
A few things I would try:
-Double check the md5 of the rom you are flashing
-Make sure it is a d2vzw rom
-Wipe caches, delete user data and wipe system
-Put the rom on the internal sdcard before flashing.
Other than that, I got nothing
Click to expand...
Click to collapse
Damn, yeah I can't figure it out; all the ones I've tried were Verizon ones, made sure to wipe everything as usual, tried putting it on the internal SD card and the external, won't work on either one. Very frustrating. But thanks for the help anyway

Ok, I think I figured out the problem (won't be sure until I try it), but I think what happened is I edited my build.prop to the Sprint GS3 to get Google Wallet to work, forgot to change it back, and updated TWRP (which installed the Sprint version, not Verizon), and that's why the flashes are failing. So if any other people are having the same problem, that might be why. Yes I'm an idiot lol. Hopefully this fixes it

Try carbon ROM.
First to work for me.
Sent from my SCH-I535 using xda app-developers app

Devilicus said:
Ok, I think I figured out the problem (won't be sure until I try it), but I think what happened is I edited my build.prop to the Sprint GS3 to get Google Wallet to work, forgot to change it back, and updated TWRP (which installed the Sprint version, not Verizon), and that's why the flashes are failing. So if any other people are having the same problem, that might be why. Yes I'm an idiot lol. Hopefully this fixes it
Click to expand...
Click to collapse
What baseband [modem] do you have installed? ...and some more info if build prop wasn't the issue. Would also be interested if, "but I think what happened is I edited my build.prop", was the issue and you fixed it. Let us know. Goodluck

JohnAreBee said:
What baseband [modem] do you have installed? ...and some more info if build prop wasn't the issue. Would also be interested if, "but I think what happened is I edited my build.prop", was the issue and you fixed it. Let us know. Goodluck
Click to expand...
Click to collapse
Yeah it turns out that was the problem. I edited my build.prop to match the Sprint GS3, so I could download Google Wallet from the Play Store and use it. I just never bothered to change the build.prop back. And when I updated TWRP through GooManager, it assumed I had a Sprint GS3 and installed the wrong recovery. When I flashed the correct Verizon version of TWRP everything worked fine. Thanks for the suggestions everyone

Devilicus said:
Yeah it turns out that was the problem. I edited my build.prop to match the Sprint GS3, so I could download Google Wallet from the Play Store and use it. I just never bothered to change the build.prop back. And when I updated TWRP through GooManager, it assumed I had a Sprint GS3 and installed the wrong recovery. When I flashed the correct Verizon version of TWRP everything worked fine. Thanks for the suggestions everyone
Click to expand...
Click to collapse
Good call. Might be worth mentioning over in the wallet thread. It could save someone the headache you just experienced. Congrats on getting it working.
Sent from my SCH-I535 using Tapatalk 2