[DO YOU HAVE FILES]I Need EVERYONE's HELP!!!

[redbaron2005]

ATTN: I NEED EVERYONE'S HELP!!! PLEASE!!!​

Here's what I need you to do!​

Find and Search through your PC's and look for any complete or decently stable ROM's, RECOVERY's, KERNEL's and any possible missing links / files / documents for the LG Optimus V regardless of it's version or kernel and Send me WORKING links, files, of anything you got. All the links for this phone are dead... I've checked all over the web. This is still a great phone, and can still be used either with Boost Mobile or simply with a Credit or Debit card. A friend and I plan on revamping this phone to see if we can't bring it back to it's glory. But in order to do so.... Got to have the Archives! Every link is dead.... PLEASE PLEASE PLEASE search around for anything LG Optimus V, VM670, Thunderc Optimus S is also appreciated.

THANK YOU FOR YOUR TIME AND PATIENCE

Send them to me, in a PM and or share them with me to my Google Drive via email.... PM for email... thanks

You may post links here only as long as the owner hasn't pulled the files for TOS Violations.
To be honest.... if your unsure, just PM the links.
I'm taking any and all files that are DEAD links
anything I can redownload as of today's date, will be unwanted.
But don't let that discourage you from SHARING THEM AWESOME FILES AND RE-UPLOADED LINKS!
THANK YOU THANK YOU THANK YOU!!!

:good::laugh:

 

[bigsupersquid]

I left a reply regarding KitKat and twrp in the hijacked mmarz thread.
as far as active links, here's one:
https://sites.google.com/site/bobzhomeroms/

also be aware when messing with recovery and roms on the Optimus V, you'll be fine if you have the original display (I think that's the Hitachi but may be the Novatek.)
it's been so long I forget which was which.
but during production, lg decided to add a different screen manufacturer, updated their kernel source with a driver to handle both.
older kernels than that will only drive the original screen.
I made a big stink about it for a while, while there was still development going on, and eventually people started patching their kernel configs to turn on the newer screens too, once everyone realized I knew what I was talking about.

so if you have the original screen model, you're golden. if you have a new screen and flash an older rom or recovery (like xionia, for example) you'll get a black screen with backlight instead of display output and be left with nothing but adb or poking around at the display blind.
fair warning.

 

[timjames474]

Here's some Optimus S stuff I used to use,was able to download from here today, https://archive.midnightchannel.net/zefie/files/cell/LGLS670/

 

[timjames474]

I left a reply regarding KitKat and twrp in the hijacked mmarz thread.
as far as active links, here's one:
https://sites.google.com/site/bobzhomeroms/

also be aware when messing with recovery and roms on the Optimus V, you'll be fine if you have the original display (I think that's the Hitachi but may be the Novatek.)
it's been so long I forget which was which.
but during production, lg decided to add a different screen manufacturer, updated their kernel source with a driver to handle both.
older kernels than that will only drive the original screen.
I made a big stink about it for a while, while there was still development going on, and eventually people started patching their kernel configs to turn on the newer screens too, once everyone realized I knew what I was talking about.

so if you have the original screen model, you're golden. if you have a new screen and flash an older rom or recovery (like xionia, for example) you'll get a black screen with backlight instead of display output and be left with nothing but adb or poking around at the display blind.
fair warning.

So the JB rom boots okay,how do i setup Sprint apn/keylayout?

 

[redbaron2005]

I left a reply regarding KitKat and twrp in the hijacked mmarz thread.
as far as active links, here's one:
https://sites.google.com/site/bobzhomeroms/

also be aware when messing with recovery and roms on the Optimus V, you'll be fine if you have the original display (I think that's the Hitachi but may be the Novatek.)
it's been so long I forget which was which.
but during production, lg decided to add a different screen manufacturer, updated their kernel source with a driver to handle both.
older kernels than that will only drive the original screen.
I made a big stink about it for a while, while there was still development going on, and eventually people started patching their kernel configs to turn on the newer screens too, once everyone realized I knew what I was talking about.

so if you have the original screen model, you're golden. if you have a new screen and flash an older rom or recovery (like xionia, for example) you'll get a black screen with backlight instead of display output and be left with nothing but adb or poking around at the display blind.
fair warning.

I remember from back in the day we had the screen problem... You fixed and addressed it...
But some ROM I baked up didn't work even with the fix... I had the Kernel made with the ROM and the screen still didn't work... I'm working past that now as a matter of fact.
Wasen't it the Pickasticks Recovery... or a file... or something either way I found your old post...
Worked with LesileAnn with somethings too Haha Thank you again for the long lost files!!

