• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root ClockWorkMod

Leslie Ann said:
Well now you will be able to mess around and share them.

As for the sig, if you mess around with Android, yeah, you will be there at some point. lol
Click to expand...

Heh I have had my hand full of times the same way just mostly tweaking and editing existing roms (more times then not yours) so it's a bit more rare on my phone then on my computer.

Dark One said:
It's too bad there isn't an experienced recovery developer who was given money to help with this.
Click to expand...

If your referring to drew I'd point out that he ended up spending his own money on the phone in order to help us out and he happens to have a full time job so though I donated I hold nothing against him for it, he tried. Plus with the new info from giantpune who knows maybe his finding will come in useful a few steps later.
 
LacWare said:
Heh I have had my hand full of times the same way just mostly tweaking and editing existing roms (more times then not yours) so it's a bit more rare on my phone then on my computer.



If your referring to drew I'd point out that he ended up spending his own money on the phone in order to help us out and he happens to have a full time job so though I donated I hold nothing against him for it, he tried. Plus with the new info from giantpune who knows maybe his finding will come in useful a few steps later.
Click to expand...

I believe he was saying "was given money" not "has given money to"

EDIT: No longer relevant, the said comment has been deemed stupid.
 
I edited my comment. It was stupid and not constructive. A constructive thing to do would be to PM him and let him know that there has been a potential breakthrough in case he isn't following this thread, so I will do that instead.
 
drew is a good guy. busy, but if he thinks he can do something with the current info thats developed I believe he will.
 
Greatpune at work... :D

1z6a6ns.jpg


Still a work in progress
 
landonh12 said:
Have we tried using the graphics.c file yet?
Click to expand...

I tried the graphics.c from the M+ and postrecoveryboot.sh from the LG Revolution in one of the ClockworkMod Builder builds a while ago.

Cool photo kwknott. Deetz?

Is that a test build from giantpune?

I'd like to know how he got it to boot.
 
ktb83 said:
I tried the graphics.c from the M+ and postrecoveryboot.sh from the LG Revolution in one of the ClockworkMod Builder builds a while ago.

Cool photo kwknott. Deetz?

Is that a test build from giantpune?

I'd like to know how he got it to boot.
Click to expand...

Yeah on chat with him now testing things out.
 
I used the graphics.c from this repo. https://github.com/Shabbypenguin/android_device_lge_ms695/blob/master/BoardConfig.mk . So far, this is booting and it mounts the partitions correctly. It reboots itself after a minute, which is similar to what happened with the first root method I released. In both cases, adbd is running as root. So maybe if we set adb to not run as root, it will fix the reboot issue.

As far as making it, I used this guide My Brain Hurts: Porting Clockwork Recovery to New Devices . At the end, one of the files you get is ramdisk-recovery.img. I used abootimg to stick that in a copy of our stock recovery and nothing more was needed.
 
giantpune said:
I used the graphics.c from this repo. https://github.com/Shabbypenguin/android_device_lge_ms695/blob/master/BoardConfig.mk . So far, this is booting and it mounts the partitions correctly. It reboots itself after a minute, which is similar to what happened with the first root method I released. In both cases, adbd is running as root. So maybe if we set adb to not run as root, it will fix the reboot issue.

As far as making it, I used this guide My Brain Hurts: Porting Clockwork Recovery to New Devices . At the end, one of the files you get is ramdisk-recovery.img. I used abootimg to stick that in a copy of our stock recovery and nothing more was needed.
Click to expand...

That's the graphics.c I used also

That was one of the guides I used, but it doesn't include everything needed, so I read a few others.

No need to specify the base In abootimg? Was it 0x00200000 in the BoardConfig.mk?

If you wouldn't mind sharing your files, I'd appreciate it.

Also, have you gotten stuck in CWM? I've been under the impression that a postrecoveryboot.sh may be needed in order to avoid that.
 
