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.
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?
I lost my backup of my original factory ROM, I tried the RC ICS ROM and it did not work. I had cyanogenmod 7.1 alpha running but now it is very unstable. I have a series problem where the phone options screen keeps randomly popping up, without me pressing the top power button. I would now like to revert back to the stock Sense 3.0 ROM that shipped with the Sensation. If anyone can help me I would so grateful as this is a super annoying problem to deal with.
I have Revolution, Clockmod Recovery and have tried multiple ROM's and find they all have some sort of bug
Another thing, the battery life has deteriorated to the point that I can not even get more than a half day of standby with a quarter of usage.
Please explain how I can get the factory ROM back on the phone with no bugs or issues. Thanks.
have you tried any other ICS ROM? majority of them are stock with minor tweaks,
insertcoin 4.3.1 is pretty stable
Click Me!
I know you'll probably do so already, but make sure you do a full wipe before flashing the stock ROM
I tried the RCmix ICS but when I installed it, all that happened was it kept popping up a dialog box non stop and was unable to use it so I reverted back to the Cyanogenmod 7.1
Can you please let me know where I can get this ROM, I will give it a shot.
RUU Roms can be found in thread
ttp://forum.xda-developers.com/showthread.php?t=1074559
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...
Hello, all.
I have a T-Mobile Blaze 4G with rooted stock ROM (Gingerbread), flashed radio version T989UVMC6, manually debloated and dewizzed. I'm running Halo launcher and Busybox Free version 9.6.
Since almost the first day I've had this phone, it would occasionally force close the phone process, usually when hanging up the phone with the Bluetooth radio on and paired with an earpiece. It happened bone stock, rooted, after I changed the modem, whenever. It seemed to happen less often after I changed the modem. The process always starts back up, but the Bluetooth device connection and system sound controls are wonky (unusable) until the phone is rebooted.
The only thing that seems to stop it is running Zepplinrox's V6 Supercharger script. That, however, occasionally freezes the entire system when trying to open certain apps, requiring a reboot. I've run earch after search on this subject, and nobody else seems to have this problem. The only thing I haven't tried is wiping the whole thing and flashing a custom ICS or JB ROM. I tried Dark Knight ver. 8 and hated it pretty much instantly.
I have two questions. Number one; Will flashing a custom ROM fix this situation? I figure that this must be a problem with the crappy stock Samsung ROM. Number two; Which ROM is fully functional and stable? I'd really like to keep this phone dependable. I don't care about the latest and greatest funky cool features that are hit-or-miss at best. I just need dependable, fast and functional.
Since you have been having issues for a while, I would suggest starting fresh. With a few runs of black hole wipe from cwm. Add a run of the gremlin remover for extra cleanliness. Then a flash of the latest ICS rooted stock rom and kernel, for reliability.
Black hole wipe. http://forum.xda-developers.com/showthread.php?t=1721057
Gremlin remover, FSC http://forum.xda-developers.com/showthread.php?t=2218713
Uvmb1 ics ROM http://forum.xda-developers.com/showthread.php?t=2329081
Romman0 said:
Since you have been having issues for a while, I would suggest starting fresh. With a few runs of black hole wipe from cwm. Add a run of the gremlin remover for extra cleanliness. Then a flash of the latest ICS rooted stock rom and kernel, for reliability.
Black hole wipe. http://forum.xda-developers.com/showthread.php?t=1721057
Gremlin remover, FSC http://forum.xda-developers.com/showthread.php?t=2218713
Uvmb1 ics ROM http://forum.xda-developers.com/showthread.php?t=2329081
Click to expand...
Click to collapse
I'll definitely go for the rooted version! Does it matter what order in which the ROM and the kernel are flashed? Also, I take it from the name of the download link that I'll have to go through the process of de-bloating this thing again. S'okay, I actually enjoy that part, but I don't want to screw it up since I've not messed with anything newer than GB. Is there a good guide somewhere on the forum for apps that can be dumped safely? I know there was one for GB stock root.
Thanks for the response.
ionizd said:
I'll definitely go for the rooted version! Does it matter what order in which the ROM and the kernel are flashed? Also, I take it from the name of the download link that I'll have to go through the process of de-bloating this thing again. S'okay, I actually enjoy that part, but I don't want to screw it up since I've not messed with anything newer than GB. Is there a good guide somewhere on the forum for apps that can be dumped safely? I know there was one for GB stock root.
Thanks for the response.
Click to expand...
Click to collapse
Flash the ROM then the kernel, rewipe cache and davlik, then profit.
The most recent ICS debloating thread. http://forum.xda-developers.com/showthread.php?t=2183726&highlight=debloat
Romman0 said:
Flash the ROM then the kernel, rewipe cache and davlik, then profit.
The most recent ICS debloating thread. http://forum.xda-developers.com/showthread.php?t=2183726&highlight=debloat
Click to expand...
Click to collapse
A few more silly questions; Do I need GAPPS or is that just for CM? Aren't the CM 10 ICS nightlies fairly stable and relatively bug-free? I use CM7 on my Nook color and it's...okay... Just a few little annoying things pop up with that. To be honest, I like the idea of starting with a clean slate and adding stuff I like rather than pulling stuff out of the Samsung stock ROM, but the issues I've had with the Nook and CM7 have sort of scared me off. Your opinions?
ionizd said:
A few more silly questions; Do I need GAPPS or is that just for CM? Aren't the CM 10 ICS nightlies fairly stable and relatively bug-free? I use CM7 on my Nook color and it's...okay... Just a few little annoying things pop up with that. To be honest, I like the idea of starting with a clean slate and adding stuff I like rather than pulling stuff out of the Samsung stock ROM, but the issues I've had with the Nook and CM7 have sort of scared me off. Your opinions?
Click to expand...
Click to collapse
All the AOSP ROMs for the Blaze needs GAPPs. And yes. The latest CM10 nightly is stable. And you said CM10 ICS? CM9 is ICS and CM10 is Jellybean.
ionizd said:
A few more silly questions; Do I need GAPPS or is that just for CM? Aren't the CM 10 ICS nightlies fairly stable and relatively bug-free? I use CM7 on my Nook color and it's...okay... Just a few little annoying things pop up with that. To be honest, I like the idea of starting with a clean slate and adding stuff I like rather than pulling stuff out of the Samsung stock ROM, but the issues I've had with the Nook and CM7 have sort of scared me off. Your opinions?
Click to expand...
Click to collapse
The stock roms don't require gapps, but like Wolf said the cm10 jb variants do.
If your willing to use cm10 it is very stable. Just use the latest CM10 nightly and not the old stable version.
Here http://forum.xda-developers.com/showthread.php?t=1922935
The jb gapps 20121011 http://goo.im/gapps/gapps-jb-20121011-signed.zip
xWolf13 said:
All the AOSP ROMs for the Blaze needs GAPPs. And yes. The latest CM10 nightly is stable. And you said CM10 ICS? CM9 is ICS and CM10 is Jellybean.
Click to expand...
Click to collapse
Of course. I get a bit confused ever since people started talking about 10.1.
Okay, I went ahead and installed the stock rooted ROM with the stock kernel. Went through the debloating process (mostly, there are some apps that I'm not sure I can do without so they stay for now), and did some customizing. I'm seeing a bit more battery drain. Is this an issue with ICS or do I need to try another kernel or supercharge the phone? I also have this crazy issue with ROM Manager ver. 5.5.3.0. It tells me that there is an updated version of Clockworkmod Recovery, but it freezes when I try to flash from ROM Manager. Also, ROM Manager freezes when I try to reboot into Clockworkmod Recovery. Maybe I need to test a bit more before I mess with it any more.
**EDIT** Well, it looks as if my CWM recovery installation is corrupted. Can I reflash it without messing up my current ROM?
ionizd said:
Okay, I went ahead and installed the stock rooted ROM with the stock kernel. Went through the debloating process (mostly, there are some apps that I'm not sure I can do without so they stay for now), and did some customizing. I'm seeing a bit more battery drain. Is this an issue with ICS or do I need to try another kernel or supercharge the phone? I also have this crazy issue with ROM Manager ver. 5.5.3.0. It tells me that there is an updated version of Clockworkmod Recovery, but it freezes when I try to flash from ROM Manager. Also, ROM Manager freezes when I try to reboot into Clockworkmod Recovery. Maybe I need to test a bit more before I mess with it any more.
**EDIT** Well, it looks as if my CWM recovery installation is corrupted. Can I reflash it without messing up my current ROM?
Click to expand...
Click to collapse
Yes, with Odin, in the Dev forum
BTW, stay away from ROM Manager with our device. I've softbricked so many times because of it, it's ridiculous
jparnell8839 said:
Yes, with Odin, in the Dev forum
BTW, stay away from ROM Manager with our device. I've softbricked so many times because of it, it's ridiculous
Click to expand...
Click to collapse
Used this method http://forum.xda-developers.com/showthread.php?t=2011585, it worked well. Still have the battery drain issue, though. : /
ionizd said:
Used this method http://forum.xda-developers.com/showthread.php?t=2011585, it worked well. Still have the battery drain issue, though. : /
Click to expand...
Click to collapse
Since you have it setup, except for battery life. I would make a backup, then try a mod one at a time and see if any help. Also check the battery stats to see if anything of is seen. ICS will use more juice than GB, generally.
I would suggest Nos/direct injection, supercharger, or cross breeder. I would use one and see, then restore and try another.
http://forum.xda-developers.com/forumdisplay.php?f=565
Some time later...
I've been using the stock rooted ICS ROM since my last post, debloated and dewizzed of course, with Holo Launcher and T989UVMC6 baseband version flashed. Just over a month has passed, and I have good news!
I FREAKING LOVE THIS PHONE!!!
All of the force close and freezing issues have vanished, the phone's battery lasts almost as long as it did on GB, it's WAY more user friendly, and the phone is as fast as it ever was.
The bad news is that my wife got a GS4 and I lust after it now. : /
Thanks to everyone for their help!