So the JB rom boots okay,how do i setup Sprint apn/keylayout?

I might be able to help you, Tell me what ROM exactly and what it says is WORKING and NOT WORKING on the main page of the post... or a link... It could be like you said a simple set up.
But I do remember having to change something to get other carriers to work. Because it was only a CDMA phone. No GSM. If I remember correctly

 

[bigsupersquid]

I remember from back in the day we had the screen problem... You fixed and addressed it...
But some ROM I baked up didn't work even with the fix... I had the Kernel made with the ROM and the screen still didn't work... I'm working past that now as a matter of fact.
Wasen't it the Pickasticks Recovery... or a file... or something either way I found your old post...
Worked with LesileAnn with somethings too Haha Thank you again for the long lost files

you have to crack open the boot.img and replace just the kernel with a working one. it's "fun."
and finding a working kernel for the newer screens now as a standalone download is really iffy. (actually, see next post. I found /one./)
if you have another jb rom with working screen you can split that boot.img and yoink its kernel for the one that doesn't have more than a backlight. you can also plop that picasticks kernel from below into any blackscreen recovery images too, they split and recombine just like a boot image.
a lot of people call the boot.img a kernel, but it's actually a combination of kernel and ramdisk.
you can use osm0sis AIK tools to disassemble and reassemble boot.img relatively painlessly.
I'm happy to promote osm0sis's work. he does great things. drop him a donation if you're so inclined, he certainly deserves it.
by the way, don't try to insert the 3.0 kitkat kernel into anything else... it probably won't boot. jb is the best bet to try it on though, thekraven nudged me into porting that kernel from the p500 for his jb roms. I'm glad he did, because the experience has been very useful on other devices.

 

[bigsupersquid]

ok, here's my gift to y'all.
https://www.androidfilehost.com/?w=files&flid=317344
archive of the primary goodies from my old failing NTFS external drive. We'll see how long it takes for androidfilehost to arbitrarily delete them like they did every other file I ever uploaded there for the optimus S/V with no warning or acknowledgment. they never even answered multiple support requests trying to find out why... I'm guessing they decided to clean their servers of things uploaded before a certain date, but no telling since they wouldn't answer.

in the kernels subfolder is a picasticks kernel i built for the old/new screens.
multiple recoveries. some are old and may blackscreen on newer devices, fair warning. some roms will be the same way. the twrp's may or may not have reversed system/userdata like my os2sd twrp, try and see. they should at least be good on any model optimus s/v screen.
several roms, including one harmonia, and PAC-rom from thekraven.
others folder has V drivers... and swype flashable zip, ripped probably from GB stock, maybe from froyo stock.
also multirom recoveries and installer if you like multiboot. thread here
have fun.

 

[timjames474]

I remember from back in the day we had the screen problem... You fixed and addressed it...
But some ROM I baked up didn't work even with the fix... I had the Kernel made with the ROM and the screen still didn't work... I'm working past that now as a matter of fact.
Wasen't it the Pickasticks Recovery... or a file... or something either way I found your old post...
Worked with LesileAnn with somethings too Haha Thank you again for the long lost files!!


I might be able to help you, Tell me what ROM exactly and what it says is WORKING and NOT WORKING on the main page of the post... or a link... It could be like you said a simple set up.
But I do remember having to change something to get other carriers to work. Because it was only a CDMA phone. No GSM. If I remember correctly

i got data fine it was more the keys that was bugging the **** outta me
this one here from another link posted here,i use Tello,which uses Sprints MMSC,and yes i figured out actvating data just last week! Downgrade to ZVD and let HFA run. Thats literally it
forgot the link https://sites.google.com/site/bobzhomeroms/vm670jb

 

[bigsupersquid]

i got data fine it was more the keys that was bugging the **** outta me
this one here from another link posted here,i use Tello,which uses Sprints MMSC,and yes i figured out actvating data just last week! Downgrade to ZVD and let HFA run. Thats literally it
forgot the link https://sites.google.com/site/bobzhomeroms/vm670jb

you need the correct .kl file, I've probably got one stashed somewhere.
it switches the two keys in software.
it's funny, because both the virgin and sprint phones have the same board, but the firmware reverses which key is read as which.
I'll look around and try to find the .kl file for you. androidfilehost deleted my flashable zips with those along with everything else for the S/V a while back as I was complaining about above, or I'd just point you there.

 

[timjames474]

