Database Info

[Q] I regret flashing CM7

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.

Can't get to CWM Recovery after Root

Just rooted my Att Inspire 4g using the ace hack. Worked great. installed the Virtuous Unity Rom 1.29. Worked for a week then started acting buggy. Black spots on the bottom left of the screen (only on main screen, not any apps). Tried updating through Rom manager and HBOOT and cant get into CWM either way. Tried loading the PD98IMG.zip onto the sd, booting into hboot, installing update and rebooting. Removed PD98IMG.zip. No go. Boots to white screen with green HTC goes black then back to white screen ---> then into the normal rom. Any ideas?

maybe try reflashing cwm from rom manager again?

Tried. No luck. I just unrooted and returned to stock. The black spots are gone now. I really loved the rom but it just became laggy and strangely unstable after a week. oh well, back to stock i guess...

Why not just load a different ROM?I'm running the honeysense HD and I love it. very good battery life. my best charge is 1 day 2 hrs. no problems with it what so ever
Sent from my Inspire 4G using XDA Premium App

Interesting issue

Hey all.
I like to flash my phone. A lot.
I flashed the cm10 build before wifi was fixed. Updated that when they fixed wifi.
Later that week I needed a working camera. So I flashed (without fxzing back to gb ) scv7 in the cm recovery. This was the version that is based on the new leak.
I have since fxz'd back to gb 3 times. The first time was because of oddness I was experiencing, such as no car dock, wifi acting odd.
The second fxz was the result of trying to install my own build of cm9. It went past the bootloader but the screen stayed blank.
I just had to fxz again last night. I tried to reinstall cm10. It just sat on the boot animation for 25 minutes. I remember it taking a bit to boot up the first time previously, but more like 10-15.
Anyone have any thoughts? I'm sitting on 2.3.6 for the moment, I would really like to get back on cm10 but I'm not sure what might be going on.
Thanks.
Luke
Edit: cardock still not working in stock unrooted 2.3.6
Sent from my MB865 using xda premium

galamdring said:
Hey all.
I like to flash my phone. A lot.
I flashed the cm10 build before wifi was fixed. Updated that when they fixed wifi.
Later that week I needed a working camera. So I flashed (without fxzing back to gb ) scv7 in the cm recovery. This was the version that is based on the new leak.
I have since fxz'd back to gb 3 times. The first time was because of oddness I was experiencing, such as no car dock, wifi acting odd.
The second fxz was the result of trying to install my own build of cm9. It went past the bootloader but the screen stayed blank.
I just had to fxz again last night. I tried to reinstall cm10. It just sat on the boot animation for 25 minutes. I remember it taking a bit to boot up the first time previously, but more like 10-15.
Anyone have any thoughts? I'm sitting on 2.3.6 for the moment, I would really like to get back on cm10 but I'm not sure what might be going on.
Thanks.
Luke
Edit: cardock still not working in stock unrooted 2.3.6
Sent from my MB865 using xda premium
Click to expand...
Click to collapse
I'm thinking that there must be something off in the bootloader. I'm hesitant to go playing with it since that is a quick road to bricking. I might dissect the boot.img that is included in the cm10 zip. I'm thinking there is a missing module, or something similar.
Any input would be appreciated.
New update. I was able to get back to CM10. I had forgotten to wipe data. Thats what I get for flashing when half asleep.
Still trying to understand what happened to stop my cardock from working. Charging in the dock works fine, but it doesn't start car dock mode, or push audio through the usb. I'd really like to get that working again.

[Q] Imo Lean Kernel, CWM and OTA

Will I need to flash the stock kernel back on my phone to take the OTA or will it work with Imo's kernel? I tried to reflash the boot.img from my nandroid and wifi was not working, so I reflashed Imo's kernel and wifi works again and I am sitting in a holding pattern. I'd rather not have to ODIN back to full stock because I only have access to PC's at work and don't really have time in the day at work to be doing stuff like that while there.
Also can I just download EZ Recovery and flash the stock recovery?
Phone is rooted, unlocked, CWM with Casual and Imo's Lean Touchwiz kernel. TIA

What exactly makes you want the update? If it's the radio (which imo is the only reason to consider the OTA) then just get the radio and flash it in CWM.

i already have the radios flashed but I've had this weird issue that seems to only happen after flashing the kernel but has only happened on a few occasions mainly on the weekends at my daughter's 2 soccer games to be exact. Camera and video have acted weird, first was video controls were upside down, had to reboot a few times for it to fix and just yesterday everything I shot shows fine in gallery but when I go to import into Instagram the pics are all rotated 90 degrees.
I can't afford to have data issues which is the reason I haven't installed a custom ROM since I use my phone for work quite a bit. Figured go back to stock kernel, take OTA to clean out any weird issues that would linger and wait for either official JB or for ROMs to get solid on data issues.

