Database Users

Cyanogenmod 4.2.6 lots of fc fix!!!!

Hey guys i just recently flashed/hacked my g1 for the first time. i went from 1.5 to 4.1.99 cyanogenmod then updated to 4.2.6. i noticed i had lots of force closes. i was trying to do a downgrade to 4.2.5 to see if it fixed the problem but i was lazy to go all the way back to RC29. So this morning i boot into recovery mode (recovery-RA-v.1.2.3.img) hit the wipe data/factory reset. BAM! skipped all the gmail activation. Turn on wifi and activate my gmail account. No MORE force closes! BTW i am on AT&T with no data plan. Hopes this helps any questions just email me [email protected]

I think that may have to do with the fact tha tyou skipped a lot in between, you went from 4.1.99 to 4.2.6, I went from 4.2.5 to 4.2.6 with no problems

is it really necessary to flash so many outdated updates just to flash the latest? I just came from Dwangs1.13 and no problems so far..so many people talk about the instability of this rom that its insane.
But back to the point made earlier...i dont remember reading that flashing from previous CM versions was a requirement...

oneG said:
is it really necessary to flash so many outdated updates just to flash the latest? I just came from Dwangs1.13 and no problems so far..so many people talk about the instability of this rom that its insane.
But back to the point made earlier...i dont remember reading that flashing from previous CM versions was a requirement...
Click to expand...
Click to collapse
It's not a requirement. I have flashed the HTC image, and then directly flashed 4.2.6, without having to flash 4.1999, or any other ones before 4.2.6 and I have had no problems. I do this all the time because I jump from CM to Hero/Sense roms

Yeppers
I am with Tazz there. After bricking my phone (totally my fault), I went from stock to Rc29, to the htc-dev image, and straight to 4.2.6, with no problems. I have had force close issues in the past that were fixed with a combination of fix_permissions and reinstallation.

I had a lot of force closes and an extremely slow device with cyanogen.
By wipping, deleting, and recreating the 2 partitions (FAT32 and ext3) on my SD, all at once, I got it running right again.
Since then it's a pleasure to use.

Fascinating.. :O
Never heard of a wipe :O
Oh come on people..

Already have JI6 & recieved an update message?

Hi
I wake up and have an update-from-tmo message . The think is that I already have the OTA JI6. does anyone knows something about this?

Anyone?..................

I haven't heard of any other update since J16.
Did you update manually to J16 or use the OTA?

Yeah, how did you update to JI6?
Install it and let us know if your firmware/baseband are the same.

I had Bionix 1.9, which already had the official OTA JI6 version. Still got the message T-Mo about the update, so I just updated it and everything seems fine. Didn't have any problems.

I have a similar problem. I had the update message but didn't want to apply it since I read about all the horror stories. I manually updated to JI6 and baseband version, etc., all reflects this (as does media hub being unlocked, hd camcorder, GPS working, new sorted gallery and other fixes). However, I still have the damn notification that pops up constantly. How do I get rid of it??

I 1st tried OTA but it got stuck on the vibrant screen so I odin the JI5 but ended up with the JI6. Don't ask me how. The odin files I have in my comp are the JI5. Another thing is that I was rooted when I OTA the JI6. Ended up with JI6 rooted

bottom buttons

finally upgraded from DI01 to ED01 and have discovered a problem. the 4 buttons on the bottom of the screen now act weird. they will light up, go out, or flicker depending on what im doing. never had this problem before and i havent seen anyone else post about it but i could have missed it. anyone have any idea?

Did you update stock di01 to stock ed01 or between custom roms?
Sent from my SCH-I500 using XDA Premium App

no, i tried the OTA update several times with the end result being the server IP error. unrooted and tried again several times with the same results. then i followed the link in another post and flashed with odin, the DL09. tried again several times to get the OTA update with no success. had to flash that several times and then finally got it to install. as it sits i am running ED01 stock but rooted. my wifes phone had had all the OTA updates and has always run stock, not even root and has some problems with the buttons as well.

