I have a VZW gtab and I have been running KhasMeks Voodoo plus v5 kernel for at least 3 months now. All of a sudden today I was getting a ton of fc's. So I rebooted and when I got back in it said that my System UID's were inconsistent and I should wipe data partition or something like that. I read around and people had tons of different ideas but I didnt see any that acutally worked other than reflashing.
So my question is should I just factory reset? And if I do that I need to disable voodoo before hand correct?
Any help is greatly appreciated
Related
Looked at the sticky, but did not see this issue. It was happening on my cyan builds once I went to donut. I swapped, updated all, wipe, install per instructions, but the prob found me again. This time I am not the official 1.6(DRC83, 2.22.19.26I) Anyone else have this happen to them?
Fixes?
Okay, so the time ranges between 30 seconds and a minute.
From what I am seeing, I may have to revert back to stock settings and give it a go. If that works, then I will attempt to ROOT again.
I only began having this issue after I upgraded to 1.6 via cyanogen.
I swapped ROMs hoping to solve the issue ( thought it may have been b/c of the experimental/beta version)
But after being on this build for one day, I am already experiencing the issue again. I even went as far as repartitioning and wiping before I started so it would be a clean slate.
ljnick19, this is an interesting problem. What call settings are enabled for you when this happens?
derfolo said:
ljnick19, this is an interesting problem. What call settings are enabled for you when this happens?
Click to expand...
Click to collapse
I have made zero changes to the standard setup there. All is normal. I have not fully customized since I applied the ROM b/c of time constraints. Just getting basic apps back on from the market.
ljnick19 said:
I have made zero changes to the standard setup there. All is normal. I have not fully customized since I applied the ROM b/c of time constraints. Just getting basic apps back on from the market.
Click to expand...
Click to collapse
The HTC recovery may have messed your radio up. Try reflashing the radio.
Thanks for the input! I was worried no would have any ideas. I'll give that a shot. Now when reflashing the radio, do I need to do the whole-radio, spl, rom, wipe thing? Or just radio?
I am also using Ra v1.2.2 recovery, could that be causing issues w/ 1.6, Donut ROMs?
One more issue to add: AdvancedLauncher (processandroid.process.acore) has stopped unexpectedly. FC almost every time i press the home button. Made the mistake of making advanced launcher my default home button action...
For the launcher make sure you have the latest version. Then reinstall or run fix permissions. U only have to flash the radio, and the recovery should only affect flashing the roms
Thanks a mill for the help, I really thought this was going to fall flat. I'll attempt later this afternoon and post results.
For those of you that took a moment to not only read, but to assist, THANK YOU!
Results are:
I went from OTA 1.6 to Cyan 4.1.999
I wiped and repartitioned the sd as well as redoing the radio
So far, I have not experienced any FC's. Unfortunately, I have not made a lot of calls either. Crazy thing was that on the OTA build today, calls seemed to be functioning, but the FC's were excessive.
I also ran fix permissions as well as cleared the dalvik cache.
Again, thanks for the support. I hope to pass it on if I am ever able to help, it is appreciated!
LJ
ok so i have moved up to gingerbread, but i seem to be having a problem. for whatever reason after about 2 weeks of running gingerbread roms they reboot themselves then as they are booting back up the boot animation will freeze on me. no one has been able to figure this out yet but i have at least been getting logs of it.
both loop issues are caused with roms UD 3.0 beta/rc1/rc2 and liquid slayher gingerbread.
clearing cache - doesnt work
clearing system- doesnt work
clearing boot - doesnt work
reflashing rom after doing all of this - doesnt work
clearing my data - works. but this is getting annoying having to set the phone back up every two weeks. Froyo roms works perfect with some FC's here and there. but i uploaded all 5 logs i have.
mediafire.com/?ihdseljud1ctgs1
logs logcat1-4.txt are UD 3.0 and logcat5.txt i just did with liquid slahyer.
please someone shed some light on the source of my problem because i have a feeling its either dalvik issue or a app issue.
I have a Galaxy S which i rooted and installed a lagfix on. I think it was Ryans OCLF i used for the lagfix.
I want to update to the official Froyo available from T-mobile via kies but having lots of problems getting it to connect (as everyone does). I have backed up contacts etc. I havent bothered backing up apps as i just wrote down the settings i have in each one and will just reinstall them after the upgrade.
What im planning on doing was completely resetting the phone back to factory settings and wiping it altogether so i have a clean phone to do the upgrade.
The problems im expecting or want to know how to avoid is with the root and lagfix i have installed. Will doing a factory reset or other reset (hopefully somebody can tell me another way of resetting) get rid of the root and lagfix or do i need to do something manually before wiping the phone? I know of something about the lagfix creating partitions etc so would a factory reset cancel the lagfix or would it cause all sorts of problems?
How do i go about removing the lagfix and resetting to the standard software that came with the phone? Also i have apps that require root so if i unroot the phone will this cause problems when they try to start or will they just not work and not be an issue?
Im not running any custom roms just the original one that came on the phone.
Sorry for all the questions and a rather long first post but im hoping to do this soon as the phone is running like a bag of smelly brown stuff lol.
Disable the lagfix first and then wipe. Root will not go away but I dont think that would be problem.PS. If I would be you I would just use odin to upgrade, there is plenty of good guides including how to use odin
Undo lagfix before any firmware upgrade .Then factory reset then go to Kies .
Remove lagfix as per the instructions with whatever lagfix you used .
Unroot not a problem its only a user administrative rights fix giving you greater access .
Personally i undo anything i can before an upgrade .
jje
Yes i would definitely undo everything before upgrading its just a question of how i do it.
I used Ryans OneClickLagFix app that was on the market at the time but now it has been altered because it allowed you to root and google didnt like this. I still have the original version i downloaded on the phone so is it just a case of clicking on "remove lagfix" and that will sort it?
Also if the root remains on the phone after i have wiped it, will this cause any problems when i put froyo on it? Is there not a different method or file for rooting froyo to the one i have used on 2.1?
on "remove lagfix" and that will sort it?
Correct .
jje
Also click Remove Ext2 Tools, and the go into the Scheduler changer and return it to CFG and uncheck the tweak buttons, if you messed with any of that.
In which order should i do all of those?
Should i remove the ext2 tools and return cfg settings etc to default before i remove the lagfix or after?
So just a quick update.
Something went totally wrong the other night on its own. This is before i had even thought of upgrading that night. Was sitting on facebook happily playing away when it started force closing within a few seconds of opening. Tried to open the market to reinstall the facebook app and the market force closed in a few seconds. It did this with every app including the email and phone etc. Even the RyansOCLF would forceclose so i couldnt remove the lagfix or unroot etc. All my settings for apps and launcher pro settings had disappeared. Only a couple of icons i had set on the home screen of launcher pro remained but i couldnt use any of them. All my phone logs were there and so were my texts etc but everything else had reset. When i tried to reapply some of my settings and then restart the phone, when i had finished the restart the settings i had reapplyed had defaulted again. Disaster!!
The only thing i could do was run a factory reset from the options menu. I crossed my fingers hoping this wouldnt brick the phone and alas it worked perfectly. Sorted out kies and connected the phone and installed 2.2.1 android. The lagfix had been cleared by the factory reset. I keep wondering if this is why i had so many problems with it taking ages to start up before. Maybe because the lagfix never really worked properly it never fully rebuilt the file system so was removed easily? Although the benchmarks were coming up double the speed of the fastest device on the results so not too sure how it was performing so fast with a duff lagfix...who knows. Anyway got it all up and running and rooted and lagfixed using the voodoo fix. Stuck launcher pro on setup everything. Got the apps i previously purchased reinstalled and restored any apps i wanted from titanium backup. Works like a dream and alot better memory usage aswell.
Thanks for all the help guys but it seems although i didnt follow any of the instructions you all posted (not out of choice...just because the phone physically wouldnt let me) it seemed to get the upgrade done without any problems.
i used this shipped rom when i got my n1 6 months ago,
Passion_Google_WWE_2.16.1700.1_FRG33_MFG_Shipment_ROM.zip
i received all the updates, it was working fine.
the other day, i decided to use the same passimg.zip file,
when phone read the sd card, i accidently selected recovery, it started to do recovery process, middle off the process i freaked out because that was not i wanted to do so i turned off the phone and install passimg.zip
i install all the programs i use and received all the updates,
now n1 sound level goes very low even it shows sound level is max,
its impossible to hear when it rings or playing music.
when i turn off and on the phone i get the sound back, after some time sound level goes very very low even sound level in max. so i turn off and on again and i get sond back,
i dont have any problem during calls i can hear,
right now
version 2.3.6
build number GRK39F
how can i fix this?
This used to happen to me on cm7 I did a full wipe and reflashed the ROM and it fixed the problem so I would suggest you reflash the passimg file.
i downloaded same passimg file and installed it to my nexus one, same proprem continuous.
when i turn off and on, everthing normal.
any ideas?
Dude Random21 said:
This used to happen to me on cm7 I did a full wipe and reflashed the ROM and it fixed the problem so I would suggest you reflash the passimg file.
Click to expand...
Click to collapse
"full wipe" means, using passimg file and install it again?
Full wipe means to do a factory reset, usually from recovery.
i figured it out. i dont know why but the problem was a program called voipraider,
i uninstalled it, problem solved, thanks for your replies...
Ok well I'm glad you got it resolved
I have this same problem. I don't have the app mentioned above installed, so I'm hoping someone can chime in with another app that may cause this issue? I've done a full factory reset, reinstalled everything (MIUI rom.) Rebooting the phone doesn't always fix the problem.. sometimes rebooting a few times will bring the sound back to normal, yet randomly all sound on the phone is barely audible at max settings. If a normal reboot doesn't work, normally wiping dalvik will fix it. Would this mean the problem lies in one of my apps somewhere? Any advice?
Are you using DarkTremor's a2sd? If so, it is a well-known problem. And wiping dalvik or just the regular cache will reset it. Due to this reason (and a few other minor ones), I switched to S2E for my app2sdext purposes, but I am not sure how well it works with MIUI (it was designed to work with CM7).
@bassmadrigal
Thanks. As I think about it, DTs a2sd is the only common thing I had in my testing. Even switching between ROMs, I kept flashing DT. Since I always have issues with MIUI's stock A2SD (based of DT).. I went back to CM7. I looked into S2E and will take that route.
I hope this fixes it.. the sound was frustrating when my alarm is going off in the AM and it's not making a peep. I'll post back in a few days in hopes that it's ceased to be a problem.
Thanks again for hopefully solving my major nuisance.
Hi Folks,
so here's my problem, the other day I got the standard "not enough space"-warning and I thought crap there must be a solution to this by now, so I checked and found that script that cleans up the cache etc.
So today suddenly apps(mostly gapps) started crashing one after another, without them even being open, just as it would do when space in /datadata got very low. The phone was basically unoperable, so I restarted it and it was stuck at the boot screen(blue flashing screen, not before). I tried everything to get rid of this, clearing different caches, new nightly, new skript version....nothing.
So I did a nandroid backup, reset the whole thing and started it, everything went fine. Another restart into recovery flash nand-backup....back to old habits :/
Still not wanting to give up I reset it again and reflashed only /system.....all worked, reset it again and only flashed /data.....stuck again. So it must have something to do with the /data-partition, since I would really love to have my data and apps back it would be great if someone could help me out here.
Device-Info: newest CM9-nigthly, kernel that CM9 uses, of course I9000
For more Info please ask!
Weeman90