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

Need your help for a few files

dspl1236

Well-Known Member
Apr 19, 2012
231
36
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
 
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
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.
 
Upvote 0
Ok, so, info so far.

The partition scheme is almost identical to the Spec.
Specs list:
Code:
major minor  #blocks  name 
179        0    3526656 mmcblk0 
179        1      32768 mmcblk0p1 = /firmware vfat (modem)
179        2       1024 mmcblk0p2 = SBL1 (SBL1)
179        3       1024 mmcblk0p3 = SBL2 (SBL2)
179        4          1 mmcblk0p4 (EXT)
179        5       1024 mmcblk0p5 (RPM)
179        6       5120 mmcblk0p6 = ROM update commands - ipth (SBL3)
179        7       5120 mmcblk0p7 = DemiGod Crash Handler/Factory Reset Module (ABOOT)
179        8      10240 mmcblk0p8 = /boot emmc (Boot)
179        9       1024 mmcblk0p9 (TZ)
179       10       3072 mmcblk0p10 (Modem_ST1)
179       11       3072 mmcblk0p11 (Modem_ST2)
179       12       8192 mmcblk0p12 = /persist ext4    blocks = 4096 (Persist)
179       13      16384 mmcblk0p13 = /recovery emmc (Recovery)
179       14      32768 mmcblk0p14 = /system/etc/firmware/misc_mdm vfat (MDM)
179       15       3072 mmcblk0p15 (M9K_EFS1)
179       16       3072 mmcblk0p16 (M9K_EFS2)
179       17       3072 mmcblk0p17 = empty (M9K_EFS3)
179       18       3072 mmcblk0p18 = empty (FSG)
179       19       1024 mmcblk0p19 = empty (SSD)
179       20       8192 mmcblk0p20 = /drm ext4 (BSP)
179       21      16384 mmcblk0p21 = empty (BLB)
179       22      73728 mmcblk0p22 = /tombstones ext4 (Tombstones)
179       23       8192 mmcblk0p23 = /mm ext4 (DRM)
179       24      24576 mmcblk0p24 (FOTA)
179       25       8192 mmcblk0p25 = /misc emmc - This is where the CWM bootloop flag is (MISC)
179       26    1048576 mmcblk0p26 = /system ext4 (System)
179       27     270336 mmcblk0p27 = /cache ext4    blocks = 4096 (Cache)
179       28    1843200 mmcblk0p28 = /data ext4    blocks = 4096 (Userdata)
179       29      16384 mmcblk0p29 = /mpt ext4 (MPT)
179       30       4096 mmcblk0p30 = empty (Grow)
Lucid List:
Code:
mmcblk0p1=MODEM
mmcblk0p2=SBL1
mmcblk0p3=SBL2
mmcblk0p4=EXT
mmcblk0p5=RPM
mmcblk0p6=SBL3
mmcblk0p7=ABOOT
mmcblk0p8=BOOT
mmcblk0p9=TZ
mmcblk0p10=MODEM_ST1
mmcblk0p11=MODEM_ST2
mmcblk0p12=PERSIST
mmcblk0p13=RECOVERY
mmcblk0p14=MDM
mmcblk0p15=M9K_EFS1
mmcblk0p16=M9K_EFS2
mmcblk0p17=M9K_EFS3
mmcblk0p18=FSG
mmcblk0p19=SSD
mmcblk0p20=BSP
mmcblk0p21=BLB
mmcblk0p22=TOMBSTONES
mmcblk0p23=DRM
mmcblk0p24=FOTA
mmcblk0p25=MISC
mmcblk0p26=SYSTEM
mmcblk0p27=CACHE
mmcblk0p28=USERDATA
mmcblk0p29=MPT
mmcblk0p30=INTERNAL
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.
http://rootzwiki.com/topic/17823-flashing-lg-signed-firmware/

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.
 
  • Like
Reactions: dspl1236
Upvote 0
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.

http://androidfiles.massivefilehost.com/lucid/lucid_ics_b1.zip

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

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.
 
Upvote 0
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.

http://androidfiles.massivefilehost.com/lucid/lucid_ics_b1.zip

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

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.

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.
http://wiisixtyfour.webs.com/files/log.txt
 
  • Like
Reactions: Neph81 and noseph
Upvote 0
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.
 
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