these are the files used to build the one from the screenshot above. Download LGE.tar.gz from Sendspace.com - send big files the easy way . It correctly writes its log in the /cache folder and that can be read when you boot up normally. And he used it to create a backup to his external SD card which worked apparently. With it rebooting itself still after a couple minutes, only an idiot would try to use it to flash anything to their phone.
 
giantpune said:
these are the files used to build the one from the screenshot above. Download LGE.tar.gz from Sendspace.com - send big files the easy way . It correctly writes its log in the /cache folder and that can be read when you boot up normally. And he used it to create a backup to his external SD card which worked apparently. With it rebooting itself still after a couple minutes, only an idiot would try to use it to flash anything to their phone.
Click to expand...

Alrighty.. Looks like we have a working recovery after the reboot issue is fixed? And released after testing?
 
if anybody is a member at xda, you can PM this guy and see if he fixed the issue. Restart CWM Recoery - xda-developers

He has the same reboot issue as us. he has the same android version (2.3.7 gingerbread). And he has a msm board, similar to ours.

EDIT:
looking at the dmesg, this thing is rebooting at 150ish seconds. I found a few threads on google about "cwm 2min reboot". If anybody is familiar with that, it sounds like we have the same issue that several others had.
 
giantpune said:
if anybody is a member at xda, you can PM this guy and see if he fixed the issue. Restart CWM Recoery - xda-developers

He has the same reboot issue as us. he has the same android version (2.3.7 gingerbread). And he has a msm board, similar to ours.

EDIT:
looking at the dmesg, this thing is rebooting at 150ish seconds. I found a few threads on google about "cwm 2min reboot". If anybody is familiar with that, it sounds like we have the same issue that several others had.
Click to expand...

That XDA thread says something about rmt_storage. Check out the bottom of the recovery.rc I was using...

my recovery.rc(init.rc renamed as recovery.rc from stock recovery.img)
Code: 
on early-init
    start ueventd
# matthew.choi@lge.com 111019 LGE_FOTA [START]
    wait /dev/block/mmcblk0

on init
    export PATH /sbin
    export ANDROID_ROOT /system
    export ANDROID_DATA /data
    export EXTERNAL_STORAGE /sdcard

    symlink /system/etc /etc

    mkdir /sdcard
    mkdir /system
    mkdir /data
    mkdir /cache
    mkdir /tmp
#    mount /tmp /tmp tmpfs
    wait /dev/block/mmcblk0p12
#    mount ext4 /dev/block/mmcblk0p12 /system ro barrier=1
    wait /dev/block/mmcblk0p13
    exec /system/bin/e2fsck -p /dev/block/mmcblk0p13
    mount ext4 /dev/block/mmcblk0p13 /data nosuid nodev barrier=1 noauto_da_alloc
    mount ext4 /dev/block/mmcblk0p14 /persist nosuid nodev barrier=1
    mount ext4 /dev/block/mmcblk0p6 /cache nosuid nodev barrier=1

on boot

    ifup lo
    hostname localhost
    domainname localdomain

    class_start default

service ueventd /sbin/ueventd
    critical

service recovery /sbin/recovery

service adbd /sbin/adbd recovery
    disabled

on property:persist.service.adb.enable=1
    start adbd

on property:persist.service.adb.enable=0
    stop adbd

# LGE_CHANGE, locate rmt_storage to /sbin for fixing crash on fota update
service rmt_storage /system/bin/rmt_storage /dev/block/mmcblk0p10 /dev/block/mmcblk0p11 /dev/block/mmcblk0p17
    user root
    disabled

on property:ro.emmc=1
    start rmt_storage
 
Ok, I can toss those lines in my rc file, and then set ro.emmc=1 in the build.prop pretty easily. My guinneapig went to bed for the night. So unless somebody else is around that is willing to let me possibly destroy their phone and show no remorse about it, we'll have to wait until tomorrow night to see if it works.
 
You must log in or register to reply here.
Back
Top Bottom