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

Root LG Lucid's ICS backup

well.. i dont really have access to it like that yet lol he literally just baught it yesterday and he knows what a brick is so it may be a while before i get my hands on a backup or system pull lol
 
rav2012 said:
has anyone been able to compile the ics viper kernel with cayman_mpcs_us_defconfig?
Click to expand...
Yup sure have and its a major cluster ****. My guess is LG never compiled it with it either.

Think I will sdiff the 2 and see what the differences are.
 
PlayfulGod said:
Yup sure have and its a major cluster ****. My guess is LG never compiled it with it either.

Think I will sdiff the 2 and see what the differences are.
Click to expand...

so far I'm stuck with this error like 2 min into compiling..
Code: 
 CC      arch/arm/mach-msm/hotplug.o
  AS      arch/arm/mach-msm/idle-v7.o
  CC      arch/arm/mach-msm/scm.o
/tmp/ccpMCCTM.s: Assembler messages:
/tmp/ccpMCCTM.s:115: Error: selected processor does not support ARM mode `smc #0'
/tmp/ccpMCCTM.s:166: Error: selected processor does not support ARM mode `smc #0'
/tmp/ccpMCCTM.s:233: Error: selected processor does not support ARM mode `smc #0'
/tmp/ccpMCCTM.s:457: Error: selected processor does not support ARM mode `smc #0'
/tmp/ccpMCCTM.s:666: Error: selected processor does not support ARM mode `smc #0'
make[1]: *** [arch/arm/mach-msm/scm.o] Error 1
make: *** [arch/arm/mach-msm] Error 2
 
rav2012 said:
so far I'm stuck with this error like 2 min into compiling..
Code: 
 CC      arch/arm/mach-msm/hotplug.o
  AS      arch/arm/mach-msm/idle-v7.o
  CC      arch/arm/mach-msm/scm.o
/tmp/ccpMCCTM.s: Assembler messages:
/tmp/ccpMCCTM.s:115: Error: selected processor does not support ARM mode `smc #0'
/tmp/ccpMCCTM.s:166: Error: selected processor does not support ARM mode `smc #0'
/tmp/ccpMCCTM.s:233: Error: selected processor does not support ARM mode `smc #0'
/tmp/ccpMCCTM.s:457: Error: selected processor does not support ARM mode `smc #0'
/tmp/ccpMCCTM.s:666: Error: selected processor does not support ARM mode `smc #0'
make[1]: *** [arch/arm/mach-msm/scm.o] Error 1
make: *** [arch/arm/mach-msm] Error 2
Click to expand...
use 4.4.3 instead of 4.6 (default in CM9/10/ics/jb)

ARCH=arm CROSS_COMPILE=~/Android/CM9/prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin/arm-eabi- make -j4

edit bolded path as needed ;)
 
I dont know if it makes a difference or not but that back came from a lucid i didnt activate
If it does make a different i can do it from another phone
 
ok now im getting this error..gonna try and paste over that display folder from the connects kernel source..

Code: 
  CC      lge/com_device/display/backlight_lm3537.o
lge/com_device/display/backlight_lm3537.c: In function 'lm3537_backlight_off':
lge/com_device/display/backlight_lm3537.c:246: error: 'gpio' undeclared (first use in this function)
lge/com_device/display/backlight_lm3537.c:246: error: (Each undeclared identifier is reported only once
lge/com_device/display/backlight_lm3537.c:246: error: for each function it appears in.)
make[3]: *** [lge/com_device/display/backlight_lm3537.o] Error 1
make[2]: *** [lge/com_device/display] Error 2
make[1]: *** [lge/com_device] Error 2
make: *** [lge] Error 2
 
rav2012 said:
ok now im getting this error..gonna try and paste over that display folder from the connects kernel source..

Code: 
  CC      lge/com_device/display/backlight_lm3537.o
