[RECOVERY] [TWRP 2.8.0.0] [v500] [9-11-2014]

Faded_329

Member
Oct 28, 2013
16
2
0
My file download was *.txt i changed the extension to *.img and used flashify it worked fine. I now noticed that when i boot into recovery an error message comes on the screen "secure boot error" or something like that, is that supposed to be there or did i do something wrong?
 

Drgravy

Senior Member
Mar 22, 2012
985
2,537
0
My file download was *.txt i changed the extension to *.img and used flashify it worked fine. I now noticed that when i boot into recovery an error message comes on the screen "secure boot error" or something like that, is that supposed to be there or did i do something wrong?
it is supposed to say that
just means the loki patch is working
 
  • Like
Reactions: katsika

urusaikara

Member
Dec 17, 2010
20
1
0
34
Seoul
I am using Korean version of Gpad and tried to flash twrp...

my firmware version is v50010e

I tried every method in this thread including chmod777 thing...

but my screen keep says

[-] Loki aboot version does not match devices.

can I get a little help? I really eager to flash cm rom...T_T
 

Drgravy

Senior Member
Mar 22, 2012
985
2,537
0
I am using Korean version of Gpad and tried to flash twrp...

my firmware version is v50010e

I tried every method in this thread including chmod777 thing...

but my screen keep says

[-] Loki aboot version does not match devices.

can I get a little help? I really eager to flash cm rom...T_T
loki does not support your device right now but we may be able to fix that


I need some info:

well I'll need some values from your: build.prop
so use your favorite root browser and navigate to system/build.prop and tell me these values:


Code:
ro.product.model=
ro.product.brand=
ro.product.name=
ro.product.device=
ro.product.board=

ro.build.version.incremental=
ro.build.version.sdk=
ro.build.version.codename=
ro.build.version.release=

ro.build.description=
ro.build.fingerprint=
ill need a copy of your aboot

plug your device into your pc with usb debugging turned on
and issue these commands in your terminal

Code:
adb shell
su
dd if=/dev/block/platform/msm_sdcc.1/by-name/aboot of=/data/local/tmp/aboot.img
chmod 644 /data/local/tmp/aboot.img
exit
exit
adb pull /data/local/tmp/aboot.img

then I will submit an issue request for the loki patch
 
  • Like
Reactions: thlorin and katsika

urusaikara

Member
Dec 17, 2010
20
1
0
34
Seoul
loki does not support your device right now but we may be able to fix that


I need some info:

well I'll need some values from your: build.prop
so use your favorite root browser and navigate to system/build.prop and tell me these values:


Code:
ro.product.model=
ro.product.brand=
ro.product.name=
ro.product.device=
ro.product.board=

ro.build.version.incremental=
ro.build.version.sdk=
ro.build.version.codename=
ro.build.version.release=

ro.build.description=
ro.build.fingerprint=
ill need a copy of your aboot

plug your device into your pc with usb debugging turned on
and issue these commands in your terminal

Code:
adb shell
su
dd if=/dev/block/platform/msm_sdcc.1/by-name/aboot of=/data/local/tmp/aboot.img
chmod 644 /data/local/tmp/aboot.img
exit
exit
adb pull /data/local/tmp/aboot.img

then I will submit an issue request for the loki patch
here is my device information and aboot img :)

ro.product.model= LG-V500
ro.product.brand= lge
ro.product.name= awifi_open_kr
ro.product.device= awifi
ro.product.board= MSM8960

ro.build.version.incremental= V50010e.1384908454
ro.build.version.sdk= 17
ro.build.version.codename= REL
ro.build.version.release= 4.2.2

ro.build.description= awifi_open_kr-user 4.2.2 JDQ39B/V50010e.1384908454 release-keys
ro.build.fingerprint= lge/awifi_open_kr/awifi:4.2.2/JDQ39B/V50010e.1384908454:user/realease-keys

thanks inadvanced~^^
 

Attachments

Last edited:

SnowPluralism

Senior Member
Jan 11, 2012
1,693
1,403
113
Inside Your Mind
Noo ... should appear only when youre booting into recovery

Enviado do meu GT-I9300 através de Tapatalk

---------- Post added at 11:09 PM ---------- Previous post was at 11:08 PM ----------

Unless you are on cm in that case ( havent tryed cm yet )
I guess it would be normal

Enviado do meu GT-I9300 através de Tapatalk
 

Gloaming

Member
Apr 23, 2012
12
0
0
I used the latest nightlies of CM11...so it isn't normal?
I try to flash again the recovery but is the same.

Sent from my LG-V500 using xda app-developers app
 

urusaikara

Member
Dec 17, 2010
20
1
0
34
Seoul
updated op

added support for all three software versions

plus I added a flashable zip

if you are already using 2.6.3.1 there is no need to update
Thanks! I am in my office and left my device at home. I will test it right away and report whther it works ;)

Sent from my LG-F320K using XDA Premium 4 mobile app
 

akaloith

Senior Member
Dec 24, 2006
232
36
48
i tried zip
i tried lok -> img and flashify
it does not fit the whole screen, seems 1080x1920 :(
at first i think it was ok
after rom toolbox i think it got to not fill fullscreen
dont know what to do any suggestions?
 

SnowPluralism

Senior Member
Jan 11, 2012
1,693
1,403
113
Inside Your Mind
It was never fullscreen. Its discussed few pages back.
Theres no current twrp theme made to fit our screen resolution and dalingrin doesnt feel the need to spend time making one since this a minor thing and all the recovery works :)
Maybe a day :)
I already took a look un making a twrp theme. But i have no time :/

Enviado do meu GT-I9300 através de Tapatalk
 

Gloaming

Member
Apr 23, 2012
12
0
0
I used the latest nightlies of CM11...so it isn't normal?
I try to flash again the recovery but is the same.

Sent from my LG-V500 using xda app-developers app
is there anyone so kind to answer me?

Everytime i turn on my pad i receive this message

Code:
Secure Booting Error!! 
Cause: Device Unlock, so Boot Success!
after that appears the cyanogenmod logo, andeverything goes well.
i'm just concerned to understand if it's my problem, or the right behavior of the tablet

thank you
 

SnowPluralism

Senior Member
Jan 11, 2012
1,693
1,403
113
Inside Your Mind
is there anyone so kind to answer me?

Everytime i turn on my pad i receive this message

Code:
Secure Booting Error!! 
Cause: Device Unlock, so Boot Success!
after that appears the cyanogenmod logo, andeverything goes well.
i'm just concerned to understand if it's my problem, or the right behavior of the tablet

thank you
My guess is that happens because loki is bypassing the bootloader so u can rum a custom kernel ( cm kernel )
So dont worry about it to much

If u wanna be certain restore back to stock rom and then check if message still apears!

Sent From My Galaxy S III Using XDA Premium 4
 
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone