Yes I know, but that only changes the permission's to rwxr-xr-x
We need rwsr-sr-x
from google, here
The Guide - Setuid & Setgid
Cool, that's just what we need. I appreciate the link too.
EDIT: After reading the page, why is the s even needed, why would x not work in every application?
If i read right, it's the 'setuid' function, which passes down the user id from the calling program (in this case, setuid to root, for full permissions)
That's exactly what it means. I may not be a coder, but my first email client was pine.
RE: Post #22 in this thread, step 1:
It says two recoveries are needed. I intend to replace the recovery I have (IHO) with xion, as it is recommended for the ROM I intend to use (Harmonia).
At what point do I install the second recovery (asopCWMod) - and what is the purpose of each?
Actually, Leslieann fixed Harmonia some time back to work with newer recoveries, and I have used the iho recovery to flash Harmonia with no problems.
You don't need the aospc recovery.
Hey bigsupersquid. I need to edit post #22 . The Question: is the Xionia recovery version 1.2518.6 now compatible with the Novatek screens? I can't find anywere in the dev's thread that suggests it is.
the original optimus s and optimus v phones were both novatek screens.
after VC/VD baseband came out for the optimus s, those started getting built with hitachi screens.
it was a few months later that those junkers started getting installed into the optimus v as well.
xionia .4 was built before the hitachi screens were being used, and .6 was built to fix the black screen problems on the (new at the time) optimus s phones with the hitachi screen.
the fix in the kernel enables both the novatek and hitachi screen drivers.
the original lg kernels for the s and v both only use the novatek driver, even though the hitachi driver is included in the kernel source. It's just not enabled in the earlier builds; but it's only one setting to change in the kernel .config, to fix the problem.
if you dig through zefie's xionia kernel thread deep enough, you can find where the black screen problem originally showed up and how he figured out that lg's VC/VD kernel release for the optimus s fixed the problem.
one potential issue, is that zefie built a VM specific version of xionia kernel and xionia recovery... however, he never built a release for VM with the hitachi driver enabled. So the xionia kernel and recovery that works with hitachi screens is a optimus s build, not an optimus v build.
it doesn't seem to cause major problems running s software on the v, but there are tiny differences in the mtd code in the kernel (and a few other pieces of the kernel as well) between the s and v; plus it swaps the home/menu buttons.
if it matters, both the optimus s and optimus v both use the exact same hardware board. The numbers on the optimus v board say "LS670" which is the optimus s model number. I verified that myself tearing down two of the OV's, one novatek and one hitachi.
I'm still confused. When I rooted this phone back in early August everybody was advising against the 1.2518.6 version for the "V", said the only one that would work with the "V" was the 1.2518.4 version.
The last time the 1.2518.6 post was edited was 03/17/2011
At what time and how was the 1.2518.6 version made compatible with the Novatek screen "V"s?
I need to know that if I advise members to put the 1.2518.6 version on the sd card to get out of a potential recovery loop should it occur, it will in fact work for this purpose on the versions with the Novatek screen.
I don't want to make things worse for them.
it's advised against because it's an optimus s version, not a v version.
some people have issues with it. like some people can't get usb mass storage with the latest xionia kernel. It's weird, some v's are tweaky.
I know from testing that the .6 has the right display drivers.
It's what I was using until messing with multirom.
I've tried .6 on old and new v's myself to verify. That's why it's in the blackscreen fix thread on AC.
from [Custom Recovery] Xionia Clockwork (CWMA v1.2518.6) - Android Forums at AndroidCentral.com, at the very top of the post.
the only reasons anymore to use xionia are the bootloop fix and flashing ancient roms with amend scripting (newer roms use edify scripting)
iho recovery is more suitable for actual use, since it doesn't seem to be as tweaky.
by the way, I haven't found a single kernel built for the optimus s or optimus v that doesn't work with the novatek screens. Just the stinking hitachi screens have trouble (at least partially because lg never released new source code after they started putting 2.2.2 on v's, and partially because older OV software was built before the hitachi screens were being installed in these phones and the devs have vanished.)
Ok, that was just the info I needed to convince me that it's ok to use the 1.2518.6 and the VM670NH in the post for both screens. The VM670NH for the primary and the 1.2518.6 for the recovery loop, stuck in recovery, boot loop issues. I use the VM670NH on my phone(Novatek screen).
Thanks. Didn't mean to sound like such a pain in the rear,80 something posts and I wasn't finding anything positive about it and the "V". Plenty for other devices.
ah, no problem. no pain, no gain!
full explanations are good for everyone who reads, anyway.
that thread is also in the optimus s subforum, not the v, so lots of v users didn't read or post there.
for reference, here's zefies xionia post in the optimus v subforum...
Xionia Goodies (Optimus V Edition) - Android Forums at AndroidCentral.com
definitely, .4 was the last recovery version he built for the v.
too bad, too, I really liked his work; then he got his optimus smashed and moved to another device.
Updated post. Now if any member goes there they won't be confused. Confusion is the enemy of a newbie. I know, I was confused when I was a newbie, now I have a brick.
Speaking of which, per are discussion, major financial setback will cause me to wait till January. Hope I don't burn this one up before then.
And that, my friend, is why I'm as cautious about testing things on my phone from too far out in left field.
The link is inactive, and will this work with a LG Optimus V?
What link are you referring to?
Not to mention, this part of the forum is nothing but the Optimus V.
Hey brotherswing, I think you need to clean the sleep out of your eyes. Lol
I wasn't the one asking if it works on the phone this forum is dedicated to.
Duh! Ok I get it now (Sound of hand hitting forehead).
ok question when you say put that file onto the root of your sd card use the usb ms toggle i have no clue what ur talking about when i boot recovery all i have is stock recovery how do i get my phone to sync to computer so that i can see my folders!? or cant i! stock recovery and emergency work and im using lg optimus v! HELP ME!!
vtimmy13, it's ok.
We'll walk you through the steps. Just shoot me a private message if you still need someone to help. It will get my attention no matter where I'm at. If my phones on (stays on 24/7) , I'll get the message.
It all started the day when I got my first Android and started digging into threads to see how I could modify the phone structure and make it more "Me". I will never forget that day or the months to follow. Like most Nubs I was gun-ho and ready for the change/challenge. However I skimmed through everything I was looking at for details that pertained to the moment (RIGHT NOW!). Like somehow I was the David Blain of technology because I just bought this sweet ass phone and I now have WILL AND DETERMINATION to make it a great device! I bricked the phone within hours, rendering a $300.00 phone useless. I won't go into details about the process I took but the phone was fried to say the least. Sooooo, I went and bought another phone! Now I HAVE THE POWER BACK! Let's get back to work...Assuming I already knew everything about a cell phone and an Android OS at this point I duplicated my first mistake by trying to flash a ROM for my old phone to a completely different model..Epic fail -.- Lost that phone too. I was always too stubborn to ask for help. When this happened there were no stickies, I realized I had "simply" failed to follow instructions. After doing some home work I went and got another phone, ANDROID and I are together again! I was able to successfully flash the device, have a recovery and back my sh!t up! I own the world at this point! Then all of the sudden I could not use the touch screen...Went into panic mode and reset instead of restore and POW! I was a chicken with it's head cut off and back to square one. Thankfully I knew how to boot into recovery at this point, after spending about nine bills on phones I was able to re-flash my backup, which at the time was uber volatile but I had my phone back. Since then I have been progressively trying to mod new phones without failure. I went from Verizon, AT&T, to MetroPCS and now to Virgin Mobile but I now have a sweet arse phone that follows me instead of me trying to follow it. Oh yeah, I save about $100.00 a month to boot. I wish simple threads like this were stickied when I was trying and dying since searching though thousands of posts for an answer is just lame. Thanks for making this a stickie!
You have my regards from all of the know-it-alls
Separate names with a comma.