LG Viper roms?

[brandonabandon]

someone know of a way to format sd card without reader? i misplaced mine and broke. gparted not recognizing and windows not recognizing for whatever reason. formatted w/ twrp, cwm still not mounting sdcard wtf.

ls shows a rom installs etc, reboots recovery,ls etc reads just bin, bloody hell.lol, does a link exist to the 6.0.1 cwm josh? can you host otherwise? no time for toying, it is nice to know that jb recovery works (sort of) with ics stock kernel though.

 

[Edward McInnish]

misplaced and broke? define broke. if you mean the card itself is literally broken (cracked, chipped, etc) chances are its toast. as for regular formatting, your best option is a reader. lately they are cheap cards though, and your likely to find one with a faster bus speed for cheaper than you paid for your old one.

 

[brandonabandon]

broke financially lol

 

[Edward McInnish]

my pc wont let me edit, so ill reply. Here is a simple thought i didnt think about before:
make a "rom" into an img file we can dd. from there, dd the img files to the correct locations (ensures a flash), then test the rom. since our current issues seem to be with recovery, it might help us test a custom rom without the initial flashing through recovery. granted its more work, but getting a rom stable first is a bit more critical than fighting with recovery, as we coud work with recovery later once we have a known working rom. I can also use root browser to wipe and replace the system from the inside (though dding an img is more likely to succeed)

granted this will only work if the system remains active when files are replaced.

As for the sd card, i it simply corrupted? or is it lost? i dont follow. formatting a card you lost would be impossible lol

 

[brandonabandon]

i misplaced my sdcard reader. my sdcard needs formatted properly, i believe.

 

[brandonabandon]

wow, i seem to have misplaced my usb drive as well.lmao i have 2 pcs and one monitor. one 32 old optiplex very slow i use it for storage and was using for flashing before my new alongside system. anyhow i just formatted my sdcard and backed up to the old pc. then i proceeded to flashing with my cwm which wiped my system and my backups are stored on my other pc. normally this wouldnt be a problem considering i could arrange a network between the two however. i just got a popup stating windows support ends today and i have to be at work in an hour. fml, oh well reflash stock if necessary.

@ed i have the out folder for cm9 build and aokp jb build and will look into dding the rom, might be a few, work and such. i will need to look into the process for doing that also.

edit phew. windows was suggesting some security program ending support. i reflashed gb to get the the bootloader. i tried flashing it @zvi before but without loki, was pointless. i have a slight problem with my sdcard now. after formatting via twrp, and reflashing gb windows xp doesnt recognize sdcard. the drivers install and the device appears but when i click on the drive the window states please insert disk into. anyhow, the format worked as fat32 and ext4, cwm should mount sdcard.

 

[brandonabandon]

Starting recovery on Thu Jan 1 00:53:38 1970 framebuffer: fd 4 (480 x 800) CW - Pastebin.com accurate cwm recovery log. if no partitions mount, why does ls read the system installs? and even more strange, how the system deletes after reboot. any suggestion?

 

[brandonabandon]

Starting recovery on Thu Jan 1 10:10:05 1970 framebuffer: fd 4 (480 x 800) ac - Pastebin.com cwm gb recovery.log. its 4 screens lol doesnt mount /emmc. flashed rom reboots recovery.

 

[Edward McInnish]

yea, i have pretty much lost hope in this device yet again. as i mentioned previously, we know the bootloader locks after updating to ICS. unfortunately no one with the knowlege of rom building bothered to look into the update to figure out what part locks the bootloader and rebuild it to leave it unlocked (possibly even hack in a fastboot that is useful for a change). now we have gotten loki to bypass the bootloader, but even they are not working properly. the only way we are going to get this device anywhere it to pretty much build from almost scratch leaving only the drivers in the build. pretty much build an entire system to our specifications. I dont have the knowledge or ability, and from the looks of things, neither does most of the community. even i know any project like this is next to impossible without knowledgeable help, and sadly i have burnt out any knowlege i have on this. I cannot begin to come up with any method to succeed in this endeavor.

 

[brandonabandon]

cwm for gb, backup and restore now working, need to fix screen (4-1) possibly fix reboot, emmc not mounting, add empty file named nandroid.md5 to the backup file to bypass md5 (toggle unaffective) for backup fix.

 

[thenameisnigel]

cwm for gb, backup and restore now working, need to fix screen (4-1) possibly fix reboot, emmc not mounting, add empty file named nandroid.md5 to the backup file to bypass md5 (toggle unaffective) for backup fix.

