1. Are you ready for the Galaxy S20? Here is everything we know so far!

Need your help for a few files

Discussion in 'Android Devices' started by dspl1236, Dec 24, 2012.

  1. dspl1236

    dspl1236 Well-Known Member
    Thread Starter

    I started to convert the VS920 Spectrum Bootloader Pwnage tool to work on my VS840 Lucid.

    I hard bricked my device testing this. pushed the wrong firmware to it.... so I am missing 6 files that were also needed for the unlock.

    If you are on ICS and rooted and willing to help it would be great. :D PM me for details

  2. Neph81

    Neph81 Android Expert

    You don't need the ICS files for the unlock. You need the GB files (assuming GB was an unlocked boot loader). You also need a custom kernel as the sfuse will trip if you try and run the stock ICS kernel without the locked boot chain.
  3. dspl1236

    dspl1236 Well-Known Member
    Thread Starter

    i know just enough to be super dangerous.

    would you like a gb cwm backup?
  4. Neph81

    Neph81 Android Expert

    I'm good. Assuming that /system rip you linked me was ICS, we should be good to go.
    dspl1236 likes this.
  5. Neph81

    Neph81 Android Expert

    Ok, so, info so far.

    The partition scheme is almost identical to the Spec.
    Specs list:
    Code (Text):
    2. major minor  #blocks  name
    3. 179        0    3526656 mmcblk0
    4. 179        1      32768 mmcblk0p1 = /firmware vfat (modem)
    5. 179        2       1024 mmcblk0p2 = SBL1 (SBL1)
    6. 179        3       1024 mmcblk0p3 = SBL2 (SBL2)
    7. 179        4          1 mmcblk0p4 (EXT)
    8. 179        5       1024 mmcblk0p5 (RPM)
    9. 179        6       5120 mmcblk0p6 = ROM update commands - ipth (SBL3)
    10. 179        7       5120 mmcblk0p7 = DemiGod Crash Handler/Factory Reset Module (ABOOT)
    11. 179        8      10240 mmcblk0p8 = /boot emmc (Boot)
    12. 179        9       1024 mmcblk0p9 (TZ)
    13. 179       10       3072 mmcblk0p10 (Modem_ST1)
    14. 179       11       3072 mmcblk0p11 (Modem_ST2)
    15. 179       12       8192 mmcblk0p12 = /persist ext4    blocks = 4096 (Persist)
    16. 179       13      16384 mmcblk0p13 = /recovery emmc (Recovery)
    17. 179       14      32768 mmcblk0p14 = /system/etc/firmware/misc_mdm vfat (MDM)
    18. 179       15       3072 mmcblk0p15 (M9K_EFS1)
    19. 179       16       3072 mmcblk0p16 (M9K_EFS2)
    20. 179       17       3072 mmcblk0p17 = empty (M9K_EFS3)
    21. 179       18       3072 mmcblk0p18 = empty (FSG)
    22. 179       19       1024 mmcblk0p19 = empty (SSD)
    23. 179       20       8192 mmcblk0p20 = /drm ext4 (BSP)
    24. 179       21      16384 mmcblk0p21 = empty (BLB)
    25. 179       22      73728 mmcblk0p22 = /tombstones ext4 (Tombstones)
    26. 179       23       8192 mmcblk0p23 = /mm ext4 (DRM)
    27. 179       24      24576 mmcblk0p24 (FOTA)
    28. 179       25       8192 mmcblk0p25 = /misc emmc - This is where the CWM bootloop flag is (MISC)
    29. 179       26    1048576 mmcblk0p26 = /system ext4 (System)
    30. 179       27     270336 mmcblk0p27 = /cache ext4    blocks = 4096 (Cache)
    31. 179       28    1843200 mmcblk0p28 = /data ext4    blocks = 4096 (Userdata)
    32. 179       29      16384 mmcblk0p29 = /mpt ext4 (MPT)
    33. 179       30       4096 mmcblk0p30 = empty (Grow)
    Lucid List:
    Code (Text):
    2. mmcblk0p1=MODEM
    3. mmcblk0p2=SBL1
    4. mmcblk0p3=SBL2
    5. mmcblk0p4=EXT
    6. mmcblk0p5=RPM
    7. mmcblk0p6=SBL3
    8. mmcblk0p7=ABOOT
    9. mmcblk0p8=BOOT
    10. mmcblk0p9=TZ
    11. mmcblk0p10=MODEM_ST1
    12. mmcblk0p11=MODEM_ST2
    13. mmcblk0p12=PERSIST
    14. mmcblk0p13=RECOVERY
    15. mmcblk0p14=MDM
    16. mmcblk0p15=M9K_EFS1
    17. mmcblk0p16=M9K_EFS2
    18. mmcblk0p17=M9K_EFS3
    19. mmcblk0p18=FSG
    20. mmcblk0p19=SSD
    21. mmcblk0p20=BSP
    22. mmcblk0p21=BLB
    23. mmcblk0p22=TOMBSTONES
    24. mmcblk0p23=DRM
    25. mmcblk0p24=FOTA
    26. mmcblk0p25=MISC
    27. mmcblk0p26=SYSTEM
    28. mmcblk0p27=CACHE
    29. mmcblk0p28=USERDATA
    30. mmcblk0p29=MPT
    31. mmcblk0p30=INTERNAL
    32. mmcblk0p31=GROW
    You'll notice that you have an extra partition because you have internal storage. I've also found that you have the files needed inside the .cab you get from LG to use this method to downgrade/upgrade/restore your phone as long as you can get into download mode.

    Just make sure to grab the firmware version for your phone. I saw V6 links floating in your forum. Here are V5 and V7

    V5: http://csmg.lgmobile.com:9002/swdat...K/VS840ZV5_00/VS840ZV5_00.S5_00.P58013.R5.cab

    V7: http://csmg.lgmobile.com:9002/swdat...S840ZV7_07/VS840ZV7_07.S7_07.P58015.R5.01.cab

    So, here is what you need and I'm leaving this info public for group effort as I can not dev without a device and I'm not looking to gain a new phone.

    Take the /system partition from ICS and build a kernel that will boot it. You will want to be on the unlocked GB build when trying the rom. It will boot when you get it right as we did the same thing when our ICS leak came out for the spec.

    Once you have a bootable ICS rom, then you can take the Pwnage tool for the spec, and replace all the dd img files with those from GB. Be careful with mmcblk0p7. This one needs to be flashed first, and if done wrong, will cause a brick. This controls the initial boot up and tells the phone to either go to download mode, recovery, or to the boot loader. Recovery can be replaced with your recovery currently used for GB. Boot will need to be replaced with your custom kernel used to boot the ICS rom. If anyone has questions on this info, please let me know.

    Edit: I was given a stock boot.img and didn't realize it. I'll take a look at it this week to see what I can find out.
    dspl1236 likes this.
  6. dspl1236

    dspl1236 Well-Known Member
    Thread Starter

    This is a great step for Lucid owners Neph!

    After I get a new Lucid I will be experimenting with this. I had intended to revert back to GB and setup cwm to play with ICS...:rolleyes: then i got over zealous....
  7. Neph81

    Neph81 Android Expert

    Can someone with a Lucid please run the following command for me (either in adb shell or terminal)

    getprop ro.board.platform

    Everything I'm seeing so far says that you guys may be closer to the Spec the realized and if you're running the MSM8660 , there is a very good chance of porting CM10 over to you.
  8. dspl1236

    dspl1236 Well-Known Member
    Thread Starter

    Has Adreno 220 and MSM 8660 but only at 1.2 ghz...I see no reason why we couldn't hit 1.5 with some kernel work. Gpu and ram are even the same speeds. This is literally a smaller spectrum.

    Happy holidays guys, I am out. :D
  9. Neph81

    Neph81 Android Expert

    Someone still running GB needs to test this and the person testing should be familiar with ADB and how to get into CWM recovery via the button method.


    Go into CWM and make a backup.(critical because this may not fully boot)
    Install rom

    One of three things will happen with this.

    1) This will boot without a flaw and we can move on to making a boot loader unlock tool.
    2) This will boot up, but not into the system. ADB is set to start at boot, so we should be able to get a logcat out of it.
    3) Doesn't boot and we'll need to write a new kernel.

    I look forward to hearing results from someone.
  10. wiisixtyfour

    wiisixtyfour Well-Known Member

    I downgraded to GB, rooted, installed CWM and tried this out. It seems to boot but the screen is black. It does play the startup sound and it is busy, but there's nothing on screen. I'm trying to get a log now but I'm not sure what the device is doing. USB is connected and it seems to be totally working except for the display.

    Here's the log I got, I eventually just turned it off and reinstalled stock ICS for now, but I can test anything else later.
    Neph81 and noseph like this.
  11. Neph81

    Neph81 Android Expert

    Thank you. This is a great step forward as it proves that the kernel can boot the OS. It's just a manner of fixing a few glitches in the ICS I was given.

    Edit: The blank screen is apparently due to the kernel not being able to open the frame buffer. This is causing the OS to not fully boot either. Both seem like fixable issues.
    noseph likes this.
  12. Neph81

    Neph81 Android Expert

    The log shows basically everything booting up fine except for the video driver. Can someone possibly get me the dmesg from the kernel after the phone has been on for about 2 minutes? This seems like a very small error and potentially it will be right into CM10 from there. We'd just need to add support for your internal memory.
  13. soldier2009

    soldier2009 Newbie

    So what you need help with
  14. zinkscott

    zinkscott Well-Known Member

    Anyone have an alternative link to the ZV7.cab download? Thanks.
  15. wiisixtyfour

    wiisixtyfour Well-Known Member

    zinkscott likes this.
  16. zinkscott

    zinkscott Well-Known Member

  17. k3nd0

    k3nd0 Lurker

  18. noseph

    noseph Well-Known Member

LG Connect 4G Forum

The LG Connect 4G release date was February 2012. Features and Specs include a 4.0" inch screen, 5MP camera, 1GB RAM, Snapdragon S3 processor, and 1540mAh battery.

February 2012
Release Date

Share This Page