Does this actually work on v522?
Some people say yes, some say no.
Can not get a clear definitive answer.
Some people say yes, some say no.
Can not get a clear definitive answer.
Team Win Recovery Project for the LG G Pad X 8.0 (V521, V522, V525)
- Thread starter shabbypenguin
- Start date
-
- Tags
- lg-g-padx
- YES it works on v522 (v522 hardware is no different than the others)
- NO you can't use it on v522 (or anything other than t-mobile v521, as far as I know) because there is currently no way to get around the bootloader locks which prevent unsigned boot images from running.
Clear enough?
This answer is so contradicting lol. You could but you can't, that's definitely not a clear answer. I get my v522 soon and I'll give a clear answer.
Last edited:
In other words hardware wise it should be compatible, Twrp. As for installing custom Roms and mods from Twrp is not possible without the bootloader being unlocked ? is what he meant.
Basically stating that even if we installed Twrp it would have no use for us as in installing Roms, mods, root, etc.
You technically you can't install TWRP with a locked bootloader. A few devices I seen on here people have been able to, but its not rare. So it either you cant or you could. Not a yes and no lol.
Its not terribly difficult to replace anything in the flash on this device, recovery included, via the update mode. What I don't know for sure is if it would make my device a paperweight due to bootloader integrity checks. In the least, the first time I boot the OS to try to use adk tools to issue 'reboot recovery' the OS should re-flash recovery from a bak that is baked into the OS image (which I can't change because as I mentioned the bootloader is locked). There is no button combo to enter recovery on this model line, you can either factory reset or enter update mode - you can only reach "recovery" via adk tools and OS. Factory recovery mode binary is just a error screen that does nothing other than wait for a while and then reboot the device.
TWRP here is built to be hardware independent, while the bootloader from LG (while generally hardware independent) is also built to respond to data in qfprom (efuses presumably, could just be some kinda encrypted blob on mmc though) - things like the model 'v522' etc are hardcoded checks in bootloader and I wouldn't be surprised if keys are model instead of device specific to prevent crossflashing.
So yes, the recovery works on the hardware for all these models because it doesn't care whats in fuses so long as the chips are all there that is uses - but that doesn't help if you can't boot to it without unlocking the bootloader. Personally I thought what I said was crystal clear, even if one doesn't want to believe it. Prove me wrong and I'll happily take it, and even find a way to scrape together a few bucks to pitch into the bounties after the fact - the sad thing is though Rogers/Fido told LG to lock up their allotment, and that is exactly what LG did right down to disabling access to fastboot. Short of a leaked dev bootloader, I don't see it happening any time soon.
TWRP here is built to be hardware independent, while the bootloader from LG (while generally hardware independent) is also built to respond to data in qfprom (efuses presumably, could just be some kinda encrypted blob on mmc though) - things like the model 'v522' etc are hardcoded checks in bootloader and I wouldn't be surprised if keys are model instead of device specific to prevent crossflashing.
So yes, the recovery works on the hardware for all these models because it doesn't care whats in fuses so long as the chips are all there that is uses - but that doesn't help if you can't boot to it without unlocking the bootloader. Personally I thought what I said was crystal clear, even if one doesn't want to believe it. Prove me wrong and I'll happily take it, and even find a way to scrape together a few bucks to pitch into the bounties after the fact - the sad thing is though Rogers/Fido told LG to lock up their allotment, and that is exactly what LG did right down to disabling access to fastboot. Short of a leaked dev bootloader, I don't see it happening any time soon.
The VK521 is very similar to the vk815 (Verizon LG G Pad X 8.3). Is there any chance this would also work on the vk815? I've listed the differences I am aware of below, I just don't know what the major factors are which would make it incompatible. They have the same processor, graphics processor, and memory size.
VK815...|...VK521
Physical size...|...8.3 inches...|...8.0 inches
Resolution...|...1080 x 1920 pixels...|...1200 x 1920 pixels
Pixel density ...|...265 ppi...|...283 ppi
System chip...|...Qualcomm Snapdragon 615 8939...|...Qualcomm Snapdragon 617 8952
LTE (FDD)...|...Bands 4, 13...|...Bands 12, 4, 3, 2, 7
Bluetooth 4.1 4.2
Alternatively, if the answer is "it is impossible to know without trying" or something to that effect, are the odds good that I will irreversibly brick my device by trying it?
I'm very interested in trying to put a custom ROM on this device, it is surprising how little work has been done on it so far.
VK815...|...VK521
Physical size...|...8.3 inches...|...8.0 inches
Resolution...|...1080 x 1920 pixels...|...1200 x 1920 pixels
Pixel density ...|...265 ppi...|...283 ppi
System chip...|...Qualcomm Snapdragon 615 8939...|...Qualcomm Snapdragon 617 8952
LTE (FDD)...|...Bands 4, 13...|...Bands 12, 4, 3, 2, 7
Bluetooth 4.1 4.2
Alternatively, if the answer is "it is impossible to know without trying" or something to that effect, are the odds good that I will irreversibly brick my device by trying it?
I'm very interested in trying to put a custom ROM on this device, it is surprising how little work has been done on it so far.
Link in the first thread doesn't seem to work anymore. Does anyone have another link? Thanks.
I have attached a copy of a ZIP file containing the original recovery 3.0.2.0 recovery file by user shabbypenguin.
Code:
LG G Pad X 8.0 (V521, V522, V525) Team Win Recovery Project 3.0.2.0.zip
13,959,727 bytes
CRC32: b66cd06c
MD5: 3c3e5e3de87a9fed521bbc4a677b1ab9
SHA-1: 628bc5bce87e38a1b39476e176a1bb59276752fe
SHA-256: c8962bcd5d8e822858fbb1de571ec808441a2dffd86c6b8b88da100cc6e56ab6
SHA-512: 03f19aec95e4d7fa0bf3bee4e5a25a289c07c2fcfd43e1061820de9d9f83c9cc8e3e8195014d48b0bd5766e8df0a294bb8a7fd5439c71aebdddec5f31999f1b7You really should have been more clear as to which link was not working. Anyways, what you seek is attached.
Last edited:
Not really.
On my G3, which last I looked could not be bootloader unlocked, I had to install TWRP while unrooted to install SuperSU in order to root.
As I used stock ROMs, I had no problem flashing with TWRP.
Here, the the indication is that the 522 must be rooted before installing TWRP and I haven't been able to find any reports of successful cases of rooting.
So... perhaps you can see the source of my confusion?
Last edited:
If you were able to boot twrp on G3 without unlocking, then you either had a bootloader that had a flaw, or purposely didn't enforce image signing - it did ship with kitkat after all, and they may not have implemented the newer chain of trust google laid out with lollipop. If you were able to boot to stock without it restoring the original bootloader or first modified the stock image via twrp, then that is just odd. All I'm coming up with looking into G3 are soft root methods like towelroot, without using twrp or cwm - nothing that suggests bootloader signature enforcement was occurring.
My own nexus 7 (shipped pre-kitkat), the process of rooting was basically - unlock bootloader, use fastboot to flash twrp, boot to twrp from fastboot to install super-su and replace backup recovery, done. Even back then unlocking the bootloader to boot unsigned twrp was required. Getting this LG device was a curveball in learning, and I still can't comprehend why they are locking me out of something I bought and paid for.
This device (v520/521/522/525) has no way to directly boot to recovery, LG has done their own thing and put in a factory reset (bootloader) and update mode (separate partition from recovery) with just a dummied recovery with no power on key method to reach it. As well, as far as I can tell except on v521 the bootloader is entirely neutered (going into fastboot just doesn't happen it just boots instead, and oem unlock commands are stripped) - as well as the complete chain of trust (image signing) being implemented and enforced when locked and a big warning when unlocked using an unsigned/modified image. I'd love to be wrong though, and I do think it is possible to unlock v522 to a 'developer unlock' via some sort of software process that would disable signature enforcement just like 'oem unlock' does - I just doubt LG is gonna share.
Last edited:
See the thread https://forum.xda-developers.com/lg...1-resurrection-remix-n-v5-8-x-oms-lg-t3598038 for the Team Win Recovery Project 3.1.1-0. Scroll down to the section labeled "Installation Files:".when 3.1.0.0? really need.
btw, thank you so much
Hi, is it THIS flashify?
https://play.google.com/store/apps/details?id=com.cgollner.flashify&hl=en
I'm actually surprise this can be flash without root.
Whenever I click on the download button, it takes me to the T-mobile homepage. Am I doing something wrong?
Site is dead. Use the twrp from this thread.
https://forum.xda-developers.com/lg...rrection-remix-n-v5-8-x-oms-lg-t3598038/page4
edit I tried to use that recovery and ended up basically bricking my tablet. Might work but mine basically replied it failed.
Last edited:
https://imgur.com/a/aHsh0
For anyone smarter than me, would anything from these two screenshots help to possibly find a way to unlock the V522 so that TWRP and root would be possible? Some of those fields are modifiable, and when value 1 isn't, then you can add something in value 2. NV RAM read gives me those values, with the option of changing them and writing them back on the device.
For anyone smarter than me, would anything from these two screenshots help to possibly find a way to unlock the V522 so that TWRP and root would be possible? Some of those fields are modifiable, and when value 1 isn't, then you can add something in value 2. NV RAM read gives me those values, with the option of changing them and writing them back on the device.
To add to this dilema; LG support wont help, however they gave me a number to futuretel which is the manufacturer/service provider for this product. they may be able to tell how to do this. I left a message so will see
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