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

Root [ALPHA][TESTING ONLY][CLOCKWORKMOD Touch 6]

rpdrizzy

Member
Feb 19, 2012
92
17
New Jersey
This is for TESTING PURPOSES ONLY!:


This is a Touch ClockworkMod Recovery for the LG Optimus F7 Boost Mobile

Linux Only

BUGS/WIP List
  • Pink Screen Bug (still functional and words still visible but everythings pink)
  • USB Mount does not work
  • WARNING: File_Contexts Error (Some partitions don't mount = /emmc /sd-ext which are non existing)
  • Resets /data/app and settings upon 2 reboots to recovery

HIGHLY EXPERIMENTAL!!!

You will need Loki and your aboot.img. I've included it in the attached zip.

*aboot.imgs may vary per device.*

Instructions are within the zip in the read me file.


I'm also working on a debloated rom. But that may take some time. Got to fix this first ;)

Download:
Dev-Host - CWM Alpha.zip - The Ultimate Free File Hosting / File Sharing Service

Changelog:
Alpha 1:
  • Fixed lost of root by moving Superuser to /system/app/
 
You should be able to use the dd command in terminal emulator or ADB Shell to backup the recovery partition and restore it before you flash the CWM one, have you thought of that?

Whats the partition number for recovery? Go into settings and enable usb debugging, then open up cmd on your computer, direct it to your adb setup and use the command "cat proc/emmc" without quotes and that will tell you the recovery partition number.

The dd command should be dd if=/dev/block/mmcblk0p??? of=/sdcard/recovery.img
 
Upvote 0
You should be able to use the dd command in terminal emulator or ADB Shell to backup the recovery partition and restore it before you flash the CWM one, have you thought of that?

Whats the partition number for recovery? Go into settings and enable usb debugging, then open up cmd on your computer, direct it to your adb setup and use the command "cat proc/emmc" without quotes and that will tell you the recovery partition number.

The dd command should be dd if=/dev/block/mmcblk0p??? of=/sdcard/recovery.img

Thanks I already have the original recovery.img as I needed it to make CWM. I just need to use Loki to revert it back.
 
Upvote 0
You should be able to use the dd command in terminal emulator or ADB Shell to backup the recovery partition and restore it before you flash the CWM one, have you thought of that?

Whats the partition number for recovery? Go into settings and enable usb debugging, then open up cmd on your computer, direct it to your adb setup and use the command "cat proc/emmc" without quotes and that will tell you the recovery partition number.

The dd command should be dd if=/dev/block/mmcblk0p??? of=/sdcard/recovery.img

To pull recovrey

dd if=/dev/block/platform/msm_sdcc.1/by-name/recovery of=/sdcard/recovery.img

To flash recovery
dd if=location_of_recovery.lok of=/dev/block/platform/msm_sdcc.1/by-name/recovery

Edit: @rpdrizzy, loki will only work on the current firmware version. If you update, you will have to flash the old aboot.img from the current version of software. This will not work on a variant of the Optimus F7 unless they flash the aboot file from the boost mobile version of the phone, or if the phone is exactly the same HW and SW wise.
 
  • Like
Reactions: rpdrizzy
Upvote 0
To pull recovrey

dd if=/dev/block/platform/msm_sdcc.1/by-name/recovery of=/sdcard/recovery.img

To flash recovery
dd if=location_of_recovery.lok of=/dev/block/platform/msm_sdcc.1/by-name/recovery

Edit: @rpdrizzy, loki will only work on the current firmware version. If you update, you will have to flash the old aboot.img from the current version of software. This will not work on a variant of the Optimus F7 unless they flash the aboot file from the boost mobile version of the phone, or if the phone is exactly the same HW and SW wise.

Flashing on locked BL 101 :)
 
Upvote 0
:D I'm just a noob trying. Lol I haven't dealt with locked bootloaders before as my previous device was a HTC and that was easy to unlock.

You're in for a ride :p
Recovery is going to be a pain to get working. It may never work. None of these devices with locked bootloaders (with msm8960 processors) from LG have a 100% working recovery. Accessing the data partition from being booted in recovery has not been fixed on any of them.
 
Upvote 0
Oh is he ever. lol

Yeah the only LG device that doesn't get it's data wiped by CWM is the Spirit so we got lucky that our recovery is usable. It's only flaw is not being able to access the internal sd which is no big deal.

