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

Root testers needed for TWRP/CWM/SD-EXT data

Hey johnny what part of texas are you in maybe when can meet up and you can show me how to get the recovery working if you don't mind or anyone for that.. the phone is good but needs a rom i don't like the stock feel...

Someone could just as easily make a video without the risk of giving out information to someone you don't know, and the phone does have a ROM, and it's easy to install, you're just not following the directions.
http://unleashedprepaids.com/showthread.php?tid=7632
Somewhere on that page there is a quick EASY guide to installing 2nd init recovery, use that.
This should only be used by advanced testers, I have tested it, but not thoroughly

.
Just use 2nd init and flash BobZ's rom if you don't like this. It's easy.
 
denton tx but it's really not that hard your just missing a step or something. did you hit volume down repeatedly while rebooting after using the 2ndinit app
 
my benchmark using this kernel and recovery
 

Attachments

  • Screenshot_2013-07-17-13-16-03.png
    Screenshot_2013-07-17-13-16-03.png
    66.5 KB · Views: 154
Cool got it to work now first thing i want to do it make a back up can i do this like regular or is there a trick to this aswell?
 
anyway i could talk you into editing the kernel to redirect /system also? therefore creating a dualboot kernel. basically you would flash the dual boot kernel to access the sd-ext rom and flash a stock kernel to access internal rom.
 
anyway i could talk you into editing the kernel to redirect /system also? therefore creating a dualboot kernel. basically you would flash the dual boot kernel to access the sd-ext rom and flash a stock kernel to access internal rom.


that would complicate things too much

you would need to partition the card with a program like Mini Partition tool

and a new recovery would would need to be made that maps system to that partition in the fstab file

and then the new kernel with the change in the init.rc

i think this whole thing with mapping data to the sd-ext is to complicated for most of the people here already

not too many people wanted to test it
 
anyway i could talk you into editing the kernel to redirect /system also? therefore creating a dualboot kernel. basically you would flash the dual boot kernel to access the sd-ext rom and flash a stock kernel to access internal rom.
I am already doing this ;) Almost done, sorting out a few problems. Waiting to hear back from candoopa, then should be just about good to go. First release will not include sd-ext, however, it will be added shortly after.
 
Zeest

Since you messaged me and asked for a copy of my CWM before it is Lokied, I am uploading these scripts for you that I made.


THIS CAN ONLY BE USED FOR THE LG MOTION

This will allow you to unpack and repack kernel and recoverie .img files (not Lokied)

It includes the stock zImage and 5 different ramdisk

1. stock-boot
2. cwm
3. cwm-sd-ext
4. twrp
5. twrp-sd-ext

The only difference with the normal and sd-ext versions are the recovery.fstab

You have to have Linux or Cygwin

Unzip LGM-PACK.zip to you home directory

hroark13@dev1a:~$ mkdir LGM-PACK
hroark13@dev1a:~$ cd LGM-PACK
hroark13@dev1a:~/LGM-PACK$ unzip ~/Downloads/LGM-PACK.zip


TO PACK A BOOT KERNEL

hroark13@dev1a:~/LGM-PACK$ ./boot.pl stock-boot
8443 blocks

repacked recovery image written at boot.img
[+] loki_patch v1.6
[+] Detected target MetroPCS LG Motion build MS77010f_01
[+] Output file written to boot.lok
hroark13@dev1a:~/LGM-PACK$


TO PACK A CWM (NORMAL)

hroark13@dev1hroark13@dev1a:~/LGM-PACK$ ./recovery.pl cwm
7411 blocks

repacked recovery image written at recovery.img
[+] loki_patch v1.6
[+] Detected target MetroPCS LG Motion build MS77010f_01
[+] Output file written to recovery.lok
hroark13@dev1a:~/LGM-PACK$

TO PACK A CWM (sd-ext)

hroark13@dev1a:~/LGM-PACK$ ./recovery.pl cwm-sd-ext
7407 blocks

repacked recovery image written at recovery.img
[+] loki_patch v1.6
[+] Detected target MetroPCS LG Motion build MS77010f_01
[+] Output file written to recovery.lok
hroark13@dev1a:~/LGM-PACK$


TO PACK A TWRP (NORMAL)

hroark13@dev1a:~/LGM-PACK$ ./recovery.pl twrp
10297 blocks

repacked recovery image written at recovery.img
[+] loki_patch v1.6
[+] Detected target MetroPCS LG Motion build MS77010f_01
[+] Output file written to recovery.lok
hroark13@dev1a:~/LGM-PACK$


TO PACK A TWRP
(sd-ext)
hroark13@dev1a:~/LGM-PACK$ ./recovery.pl twrp-sd-ext
10297 blocks

repacked recovery image written at recovery.img
[+] loki_patch v1.6
[+] Detected target MetroPCS LG Motion build MS77010f_01
[+] Output file written to recovery.lok
hroark13@dev1a:~/LGM-PACK$







https://www.dropbox.com/s/bcrm42juz43jdoi/LGM-PACK.zip






hK
 
Thank you candoopa, I appreciate it. However, I have realized that, as I must make modifications to the recovery for my purposes, a pre-assembled recovery will not work. Would you mind sharing how you fixed the coloring, either through post or pm?
Thanks,
zeest
 
Thank you candoopa, I appreciate it. However, I have realized that, as I must make modifications to the recovery for my purposes, a pre-assembled recovery will not work. Would you mind sharing how you fixed the coloring, either through post or pm?
Thanks,
zeest


to fix the coloring add this line

TARGET_RECOVERY_PIXEL_FORMAT := "RGBX_8888"


to the BoardConfig.mk



I did not use the same tree as the CM10 tree, since it was not really made for recoveries

I took shabby's tree and made some small changes to it

here is the tree


https://www.dropbox.com/s/usizpgo5j1rmxfx/l0.zip








hK
 
Back
Top Bottom