Related
Hello All:
Here is a rundown...
Started with JF1.42-RC33 with Apps, Data, Dalvik to SD...
Went to JF1.5 without a wipe and then updated the radio.
All of this went fine. Now when I start up the phone, it
gives me the "System UIDs Inconsistent" message. I press
the button and then everything loads fine. All 125 Apps
are there, Market works correctly, notes are still there,
and I have tested every App and there are no issues.
Loving the new ROM by the way... no stability issues so
far.
The message on the phone says to wipe the data. If there
is not other way to get rid of the nagging error then so
be it... I still have my Nandroid backup from the JF1.42
image.
Just wanted to see if there was possibly a way to fix this
in ADB or the recovery console...
Also, it is in my nature to try and understand these things.
Could this have happened because my /data directory is
on the SD and therefore was not cleared during the Flash
process? Just guessing...
Any ideas?
L8r,
Vermithrax
Vermithrax said:
Hello All:
Here is a rundown...
Started with JF1.42-RC33 with Apps, Data, Dalvik to SD...
Went to JF1.5 without a wipe and then updated the radio.
All of this went fine. Now when I start up the phone, it
gives me the "System UIDs Inconsistent" message. I press
the button and then everything loads fine. All 125 Apps
are there, Market works correctly, notes are still there,
and I have tested every App and there are no issues.
Loving the new ROM by the way... no stability issues so
far.
The message on the phone says to wipe the data. If there
is not other way to get rid of the nagging error then so
be it... I still have my Nandroid backup from the JF1.42
image.
Just wanted to see if there was possibly a way to fix this
in ADB or the recovery console...
Also, it is in my nature to try and understand these things.
Could this have happened because my /data directory is
on the SD and therefore was not cleared during the Flash
process? Just guessing...
Any ideas?
L8r,
Vermithrax
Click to expand...
Click to collapse
wipe and re-set your symbolic links .. all your apps will be back but not their data..
Thanks... I guess I will just take the easy way out and wipe the phone... I have tried various ADB and busybox commands to no avail... What I do not understand is the phone works perfectly after the Nag screen is gone... No force closes... no missing functionality...
I will not do the wipe until this afternoon... Just in case some Linux guru has any ideas...
L8r,
Vermithrax
Unless the nag screen bothers you, or shows up more than once per boot, Id leave it. If you start seeing instability or forcecloses then Id wipe.
Unless there is a good reason to Id avoid a wipe. Of course I dont have OCD so one nag per reboot wouldnt bother me. If you do or it does bother you then yeah wipe.
Solved... For me at least...
I had solved this problem some time ago, but I just thought I would add this to the thread in case others find their way here through a search...
All I did was move the /data/data back to the internal memory...
rm /data/data
busybox cp -a /system/sd/data /data
rm -r /system/sd/data /data
reboot
Had a couple of stale NFS file errors, so I could not really delete the /data directory from the /system/sd. However, there are threads that help with this issue.
Probably the cleanest solution HERE
hello all,
did a search through this forum didn't see any posts regarding the subject. I was running GummyCharged FE 1.9 and was getting process.acore force close messages more often than I cared for. did not have that issue with GummyCharged FE 1.8.x releases. I think it may have something to do with my contacts though not sure. can anybody shed some light on this?
U may have to reflash. Its happened to me on numerous roms, and a reflash usually fixes the issue. I know its something u might not wanna do, but I would just to get rid of the issue.
Sent from deez nutts. Oh, and my Gummy'd up Charge!!!!
youngpettyboi said:
U may have to reflash. Its happened to me on numerous roms, and a reflash usually fixes the issue. I know its something u might not wanna do, but I would just to get rid of the issue.
Sent from deez nutts. Oh, and my Gummy'd up Charge!!!!
Click to expand...
Click to collapse
Agreed, at least that was the fix for the fassy. Havent had it yet on the Charge
Yea, its the only way really. I tried fixing permissions, that didnt work. A full wipe worked. Also, if u install a theme over another theme without wiping cache and dalvik cache, u will get TONS of fc's. Happened to me. But it was an experiment lol.
Sent from deez nutts. Oh, and my Gummy'd up Charge!!!!
youngpettyboi said:
Yea, its the only way really. I tried fixing permissions, that didnt work. A full wipe worked. Also, if u install a theme over another theme without wiping cache and dalvik cache, u will get TONS of fc's. Happened to me. But it was an experiment lol.
Sent from deez nutts. Oh, and my Gummy'd up Charge!!!!
Click to expand...
Click to collapse
What if I've done multiple reflashes and wiped data, cache, and dalvik before flashing? Any other ideas?
Thanks.
Flashed using CWM or using Odin?
1st an FYI - If you run the fix_permission from CWMR, you need to check the log afterward. It has been broke (wrong path...cannot find packages.xml ) until the 08/07 version (which was only released as part of a few kernel packages). Even then, it seems people were getting mixed results (I haven't tried the newly released version yet).
I don't know if the script will help you though. If I remember correctly (I came from the Defy world), it had something to do with bad application cache (different from system cache and dalvik-cache). First question is, when you did a wipe/reinstall, did you restore any application's settings (e.g. My Backup, the Verizon's Backup Sync, Titanium Backup, Android Restore, etc.)? It would also help explain why a wipe/reinstall wouldn't help.
Also, purely a side note...if you wipe /data, then /data/dalvik-cache (along with everything else in /data) is gone too. Wiping both doesn't do anything (or if it does...then you have an even bigger problem in the /data didn't get wiped properly and should really look into that).
Raccroc said:
First question is, when you did a wipe/reinstall, did you restore any application's settings (e.g. My Backup, the Verizon's Backup Sync, Titanium Backup, Android Restore, etc.)? It would also help explain why a wipe/reinstall wouldn't help.
Click to expand...
Click to collapse
Got to agree with this. Most likely a data restore problem through titanium backup or a program similar. If not, then many people would have the same problem, not just you.
Let us know your restore process... like what do you go through when you redo your phone.
What can I do?
I've performed numerous wipe/reflash of system/device/cache/dalvik cache, and I still receive this error....
It's driving me mad... anything I can do to rid myself of this blasted error once and for all?
It's followed me through Gummy Charged 1.0, 1.5 and now 2.0.
So I've turned off contact syncing with all my accounts and this seems to have fixed the issue. Anyone know if I can permamently fix this? I'd really like to have contact syncing.
Sent from my Gummy Charged GBE 2.0 using Tapatalk
That error is usually from bad system data. Wipe data/ factory reset. Don't restore system data.
Backup your texts if they are important to you with SMS backup
Sent from my SCH-I510 using Tapatalk
I have completely wiped several times and I still get the error. Cache, Data System Wipe, Dalvik Cache, and voltage settings. I only get the error when syncing contacts.
I do full wipe each time a new version of Gummy is released. I also no longer restore Data from apparel using a tool like Titanium nor Mybackup. This has happened on a number of ROMs
Sent from my Gummy Charged GBE 2.0 using Tapatalk
jraskal said:
I have completely wiped several times and I still get the error. Cache, Data System Wipe, Dalvik Cache, and voltage settings. I only get the error when syncing contacts.
I do full wipe each time a new version of Gummy is released. I also no longer restore Data from apparel using a tool like Titanium nor Mybackup. This has happened on a number of ROMs
Sent from my Gummy Charged GBE 2.0 using Tapatalk
Click to expand...
Click to collapse
The force closes may be a precursor of worse things to come. That has been the case with me. I usually go all the way back to bone stock when I have persistent force closen rebooting, or freezing issues. My last crash in Gummy 2 FE was enough. I ended up soft bricking to the point that it would not even power up. I was fortunate that I was able to get into download mode and go to stock (after a couple of attempts)
Have you tried going back to stock yet?
No not yet, Im hoping to avoid that. My phone runs perfectly with contact syncing off.
For the time being I just download my google contacts into a csv and import that file manually.
Sent from my Gummy Charged GBE 2.0 using Tapatalk
I know I'm a year and a half late to the game here, but I was having this problem on my G Tablet with TNT Lite, and after doing a bunch of hunting, I found a fix that worked that (theoretically) should work with other devices. The first part is really easy, but might not to the trick. The second part isn't much tougher, and put everything back as good as new with no recurrences.
This issue is linked to your contacts. If you go into Settings>Applications>System Applications>Contacts Sync Adapter and press Clear Data, this error usually goes away. If this doesn't work, try clearing the data on Settings>Applications>System Applications>Contacts or Settings>Applications>System Applications>Contacts Storage.
Still no luck?
Open Root Explorer. Go to the following folder: /data/data/com.android.providers.contacts/databases/
*Note* this is not the data folder in sdcard, but the data folder in root (/).
See if there is a “.db-journal” file in the folder. If there is, just delete the databases folder in /data/data/com.android.providers.contacts and reboot.
The contacts database will be rebuilt and re-synced, and the error message will stop popping up.
This solution worked for me TWICE with two different ROMS so I suggest you try it out:
Go to Settings –> Applications –> Manage Applications –> All (button on the top that lets you see all applications) –> scroll down to “Contacts Storage” –> Click on “Clear Data”.
Voila, problem solved I hope this still helps people since I dont think the owner of the thread has this problem still.
pablogzzc said:
This solution worked for me TWICE with two different ROMS so I suggest you try it out:
Go to Settings –> Applications –> Manage Applications –> All (button on the top that lets you see all applications) –> scroll down to “Contacts Storage” –> Click on “Clear Data”.
Voila, problem solved I hope this still helps people since I dont think the owner of the thread has this problem still.
Click to expand...
Click to collapse
Thank you.
This worked for me, while a Factory Reset didn't. So much for "factory."
pablogzzc said:
This solution worked for me TWICE with two different ROMS so I suggest you try it out:
Go to Settings –> Applications –> Manage Applications –> All (button on the top that lets you see all applications) –> scroll down to “Contacts Storage” –> Click on “Clear Data”.
Voila, problem solved I hope this still helps people since I dont think the owner of the thread has this problem still.
Click to expand...
Click to collapse
Yay thanks it worked for me
But why does this fc happen though? :/
My P1000 shut down randomly, so I tried to put everything new on it. After flash and all the other stuff it won't run properly anymore. Everytime I get 'System UIDs Inconsistent'. used Odin and Heimdall, I did wipe the data and the cache, I can see with ADB it is gone, but after reboot all the corrupt apps and system failures are back again. I installed several different firmwares, nothing worked.
I have changed permissions with chmod and deleted by hand several files, amongst them the everytime restarting but crashing apps like skype and whatsapp.
When I perform wipe, delete, rename or move actions in ADB the results are what I wanted. But when I restart everything is back again. I even deleted almost anything, did not work.
This happened in all the roms I installed, so it must be a problem in the filesystem or so. Any idea how to permanently delete stuff while in adb shell? I already gave myself all the rights on the tablet, synced it after the deletes, nothing works.
Or does anybody know how to start from scratch?
I cannot start the tab anymore in normal mode, but I do have recovery mode and overcome cwm.
best of luck
nbreed said:
My P1000 shut down randomly, so I tried to put everything new on it. After flash and all the other stuff it won't run properly anymore. Everytime I get 'System UIDs Inconsistent'. used Odin and Heimdall, I did wipe the data and the cache, I can see with ADB it is gone, but after reboot all the corrupt apps and system failures are back again. I installed several different firmwares, nothing worked.
I have changed permissions with chmod and deleted by hand several files, amongst them the everytime restarting but crashing apps like skype and whatsapp.
When I perform wipe, delete, rename or move actions in ADB the results are what I wanted. But when I restart everything is back again. I even deleted almost anything, did not work.
This happened in all the roms I installed, so it must be a problem in the filesystem or so. Any idea how to permanently delete stuff while in adb shell? I already gave myself all the rights on the tablet, synced it after the deletes, nothing works.
Or does anybody know how to start from scratch?
I cannot start the tab anymore in normal mode, but I do have recovery mode and overcome cwm.
Click to expand...
Click to collapse
try plugging it up while its in cwm and access the adb shell while its displaying. the prompt should be ~# if its universal. maybe you can completely wipe everything and flash a recovery at the same time? that may keep it deleted. i dont know. just a suggestion. i hope you succeed... tell me how it goes.
thanks for answering.
i tried all that, even did a complete format of the internal sd card, in adb with parted and also in windows with a mounted card. it says it is deleted, but after reboot it is all back again...
Do you have a backup of a working ROM you can restore?
Crap.... Hmm... Have you tried any formatting software? Try to find a programmer who can wipe it completely, re partition, and reinstall the stock rom. Then try to restore to something before the problems
Sent from my R800at using XDA
Use flashtool. I've heard it can unbrick, maybe it'll help???
Sent from my R800at using XDA
nbreed said:
My P1000 shut down randomly, so I tried to put everything new on it. After flash and all the other stuff it won't run properly anymore. Everytime I get 'System UIDs Inconsistent'. used Odin and Heimdall, I did wipe the data and the cache, I can see with ADB it is gone, but after reboot all the corrupt apps and system failures are back again. I installed several different firmwares, nothing worked.
I have changed permissions with chmod and deleted by hand several files, amongst them the everytime restarting but crashing apps like skype and whatsapp.
When I perform wipe, delete, rename or move actions in ADB the results are what I wanted. But when I restart everything is back again. I even deleted almost anything, did not work.
This happened in all the roms I installed, so it must be a problem in the filesystem or so. Any idea how to permanently delete stuff while in adb shell? I already gave myself all the rights on the tablet, synced it after the deletes, nothing works.
Or does anybody know how to start from scratch?
I cannot start the tab anymore in normal mode, but I do have recovery mode and overcome cwm.
Click to expand...
Click to collapse
this Q
With Q???
Recovery rom can be installed, but is gone after reboot. Formatting in windows or linux (adb) performs without errors, but after reboot, yes you guessed right, it is back. So this internal sd card has a life of its own, the only thing I can do is install a working system with flashing, but then no app will work, every activation of whatever app will give inconsistent uids errors. And I cannot install new apps, because vending.apk (market) will crash. I installed vending by hand (adb), then it work for a moment, but after reboot to use it the normal way, again crashed.
AS LONG AS I CANNOT REPLACE THE SDCARD IT IS HOPELESS?!?
This morning I left the unwilling android tab in the power adapter to be fully charged for a new go. But: it is now a real brick. It won't power up any more, the button lights do not flash anymore, the only thing it does, is showing the battery. Never again will I buy such an expensive underdeveloped piece of plastic crap again!
Calm down... You need to boot into recovery mode and try using formatting the sd. If comp can recognize, format the sd with the computer. It's not the android. It's what you did. Sorry
ROOTED Xperia Play 4G 2.3.3
can you read? i did format the sdcard in adb with parted, i did format it on the pc. but when i reboot EVERYTHING is back again. before rebooting it is totally empty. after reboot the old non-working stuff is back.
end of android, no end of samsung for me
Help
How do I install the radio over abd
News on this issue?
nbreed said:
can you read? i did format the sdcard in adb with parted, i did format it on the pc. but when i reboot EVERYTHING is back again. before rebooting it is totally empty. after reboot the old non-working stuff is back.
end of android, no end of samsung for me
Click to expand...
Click to collapse
I have the very same problem, did you managed to fix it ??
I wiped cache and dalvik cache, then installed the ZIP -- and after more than five minutes, the screen is still on "Installing update..." How long does this take?
Ten minutes later, I took the battery out to hard reboot the phone. It all came back OK (took a while because it had to build back the cache), but I'm not sure if the update took.
I did notice this error:
E:can't mount /dev/block/mmcblk1p2
(File exists)
But then it said it did delete the dalvik cache, so I thought it was all right, but maybe it didn't quite work. I'm using System Recovery to go into Recovery GFAN.COM V2.5.1.8. How do I successfully wipe the dalvik cache?
Are u using Full Touch Recovery?
If yes - change to normal recovery, I had this problem and now it works.
If no - I don't know, maybe someone other helps you
ch3mn3y said:
Are u using Full Touch Recovery?
If yes - change to normal recovery, I had this problem and now it works.
If no - I don't know, maybe someone other helps you
Click to expand...
Click to collapse
No, I'm not using FTR. I'm not even using ROM Manager -- I use System Recovery (an apk I found). It's the Moto A4 bootstrap that's based on Koush's CWM Recovery.
There is a problem with my signing on linux, I'll try and get a quick fix for the .zip tonight... until then:
1. Push files to correct folders.
2. Fix permissions to rw-r-r
3. Reboot
EDIT:
This is for the x2 right?? You should post in the Droid x2 Q&A section if so. It's not for other phones, only the Dx2.
Regardless, Problem fixed.
Are you saying I should unzip the files and then change their permission? What you describe, rw-r-r, is chmod 644. So I should extract, chmod, re-zip, then run the flash update? And yes, this is for the X2.
No l, just redownload, I fixd the problem.
Tapin' the Talk on my HTC Trophy
Just re-downloaded it, but nothing's different -- still having the same issue where it freezes at Installing update. I noticed there are two directories off of root now, Dx2_GB_BatteryFix and META-INF -- is that correct?
I am having the same issue with the zip file. Although I wouldn't say I am a noob, pushing these files is something new to me. If the zip cannot be properly signed or there is difficulty unforeseen in being able to do so, can someone explain in some detail how to push this?
Many thanks!
EDIT: So I figured it out using File Expert. Copied and overwrote battd to system/bin and libbattd.so to system/lib and corrected the permissions as you stated, rebooted and wiped cache and dalvik cache. All seems good now! Thanks for the fix.
Barebone SGS4G KJ6 ROM
Use at your own risk, I take no responsibility for anything that may happen to your phone because of this ROM.
Here is a ROM that I made for myself, but what the heck, let's share. This ROM is very stock-like with just few usability mods.
Features
Will not wipe your programs or data, /data is preserved upon install
Heavily debloated. Most essentials apps are still there (like WiFi Calling)
No extra programs added, you need to add your own
ODEXed to save space in /data
CarrierIQ is completely removed
Extended Power Menu (including Screenshot)
Extended Quick Panel (10 buttons, including Data toggle)
1% battery (horizontal)
CRT-Off
Time zone version 2012b
/etc/hosts to cut ads out of the box (keep up to date with AdAway or similar)
Few conservative presets in build.prop and init.d
Basic with a Twist 1.1.3 kernel included
Notes
* Don't get confused about ODEXing, it's actually better to run and saves quite a bit of space in /data.
* Some Google apps (Maps, Streets, Voice) and Adobe Flash are removed from /system. Install them from market. Benefit - they can be moved to SD card this way.
* Original Swype is removed, is somebody needs it flash this.
* In case you need it, use this thread to add some bloat back.
* Factory Reset is removed from Settings->Privacy, use CWM if you ever need to reset all data.
* KJ6 modem included. Use this thread to flash a different modem if needed.
Install
Flash with CWM. Wait until the system boots up, then wait few more minutes for it to settle.
Download
v1.1.3
v1.1.2
v1.1.1
v1.1.0
v1.0.8
Changelog
1.1.3
Removed "Mobile data connection disabled. Connect?" popup on boot
1.1.2
Removed Factory Reset from Settings->Privacy
Updated kernel
1.1.1
Fixed voicemail notifications not working without Visual Voice Mail installed
1.1.0
CIQ is properly removed
Some neutral cosmetics (logo, animations)
Minor update to the kernel
1.0.8
Fixed slow stock browser scrolling
1.0.7
Extended Quick Panel
1.0.6
Added Screenshot to power menu
1.0.5
Removed DriveSmart and Software Update from Settings menu
1.0.4
Put original framework-res.apk certificate back
1.0.3
Added power menu mod
1.0.2
Original public release
does it have a screenshot option from the power menu??
m0bstr said:
does it have a screenshot option from the power menu??
Click to expand...
Click to collapse
Nope, never bothered with power menu. I don't reboot the phone too often and to say the truth don't even remember when last time I needed to take a screenshot. I use ShootMe and QuickBoot when I need to, they both do the job just fine.
Yes, power menu is fully modded now, including Screenshot option.
Thank you for this, Anton! Love your kernel. Is this ROM ok for OC/UVing with you OC/UV kernel? I think this will be the second ROM I have ever installed. Haven't bothered to try anything since first getting Val Final.
Download link is not working
Sent from my SGH-T959V using XDA
Does this come pre-rooted?
Blaggah said:
Does this come pre-rooted?
Click to expand...
Click to collapse
Yeppers it does.
I updated the link. I actually took it down on purpose, wanted to look at something but never had time.
I was troubleshooting an error message during boot time, so I traced it to the CIQ trying to execute some on-boot code, which was removed by Krylon. Strangely the original code itself doesn't do much, it's initilizing a broadcast receiver with an empty onReceive method. Removing this was a moot point, it probably didn't do much. I disabled the BOOT_COMPLETED permission for the service to avoid the error message.
So I looked at the CIQ more closely. What I found is a little peculiar. The main CIQ code is integrated quite deeply into the framework, it cannot be removed easily, there are just too many calls that send various metrics to the CIQ Agent. The main CIQ classes are not in the framework.jar, they are in ext.jar. Probably that's why nobody noticed them and never tried to modify them. What is strange that many calls seem to be not implemented. For example the sumbitMetric is an empty method, shouldSubmitMetric always returns zero, etc.
It's possible that T-Mobile decided not to use CIQ on our phone (at least extensively), but instead of removing it completely just plugged few calls.
I'm removing the "CIQ removed" description because it's actually not removed, although may not be doing much.
I cannot get it to boot. After the "Galaxy S 4G" screen, the screen goes back then nothing ever happens. I rebooted into CWM (which still shows Team Acid's logo) and tried fixing permissions to no avail.
Given that the OP says it won't wipe programs, data, etc, was it possibly a Bad Idea™ to have wiped everything before installing this ROM?
Update:
Indeed, installing from a blank phone (literally, I wiped everything) didn't work for me. I flashed Bryan's one-click with CWM, it booted, rebooted into recovery, flashed this, and it booted. Now for testing. Thanks, Anton!
I had the same issue as well... Thought it was just my phone
Sent from my SGH-T959V using xda premium
Would be interesting to look at the logcat to see where it's stuck.
There was a possible problem with 1.0.3 that I pulled off. The current one that I re-uploaded - I tried to install in on both fresh phone (after factory reset) and on top of a running ROM , everything seemed fine.
The problem was with framework-res.apk. I had to resign in because I changed some permissions in AndroidManifest.xml (related to CIQ), but something went wrong the first time.
There is a little bit of controversy with signing of framework-res.apk. Some say it's OK, some say the original cert should be kept. Maybe somebody else would chime in and tell me if I screwed it up or not.
wont flash
I wipe everything, the ROM installs, and then black screen...noting. Let it sit for 20min however this did not resolve issue. I was able to install Valhalla no prob. flashed your rom on top of Valhalla and then my phone boots your rom. Do i need to install on top of another rom? I should just be able to whipe my phone and install your rom correct?
AntonX said:
Would be interesting to look at the logcat to see where it's stuck.
Click to expand...
Click to collapse
I can probably capture that because I can use adb to get into the OS. I ran top to see what, if anything, was hogging CPU but there was nothing obvious & CPU usage was minimal. I have the phone running now but I'm willing to wipe it again and re-flash. Mind you, I did more than factory reset. I was quite literally trying to start from scratch, so here's what I did (if this helps at all):
Backed up /efs to my PC
Backed up the SD card to my PC
Wiped cache
Wiped Davlik cache
Wiped battery stats
Performed a nandroid backup
Copied the backup from /sdcard/clockworkmod/backup to my PC
Formatted /data, /system, & /sdcard
Rebooted back into recovery
Copied the ROM to the SD card
Flashed it
Let it cook for ~20 minutes
So it was quite literally a blank slate.
AntonX said:
There was a possible problem with 1.0.3 that I pulled off. The current one that I re-uploaded - I tried to install in on both fresh phone (after factory reset) and on top of a running ROM , everything seemed fine.
The problem was with framework-res.apk. I had to resign in because I changed some permissions in AndroidManifest.xml (related to CIQ), but something went wrong the first time.
There is a little bit of controversy with signing of framework-res.apk. Some say it's OK, some say the original cert should be kept. Maybe somebody else would chime in and tell me if I screwed it up or not.
Click to expand...
Click to collapse
I appreciate all of your hard work. When I get the chance I'll download the latest, follow my steps above, & let you know what I find.
stephen_w said:
I appreciate all of your hard work. When I get the chance I'll download the latest, follow my steps above, & let you know what I find.
Click to expand...
Click to collapse
Wow, you really wiped everything from your phone
I'd appreciate if you send me the log. All you need to do is to save the file with "adb logcat -d >MyLogFile.log" after couple of minutes of this black screen. On an factory reset phone ODEXed ROM should boot very fast the first time because it doesn't have to build Dalvik.
I just tried downloading from my own link and reinstalling, everything seems OK. I also tried installing after full phone reset yesterday, it went fine too. I don't want to reset and restore everything anymore, too lazy
If it proves to be the certificate in the framework-res.apk, I may need to put the original AndroidManifest.xml back.
Hey Anton,
You can snag the logcat from here. In case anyone wants them & to clarify what I did, here are the steps I followed (similar to above but more detailed):
- Boot into CWM
adb reboot recovery- Disable voodoo lagfix
- voodoo lagfix- disable lagfix- /system lagfix off- Reboot
- Create a backup directory structure on your PC (mine is in C:\Users\username\Downloads\SGS4G)
mkdir backupscd backupsmkdir efs nandroid sdcard- Backup /efs to your PC
cd efsadb pull /efs/- Backup /sdcard to your PC
cd ..\sdcardadb pull /sdcard/- Boot into CWM
adb reboot recovery- Wipe cache
- wipe cache partition- Wipe Dalvik cache
- advanced- Wipe Dalvik Cache- Wipe battery stats
- Wipe Battery Stats- Create a nandroid backup
- +++++Go Back+++++- backup and restore- backup- Copy the backup to your PC
cd ..\nandroidadb pull /sdcard/clockworkmod/backup/- Format /data
- mounts and storage- format /data- Format /sdcard
- format /sdcard- Format /system
- format /system- Reboot into CWM (necessary for CWM to see the sdcard contents)
- +++++Go Back+++++- advanced- Reboot Recovery- Copy the ROM to the sdcard (this is from the directory in which the ROM is located on your PC)
adb push ROM-sms-T959V-GB2.3.6-antsvx.1.0.3.zip /sdcard/- Flash the ROM
- install zip from sdcard- choose zip from sdcard- ROM-sms-T959V-GB2.3.6-antsvx.1.0.3.zip- Reboot & let it sit for ~10 minutes
Sorry for the lengthy post, but I wanted to ensure there was transparency in what I did.
stephen_w,
Seems that it's not framework-res.apk issue, it's not complaining about any certificates.
A lot of unknown permissions in the log, but it's OK, we've removed some of the system packages that grant those permissions but they do more harm than good in the end.
The crash has something to do with that: *** FATAL EXCEPTION IN SYSTEM PROCESS: PowerManagerService. Hm......
Question. If after loading the ROM you shut down completely (power off) first and then boot instead of rebooting right from CWM, will it still do the same?
Btw you don't have to clean everything that extensively. Just do factory reset to erase /data and flash. Dalvik and /cache are cleared but the installer, the /system is completely overwritten anyway.
Weird...it flashed fine for me with no wipe....
I did move on and never gave it a break in....but it did work
Sent from my SGH-T959V using xda premium
AntonX said:
stephen_w,
Question. If after loading the ROM you shut down completely (power off) first and then boot instead of rebooting right from CWM, will it still do the same?
Btw you don't have to clean everything that extensively. Just do factory reset to erase /data and flash. Dalvik and /cache are cleared but the installer, the /system is completely overwritten anyway.
Click to expand...
Click to collapse
I usually don't do it that extensively at all. I was writing a process for myself in case I wanted to really clean it out So this gave me a good excuse to test it. I was having some weirdness which prompted me to write the instructions for myself.
I haven't tried shutting it down after the install. I can certainly try that for you, if you like.
So its something to do with power management. That's weird. Is there something we did to our phones before that is causing the issue now?
Sent from my SGH-T959V using xda premium
Lawful123 said:
So its something to do with power management. That's weird. Is there something we did to our phones before that is causing the issue now?
Click to expand...
Click to collapse
Doubtful. Nothing I can think of, off-hand. I have to wait until later this afternoon/evening to reflash it and try powering off vs. rebooting from recovery. If you have the chance, please feel free and let us know what happens.