• 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

ifytbairz said:
I haven't, but I've reinstalled the ROM multiple times, still get this issue
Click to expand...

If there was an issue with your download, then reinstalling the same download will not fix your issue. Check the MD5sum and if it is not the same, redownload the rom then check the MD5sum again. There are free apps on the Play Store that can be used to check the MD5sum.
 
ifytbairz said:
i keep getting 'Error while recovering /data!' in recovery. what's up with that?
Click to expand...

Good question. It sounds like your Nandroid backup may be corrupt either when it was made or sometime afterward by an app or something. CWM isn't perfect, just mostly. You can always make another backup, however, but that definitely sucks and I'm sorry to hear that you were unable to restore your /data partition. It happens to the best of us :/ But, hey; we're dealing with an older version of Android here, after all :p

ron330 said:
i have 2.4.0.3 and i'm still having the reboot issue what can i try to fix it?
Click to expand...

That's unfortunate! You can try anything aforementioned in this thread, and also the stuff that is highly detailed in the OP and in the ROM's installation instructions :)

Did you...
  1. Follow the proper installation instructions provided in the OP by:
    • Downloading the correct version of the ROM for your carrier?
    • Verifying the MD5 or SHA1 sum provided for this ROM, prior to installing it, after you copied the .zip to your phone?
    • If you were switching to Sleipnir from a different ROM altogether, did you wipe /data before installing Sleipnir?
    • Fixing Permissions in CWM after installing Sleipnir?
  2. Have too high of a maximum frequency in your CPU tuner app of choice, and tried lowering it down a notch or two, three, or more, post-install?
  3. Have too low of a minimum frequency in your CPU tuner app of choice, and tried raising it up a notch or two, three, or more, post-install?
  4. Get a crash after trying to update or install an app through Google Play when it needed to update itself, and reboot back into CWM to wipe /cache, dalvik-cache, and running Fix Permissions?
  5. Did you try wiping the battery stats?
  6. Etc.? :)
 
Artine said:
Good question. It sounds like your Nandroid backup may be corrupt either when it was made or sometime afterward by an app or something. CWM isn't perfect, just mostly. You can always make another backup, however, but that definitely sucks and I'm sorry to hear that you were unable to restore your /data partition. It happens to the best of us :/ But, hey; we're dealing with an older version of Android here, after all :p



That's unfortunate! You can try anything aforementioned in this thread, and also the stuff that is highly detailed in the OP and in the ROM's installation instructions :)

Did you...
  1. Follow the proper installation instructions provided in the OP by:
    • Downloading the correct version of the ROM for your carrier?
    • Verifying the MD5 or SHA1 sum provided for this ROM, prior to installing it, after you copied the .zip to your phone?
    • If you were switching to Sleipnir from a different ROM altogether, did you wipe /data before installing Sleipnir?
    • Fixing Permissions in CWM after installing Sleipnir?
  2. Have too high of a maximum frequency in your CPU tuner app of choice, and tried lowering it down a notch or two, three, or more, post-install?
  3. Have too low of a minimum frequency in your CPU tuner app of choice, and tried raising it up a notch or two, three, or more, post-install?
  4. Get a crash after trying to update or install an app through Google Play when it needed to update itself, and reboot back into CWM to wipe /cache, dalvik-cache, and running Fix Permissions?
  5. Did you try wiping the battery stats?
  6. Etc.? :)
Click to expand...

Okay I was getting reboots on the last version of this ROM. It def happened more when I had it plugged into the charger actually....

Updating to the latest right now, and I'm following the First Time install instructions to a T. Even checked the MD5 and SHA1 AFTER the file was on my Android device.

Nothing was backed up, so this is a FRESH FRESH install.

I'll report any issues I encounter.

I won't be around long though, probably a week at most. Getting into that Galaxy S2 action here pretty soon.

Well Flashing an Epic 4G Touch Sprint version to Virgin Mobile anyway.
 
kaivorth said:
Okay I was getting reboots on the last version of this ROM. It def happened more when I had it plugged into the charger actually....

Updating to the latest right now, and I'm following the First Time install instructions to a T. Even checked the MD5 and SHA1 AFTER the file was on my Android device.