Hey Sammy, I noticed the LG Spectrum 2 might need our help. (unbrick guide and kernel) lol. Let me know if you're interested.
 
Upvote 0
Oh is he ever. lol

Yeah the only LG device that doesn't get it's data wiped by CWM is the Spirit so we got lucky that our recovery is usable. It's only flaw is not being able to access the internal sd which is no big deal.

Hey Sammy, I noticed the LG Spectrum 2 might need our help. (unbrick guide and kernel) lol. Let me know if you're interested.

I gave a guy the cab file for him to dev as well as unbrick and he's doing the devving for that phone afaik. His username starts with an m and I cant remember it...lol. He's the reason loki supported the spectrum 2. He came to #oudhitsquad and asked for support.
 
Upvote 0
I gave a guy the cab file for him to dev as well as unbrick and he's doing the devving for that phone afaik. His username starts with an m and I cant remember it...lol. He's the reason loki supported the spectrum 2. He came to #oudhitsquad and asked for support.
Cool, I guess I'll wait a couple weeks. If nothing is posted there by then, I'll head over and give the users instructions on how to pull the files I need for kernel lol. :p
 
Upvote 0
Or, I'll give it to you :p

Do you want to learn how I get firmware and extract it?? I'll be too busy when college starts.
That sounds like a good idea lol. ATM I only know how to get stock rom by building source code which is a PITA (not worth it).

I remember the good ol college days, sometimes a pain, but well worth it. Some of the most important people in my life I met there.
 
Upvote 0
First, you'll need windows installed, or a virtual box with at least 4GBs of ram dedicated to it (just so it doesn't get slow). The extract process uses more ram than processing power.

Then I'll need you to install teamviewer on your windows environment so I can show you.
You'll also need fast internet to dl the firmware..slow internet usually results in bad downloads. Good download speed is 512kb/s (if it's a speedtest that would be like 5-10MB/s)

Great download speed is 1-3MB/s (20-30MB/s on speedtest).

If your download speeds suck, go to a library :p the library has amazing internet speeds. Or at least mine does, but their PCs tend to suck.
 
  • Like
Reactions: GameTheory
Upvote 0
@rpdrizzy

I have a couple questions for troubleshooting purposes....

1. Did you add a graphics.c file to the build and also a recovery.fstab file?
2. Is the recovery able to mount external sd?

I used the recovery.fstab with the correct partitions however I was unable to find/make a graphics.c for the F7. I know its needed to fix the graphics issue. Also it is able to Mount the external SD but not the internal SD.
 
Upvote 0
for the color ,cwrp recovery have some info
How to Compile TWRP from Source - TWRP 2.X - RootzWiki
ARGET_RECOVERY_PIXEL_FORMAT := "BGRA_8888"
TARGET_RECOVERY_PIXEL_FORMAT := "RGBX_8888"
TARGET_RECOVERY_PIXEL_FORMAT := "RGB_565"
and decompile 2nd recovery can find some info
http://unleashedprepaids.com/upload/devs/playfulgod/phones/LG/MS870/lte2_l1m_recovery.apk

recovery.fstab
===
# mount point fstype device [device2]

/boot emmc /dev/block/platform/msm_sdcc.1/by-name/boot
/cache ext4 /dev/block/platform/msm_sdcc.1/by-name/cache
/data ext4 /dev/block/platform/msm_sdcc.1/by-name/userdata
/misc emmc /dev/block/platform/msm_sdcc.1/by-name/misc
/recovery emmc /dev/block/platform/msm_sdcc.1/by-name/recovery
/sdcard datamedia /dev/null
/external_sd vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1
/system ext4 /dev/block/platform/msm_sdcc.1/by-name/system
 
Upvote 0
Sorry Guys hadn't had some time to work on this as my developer PC has been confiscated temporarily. I did fix the color issue however I was not able to prevent it from wiping Data and Cache upon reboot. And the internal SD wouldn't mount. Once I get it back I'll continue to work on it as best as I can. However I'm switching to either the Moto X or the Oppo Find 5.
 
Upvote 0

BEST TECH IN 2023

We've been tracking upcoming products and ranking the best tech since 2007. Thanks for trusting our opinion: we get rewarded through affiliate links that earn us a commission and we invite you to learn more about us.

Smartphones