I submitted a patch for the /emmc fix to GitHub but waiting for Josh to merge it.
And instead of CWM, try this: https://github.com/thenameisnigel/OpenRecovery.git

Has to be built on CM11 sources though.

 

[anon(963605)]

I think you said ADB was working on the rom, but there was nothing in /system? Couldn't you like, adb push all the system files in there and reboot?

 

[thenameisnigel]

I think you said ADB was working on the rom, but there was nothing in /system? Couldn't you like, adb push all the system files in there and reboot?

If ADB was working, then it was in fact files on the /system partition, since adb requires adbd to be present and working.

Sent from my SPH-L710 using Tapatalk

 

[Edward McInnish]

which would imply the rom its self is a fail. but that doesn't resolve the recovery issues lol. this is the first device i have tracked in dev that has given issues like this.

 

[thenameisnigel]

which would imply the rom its self is a fail. but that doesn't resolve the recovery issues lol. this is the first device i have tracked in dev that has given issues like this.

Never said it did, I gave Brandon a recovery to try to build above so he can see if it fixes it or not.

Sent from my SPH-L710 using Tapatalk

 

[brandonabandon]

No point in flashing from ics until we find a bootloader workaround. everytime you reboot it erases any foreign files. I flashed the gb aboot as pg suggested in ics. It hangs at logo after reboot. Im not sire which partition is the bootloader. Flashing gb bootloader in ics maybe. Working on cm7 build atm.

 

[thenameisnigel]

Edit: Lol nvm, I'm done.

Sent from my SPH-L710 using Tapatalk

 

[brandonabandon]

the spectrum team did. http://androidforums.com/spectrum-a...oot-cwm-lg-spectrum-4g-ics-linux-install.html. pg said to some time ago, idk which partition is the bl though. why wouldnt the gb bl operate under ics?

i recompiled the gb recovery to an earlier version 5.0.2.6 , some trouble with restore fixed, same trouble with /emmc mount.

@nigel, a patch for gb cwm recovery or open? if not gb, could you look into it or suggest where to start?

@josh,anyone really, lol http://forum.xda-developers.com/showthread.php?t=1879915 this link for the lg bin extractor tool, some emails between paul and i, i sent the .tot for support a few months ago, and he hasnt responded. im not sure if he forgot, i misunderstood him, or he brushed me off. anyhow, i think josh could hack this to get the gb bl from the stock stuff.

 

[brandonabandon]

brandonabandon@beast:~$ adb logcat --------- beginning of /dev/log/main I/DEBU - Pastebin.com HERE IT IS BRO LMFAO. the first glance of cm on a lg viper! cm7! and here is the proof

brandonabandon@beast:~$ adb shell
# ls
firmware
tombstones
mpt
LGE_RC
config
cache
persist
sdcard
acct
mnt
vendor
d
etc
ueventd.rc
ueventd.goldfish.rc
system
sys
sbin
proc
init.target.rc
init.rc
init.qcom.sh
init.qcom.rc
init.goldfish.rc
init
default.prop
data
chargerimages
bootimages
root
dev
smpl_boot
# ls /system
lost+found
etc
recovery-from-boot.p
app
bin
build.prop
fonts
framework
lib
usr
xbin
#
still problems with restore unfortunately. the above info was grabbed from the terminal after a reboot (reboot doesnt work.) <--battery pull. after a factory reset, and attempt to restore no matter what flash, restore, any command =recovery loop.lol

edit: restore is working. the workaround and possibly the problem(s) the problems/solutions 1) md5 mismatch? do a backup as usual, reboot, install nandroid manager+busybox via google play store, open nandroid manager and generate a md5sum of yer backup.done 2)may or may not be a problem, not willing to test at this time, but do not factory reset to recovery. rather from terminal (if faulty flash) adb reboot recovery. 3)may or may not be a problem, installing the unofficial cm rather than the nightly produced by make (probably the problem) i believe the recovery was being flashed (recovery not included in the nightly) causing the problem.

tested against my better wishes, it appears factory reset derails the recovery.

 

[Edward McInnish]

err so basically you have a working cm7? If it wasnt gingerbread, i would be excited,but i hate gingerbread with more passion than i do ICS (nasty experiences). I seriously cannot wait to get some blank cd's so i can burn and install ubuntu on my other hdd. from there i will work on a JB rom.