Related
I wish I had known before flashing CM7 that many have had problems with the gps. I certainly do. I tried using my nandroid backup to go back to the Froyo ROM I had flashed from AddictiveTips, but backup and restore on ClockworkMod just leaves me with a blank screen. I've seen some tips on fixing gps, but most involving going back to a sense ROM and starting over. I'm not a computer whiz and some suggestions are hard to follow. I tried one involving Fast Reboot and Faster Fix, but it didn't work. Since ClockworkMod's restore won't work, I have to either wait for the CM7 gps problem to be fixed later or try re-installing the Froyo ROM from the SD card (which may or may not work). The gps with Froyo worked great. Any suggestions?
Nandroid backup didn't work?
And what problems are you having with gapps?
Me myself have problems in CM7 as well -> the gapps cannot be installed (well, CWM didn't mention any error when installing) but after boot up no gapps is there, after tons of research here and no solution too, and I rolled back to froyo.
Barfaroo said:
I wish I had known before flashing CM7 that many have had problems with the gps. I certainly do. I tried using my nandroid backup to go back to the Froyo ROM I had flashed from AddictiveTips, but backup and restore on ClockworkMod just leaves me with a blank screen. I've seen some tips on fixing gps, but most involving going back to a sense ROM and starting over. I'm not a computer whiz and some suggestions are hard to follow. I tried one involving Fast Reboot and Faster Fix, but it didn't work. Since ClockworkMod's restore won't work, I have to either wait for the CM7 gps problem to be fixed later or try re-installing the Froyo ROM from the SD card (which may or may not work). The gps with Froyo worked great. Any suggestions?
Click to expand...
Click to collapse
CM7 working fine on my HD2. I'm running it from my SD though because I don't want to root.
From what I understand the GPS will not be fixed by a cm update its got something to do with the hardware you have to do http://forum.xda-developers.com/showpost.php?p=11853529&postcount=2085 this to fix it. After I did the gpsclr fix mine has worked flawlessly. Also I don't think its only cm roms that have this issue.
Sent from my PC36100 using XDA Premium App
ah i mistook gps for gapps. my mistake... lol
Odd... CM7 works perfectly on my Motorola Droid and Nook Color and I've also never had a GPS problem (even on older nightlies). What make and model is your phone? And are you running off a CM7 nightly (if so what build?) or an RC (the latest is RC4 as far as I know)?
Gps worked perfectly using Froyo (rooted, ROM from AddictiveTips). I have an HTC Desire (CDMA) from US Celular. No, I'm not running off nightlies. I installed CM7 RC4.
The fix suggested above sounds like I would have to first flash a sense ROM and then come back to CM7. Other than giving me extra space for apps, it isn't worth it. I could get by with Froyo since everything worked with it. With CM7, the gps doesn't work at all. Maps keeps searching for satellites and never finds them. I really miss not having voice directions.
Barfaroo said:
I wish I had known before flashing CM7 that many have had problems with the gps. I certainly do. I tried using my nandroid backup to go back to the Froyo ROM I had flashed from AddictiveTips, but backup and restore on ClockworkMod just leaves me with a blank screen. I've seen some tips on fixing gps, but most involving going back to a sense ROM and starting over. I'm not a computer whiz and some suggestions are hard to follow. I tried one involving Fast Reboot and Faster Fix, but it didn't work. Since ClockworkMod's restore won't work, I have to either wait for the CM7 gps problem to be fixed later or try re-installing the Froyo ROM from the SD card (which may or may not work). The gps with Froyo worked great. Any suggestions?
Click to expand...
Click to collapse
all you need to do>
get a fresh rom myns or any that you like in reality it doesnt have to be sense if you just want to get away from cm7 altogether
but then boot into cm7,
plug it into your computer
load the new rom onto your phone
boot into recovery
then install the new rom.
sound good?
I appreciate the suggestions, but I decided to go back to Froyo and my gps is working again! Unfortunately, Clockworkmod won't let me re-install any backups, and I have no idea why. All I get is a blank screen. Fortunately, I can install from the SD card, which I did to get Froyo back. Since nandroid backups don't seem to work, I have to setup my phone from scratch everytime I make a ROM change.
So guys since we have the choice which are u doing
unroot to stock gingerbread
flash to stock gingerbread
wait for the dev gingerbread
I'm getting ready to do all of the above...because I'm a crackflasher...and I have to try everything available, lol.]
Stuck on vacation
Maybe there will be a good rom worth upgrading to by the time I get back, but the baseband seems to be the biggest advantge. I'll have to do both.
I run Cyanogenmod, I'll just stick with that. Here soon they'll incorporate everything useful from it.
Well, nevermind...I restored stock, stock recovery, unrooted, tried to update, but found out that my phone is a 999DWP...so reflashed cwm, rerooted, and back to my cm7 nandroid.
Guess the G2x community isn't for a good pole.
IM definitely waiting on the devs to play with it.
Did anybody get the back to the future reference?
Well I ordered a G2X the other day and finally I received it. It came with Gingerbread 2.3.3 from the factory. (worked flawlessly) Keep reading.
After a couple days I wanted to try out CM7 on it. So, I rooted the phone by using NVflash and doing all that good stuff, then I flashed the phone with (Gingerbread OTA 2.3.3 Rooted flashable zip v1.0.0) I couldn't get root with SuperOneClick so that was my only option. Well I got root and that's when the fun started.
I installed CM7 on it, seemed to run fine, looked fine. But simple me, I wanted to go back to Plane jane 2.3.3 So, I did all the usual stuff (backing up, wiping data, formatting caches), then I ran OneClickRecoveryFlasher...and restored the phone with LG-P999-V10f.zip (supposedly a stock flash for 2.2.2)
well it all seemed to work fine apon finishing. It booted fine, ran ok. However now I have some really bad problems. The major one is that my wifi doesn't work worth a damn now, the connection is highly intermittent. I can't use the market to download apps because it dies out often, along with anything else network related. (browsing works 5% of the time) You catch my drift. My other android phones have no trouble with anything. Now here where it gets weird, I supposedly restored my phone back to stock. However, the phone reports a proper android version 2.2.2 which is what I flashed it to. However it shows kernel 2.6.32.9 Baseband is July 15th 2011. When I use LG's phone update tool it says I am running V21E which is Gingerbread 2.3.3 ...but that's not true because it is actually 2.2.2
I have no clue what to do, I am stuck. I just want to either have a stock G2X running either 2.2.2 or 2.3.3
beast6228 said:
Well I ordered a G2X the other day and finally I received it. It came with Gingerbread 2.3.3 from the factory. (worked flawlessly) Keep reading.
After a couple days I wanted to try out CM7 on it. So, I rooted the phone by using NVflash and doing all that good stuff, then I flashed the phone with (Gingerbread OTA 2.3.3 Rooted flashable zip v1.0.0) I couldn't get root with SuperOneClick so that was my only option. Well I got root and that's when the fun started.
I installed CM7 on it, seemed to run fine, looked fine. But simple me, I wanted to go back to Plane jane 2.3.3 So, I did all the usual stuff (backing up, wiping data, formatting caches), then I ran OneClickRecoveryFlasher...and restored the phone with LG-P999-V10f.zip (supposedly a stock flash for 2.2.2)
well it all seemed to work fine apon finishing. It booted fine, ran ok. However now I have some really bad problems. The major one is that my wifi doesn't work worth a damn now, the connection is highly intermittent. I can't use the market to download apps because it dies out often, along with anything else network related. (browsing works 5% of the time) You catch my drift. My other android phones have no trouble with anything. Now here where it gets weird, I supposedly restored my phone back to stock. However, the phone reports a proper android version 2.2.2 which is what I flashed it to. However it shows kernel 2.6.32.9 Baseband is July 15th 2011. When I use LG's phone update tool it says I am running V21E which is Gingerbread 2.3.3 ...but that's not true because it is actually 2.2.2
I have no clue what to do, I am stuck. I just want to either have a stock G2X running either 2.2.2 or 2.3.3
Click to expand...
Click to collapse
You are probably going to have use Xboarders ROM then flash the unroot.zip he has in this thread http://forum.xda-developers.com/showthread.php?t=1158513.
See if that works to get you back to 2.3.3 completely stock.
It says that because it checks the baseband to see how recent it was, that's why it thinks you're on v21e.
As of now, there's no way to flash back to the old baseband, since people don't include the baseband in their ROMs, as that can cause a whole host of problems. The solution is to do exactly what tidewaterns said, that just gives you a little extra background info.
I am going to give this a try and see what happens, I will post results.
Well I tried the slimmed down version of Xboarders's rom and it seems to be working well so far. I originally installed his Stock OTA rom and that's when I started having problems. Oh well. thanks guys for all the help.
Crash course about root and roms: Superoneclick roots the rom you have in place. Flashing xboarders rom didn't "give you root" for the other roms you flashed, it is simply one rom out of many that is pre-rooted by the dev who packaged it up. When you flash it you have a rom that is rooted. If you had flashed CM7 (another rom that provides root access to its system files) then you'd have had a different rom that was pre-rooted by its dev.
Are you catching what I'm saying? Flashing xboarders rom didn't "give you root" any more than CM7 "gave you root." Root is built in to those roms.
If you want to restore to an unrooted stock rom browse the threads in the development section. There are a couple of stock nandroid backups posted that you can restore via clockworkmod recovery and then you'll have a stock unrooted rom. You can even do that and still have clockworkmod recovery in case you want to flash a different rom to your phone again.
And PLEASE remember when flashing from one rom to a different rom, WIPE WIPE WIPE data, cache, dalvik cache, then flash rom, then fix permissions, then reboot. This will save you SO MANY headaches.
G2X CM7
I learned something new Thanks for the info. And yes, this last time when I installed, I wiped and formatted just about everything I could possibly do, including fix permissions..seemed to do the trick.
beast6228 said:
I learned something new Thanks for the info. And yes, this last time when I installed, I wiped and formatted just about everything I could possibly do, including fix permissions..seemed to do the trick.
Click to expand...
Click to collapse
Sweet! If you're simply updating to a newer version of the same rom you can probably get away with just wiping cache and dalvik cache and then flashing. Its just when you switch to a totally different rom that you need to do a full wipe. Gives you a clean slate to start with.
G2X CM7
I'm curious about one thing though. What would I accomplish by using Nandroid and flashing a bin? I see there is a BIN_LGP999AT-01-V10f-310-260-MAR-27-2011+0.zip file that is available for this phone, although I have no clue on how to install Nandroid. Anyways, wouldn't flashing a BIN be the ultimate way to restore the G2X?
so my sgs4g was rooted and got on gb with the gb starter pack thread, after which i jumped around between a few roms and am currently running octaneGB.
however, it has always had stability problems, and i can't figure out why. possibly because i messed up bootloaders? i'm pretty sure it can't be the fault of the roms i flashed.
from here, all I want is a stable phone.
can i wipe the phone as it is and then use the oneclick heimdall SMS kj6? would this put me on rooted GB with CWM and good bootloaders? could i simply cwm flash a rom like valhalla after that?
any advice would be appreciated, thanks!
nvertigo said:
so my sgs4g was rooted and got on gb with the gb starter pack thread, after which i jumped around between a few roms and am currently running octaneGB.
however, it has always had stability problems, and i can't figure out why. possibly because i messed up bootloaders? i'm pretty sure it can't be the fault of the roms i flashed.
from here, all I want is a stable phone.
can i wipe the phone as it is and then use the oneclick heimdall SMS kj6? would this put me on rooted GB with CWM and good bootloaders? could i simply cwm flash a rom like valhalla after that?
any advice would be appreciated, thanks!
Click to expand...
Click to collapse
Yes, you can use the one-click to put KJ6 on there then flash a different ROM via CWM.
Personally I've had the best experience with Valhalla ROMs. Last night I just flashed RAVERX3X latest Valhalla Black build. Its low profile so it's quick and responsive, and even better, not a single instability issue.
Sent from my SGH-T959V using XDA App
thanks for the advice guys!
I did the first flash step, which worked successfully and rebooted my phone. then i tried to flash the bootloaders that came with it, but uploading PIT 1/10 failed, and it froze trying to end session. i pulled the battery and the phone seemed bricked, but i connected the cable and oneclick said it was connected (no download mode screen, no lights at all). so i did the initial one-click flash and let it reboot again, then flashed valhalla black.
nothing SEEMS to be wrong, but i'm a little scared. can anyone weigh in on what happened?
You're ok. I can't explain what happened but people have reported similar issues, nothing on the screen but it can be seen in ODIN, and were able to recover (as you did) just fine.
Sent from my SGH-T959V using XDA App
This section of XDA is small, but good in terms of quality.
I just flashed Raver's Cyanogenmod/Valhalla hybrid and it is smooth and stable.
One-Click...
At the beginning of the week, I still had Froyo on my device.
I used Bryan's one-click (SMS-KJ6-beta2d_Stock-Rom_with_Bootloaders-One-Click.jar)...
(I had a scare, too... which involved the so-called "Rainbow screen" -- but FB suggested I run the one-click, again and also to do the Bootloaders -- and everything turned out ok).
But, I needed to get CWM 5 (and, that particular one-click had CWM 3.0.2.8x)
So, I flashed an update of Bryan's kernel (sms-T959V-KJ6-v0.1.1-rc1-unsigned-update.zip)
And, because I was feeling overjoyed at all the goodness that I'd seen so far, I flashed RaverX3X's rc3.zip (from Team Acid's Source Forge site)...
And, life is really, really, really... good.
yep
+1 Valhalla black edition! Installed today and love love love.
ok... my phone is now crashing and rebooting all over the place after flashing valhalla black. it seemed fine for the first hour. should i try the one-click again? or did i not wait 10 minutes after flashing the rom, maybe?
anyone know what could be the problem?
thanks in advance!
nvertigo said:
ok... my phone is now crashing and rebooting all over the place after flashing valhalla black. it seemed fine for the first hour. should i try the one-click again? or did i not wait 10 minutes after flashing the rom, maybe?
anyone know what could be the problem?
thanks in advance!
Click to expand...
Click to collapse
Not sure about the crashing but I experienced reboots because of the kernel Valhalla Black uses. There are fixes out there for that part of the problem but what you should really is perform a factory data reset, do the one to get a ROM with CWM on it, then use CWM to install Valhalla Black per the instructions on the page for it. I've a feeling you'll be much more stable after that.
As for the 10 minutes, that's basically to allow your phone to rebuild the Davlik cache (cache with optimizations for your apps). Definitely let it sit while it does that just to be safe.
thanks yet again. will try this asap!
can i assume that my bootloaders are correct after the weird issues from the last page? you mentioned that it happened to several people, but it still bothers me that technically it never got past 1/10 uploading PIT file :x
also, regarding the problems with the kernel, can anyone point me to a kernel that works with valhalla final and is known to be fully stable? i want to try to do everything to get the phone usable.
nvertigo said:
thanks yet again. will try this asap!
can i assume that my bootloaders are correct after the weird issues from the last page? you mentioned that it happened to several people, but it still bothers me that technically it never got past 1/10 uploading PIT file :x
also, regarding the problems with the kernel, can anyone point me to a kernel that works with valhalla final and is known to be fully stable? i want to try to do everything to get the phone usable.
Click to expand...
Click to collapse
If it was fully booting and you weren't getting the "rainbow" screen, then your boot loaders are fine. If in doubt, go check out bhundven's one-clicks, and run one of them - twice. The first time it doesn't let you check the boot loader box but the 2nd time it does.
Valhalla Final comes with bundven's beta 2c kernel. I believe people are running that without issue. Keep in mind Valhalla Final and Valhalla Black are two different ROMs with two different kernels.
I did a one-click back to stock (factory reset, cache wipes, etc.) & am running bhundven's latest beta kernel with no problems (thus far).
So I went back to stock froyo and did a complete wipe of everything, even my sd cards. then I plugged into kies mini and updated to gingerbread, and about every time my phone went into standby mode after maybe 10 minutes it would do a soft reboot. I thought it might just be a problem with the stock rom, so I rooted and got a custom kernel, and I installed many different stock based gingerbread roms, all with the same effect. then, I tried cm7 and had NO PROBLEM with the reboots. also, I have no problems on any froyo roms or any aosp based roms. thanks for any help with this
Try using the one click to stock or the updated odin packages. Follow their instructions to the letter....
http://forum.xda-developers.com/showthread.php?t=1610374
That didn't work either...
Sent from my phone
Reboots
I was running MIUI on my phone and had problems and took it to the local ATT repair shop and of course their solution was to clear out the phone and revert back to stock Gingerbread UCLB. It seemed to run well for awhile, but after about two weeks I started having random and multiple reboots too. I then odin'ed the rooted stock gingerbread (I believe posted by Entrophy) and loaded the RemICS 1.2a Rom. It seems much faster and smoother than the stock rom. We will see how it lasts. Does anyone seem to have problems with loaded Roms seeming to deteriorate after awhile? It seems like on both my Infuse and a Captivate that I have, the performance and stability seems to go bad over time...