Hey guys,
I currently have CM7 flashed but for some reason the arrows on the send/receive portion of the 3G icon are not flashing. I tried flashing a different rom, wiped data/cache and it happened on that rom too. Any ideas?
Thanks!!
So are you still sending and receiving data when this happens.
Most AOSP roms don't support data arrows yet.
Sent from my Incredible 2
It was flashing before I reflashed cm7 for the kernel.
Sent from my Incredible 2 using XDA App
i flashed my stock rom back and the arrows are blinking so im assuming its a bug in cm7 or any aosp rom currently maybe with 2.3.7?
Related
Recently flashed to CM7 RC2.
Wifi connects with no issues.
Flashes Savaged Zen's lates BFS/Froyo Kernel and Wifi does not pickup any networks.
I've re-flashed CM7 several times and have confirmed Wifi connectivity but the minute I flash Savaged Zen's newest Kernel, I cannot pick up any networks.
I ususally run Sense based ROMs and havent ran AOSP rom for some time.
Does anyone have any recommendations or suggestions?
The battery life seems GREAT but I definitely need WiFi connectivity and don't seem to find anyone else having issues like this.
PS - I clear cache/Dalvik/Factory reset everytime I flash a new ROM.
Thanks in advance.
Cm7 is a GB rom correct? Don't use the Froyo kernal on a GB rom..?
Sent from my PC36100 using XDA App
Damn
you sir are a god.
me on the other hand, a total retard.
lol. that did the trick.
I'm having almost the exact same problem, except wimax doesnt work the second i flash savage.... i made sure I flashed gb, anybody know??
evo.altig said:
I'm having almost the exact same problem, except wimax doesnt work the second i flash savage.... i made sure I flashed gb, anybody know??
Click to expand...
Click to collapse
what version/nightly of cm7 are you running?
im using cm7 rc2
Thank u for helping
evo.altig said:
im using cm7 rc2
Thank u for helping
Click to expand...
Click to collapse
Download WiMAX key checker off of the market and make sure you have your WiMAX keys just an idea to start
Sent from my Evo 3D
Hello forum,
I recently switched from CM7 because I was having some issue with random resets and FCing with Maps that slow down and shut off my phone. I flashed to the New Fresh ROM to try it out. That worked fine, but I missed the pull down notification bar. I tried Salvage-Zen but got stuck in a boot-loop and then I tried Salvage. I got past the boot screen but when the Android pops up even though I click I can't go any further. Does anybody know of a possible solution?
Few suggestions: Are you wiping properly, do you have the latest recovery (amon ra or clockwork), are you flashing gapps, did you update to all the latest radios/wimax/prl?
Why don't you try to flash decks aosp rom!
http://forum.xda-developers.com/showthread.php?t=1078558
Sent from my PC36100
jjchdc said:
Hello forum,
I recently switched from CM7 because I was having some issue with random resets and FCing with Maps that slow down and shut off my phone. I flashed to the New Fresh ROM to try it out. That worked fine, but I missed the pull down notification bar. I tried Salvage-Zen but got stuck in a boot-loop and then I tried Salvage. I got past the boot screen but when the Android pops up even though I click I can't go any further. Does anybody know of a possible solution?
Click to expand...
Click to collapse
do you do a clean wipe before flashing roms or are you just installing one on top of the other. I would suggest looking for Caulkins format all zip and run it prior to flashing a rom
Same problem on friends phone just use amon RA wipe everything twice and flash and be patient with the white evo 4 g screen it may take a while there.
Sent from my PC36100 using XDA Premium App
I'm wiping completely using both Clockwork and Amon but its still a no go and I flash falls when using aosp. I'll try that Rom and report the results.
Sent from my PC36100 using XDA App
playya said:
do you do a clean wipe before flashing roms or are you just installing one on top of the other. I would suggest looking for Caulkins format all zip and run it prior to flashing a rom
Click to expand...
Click to collapse
The format all was just what I needed. Thank you very much!
I rooted my phone and my girlfriends phone at the same time using Unrevoked 3. We're even running the same rom MIUI in the latest build. My phone runs perfectly but my girlfriends phone runs on a 1x signal instead of a 3G. What should I do?
Update all your radios by switching back to a sense Rom and doing it manually or flash one of calks .zip files (Google it or search xda) should fix things
Sent from my PC36100 using xda premium
I am running cm 10, but I want to switch back to the sense 4.0 from ultimate kang bang. I had the ROM already downloaded and flashed it after the full wipe through clockwork mod. No matter what I do the phone refuses to connect to any kind of signal other than WiFi...anyone know how I can fix the signal issue????
Sent from my Incredible 2 using xda app-developers app
Whenever I have signal issues with ports I flash a stock ROM and update prl and programming.
Then I flash the new ROM.
Give it a shot.
Hey all -- wondering if anyone else has experienced this issue.
So, I flashed the firmware upgrade that nits posted along with the leaked Verizon ICS rom. I couldn't resolve the wifi/mobile data toggle issue to my satisfaction, so I figured I would go to another rom as my daily driver for the time being. However, now anytime I flash a sense-based rom, my phone reboots right after the rom loads up and goes to the lockscreen. It really seems like it is rebooting at the time the radio is trying to get a signal. I tried using different radios to see if that would resolve the issue, but no dice. I even bootloaded a pg32img of the stock rom (hboot .98, which kept me s-off but caused me to lose my recovery so I had to push that back on through fastboot), but I still can't flash any sense-based roms without the phone restarting soon after it loads and goes to the lockscreen. This includes the UKB roms and Eclipticsense. I do not experience this problem with AOSP roms, and I'm currently running CM7.2 without any issues (I can run it with the newest firmware from the leak, and even with an older GB radio).
Thoughts?
tryo0004 said:
Hey all -- wondering if anyone else has experienced this issue.
So, I flashed the firmware upgrade that nits posted along with the leaked Verizon ICS rom. I couldn't resolve the wifi/mobile data toggle issue to my satisfaction, so I figured I would go to another rom as my daily driver for the time being. However, now anytime I flash a sense-based rom, my phone reboots right after the rom loads up and goes to the lockscreen. It really seems like it is rebooting at the time the radio is trying to get a signal. I tried using different radios to see if that would resolve the issue, but no dice. I even bootloaded a pg32img of the stock rom (hboot .98, which kept me s-off but caused me to lose my recovery so I had to push that back on through fastboot), but I still can't flash any sense-based roms without the phone restarting soon after it loads and goes to the lockscreen. This includes the UKB roms and Eclipticsense. I do not experience this problem with AOSP roms, and I'm currently running CM7.2 without any issues (I can run it with the newest firmware from the leak, and even with an older GB radio).
Thoughts?
Click to expand...
Click to collapse
Have you tried formatting system?
Sent from my Goonified Paranoid Jelly Droid Incredible 2
Multiple times. I've repeatedly wiped all partitions except the SD card. I generally do this whenever flashing a new rom.
Sent from my Incredible 2 using xda app-developers app
upgrade to 0312 radio if you are on latest software will solve boot loops on sense roms
Sent from my ADR6410LVW using xda app-developers app
Aldo101t said:
upgrade to 0312 radio if you are on latest software will solve boot loops on sense roms
Sent from my ADR6410LVW using xda app-developers app
Click to expand...
Click to collapse
thank you very much for the advice. i will give that a try and report the result. really been itching to flash the new eclipticsense 3.0.
Fixed it. Big thanks!
Sent from my Incredible 2 using xda app-developers app