Nothing was backed up, so this is a FRESH FRESH install.

I'll report any issues I encounter.

I won't be around long though, probably a week at most. Getting into that Galaxy S2 action here pretty soon.

Well Flashing an Epic 4G Touch Sprint version to Virgin Mobile anyway.
Click to expand...

That's not good! Thank you though; I look forward to any and all updates! :)
 
On Google Navigation, how do you change the gray background color after you type in an address and it asks you "Did you mean?". It's also the same color after you use "talk to text". The gray background with black font is very tough to read at times.

TIA
 
I seem to have an issue. For some reason, my OE won't connect to a WEP network. No problems with WPA/WPA2, but my friends' ISP locked down their router/modem, so they can't change it. Any ideas?
 
Sinner67 said:
If there was an issue with your download, then reinstalling the same download will not fix your issue. Check the MD5sum and if it is not the same, redownload the rom then check the MD5sum again. There are free apps on the Play Store that can be used to check the MD5sum.
Click to expand...

okay. I redownloaded the ROM, verified the MD5 is a match, reinstalled from the new download, still get this issue sometimes. Also, I get random reboots now as well..
 
I as well have been experiencing random reboots. I just got a reboot during a call. In mid sentence my phone just rebooted. **EDIT** not sure whats happening but i can't make any phone calls with out getting a reboot 10 seconds into the conversation. as far as i can get is " hey how are" the it reboots. it's happened 2 times now.
 
LOL artine I'm not a newbie. I've been running your Rom since I rooted man like last yearish. I formatted cache and delvik cache and fixed permissions and so far it seems to be OK. Hopefully that fixed it. This is my favorite Rom. Even with the occasional hiccups.
 
Co1dNight said:
Does it support WEP encryption?
Click to expand...

The option is there when I'm setting up the network connection, so I assume that it's supposed to. Just for some reason, it won't connect to that WEP network. Haven't tried with any others, nobody else I know uses WEP, but like I said, their router is locked down, they can't change anything.
 
Is it possible to flash this from then flash the custom Kernal from cm9 and still be able to use the camera nd if its stable has anyone done this
 
ronii said:
Is it possible to flash this from then flash the custom Kernal from cm9 and still be able to use the camera nd if its stable has anyone done this
Click to expand...

I wouldn't recommend using a kernel from 2.3 on 4.0 or 4.0 on 2.3, because there were A LOT of changes from 2.3 to 3.0 to 4.0 so it could give you a hard time.
 
sinkist77 said:
LOL artine I'm not a newbie. I've been running your Rom since I rooted man like last yearish. I formatted cache and delvik cache and fixed permissions and so far it seems to be OK. Hopefully that fixed it. This is my favorite Rom. Even with the occasional hiccups.
Click to expand...

I know XD Lol :)

If not, let me know. I'm more intrigued by software issues than hardware issues at this point :p

ymerejo42 said:
The option is there when I'm setting up the network connection, so I assume that it's supposed to. Just for some reason, it won't connect to that WEP network. Haven't tried with any others, nobody else I know uses WEP, but like I said, their router is locked down, they can't change anything.
Click to expand...

See my above post. Also, if they purchased their router separately from their modem, it's a fair bet it might not actually be locked down. I'm not too sure, but in my experience, they can't lock down your router if it was purchased separately, and not through them. If that is the case, then they can customize the router's settings and change the encryption type fairly easily. Otherwise, if this is a two-in-one and/or purchased directly from the ISP... yay? :p
 
Well I've had one reboot today. So what would cause a reboot? I would love to be able to work things out myself but I don't even know where to start.
 
Artine said:
See my:):pabove post. Also, if they purchased their router separately from their modem, it's a fair bet it might not actually be locked down. I'm not too sure, but in my experience, they can't lock down your router if it was purchased separately, and not through them. If that is the case, then they can customize the router's settings and change the encryption type fairly easily. Otherwise, if this is a two-in-one and/or purchased directly from the ISP... yay? :p
Click to expand...

Two-in-one leased from their ISP, to be exact.

Also, on Firefox Beta for Android, I can't delete those smileys. Annoying.
 
You must log in or register to reply here.
Back
Top Bottom