you need the correct .kl file, I've probably got one stashed somewhere.
it switches the two keys in software.
it's funny, because both the virgin and sprint phones have the same board, but the firmware reverses which key is read as which.
I'll look around and try to find the .kl file for you. androidfilehost deleted my flashable zips with those along with everything else for the S/V a while back as I was complaining about above, or I'd just point you there.

if you manage to find it,do let me know! TIA

 

[bigsupersquid]

if you manage to find it,do let me know! TIA

I can pull the one from the rom on my V and switch the keys.
no flashable zip, you'll have to use adb to install it, I'll post the commands
it's home and menu that are swapped if I remember right, is that correct?
it's actually a .kcm file, I've messed with so many devices I mix things up sometimes.

 

[timjames474]

Sorry for being gone so long,yes those are the keys,my Optimus S had been dropped one time too many but i finally replaced it and am still interested in getting those files and commands

 

[bigsupersquid]

alright, I'll pull the file and swap those two keys.
I don't remember any oddball locations for the file across different roms... but since it has been a while since I did anything much with this device, just to make sure, I'll add a test to the instructions to make sure it's going into the right location.

 

[timjames474]

alright, I'll pull the file and swap those two keys.
I don't remember any oddball locations for the file across different roms... but since it has been a while since I did anything much with this device, just to make sure, I'll add a test to the instructions to make sure it's going into the right location.

Seems that it always goes to /system/usr and the two folders are keylayout and key(something else idr) the one that i cannot remember the name for is where the .kcm files are at

 

[bigsupersquid]

since harmonia has two applicable .kl files, thunder.kl and thunder_keypad.kl I'm not sure which to mess with.
they're in /system/usr/keylayout/
the process is to adb pull the thunder*.kl file from your working ROM (whichever file it is, thunder.kl or thunder_keypad.kl,) back it up on computer with a copy in case you mess it up, then:
change all instances of HOME to MENU and MENU to HOME. I can't remember how much difference the WAKE and WAKE_DROPPED field makes, but you can switch those too, or leave that alone and try it.
if you're using M$ window$, don't push the enter/return key while editing unless you're editing with notepad++, the default editor screws up carriage return line feed character codes. mac or linux shouldn't dork up the CRLFs.
chmod 644 the file after pushing it back, and chown root:root
I'd have to grab it from one of the cm rom files I uploaded for a better reference, and I'd rather not re-download them or try to get my failing external drive they're on to mount at the moment.

 

[timjames474]

since harmonia has two applicable .kl files, thunder.kl and thunder_keypad.kl I'm not sure which to mess with.
they're in /system/usr/keylayout/
the process is to adb pull the thunder*.kl file from your working ROM (whichever file it is, thunder.kl or thunder_keypad.kl,) back it up on computer with a copy in case you mess it up, then:
change all instances of HOME to MENU and MENU to HOME. I can't remember how much difference the WAKE and WAKE_DROPPED field makes, but you can switch those too, or leave that alone and try it.
if you're using M$ window$, don't push the enter/return key while editing unless you're editing with notepad++, the default editor screws up carriage return line feed character codes. mac or linux shouldn't dork up the CRLFs.
chmod 644 the file after pushing it back, and chown root:root
I'd have to grab it from one of the cm rom files I uploaded for a better reference, and I'd rather not re-download them or try to get my failing external drive they're on to mount at the moment.

I was able to pull from CM7 for LS670 and swap,fix perms and voila! Also noticed getting gapps to work on BobzHomes jb is a PITA,as there appears to be no setupwizard so it thinks its in setup,but its not. i looked at build.prop and shut off the setupwizard bypass but nothin. Nearing the point where i say frick gapps at this point

 

[bigsupersquid]

I was able to pull from CM7 for LS670 and swap,fix perms and voila! Also noticed getting gapps to work on BobzHomes jb is a PITA,as there appears to be no setupwizard so it thinks its in setup,but its not. i looked at build.prop and shut off the setupwizard bypass but nothin. Nearing the point where i say frick gapps at this point

yeah, gapps suck. and it's even worse dealing with them on a device which has such a small system and data partition.
you might look into microg. I prefer it anyway.
glad you got the keyswap to work.

 

[timjames474]

yeah, gapps suck. and it's even worse dealing with them on a device which has such a small system and data partition.
you might look into microg. I prefer it anyway.
glad you got the keyswap to work.

MicroG has a broken login,the login box is all the way off screen for me,but ive since gotten a modern phone at the gentle prodding at Tello anyway