• 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

Ok since my phone doesn't like to flash anything for the life of it, is it possible just to use the system ui apk and the framework apk from this rom just to get the look?
 
And if anyone would like to take giantpunes custom kernel and add kernel-level init.d official support (so it isn't ad-hoc / half-working anymore, but completely / fully working instead), let me know and I'll be happy to add it (installing or running Linux from a Live CD is a little out of the question at the moment).

... and yeah. That's all I've got for now, stay tuned :)

Are you asking someone to put in the init.d support or saying if enough want it, you will?
 
Ok since my phone doesn't like to flash anything for the life of it, is it possible just to use the system ui apk and the framework apk from this rom just to get the look?

Sure. Grab framework.jar and android.policy.jar too if you want the extended power menu.
 
There is an issue with soft reboots that I believe are centralized to the Settings.xml modifications I made (the rest of the modifications shouldn't be causing any issues). The official links to v2.3.9 are back up until that issue is fixed (and hopefully fixes some of the issues I too have been experiencing on the build - Airplane Mode and Sound turn on and off randomly every few hours or so, by themselves, which makes no sense at all, which I'm guessing is a conflict between JuiceDefender Ultimate and the modified Settings.xml). Thanks to everyone for the feedback, however :) No, I don't have official internet access yet (not until the 17th, actually), but my girlfriend and I are successfully moved in and in the mean time I'm ad-hocing internet access with 3G. Actually, right now, I'm using her laptop while my computer DBANs, ad-hoced with 3G, while using a bluetooth speaker connected to her laptop that I'm playing the radio through with my phone. To whomever thought the device was a weak budget phone, think again :p

I'll be hard at work on both my computer and on Sleipnir to get some of the kinks worked out. I would leave v2.4.0 up, because some of you aren't experiencing issues, but even I myself am experiencing some issues on v2.4.0 and my best guess is that many of you can run into the same bugs as well at some point - so it i just wiser to take v2.4.0 down for now until I can get the kinks worked out. And if anyone would like to take giantpunes custom kernel and add kernel-level init.d official support (so it isn't ad-hoc / half-working anymore, but completely / fully working instead), let me know and I'll be happy to add it (installing or running Linux from a Live CD is a little out of the question at the moment).

... and yeah. That's all I've got for now, stay tuned :)
You can try this. boot.img download - 2shared I just used dsixda's kitchen. It booted and I tested by doing the steps below and it worked, but then I did the same test with GP's original kernel and it also worked, so idk.

Quote:
Originally Posted by kingsonwongs
how to check init.d work?

for example:

/system/etc/init.d/00test
Code:
#!/system/bin/sh su -c "echo "pass" > /sdcard/pass"
If a file called "pass" will appear on your sdcard it's working
 
Cool thanks! But do I install those to the same way as the other 2?
You just want to use a file manager to replace those files on your phone? I'm not sure if that will work. Make sure you have a nandroid before you do anything. If you're using Aeneas you can just drag the files that you want from Sleipnir and plop them in to Aeneas.

Do you have the latest CWM?
 
You just want to use a file manager to replace those files on your phone? I'm not sure if that will work. Make sure you have a nandroid before you do anything. If you're using Aeneas you can just drag the files that you want from Sleipnir and plop them in to Aeneas.

Do you have the latest CWM?


Yes, and I'm on the stock rom..
 
You can try this. boot.img download - 2shared I just used dsixda's kitchen. It booted and I tested by doing the steps below and it worked, but then I did the same test with GP's original kernel and it also worked, so idk.

What exactly does this change? init.d? Overclocked? I see dsixda's kitchen doesn't list the Elite as a supported device, did you set it up yourself or is there a supported version floating around?
 
As far as the changelog is concerned, I've left it untouched since the v2.4.0 update. Changelogs are posted right above the download links for the ROM, in plain, clear, and easy view/sight.

Hmmmm I guess it wasn't the Version after all. Just installed 3.9 and my data still isn't working. It was working fine before I updated but I was using 3.8 before.

Data issues are unrelated to ROM, since data appears to be working just fine for everyone else (including myself, as I'm able to type this out on a computer using my phone's 3G on an ad-hoc wifi tether).

Are you asking someone to put in the init.d support or saying if enough want it, you will?

Neither, really. Everyone wants it (or probably does, anyway, as it only benefits the device). I'm saying that if someone is able to right now and is willing to, I would recommend modifying giantpune's latest VM kernel (more up to date, and saves having to replace the kernel modules), to add in complete init.d support instead of the ad-hoc support we have now. If no one does and/or is willing to, I will be able to in the next week or so (start working on full init.d support). But if someone is willing to and does it before I get the chance to, I would be happy to add that modified-giantpune's-kernel to Sleipnir.

