• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root [ROM] Sleipnir v2.4.0.5 - 10/24/13 - VM & SPRINT

I'd suggest you try to do a clean fresh install: Wipe data, system, cache and dalvik; flash the rom having first made sure to match the md5 sum; then boot it up and make sure the basics are working before trying to set it up or restore any apps or data.

The more steps you take the more likely things are to go wrong. Keep it simple at first, and if you have the space and the inclination; make a nandroid once you get a fresh boot, and another once you get all your apps and data set up in a non-crashy way.

It can also speed things up to make a flashable zip of some of the core programs you use, and once you're sure that it's booting properly, flash the zip and save yourself the time of installing the apks manually.
 
miediev said:
I'd suggest you try to do a clean fresh install: Wipe data, system, cache and dalvik; flash the rom having first made sure to match the md5 sum; then boot it up and make sure the basics are working before trying to set it up or restore any apps or data.

The more steps you take the more likely things are to go wrong. Keep it simple at first, and if you have the space and the inclination; make a nandroid once you get a fresh boot, and another once you get all your apps and data set up in a non-crashy way.

It can also speed things up to make a flashable zip of some of the core programs you use, and once you're sure that it's booting properly, flash the zip and save yourself the time of installing the apks manually.
Click to expand...
I didn't get the chance to do anything because the messages would not stop,
So I just pulled the battery reboot into recovery & restored CM9 from my backups!!
 
The hard truths are this. Wipe...wipe and wipe again, unless expressly stated otherwise by the developer. I'm a crack flasher on my Nexus and I always fo a full wipe regardless. Its easier to restore apps and set up home screens than troubleshoot FC's and bad app behavior. Just my personal experience and preferences. (Not to mention the possibility of corrupted data from titanium etc.)
 
I haven't gone through all of the pages in the thread, but I am having a problem (unsure whether it's related to Sleipnir). My main app screen will intermittently dim and lock up (can't open any apps and buttons don't work). My only choice then is to reboot, which temporarily fixes it. Can anyone shed any light on this?
Thanks
 
Pickngrin said:
I haven't gone through all of the pages in the thread, but I am having a problem (unsure whether it's related to Sleipnir). My main app screen will intermittently dim and lock up (can't open any apps and buttons don't work). My only choice then is to reboot, which temporarily fixes it. Can anyone shed any light on this?
Thanks
Click to expand...

What clock speed are you running?
 
I have a suggestion for this rom.
Status bar brightness adjustment, like in CM. It would make hideing phones in school more easy and faster.
Or at least it would for me. :D
 
starkraving said:
The hard truths are this. Wipe...wipe and wipe again, unless expressly stated otherwise by the developer. I'm a crack flasher on my Nexus and I always fo a full wipe regardless. Its easier to restore apps and set up home screens than troubleshoot FC's and bad app behavior. Just my personal experience and preferences. (Not to mention the possibility of corrupted data from titanium etc.)
Click to expand...
I'm a "serial" flasher as well & I always wipe, wipe, wipe & never restore anything from "TB", I keep "TB" for emergencies" otherwise I restore "Data" in recovery....
Thanks for your help!!
 
This is just sort of a blanket reply:

Since the three of you are having unique issues that haven't come up before, the installation instructions for new-comers or ROM-switchers need to be followed verbatim, and always make sure that the MD5 sum is verified, /cache and dalvik-cache are wiped, /system is wiped, and /data is wiped. Flash the ROM, then run Fix Permissions. Otherwise, try changing your CPU clock speed and/or the governor. Most or all of the problems the three of you run into sound as though either an app is causing the problem, the ROM corrupted on downloaded, or not all of the necessary steps were followed for installation. And, sometimes, not even the proper method for restoring data post-ROM switch will work (it isn't foolproof, but compared to the near-zero percent chance of TiB working post-ROM switch, it's a much better chance). If you're switching from CM to Sleipnir, or vice versa, I suggest doing a Factory Reset because it's likely that, giving the different Android versions that the /data partition existed on/within, retaining it is likely going to cause problems.

If all of this has been done and the problems are still coming up, let me know. As far as I can tell though, no one else seems to have run into these problems - and the ROM's current build has been downloaded a combined number of 169 times, with only three instances of problems reported so far. If I can solve those bugs, I would love to! :)
 
Artine said:
This is just sort of a blanket reply:

Since the three of you are having unique issues that haven't come up before, the installation instructions for new-comers or ROM-switchers need to be followed verbatim, and always make sure that the MD5 sum is verified, /cache and dalvik-cache are wiped, /system is wiped, and /data is wiped. Flash the ROM, then run Fix Permissions. Otherwise, try changing your CPU clock speed and/or the governor. Most or all of the problems the three of you run into sound as though either an app is causing the problem, the ROM corrupted on downloaded, or not all of the necessary steps were followed for installation. And, sometimes, not even the proper method for restoring data post-ROM switch will work (it isn't foolproof, but compared to the near-zero percent chance of TiB working post-ROM switch, it's a much better chance). If you're switching from CM to Sleipnir, or vice versa, I suggest doing a Factory Reset because it's likely that, giving the different Android versions that the /data partition existed on/within, retaining it is likely going to cause problems.

If all of this has been done and the problems are still coming up, let me know. As far as I can tell though, no one else seems to have run into these problems - and the ROM's current build has been downloaded a combined number of 169 times, with only three instances of problems reported so far. If I can solve those bugs, I would love to! :)
Click to expand...
After following the instructions to the letter, Problems are still there, (although not as many force closes ) It's specific to this device I'm sure...It only wants to run CM9....lol
Thanks for your help

I will however keep trying & report back what happens
 
cfreeman90 said:
After following the instructions to the letter, Problems are still there, (although not as many force closes ) It's specific to this device I'm sure...It only wants to run CM9....lol
Thanks for your help

I will however keep trying & report back what happens
Click to expand...

That's.... weird. What is force closing, by the way, specifically?
 
So I had to do several things just to get the newest version to work, and it fixed about half or more of my problems. Something I had a big problem with was when just updating to the newest Sleipnir, the phone would go into a bootloop shortly after startup. This usually would happen around the time the phone would do the media check for the SD card. I came to the conclusion that Sleipnir is a lot like me and really groggy when it first wakes up and doesn't feel like dealing with a lot of crap at once when waking up in the morning. I picked up two programs:
Rescan Media Root
Gemini App Manager
Using the Rescan Media Root I stopped media scan at startup. That took care of a lot of boot up issues. Then I tackled the apps that just like to start up as soon as the phone comes on. This is where the Gemini App Manager comes in. Using it I went in and shut off all of the apps that started up right away that I didn't need until asked for. Turns out, all of them were set to wake up with the phone lol. I don't need Simpsons, Tapped Out on startup do I? So for those having issues I would suggest:
Titanium back up apps only
Nandriod as always
Do all your wipes and start clean with a fresh install
Go in and download the two apps listed above
Set the media scan to stop starting on boot up
Titanium backup JUST THE APPS, not system data. If possible get your google related items downloaded first through the playstore since google system settings get cranky otherwise.
Use the Gemini App Manager afterwords and stop any unnecessary apps from starting on boot.
If all goes well reset the phone and it should startup with no issues.

This method might not fix everything but it helped me so I thought I would put this up just in case.
 
You must log in or register to reply here.
Back
Top Bottom