LG Viper roms?

Toggle sidebar Toggle sidebar
http://pastebin.com/2Gv9iZ9H<--dbl really solved.lol

^"E/kickstart( 167): RUNNING: /system/bin/ks -v -p /dev/ttyHSL1 -d 10:/system/etc/firmware/dbl.mbn"


vold.fstab-

dev_mount sdcard /mnt/sdcard auto /devices/platform/msm_sdcc.3/mmc_host /devices/platform/msm_sdcc.1/mmc_host
 
Last edited:
Not an expert here but whatever dictates the partition scheme has an invalid configuration, not sure where the file is though.

Has anyone reading this compiled a kernel successfully? I'm having trouble compiling it on 13.10. What build environment did you use and could you summarize build steps?
 
im attempting to port vanilla aosp gingerbread to the viper. im useing dannymans gb kernel boot7 (found within forums.) my build environment is ubuntu 12.04, gcc-gcc (Ubuntu/Linaro 4.6.3-1ubuntu5) 4.6.3, and java version "1.6.0_45"
Java(TM) SE Runtime Environment (build 1.6.0_45-b06)
Java HotSpot(TM) 64-Bit Server VM (build 20.45-b01, mixed mode.)
steps to compile, i follow the android build environment setup Downloading the Source | Android Developers
and repo the aosp gingerbread source. the viper has a github, for ics and jellybean https://github.com/ProjectOpenCannibal/android_device_lge_ls840 , kernel source as well https://github.com/thenameisnigel/android_kernel_lge_ls840. i am unable to boot any of the builds. i decided to mod the device tree to build gb, im also currently working on a cm7 rom, although experiencing difficulty adding lge support to the kernel. another problem may be with device settings...booting is the first step. to answer yer questions yes the ics kernel will compile and no, nobody has got it to boot (custom build.) the device has a locked bootloader at the ics update which i am working on getting unlocked. i believe JTAG is neccesarry to retieve the aboot.img needed for loki tools to unlock the bootloader for the viper, the standard method unfortunately does not work. however, i am currently working on a different method, which may retrieve the aboot.img. long story short, i built gb aosp, cm7, ics aosp, ics aokp, cm9, cm10, cm10.1, and all form of jb besides kk for both aosp and aokp as well. none boot.lol thankfully to dannyman though, i am able to at least boot the latest gb aosp build to splash which will produce a logcat. all my builds have failed to reach the splash screen thus far. im hoping its my own build mistakes and not an impassible obstacle preventing any development for the device. feel free to ask any questions, and thank you for enquiring. heads up, the viper was declared eol and basically the 3 or 4 people responding on this forum is the dev support. this is my first android devoloping project btw.
 
@brandonabandon
Thank you for the build steps and info! Also,
I've retrieved the aboot before. It is in the mmc block partitions. It's only a matter of checking the header, but i'll do a sweep through them and check which one it is right now.
 
I'm pretty sure it's /dev/block/mmcblk0p8
It even says so in the old device trees on github
YWlw

U5WJ


Edit:
Wait, hurr durr. I haven't flashed ics yet.. Sorry let me get ics on this thing and run another sweep just to be sure this is the one

Edit2:
Alright, looks like it might be /dev/block/mmcblk0p7 either this or the above.
1iWr