try reflashing a kernel... i only dealt with that problem once a while back and i just reflashed everything and that seemed to fix it.
Also i used to restore system files from titanium backup and sometimes it didn't play nice with whatever i upgraded to and that would cause the backlights to bug out before i got force close messages.

[Q] HELP!!! 7.014.02 Update Problems

I just purchased the A500 and have successfully updated 7.014.01 and then when I try and update to 7.014.02 I get Update Failed message. Anyone have any ideas as to how to fix it? Tech Support recommends that I send it back, but it will take 2-3 weeks and it will be a royal pain and will be my last resort.

sonjamin said:
I just purchased the A500 and have successfully updated 7.014.01 and then when I try and update to 7.014.02 I get Update Failed message. Anyone have any ideas as to how to fix it? Tech Support recommends that I send it back, but it will take 2-3 weeks and it will be a royal pain and will be my last resort.
Click to expand...
Click to collapse
I'll assume this is the 3.2.1 update as it usually comes in 2 update files.
I'll guess your 2nd update download was corrupted somehow. Probably a good thing, as some people had bricked tab's as a result of a failed update.
If your tab runs fine, don't worry about it, and ignore the update. They'll probably just give you another tab, and you'll go through the same thing again.
Not really a whole lot in the 3.2.1 update anyhow. Only thing I noticed, is a slight difference in screen sensitivity and just a touch smoother in the app drawer. Other than that, no other real performance gains.
In a few months, they'll push the ICS update. So it will all be moot.
But, if you really want to do this small update, you'll have to root, install CWM recovery, then flash a rooted update manually. I think TimmyDean posted these awhile back, but not sure.
Or, you can just flash a 3.2.1 custom rom.
But if your tab runs ok, and you don;t want to come to the dark side, then forget about it and wait for ICS.

Frequent SOD after 4.3 update

I started with a stock 4.2.2 and the only modification to the phone was unlocked bootloader and root (no custom recovery or anything like that).
The phone has had a couple of SOD instances but they were very rare. After doing a sideload OTA update I've had it SOD twice in the last 2 days. I haven't re-rooted this phone (waiting for SuperSU to be less...hacky) or installed anything to mess with power management. I read that there may be a netflix SOD issue but it's not applicable as I don't have the app.
Anyone else get SOD with 4.3 or am I the only one?

smapdi said:
I started with a stock 4.2.2 and the only modification to the phone was unlocked bootloader and root (no custom recovery or anything like that).
The phone has had a couple of SOD instances but they were very rare. After doing a sideload OTA update I've had it SOD twice in the last 2 days. I haven't re-rooted this phone (waiting for SuperSU to be less...hacky) or installed anything to mess with power management. I read that there may be a netflix SOD issue but it's not applicable as I don't have the app.
Anyone else get SOD with 4.3 or am I the only one?
Click to expand...
Click to collapse
You are not alone. My wife's phone is experiencing the same issues. I have chosen not to install the update for this very reason. Hopefully it will get fixed and there will be a new update in the near future. Sorry I don't yet have a solution.

pfederighi said:
You are not alone. My wife's phone is experiencing the same issues. I have chosen not to install the update for this very reason. Hopefully it will get fixed and there will be a new update in the near future. Sorry I don't yet have a solution.
Click to expand...
Click to collapse
Yeah, me too. I have had instances where it has just completely shut off and i've had to hard reboot. My other half also has a similar issue on the N4 and these were when I was on stock. I'm now running PA 3.90 and I haven't had any (as of yet)

Kitch16 said:
Yeah, me too. I have had instances where it has just completely shut off and i've had to hard reboot. My other half also has a similar issue on the N4 and these were when I was on stock. I'm now running PA 3.90 and I haven't had any (as of yet)
Click to expand...
Click to collapse
For what it's worth, doing a "factory reset" cured my wife's phone of the issue. Be sure to do a backup of important data like contacts and picture first.