lge/com_device/display/backlight_lm3537.c: In function 'lm3537_backlight_off':
lge/com_device/display/backlight_lm3537.c:246: error: 'gpio' undeclared (first use in this function)
lge/com_device/display/backlight_lm3537.c:246: error: (Each undeclared identifier is reported only once
lge/com_device/display/backlight_lm3537.c:246: error: for each function it appears in.)
make[3]: *** [lge/com_device/display/backlight_lm3537.o] Error 1
make[2]: *** [lge/com_device/display] Error 2
make[1]: *** [lge/com_device] Error 2
make: *** [lge] Error 2
Click to expand...
mpcs defconfig?
 
fatdaddysnacks said:
I dont know if it makes a difference or not but that back came from a lucid i didnt activate
If it does make a different i can do it from another phone
Click to expand...

I don't think it makes a difference. No worries. :)

rav2012 said:
ok now im getting this error..gonna try and paste over that display folder from the connects kernel source..
Click to expand...

Damn bro you're an undercover dev. Had I had known I would have just left this in your hands. Lol
 
PlayfulGod said:
I put a flashable zip together with the posted files and it no boot for me. Currently working with the vipers kernel src that happens to includes a cayman_mpcs_us_defconfig for the connect.... makes ya wonder huh???

but working on getting it to compile with ^^^ config.
Click to expand...

omg PG, i frixn love you! im running your black plague on my connect and using it as a base i have fallen in love with my connect again, if you're willing to put some time into this i will love you forever and ever. will happily beta test!!!
 
boomer21b said:
omg PG, i frixn love you! im running your black plague on my connect and using it as a base i have fallen in love with my connect again, if you're willing to put some time into this i will love you forever and ever. will happily beta test!!!
Click to expand...
well we'd prolly have better luck with the lucids src... but it hasnt dropped yet. ;)
 
airtioteclint said:
I don't think it makes a difference. No worries. :)



Damn bro you're an undercover dev. Had I had known I would have just left this in your hands. Lol
Click to expand...
so wait... connect and lucid are very close related devices? i may be able to help in one way or another if anyone thinks ill be of use LOL
 
PlayfulGod said:
well we'd prolly have better luck with the lucids src... but it hasnt dropped yet. ;)
Click to expand...

... do we know when that will happen? and im completely useless with development but if there is anything i can do to help, let me know. i have a connect and will happily be a guinea pig. PG, i bookmarked your donate link. i have every intention of giving you a bit on payday, you deserve it for plague. i cant even begin to tell you how much i love it.
 
ldrifta said:
so wait... connect and lucid are very close related devices? i may be able to help in one way or another if anyone thinks ill be of use LOL
Click to expand...
yea bro, connect, lucid, & viper are all cayman/840, the viper being the most different. but they each use different displays and a few other tidbits.

boomer21b said:
... do we know when that will happen? and im completely useless with development but if there is anything i can do to help, let me know. i have a connect and will happily be a guinea pig. PG, i bookmarked your donate link. i have every intention of giving you a bit on payday, you deserve it for plague. i cant even begin to tell you how much i love it.
Click to expand...
should be in the next week or so if they stick to their norm. And thank you!! :)
 
PlayfulGod said:
yea bro, connect, lucid, & viper are all cayman/840, the viper being the most different. but they each use different displays and a few other tidbits.


should be in the next week or so if they stick to their norm. And thank you!! :)
Click to expand...
ahhh i seee :D well thats cool, im bored and willing to help lol just let me know..
 
sammyz said:
Lucid is most different, please correct me if I'm wrong :)
Click to expand...
Not really diff displays on all 3, internal storage size isnt a factor, viper has different partition map is why I say its the most different.

A ROM for either wont boot on the other and is prolly due to little differeneces on the boards themeselves and why the defconfigs for the lucid and connect wont compile w/o alot of work.



And what is the as840?
 
You must log in or register to reply here.
Back
Top Bottom