Edit3:
I just extracted the zvk tot and the aboot matches whats in mmcblk0p7, though it is two mb smaller. Not sure why.. compression maybe?(sub-edit: it's just padding)
anyway it also came with a neat partition table just in case anyone needed them all listed

Code: 
AP HEADER
----------
Magic Number                  0x0       : 44 DD 55 AA
                              0x600     : AA BB 00 CC
                              0x2000    : 33 EC 55 AA
Number of Partitions          32

PARTITION ENTRIES
-----------------

PARTITION ENTRY
------------
  Data Block Name           MODEM
  Data Block ID             1
  Size on File              64512
  File Offset               0
  Size on Disk              65537
  Disk Offset               0

PARTITION ENTRY
------------
  Data Block Name           SBL1
  Data Block ID             2
  Size on File              1024
  File Offset               64512
  Size on Disk              2048
  Disk Offset               65537

PARTITION ENTRY
------------
  Data Block Name           SBL2
  Data Block ID             3
  Size on File              1024
  File Offset               65536
  Size on Disk              2048
  Disk Offset               67585

PARTITION ENTRY
------------
  Data Block Name           EXT
  Data Block ID             4
  Size on File              1024
  File Offset               66560
  Size on Disk              12287
  Disk Offset               69633

PARTITION ENTRY
------------
  Data Block Name           RPM
  Data Block ID             5
  Size on File              1024
  File Offset               67584
  Size on Disk              16384
  Disk Offset               81920

PARTITION ENTRY
------------
  Data Block Name           SBL3
  Data Block ID             6
  Size on File              2048
  File Offset               68608
  Size on Disk              16384
  Disk Offset               98304

PARTITION ENTRY
------------
  Data Block Name           ABOOT
  Data Block ID             7
  Size on File              6144
  File Offset               70656
  Size on Disk              16384
  Disk Offset               114688

PARTITION ENTRY
------------
  Data Block Name           BOOT
  Data Block ID             8
  Size on File              17408
  File Offset               76800
  Size on Disk              32768
  Disk Offset               131072

PARTITION ENTRY
------------
  Data Block Name           TZ
  Data Block ID             9
  Size on File              1024
  File Offset               94208
  Size on Disk              16384
  Disk Offset               163840

PARTITION ENTRY
------------
  Data Block Name           MODEM_ST1
  Data Block ID             10
  Size on File              0
  File Offset               95232
  Size on Disk              16384
  Disk Offset               180224

PARTITION ENTRY
------------
  Data Block Name           MODEM_ST2
  Data Block ID             11
  Size on File              0
  File Offset               95232
  Size on Disk              16384
  Disk Offset               196608

PARTITION ENTRY
------------
  Data Block Name           PERSIST
  Data Block ID             12
  Size on File              16384
  File Offset               95232
  Size on Disk              16384
  Disk Offset               212992

PARTITION ENTRY
------------
  Data Block Name           RECOVERY
  Data Block ID             13
  Size on File              17408
  File Offset               111616
  Size on Disk              32768
  Disk Offset               229376

PARTITION ENTRY
------------
  Data Block Name           MDM
  Data Block ID             14
  Size on File              52224
  File Offset               129024
  Size on Disk              65536
  Disk Offset               262144

PARTITION ENTRY
------------
  Data Block Name           M9K_EFS1
  Data Block ID             15
  Size on File              0
  File Offset               181248
  Size on Disk              16384
  Disk Offset               327680

PARTITION ENTRY
------------
  Data Block Name           M9K_EFS2
  Data Block ID             16
  Size on File              0
  File Offset               181248
  Size on Disk              16384
  Disk Offset               344064

PARTITION ENTRY
------------
  Data Block Name           M9K_EFS3
  Data Block ID             17
  Size on File              0
  File Offset               181248
  Size on Disk              16384
  Disk Offset               360448

PARTITION ENTRY
------------
  Data Block Name           FSG
  Data Block ID             18
  Size on File              0
  File Offset               181248
  Size on Disk              16384
  Disk Offset               376832

PARTITION ENTRY
------------
  Data Block Name           SSD
  Data Block ID             19
  Size on File              0
  File Offset               181248
  Size on Disk              16384
  Disk Offset               393216

PARTITION ENTRY
------------
  Data Block Name           BSP
  Data Block ID             20
  Size on File              0
  File Offset               181248
  Size on Disk              16384
  Disk Offset               409600

PARTITION ENTRY
------------
  Data Block Name           BLB
  Data Block ID             21
  Size on File              0
  File Offset               181248
  Size on Disk              32768
  Disk Offset               425984

PARTITION ENTRY
------------
  Data Block Name           TOMBSTONES
  Data Block ID             22
  Size on File              1024
  File Offset               181248
  Size on Disk              147456
  Disk Offset               458752

PARTITION ENTRY
------------
  Data Block Name           DRM
  Data Block ID             23
  Size on File              0
  File Offset               182272
  Size on Disk              16384
  Disk Offset               606208

PARTITION ENTRY
------------
  Data Block Name           FOTA
  Data Block ID             24
  Size on File              0
  File Offset               182272
  Size on Disk              49152
  Disk Offset               622592

PARTITION ENTRY
------------
  Data Block Name           MISC
  Data Block ID             25
  Size on File              0
  File Offset               182272
  Size on Disk              16384
  Disk Offset               671744

PARTITION ENTRY
------------
  Data Block Name           TZ_BKP
  Data Block ID             26
  Size on File              0
  File Offset               182272
  Size on Disk              16384
  Disk Offset               688128

PARTITION ENTRY
------------
  Data Block Name           SYSTEM
  Data Block ID             27
  Size on File              2097152
  File Offset               182272
  Size on Disk              2097152
  Disk Offset               704512

PARTITION ENTRY
------------
  Data Block Name           CACHE
  Data Block ID             28
  Size on File              540672
  File Offset               2279424
  Size on Disk              655360
  Disk Offset               2801664

PARTITION ENTRY
------------
  Data Block Name           USERDATA
  Data Block ID             29
  Size on File              1024
  File Offset               2820096
  Size on Disk              3686400
  Disk Offset               3457024

PARTITION ENTRY
------------
  Data Block Name           LGE_RC
  Data Block ID             30
  Size on File              0
  File Offset               2821120
  Size on Disk              16384
  Disk Offset               7143424

PARTITION ENTRY
------------
  Data Block Name           MPT
  Data Block ID             31
  Size on File              0
  File Offset               2821120
  Size on Disk              32768
  Disk Offset               7159808

PARTITION ENTRY
------------
  Data Block Name           GROW
  Data Block ID             32
  Size on File              0
  File Offset               2821120
  Size on Disk              10240
  Disk Offset               7192576
http://pastebin.com/ZyJjiGQc

Edit4:
I've noticed that our aboot has a different base address than other lg phones ported to loki, i'm looking into porting it myself which will be extremely tricky.. But we may be able to do it together. But just in case if you have an xda account maybe you can ask bliss(dan rosenburg) the creator of loki to see if he can port it, he should only need the aboot.img to do it, worth a try.

I'll be making regular commits to my github here.
https://github.com/Jaegerjaquez69/loki
 
Last edited:
I hope I didn't kill this off :'(

I believe I've gotten somewhere porting loki over.
I managed to confirm the MS770 check_sig address with a boot_pattern I found both ours and their aboot images. I used it on ours but no way to test this out till i figure out how the header(hdr) works and how to get the value/address for it. Anyone with any knoledge here would be greatly appreciated. Maybe show a friend who's good at RE? or bliss :p

Okay here is something. I think I may have ported loki somewhat. It doesnt go straight to the "enter the fastboot!"
I flashed twrp recovery lokified and tried booting into it and got this
We need a recovery built with ICS in mind i think this one has the gb kernel in it. I'll keep looking into this error. I think it may mean it's actually unlocked!
It may not boot past the LG kernel logo, but it's something!
Ad1SR4c.jpg

After a bit of googling, the error is from loki. Loki worked!!!!!!!!!!!!!!!!!!!!!
I can't believe I did it! Man that was challenging.

Edit: before bed i'll go ahead and flash a non stock boot.img the one that gets rid of the security error.

It booted.

okay i'm so excited i'm going to have to try a kernel i compiled myself before i can sleep!!!!!!!!!!!!!!!!!!

Edit2:
Kernel didn't boot, but no security error and no enter the fastboot.
Well it's been long time coming. But it's finally there. Unsigned kernels and recoveries for the viper, thought i'd never see the day.
I wish I would have done it ealier when people were more active.. Maybe this will bring some back!

@brandon:
Lets have some fun with this!

You should be able to just do:
Code: 
git clone https://github.com/Jaegerjaquez69/loki .
make

And it will compile loki_tool for you so you can use it on kernels and recoveries
 
Last edited:
Jaegerjaquez69 said:
I hope I didn't kill this off :'(

I believe I've gotten somewhere porting loki over.
I managed to confirm the MS770 check_sig address with a boot_pattern I found both ours and their aboot images. I used it on ours but no way to test this out till i figure out how the header(hdr) works and how to get the value/address for it. Anyone with any knoledge here would be greatly appreciated. Maybe show a friend who's good at RE? or bliss :p

Okay here is something. I think I may have ported loki somewhat. It doesnt go straight to the "enter the fastboot!"
I flashed twrp recovery lokified and tried booting into it and got this
We need a recovery built with ICS in mind i think this one has the gb kernel in it. I'll keep looking into this error. I think it may mean it's actually unlocked!
It may not boot past the LG kernel logo, but it's something!
View attachment 112616

After a bit of googling, the error is from loki. Loki worked!!!!!!!!!!!!!!!!!!!!!
I can't believe I did it! Man that was challenging.

Edit: before bed i'll go ahead and flash a non stock boot.img the one that gets rid of the security error.

It booted.

okay i'm so excited i'm going to have to try a kernel i compiled myself before i can sleep!!!!!!!!!!!!!!!!!!

Edit2:
Kernel didn't boot, but no security error and no enter the fastboot.
Well it's been long time coming. But it's finally there. Unsigned kernels and recoveries for the viper, thought i'd never see the day.
I wish I would have done it ealier when people were more active.. Maybe this will bring some back!

@brandon:
Lets have some fun with this!

You should be able to just do:
Code: 
git clone https://github.com/Jaegerjaquez69/loki .
make

And it will compile loki_tool for you so you can use it on kernels and recoveries
Click to expand...

Okay, I'll get to working on the recoveries. Couldn't do it without you, so thanks!

Sent from my SPH-L710 using Tapatalk
 
Great, same here. What do you think about cm 10.2, could we get it to run with the ics kernel?

And btw, no problem. I wanted it bad myself and got it through sheer desperation haha. And one more thing, in case you havent noticed already, i'm JoshCo1n/whatevermyothernick was, i had to keep leaving for personal reasons but im here and can work again. I also can't remember passwords and don't have access to the email for JoshCo1n... Long story lol
 
Jaegerjaquez69 said:
Great, same here. What do you think about cm 10.2, could we get it to run with the ics kernel?

And btw, no problem. I wanted it bad myself and got it through sheer desperation haha. And one more thing, in case you havent noticed already, i'm JoshCo1n/whatevermyothernick was, i had to keep leaving for personal reasons but im here and can work again. I also can't remember passwords and don't have access to the email for JoshCo1n... Long story lol
Click to expand...

Shouldn't be that hard to get it to work with the ICS kernel source, only should require minimum charges.

Sent from my SPH-L710 using Tapatalk
 
brandonabandon said:
aboot.img please.....i will host if necessary :)
Click to expand...

im not at home right now but let me if i can explain this right. this doesnt patch the aboot it patches the kernel and rom files to work with our stock ics aboot. so just compile whats in the repo and run loki_tool on the kernep/recovery you want to use and it should work :)
 
@nigel
so would we need to start working on a new device tree or would it be sensible to modify the old one?

sorry for the double post, on my brothers phone
 
Jaegerjaquez69 said:
@nigel
so would we need to start working on a new device tree or would it be sensible to modify the old one?

sorry for the double post, on my brothers phone
Click to expand...

Yeah, a new one is needed because the old one is cluttered with Samsung stuff (my fault) and cleaning the old one up would be more work than just starting over.

I'll start a new one right now.

Sent from my SPH-L710 using Tapatalk
 
Jaegerjaquez69 said:
@nigel
so would we need to start working on a new device tree or would it be sensible to modify the old one?

sorry for the double post, on my brothers phone
Click to expand...

I think we should try to get a CM9 build first since we have the ICS kernel source.

Also, I need a ZVK backup from recovery so I can get started. Can someone upload it?

Sent from my SPH-L710 using Tapatalk
 
Okay, I went on ahead and complied COT Recovery, but I'm not sure if it'll play nice with ICS since it was built with the CM10.2 environment which contains SEAndroid.

Sent from my SPH-L710 using Tapatalk
 
Okay just got home after picking up my new server. Can't use it as a build server just yet, need a bit more ram. It's pretty barebones right now.
HP Proliant DL 360 G5.. with only 2 x 512 dimms.. lol

But alright new device tree it is!

For the system backup i need a custom recovery first, i can test cot if it's ready to be tested.
 
Jaegerjaquez69 said:
Okay just got home after picking up my new server. Can't use it as a build server just yet, need a bit more ram. It's pretty barebones right now.
HP Proliant DL 360 G5.. with only 2 x 512 dimms.. lol

But alright new device tree it is!

For the system backup i need a custom recovery first, i can test cot if it's ready to be tested.
Click to expand...

Can you just build a CWM image at builder.clockworkmod.com and
lokify it since I'm syncing CM9.

Sent from my SPH-L710 using Tapatalk
 
sorry was trying to get something set up on the server. I'll try the builder now.
Build: http://jenkins.cyanogenmod.com/job/recovery/61285/
it's bootlooping :\
right after attempting to boot, blank screen and loops

Small update:
Thanks to djrbliss we've been included into the official loki source
https://github.com/djrbliss/loki
So you should now be able to use this to lokify your images.

@nigel:
i'll just try building twrp again since the builder image wouldn't work for some strange reason.
 
Last edited:
You must log in or register to reply here.

Similar threads

C
Need help reinstalling OS, I think
Replies
28
Views
3K
Samsung Galaxy S9 & S9+
mustang7757
mustang7757
E
best way to migrate to new moto 5g 2025
Replies
8
Views
1K
Moto G
erhard52
E
Dan_B1979
Ordered my first Pixel (non-Fold) phone since the 7 Pro...
Replies
6
Views
1K
Google Pixel 9, Pixel 9 Pro, & Pixel 9 Pro XL
Dan_B1979
Dan_B1979
gray2018
LG V30 - One of my favorite devices
Replies
9
Views
2K
LG V30
Laura Knotek
Laura Knotek
B
Add apps to home screen (but I can't find the icons?)
Replies
7
Views
3K
Samsung Galaxy Tab S9
mustang7757
mustang7757

Latest posts

Trending Posts

Members online

Total: 3,314 (members: 9, guests: 3,305)

Forum statistics

Threads
957,083
Messages
6,971,417
Members
3,163,713
Latest member
Opoliraka

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom