n0ve
Android Expert
Same issue w/ PG's CWM (GB based), unsure as to why, appreciate your time though we'll get it
.-
After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.
Root [CWM][WIP][DEV] Clockworkmod Recovery for the LG Viper 4G LGLS840
- Thread starter PlayfulGod
- Start date
-
- Tags
- lg viper 4g
.Same issue w/ PG's CWM (GB based), unsure as to why, appreciate your time though we'll get it
I haven't given up yet just waiting on the guy I'm working with to have some free time
wickidd
Newbie
That's what the postbootrecovery.sh is for. It has to be written right for it to cleanup from setting up for booting into recovery (hope you can follow the logic in that, lol) - which is pretty much all that file does. I think I have one that'll work, but I'm currently on my windows side. I'll post back with the script once I'm on my dev environment, which I will be later on today, because I have to work on this, and compile a jb kernel for my ns4g, since every one I've tried so far from xda is lagging the crap out of my phone with the new jb rom I'm using - but that's another story for another place, lol.
Later all!
~WickiD~
Later all!
~WickiD~
n0ve
Android Expert
Lol i logged in to post that we need to edit that script....wickid is 100% correct ..as usual lol
well..except that one time..as far as the file, i believe it has to be created based off of stock bootrecovery script. Dont quote me on that i gotta check.
wickidd
Newbie
Lol i logged in to post that we need to edit that script....wickid is 100% correct ..as usual lol
Actually, I haven't been able to find much documentation on it. I pulled it from a close relative device that I found, where it was posted on xda that the booting works the same way (the connect or lucid, maybe? I can't remember right off hand)
You won't find it, 1) because the recovery partition gets mounted as a temporary loop, and not normally searchable with the device, as-is, and 2) it's not in the partition, even if you did mount it that way. (which, answers your response too, n0ve)
No, the file, as far as I can tell, has to be written on a per-device basis, much like when you port a new rom, have to rebuild the device tree, and have to basically hand-write the Android.mk, and other such files. (not an easy task, btw.. those interested in porting roms, take note if you're not experienced, this will be your MOST time-consuming task in porting..)
Here's the postbootrecovery.sh* that I found:
Code:
#!/sbin/sh
sleep 5
for i in $(seq 1 10)
do
TMP=$(mount | grep /tmp)
if [ -z "$TMP" ]
then
break
fi
umount -l /tmp
sleep 1
done
busybox mount -o rw,remount /
rm -r /tmp
mkdir -p /tmpHope this helps you guys out, worny, in getting this finished up, and to everyone else, answers some questions regarding this topic.
Later guys!
~WickiD~
wickidd
Newbie
If you're using Koush's builder (aka CWM) to build the recovery img, then you need it for that. I'm not sure the details of how you all are doing this, but you'll probably need it for that too. Either way, simple answer, the recovery.img.
Oh, and here's the stock recovery.fstab (644, root:root) if it helps:
Code:
/tmp ramdisk
/boot emmc /dev/block/mmcblk0p8
/cache ext4 /dev/block/mmcblk0p28
/data ext4 /dev/block/mmcblk0p29
/misc emmc /dev/block/mmcblk0p25
/recovery emmc /dev/block/mmcblk0p13
/sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1
/system ext4 /dev/block/mmcblk0p27
PlayfulGod
Extreme Android User
you all have completely lost me with some of the things you are attempting to do.
wickidd, I'm not even sure what that script you posted is pose to do other than mount /tmp as writeable, which shouldnt be needed as android doesnt use /tmp, it uses /data/local/tmp which is r/w already.
worny, no offense, but I hope whom you are working with knows what they are doing, because you dont seem too.
there prolly isnt much needed to be done to the cwm I built for the viper, just fine tuned, which is hard for me to do w/o the device.
And n0ve the CWM I built is built off CM's ics branch, only the kernel is GB, which isnt a factor.
and /tmp ramdisk is not in the recovery.fstab stock or otherwise.
And LG's need too many factors added in to be able to use builder.clockwork w/o having a working repo already forked into CM repos, thus needs to be built locally until there is a working repo to request to be forked in.
wickidd, I'm not even sure what that script you posted is pose to do other than mount /tmp as writeable, which shouldnt be needed as android doesnt use /tmp, it uses /data/local/tmp which is r/w already.
worny, no offense, but I hope whom you are working with knows what they are doing, because you dont seem too.
there prolly isnt much needed to be done to the cwm I built for the viper, just fine tuned, which is hard for me to do w/o the device.
And n0ve the CWM I built is built off CM's ics branch, only the kernel is GB, which isnt a factor.
and /tmp ramdisk is not in the recovery.fstab stock or otherwise.
And LG's need too many factors added in to be able to use builder.clockwork w/o having a working repo already forked into CM repos, thus needs to be built locally until there is a working repo to request to be forked in.
I know I don't know anything as far as building, I'm just asking questions about what would need to be done. The guy I've been working with knows his stuff he has built rooms, kernals and recoveries for the optimus line of phones. His works but has the same reboot issue the recovery we have on the android central site has.
PlayfulGod
Extreme Android User
n0ve
Android Expert
I'm wondering the same thing.. Cuz we must know him/her..
PlayfulGod
Extreme Android User
well I was thinking more of just heard of em at least lol
n0ve
Android Expert
@PG...I thought right away that the builder won't work w. LG partitions and had assumed your cwm build was gb pull not just kernel. Anyway as you pointed out lot of misdirection and confusion lol but now w. Wickid back and our newest member should be able to progress. Also question: I'm planning to round up a donation viper for you if willing /have time to do your magic.... Let me know if I shouldn't..
@All...has anyone even successfully loaded ics?
@All...has anyone even successfully loaded ics?
PlayfulGod
Extreme Android User
Yea with one in hand I should be able to get cwm going for it. Just the issues reported back to me when I first worked on it n had testers and the feedback from you all steer me away from working on it blind. lol
n0ve
Android Expert
Lol i consider know as heard of meaning if this dev is capable, we'd most likely know the name and or be close w/. Well then ill get that going ASAP to have a donation for you. I myself don't program really. I've just been testing mods/tweaks/ preparing for a stripped stock rom. I am lost as well i saw this ics source post and all of a sudden there's active members well at least shows dedication. Also any work you may do blindly before I get one to you.. I'll test everything w. detailed reports...k time to gather dough for donation. I seen bricked ones on Craigslist cheap but easy fix soft bricks like what I've seen 40 times already.
PlayfulGod
Extreme Android User
Well I wouldnt get your hopes up on the ics, meaning being able to do much with it, if its like any of the other LG devices I seen with ics, it will be purdy much locked down with at the most getting root on it for the time being.
wickidd
Newbie
n0ve is right, I pulled that script from somewhere on xda, and it was for a device that boots the same as the viper and has the same factory reset thing. Koush's cwm builder asks for that script as an option, and I thought it may help for not having to pull the battery to boot normally, since it cleans up what was temporarily done for the recovery in the first place.
I hope that clears up the confusion on that.
And that is the EXACT recovery.fstab that I pulled from the stock recovery from my girl's viper. Trust, it's a direct copy and paste. I just left out all the unneeded crap at the top of the file. There's actually 2, 1 is recovery.fstab, and the other is recovery.mmc_fstab, but I couldn't figure out why you would need 2 of them, since the paths and mounts in both point to the same places, with just a different way of getting to them, so I just picked the most logical one, basing my logic on knowing how to mount crap in a linux(based/like) environment. Trust me man, I pulled that directly.
Anyway, yeah, let's get a fundraiser going so you can get one of these. The specs on this phone make it great, but being stuck back on gb, completely diminishes what it's completely capable of. I would love to see ics or even, if it makes it that far (it is a factory overclocked dual-core, fgs!), jb on it.
Anyway, I'm off to bed, gnite all!
n0ve
Android Expert
I could care less right now about ICS. Got enough build/local prop edits going to keep me quite pleased for now.
jakecompton
Lurker
how do you root the lg viper 4g lte. im using the one click software thing. with odin. and when i download the insecure original kernel. it wont flash. and on odin it doesnt have the yellow thing underneath it. any suggestions on how to doing it. i downloaded kies just in case and still nothing. please help