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.
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?
Would be interesting to look at the logcat to see where it's stuck.
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.
Quote:
Originally Posted by AntonX
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.
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.
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.
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.
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 backups
cd backups
mkdir efs nandroid sdcard
- Backup /efs to your PC
cd efs
adb pull /efs/
- Backup /sdcard to your PC
cd ..\sdcard
adb 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 ..\nandroid
adb 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)
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.
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.
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?
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.
XDA Developers was founded by developers, for developers. It is now a valuable resource for people who want to make the most of their mobile devices, from customizing the look and feel to adding new functionality. Are you a developer?