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

ovu85

Senior Member
Sep 22, 2011
498
65
58
Hi, I have the V50020b 4.4.2 rooted with ioroot, bootloader is locked (couldn't enter)
I tried to sideload Twrp but the install aborted.

how can i install TWRP?

Thanks!
 

ovu85

Senior Member
Sep 22, 2011
498
65
58
Boot into fastboot, fasboot flash recovery name_of_recovery or use flashify.
i can't enter fastboot.
I've installed Flashify and flashed twrp recovery and i get
Secure booting Error
Cause: boot certification verify
my bootloader is still locked because i can't enter fastboot mode
 

MonaLisaOverdrive

Senior Member
Apr 28, 2013
112
18
0
I've checked this thread and a few others so apologies if this is obvious...is there a TWRP or CWM for a VK81035a running 5.0.2?

Everything I've seen so far is for V500 and/or 4.4.2 and Flashify doesn't include the GPad 8.3 as a supported model
 

roirraW "edor" ehT

Recognized Contributor
May 8, 2010
8,906
4,982
253
Columbus, OH
I've checked this thread and a few others so apologies if this is obvious...is there a TWRP or CWM for a VK81035a running 5.0.2?

Everything I've seen so far is for V500 and/or 4.4.2 and Flashify doesn't include the GPad 8.3 as a supported model
Do a search on this and the Development section for VK810. You have to install v2.7.0.1 first, then you can upgrade to the latest also available here.

Note this caveat. So far, we haven't found a way around the following: you have to have the bootloader from 4.2.2 to get into TWRP (you can find the bootloader and the terminal or adb commands in my section on Android File Host in my signature), but 35A and 36B ROMs won't boot without the 35A and 36B bootloaders. But you can switch them as you need to.

You can find those that you can flash in my section on Android File Host too.

It's funny, I never usually look at this thread.

[VK810.4G] [altev] [ViKtory810ROM] official LG G Pad 8.3 Lollipop 36B_00 5.0.2
[VK810.4G] [altev] official LG G Pad 8.3 Lollipop 36B_00 5.0.2 DEBLOAT SCRIPTS and copies of all the files they remove
[VK810.4G] [altev] OTAs, .IMGs and KDZs, oh my
 
Last edited:
  • Like
Reactions: jonup

jonup

Senior Member
Dec 27, 2012
3,493
2,689
0
Do a search on this and the Development section for VK810. You have to install v2.7.0.1 first, then you can upgrade to the latest also available here.

Note this caveat. So far, we haven't found a way around the following: you have to have the bootloader from 4.2.2 to get into TWRP (you can find the bootloader and the terminal or adb commands in my section on Android File Host in my signature), but 35A and 36B ROMs won't boot without the 35A and 36B bootloaders. But you can switch them as you need to.

You can find those that you can flash in my section on Android File Host too.

It's funny, I never usually look at this thread.

[VK810.4G] [altev] [ViKtory810ROM] official LG G Pad 8.3 Lollipop 36B_00 5.0.2
[VK810.4G] [altev] official LG G Pad 8.3 Lollipop 36B_00 5.0.2 DEBLOAT SCRIPTS and copies of all the files they remove
[VK810.4G] [altev] OTAs, .IMGs and KDZs, oh my
Thanks for being so helpful! This not relevant to me, but gratitude is due where it is due
 

MonaLisaOverdrive

Senior Member
Apr 28, 2013
112
18
0
Do a search on this and the Development section for VK810. You have to install v2.7.0.1 first, then you can upgrade to the latest also available here.

Note this caveat. So far, we haven't found a way around the following: you have to have the bootloader from 4.2.2 to get into TWRP (you can find the bootloader and the terminal or adb commands in my section on Android File Host in my signature), but 35A and 36B ROMs won't boot without the 35A and 36B bootloaders. But you can switch them as you need to.

You can find those that you can flash in my section on Android File Host too.

It's funny, I never usually look at this thread.

[VK810.4G] [altev] [ViKtory810ROM] official LG G Pad 8.3 Lollipop 36B_00 5.0.2
[VK810.4G] [altev] official LG G Pad 8.3 Lollipop 36B_00 5.0.2 DEBLOAT SCRIPTS and copies of all the files they remove
[VK810.4G] [altev] OTAs, .IMGs and KDZs, oh my
At least one of the threads on recoveries...and possibly an external article as well...point to this thread.

Thanks for posting the caveat. Clarification question: Are you saying that the 35A ROMs need the earlier (4.2.2) bootloader to install TWRP, but won't boot without the current (5.0.2) bootloader?

If so, is this something that is currently being investigated?

Sent from my VK810 4G using Tapatalk
 
  • Like
Reactions: roirraW "edor" ehT

roirraW "edor" ehT

Recognized Contributor
May 8, 2010
8,906
4,982
253
Columbus, OH
At least one of the threads on recoveries...and possibly an external article as well...point to this thread.

Thanks for posting the caveat. Clarification question: Are you saying that the 35A ROMs need the earlier (4.2.2) bootloader to install TWRP, but won't boot without the current (5.0.2) bootloader?

If so, is this something that is currently being investigated?

Sent from my VK810 4G using Tapatalk
You're welcome! Correct, but not just to install TWRP. To get into it again later. Not that I know of to the second question. I don't have enough know how yet apparently. Another dev helped me try something that should have worked but it didn't.

It works well enough for me. From running Android can use terminal to flash the 4.2.2 bootloader, reboot to recovery, then once done in recovery, the last thing before exiting flash the appropriate 35A or 36B bootloader and boot into the ROM.
Thanks for being so helpful! This not relevant to me, but gratitude is due where it is due
Thanks! And you're welcome! [emoji4]

[VK810.4G] [altev] [ViKtory810ROM] official LG G Pad 8.3 Lollipop 36B_00 5.0.2
[VK810.4G] [altev] official LG G Pad 8.3 Lollipop 36B_00 5.0.2 DEBLOAT SCRIPTS and copies of all the files they remove
[VK810.4G] [altev] OTAs, .IMGs and KDZs, oh my
 
  • Like
Reactions: MonaLisaOverdrive

MonaLisaOverdrive

Senior Member
Apr 28, 2013
112
18
0
You're welcome! Correct, but not just to install TWRP. To get into it again later. Not that I know of to the second question. I don't have enough know how yet apparently. Another dev helped me try something that should have worked but it didn't.
Last (hopefully) clarification questions: So basically I'd be running two bootloaders side by side? One to boot the device and another to boot into TWRP? Also, do I still use the download and run the instructions in the first post in this thread, even though the download says "Please note this is for 4.2.2 only"?

I'm still a novice when it comes to Android internals but I'll poke around to see if there's an obvious reason for needing the 4.2.2 bootloader.

It works well enough for me. From running Android can use terminal to flash the 4.2.2 bootloader, reboot to recovery, then once done in recovery, the last thing before exiting flash the appropriate 35A or 36B bootloader and boot into the ROM.
Does CWM have this requirement (4.2.2 bootloader to install/enter recovery, 5.0.2 bootloader to boot device)?

 
Last edited:

roirraW "edor" ehT

Recognized Contributor
May 8, 2010
8,906
4,982
253
Columbus, OH
Last (hopefully) clarification questions: So basically I'd be running two bootloaders side by side? One to boot the device and another to boot into TWRP? Also, do I still use the download and run the instructions in the first post in [URL=" thread[/URL], even though the download says "Please note this is for 4.2.2 only"?

I'm still a novice when it comes to Android internals but I'll poke around to see if there's an obvious reason for needing the 4.2.2 bootloader.

Does CWM have this requirement (4.2.2 bootloader to install/enter recovery, 5.0.2 bootloader to boot device)?
I wouldn't choose to call it side by side because I think that's confusing personally, but yes. You have to downgrade your bootloader to 4.2.2 before installing TWRP 2.7.0.1. It won't work without doing that first.

Yes, any custom recovery including CWM requires the 4.2.2 bootloader to get into custom recovery. The 4.2.2 bootloader has an exploit that allows getting TWRP to install in the first place, and to allow getting into custom recovery. Even if you chose to use CWM, you'd still absolutely HAVE to install TWRP v2.7.0.1 because it's a special one made to take advantage of the Loki exploit in the 4.2.2 bootloader. From there, you can then flash whatever custom recovery you want that's made specifically for the VK810.

That aspect is similar to the situation on the VS985 G3, where we need the 4.4.2 bootloader to get into custom recovery. I do have some more ideas to try on the VK810 but who knows when or if I'll get a chance to test them.
 

Deltadroid

Recognized Contributor
Apr 19, 2013
3,764
9,879
263
I'm not sure about the vk810, but the v500 requires an aboot.img from 4.4.2 (kitkat) or 4.2.2 (jellybean) for a "bumped" recovery to work. When lollipop was released, LG changed the verification signature so that bumped images no longer work with the lollipop aboot.img. Before we had "bumped" images (which is basically an image with the official LG signature to pass the boot loader verification check), we had to use Loki. Loki only works with an aboot.img from 4.2.2.

It is not actually the bootloader that must be downgraded for Loki to work. It is aboot.
 
Last edited:

Deltadroid

Recognized Contributor
Apr 19, 2013
3,764
9,879
263
aboot is part of the firmware, but when updating the bootloader, we are usually only talking about:

rpm.img, sbl1.img, sbl2.img, sbl3.img, tz.img.

aboot.img is usually not touched because it affects loki compatibility and bump compatibility and it is not necessary to upgrade that. But, since we are all using bumped images, aboot can be updated to 4.4.2. When we used loki, we had to keep aboot on version 4.2.2. The aboot from lollipop breaks both methods (bumped and loki).
 

roirraW "edor" ehT

Recognized Contributor
May 8, 2010
8,906
4,982
253
Columbus, OH
aboot is part of the firmware, but when updating the bootloader, we are usually only talking about:

rpm.img, sbl1.img, sbl2.img, sbl3.img, tz.img.

aboot.img is usually not touched because it affects loki compatibility and bump compatibility and it is not necessary to upgrade that. But, since we are all using bumped images, aboot can be updated to 4.4.2. When we used loki, we had to keep aboot on version 4.2.2. The aboot from lollipop breaks both methods (bumped and loki).
Apparently on the VS985 and VK810 we have different terminology. We refer to all those partitions, in addition to the aboot.img, together as a group as the "bootstack", but we call the aboot.img the bootloader. *shrug*
 
  • Like
Reactions: Deltadroid

MonaLisaOverdrive

Senior Member
Apr 28, 2013
112
18
0
You're welcome! Correct, but not just to install TWRP. To get into it again later. Not that I know of to the second question. I don't have enough know how yet apparently. Another dev helped me try something that should have worked but it didn't.

It works well enough for me. From running Android can use terminal to flash the 4.2.2 bootloader, reboot to recovery, then once done in recovery, the last thing before exiting flash the appropriate 35A or 36B bootloader and boot into the ROM.

Thanks! And you're welcome! [emoji4]

[VK810.4G] [altev] [ViKtory810ROM] official LG G Pad 8.3 Lollipop 36B_00 5.0.2
[VK810.4G] [altev] official LG G Pad 8.3 Lollipop 36B_00 5.0.2 DEBLOAT SCRIPTS and copies of all the files they remove
[VK810.4G] [altev] OTAs, .IMGs and KDZs, oh my
I wouldn't choose to call it side by side because I think that's confusing personally, but yes. You have to downgrade your bootloader to 4.2.2 before installing TWRP 2.7.0.1. It won't work without doing that first.

Yes, any custom recovery including CWM requires the 4.2.2 bootloader to get into custom recovery. The 4.2.2 bootloader has an exploit that allows getting TWRP to install in the first place, and to allow getting into custom recovery. Even if you chose to use CWM, you'd still absolutely HAVE to install TWRP v2.7.0.1 because it's a special one made to take advantage of the Loki exploit in the 4.2.2 bootloader. From there, you can then flash whatever custom recovery you want that's made specifically for the VK810.

That aspect is similar to the situation on the VS985 G3, where we need the 4.4.2 bootloader to get into custom recovery. I do have some more ideas to try on the VK810 but who knows when or if I'll get a chance to test them.
Thanks for the info.

One more question that I forgot: Are there utilities that manage the process of flashing 4.2.2 to get into TWRP, then flashing 5.0.2 to boot the device?

I'll look for instructions to flash 4.2.2 and load TWRP
 
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