mav3rick478 said:
Also can I just download EZ Recovery and flash the stock recovery?
Phone is rooted, unlocked, CWM with Casual and Imo's Lean Touchwiz kernel. TIA
Click to expand...
Click to collapse
Yes, but remember if you don't already have the OTA notification nothing with come just because you removed the custom recovery. If you've already received that notification then disregard this post.
Sent from my SCH-I535 using xda app-developers app

Thanks Snoop, been getting the OTA notification for 2 weeks now. I thought originally after it failed because of CWM it disappeared but woke up a few mornings to my phone being in CWM asking if i wanted to install the OTA and thinking to myself, "good god how long has my screen been on?!"

mav3rick478 said:
Thanks Snoop, been getting the OTA notification for 2 weeks now. I thought originally after it failed because of CWM it disappeared but woke up a few mornings to my phone being in CWM asking if i wanted to install the OTA and thinking to myself, "good god how long has my screen been on?!"
Click to expand...
Click to collapse
No problem. If you still notice weird issues then Odin to an older firmware and accept the OTA from there.
Sent from my SCH-I535 using xda app-developers app

[Q] Strange Rom Issues

Alrighty, this is one of the weirdest things I've had happen with a phone since I started doing this on the original Droid. Lately I've been using Jellybeans Rom, its been great and my longest running ROM so far, but like a lot of people here I have to try out new stuff quite often just to try it. Well anymore I cant seem to try much else, I wanted to run the newest Liquid Smooth 2.3 ROM that just hit and it wont work at all really, before I redid the whole phone every time I flashed LS 2.3 I couldnt even hit the start button when the ROM first installed, when I did it wouldnt do anything and then the screen would go black and I would have to hard reset or battery pull. Next boot up seemed to go fine, got my gmail up and running and titanium downloaded and then after that, hitting settings options would lock up the phone in just about any app I had, never even got around to trying to restore anything with titanium.
Re-flashed LS 2.3 three or four times and nothing changed, tried fixing permissions, fully wiping, etc. didnt matter. So naturally I figured it was simply the ROM on my phone (mind you LS 2.2 worked fine before) so I went and decided I would try out Avatar ROM, CM based with MIUI themes, this ROM did pretty much the same thing. No idea why...
Next I figured something maybe was wrong with my phone so I went back to the drawing board and started from factory with ODIN, I redid my ROM with stock/root, unlocked the boot loader again and redid custom recovery and all the same thing with LS 2.3 happened all over again, Stock ROM worked great for the bit of time I used it before I tried to reflash LS 2.3 again, Now I'm back running Jellybeans v.15 and it runs perfectly fine as well.
I really have no idea what the problem is, both of those ROMs I've tried are CM based original development, so I'm wondering if its something in there thats causing an issue over the TW ROMs I've used. I've used other TW ROMs with decent success, but I've had some issues with those too that you wouldnt think should happen but it wasnt anything worth noting, just like Jellybeans the best, but even some of those would give me slow down problems and occasional lock ups when Jellybeans doesnt.
Anyone have any clue as to what could be causing this? I used to be able to run non TW roms just fine and its only been in the past month that this has started happening that I've noticed, I've had the phone since January and have been flashing away this whole time and now I cant seem to try out any more ROMs without having major issues......ugh

Your situation is a very random situation but I have something similar happened to me involving TW ROMs in that some of them froze on me. I had to flash the stock ROM.

Bump, anyone having any kind of similar problems?
Sent from my SCH-I535 using xda premium

Vidfreek said:
Bump, anyone having any kind of similar problems?
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
If you've only had these issues in the last month, it could be attributed to the Linux 3.4 kernel that every AOSP rom has moved to. I wouldn't let that stop you though. Are you downloading these rom zips over WiFi or mobile data? Were your downloads taking awhile as well? I know either GOO or AFH was having server issues recently which may have coincided with your downloads. I'd suggest using WiFi if you aren't already and trying again?
Sent from my SCH-I535 using xda app-developers app

Yeah its only been fairly recent and all roms I've tried have been updated since the very end of april, if my phone has major problems with that linux kernal am I going to be able to flash anything again? Everything I downloaded was over wifi but I can try all the downloads again but I'm thinking that won't fix anything, just weird stuff
Sent from my SCH-I535 using xda premium