Yes, and I'm on the stock rom..

I would try following the flashing guide verbatim (word for word) in the CWM FAQ-Guide, making sure you meet the prerequisites, then follow the flashing/installing procedures for your ROM of choice. Your phone should flash ROMs just fine.
 
Data issues are unrelated to ROM, since data appears to be working just fine for everyone else (including myself, as I'm able to type this out on a computer using my phone's 3G on an ad-hoc wifi tether).
Any idea how to fix this? My data stopped working after I installed 4.0. Do you happen to have a link to 3.8? I accidentally deleted it. That was the last one I had and it was working fine. Plus the search button on 3.9 doesn't work.
 
Any idea how to fix this? My data stopped working after I installed 4.0. Do you happen to have a link to 3.8? I accidentally deleted it. That was the last one I had and it was working fine. Plus the search button on 3.9 doesn't work.

4.0? I must have been asleep for a long time :p v2.3.8 is unstable and v2.3.9 is stable and is bug free, aside from the search button being nullified (on a side note, I've always wondered why they ever bothered to implement one for a phone, they aren't even remotely close to having enough capacity to warrant a search-device feature in any respect, unless you have a large number of contacts, which I do, but even then if you drag the scrollbar it scrolls by letter, making finding the contact of choice still a fairly quick process). There are a few threads regarding data issues and how to fix them - and I'd link to them in this post but right now my 3G speeds are, well, 1X and that would take about an hour to pull up each one :p But I would consult any of those threads and see if they might help fix your data issues - but considering that no one else appears to be experiencing them (even on buggy v2.4.0), and I'm using 3G (secretly 1X) just fine, I would say that for sure they're unrelated to the ROM. The only other thing I could suggest is what is always suggested before flashing any ROM, upgrade or not, which is to verify the MD5sum. It's painless, fairly quick, and can save you from having light issues like data problems, to heavy issues like the phone bricking. Which is also why, with every build, there's an MD5sum :)
 
Any idea how to fix this? My data stopped working after I installed 4.0. Do you happen to have a link to 3.8? I accidentally deleted it. That was the last one I had and it was working fine. Plus the search button on 3.9 doesn't work.

Just to make sure the obvious is mentioned.......you did check to make sure your data was still turned on, right??

settings> wireless & networks> Mobile networks> Data enabled (profit!!) :smokingsomb:
 
I reverted back to stock. I've tried everything from a clean install of state near 2 simple upgrades. I retain too many bugs my battery dies very quickly and if I have less than 5 percent the operating system boot loops. I'm sure the fact that these phones being LG's beta for cheaper Hardware could be the factor as well. The keyboard bugs are so frustrating. That I've come very close to smashin this phone several times

Gl all I'm selling this lagged bugged oe and returning to the ov with the ever polished cyanogenmod - gl all and ty for the experience
 
They offered me a free one also but i didn't have it rooted they helped me reset it and i didn't have to get a new one though

Sent from my LG-VM696 using Tapatalk 2
 
sorry to hijack the thread, but do i really need to restore this phone to stock rom for return?

No worries. It's worth noting that some people have returned their OEs while they were still rooted, and never encountered any problems. To completely unroot, though, and be worry-free, follow the steps in the http://androidforums.com/elite-all-...phone-using-official-tools-dll-bin-files.html thread.

EDIT: On a side note, regarding v2.4.0 (revised), it's finished now but I have to wait for some place with wifi - of greater speed than 3G ad-hoc tethering can provide - to open, or for Comcast (I've tried pretty much all of the ISPs, Comcast is my favourite) to come in two days to give us high speed internet, before I can actually upload v2.4.0. Settings.xml has been reverted to the stock version, vanilla, which I believe should relieve all of the issues that presented themselves before. As far as MMS issues are concerned, there is an ongoing VM MMS problem unrelated to ROMs. You may also want to look into a better messaging app such as GO SMS, or Handcent, both of which are free, and much more powerful. If the MMS issues (unable to send and/or receive) present to you, and only on the stock messaging app, post that here once the revised v2.4.0 is up and I'll see what I can do (as usual, if it's happening to many of you, it's likely the app itself, and it will have to be reverted to stock).

On another side note, an interesting idea that would be quite useful, I think, would to write an init.d script (or just a regular script) that runs on boot every month or so to back up SMS/MMS. I've mentioned before that you don't need to pay for an app to do this, since that data is stored in /data/data/com.android.providers.telephony/databases/mmssms.db. Anyone able to do some scripting?
 
Where do i check to verify the wifi is correct (md5 was good), i still can't turn it on after i install my apps?

Sent from my LG-VM696 using Tapatalk 2
 
Back
Top Bottom