Team Win Recovery Project for the LG G Pad X 8.0 (V521, V522, V525)

[eriklion]

ive uplaoded a version taht fixed that, but im unable to mount external_sd or usb otg. sda1 doesnt show up for me in /dev/block and even manually trying to mount sdcard to mccblk1p1 fails due to an invalid arguement, how did you mount yours?

for external sd, I did mount /dev/block/mmcblk1p1 /external_sd I might add that this assumes that the first partition on the SDcard is vfat/exfat
for OTG(USB port, cant have power connected first otherwise the USB port will not work. Plug USB device first then power.), I did mount /dev/block/sda1 /usb-otg or wherever it's supposed to be.

Is there anything that I could grab for you from my device? let me know, I've got IRC and I'm not afraid to use it #motomagic, #lg-irc etc. Nick is QuinnLion

 

[pressmoon]

TWRP Still Not Working

you need to go to wipe > format data. your devices data is by default encrypted and twrp cant decrypt it. once youve wiped data, reboot recovery and then do a factory reset. your device will boot and function as normal and youll have a fully working twrp

I've wiped and did a factory resent and TWRP still won't show the full 133 GB's available on my pad. It only shows 6052 in internal storage which means it won't do a backup as there's not enough space to do so.

I've reflashed it several times and it's still the same. I've never had this problem with it before on several different phones. Any other suggestions please?

I'd greatly appreciate it.

 

[shabbypenguin]

I've wiped and did a factory resent and TWRP still won't show the full 133 GB's available on my pad. It only shows 6052 in internal storage which means it won't do a backup as there's not enough space to do so.

I've reflashed it several times and it's still the same. I've never had this problem with it before on several different phones. Any other suggestions please?

I'd greatly appreciate it.

https://github.com/TeamWin/Team-Win-Recovery-Project/issues/529

adoptable storage doesnt work in twrp yet.

i havent yet fixed the microsdcard yet either. it sounds like its reporting internal storage and thats all, which is what it should be doing atm.

 

[pressmoon]

That Is the Problem

https://github.com/TeamWin/Team-Win-Recovery-Project/issues/529

adoptable storage doesnt work in twrp yet.

i havent yet fixed the microsdcard yet either. it sounds like its reporting internal storage and thats all, which is what it should be doing atm.

That's it then so my only option if I want to use TWRP is to do away with having adopted my SD card. Then I'm limiting how much space I have available on internal storage. No TWRP for me then.

Thank you for explaining that to me Shabby P.

 

[shabbypenguin]

That's it then so my only option if I want to use TWRP is to do away with having adopted my SD card. Then I'm limiting how much space I have available on internal storage. No TWRP for me then.

Thank you for explaining that to me Shabby P.

once i get microsdcard working you can split teh sdcard up and do 75% on adoptable storage and 25% for twrp/pictures etc

 

[pressmoon]

That Would Be Great

once i get microsdcard working you can split teh sdcard up and do 75% on adoptable storage and 25% for twrp/pictures etc

Once you do that would you publish it on the 1st page along with how to root so that all would be aware of it? If so, that would be great.

Thank you again Shabby P.

 

[k0nane]

Still putting in the service for unloved devices, eh Shab?

 

[avishah395]

@shabbypenguin If you know, how long would it take for someone to make a custom kernel disabling the boot message "cannot check for software corruption"?

 

[shabbypenguin]

Still putting in the service for unloved devices, eh Shab?

I knew this recovery was good, but I didn't expect it to be so good to bring people back from the dead :x. nah, this is just a one off device cuz i bought it (was a really good promo for father's day). I've pretty much given up on android development, far better things to be spending my time on

@shabbypenguin If you know, how long would it take for someone to make a custom kernel disabling the boot message "cannot check for software corruption"?

its in the bootloader as previously mentioned.

 

[k0nane]

I've pretty much given up on android development, far better things to be spending my time on .

Same, at least from this side - app development, however... ...is another topic that doesn't belong in this thread.

 

[shabbypenguin]

Same, at least from this side - app development, however... ...is another topic that doesn't belong in this thread.

my contact info is still the same

 

[avishah395]

I knew this recovery was good, but I didn't expect it to be so good to bring people back from the dead :x. nah, this is just a one off device cuz i bought it (was a really good promo for father's day). I've pretty much given up on android development, far better things to be spending my time on



its in the bootloader as previously mentioned.

Ok, if it's in the bootloader. How do I disable the message? Am I missing something here?

 

[shabbypenguin]

Ok, if it's in the bootloader. How do I disable the message? Am I missing something here?

dump the bootloader, scan through with a hex editor, edit the file, resign it with lg's private key and then flash it back onto your tablet.

 

[avishah395]

dump the bootloader, scan through with a hex editor, edit the file, resign it with lg's private key and then flash it back onto your tablet.

That's definitely something I cannot do. You lost me at dump the bootloader, I don't even know how to do that.

---------- Post added at 08:10 AM ---------- Previous post was at 07:25 AM ----------

Updated Instructions: This guide will work for all rooted variants.

1. Follow the root guide to get your device rooted.
2. Download the TWRP image above.
3. Install Flashify
4. Open 'Flashify' and give it superuser permissions.
5. Tap 'Recovery image' and 'Choose a file' and navigate to where you have downloaded the TWRP image on your device.
6. When the flash has completed, tap 'Reboot now' and you should boot into TWRP.
7. Go to 'Wipe' and Format Data to remove encryption on the internal storage. This will delete any of the files and data you have, make sure you have your device backed up with LG Backup for an easy restore.
8. You may now begin to use TWRP normally. Create a backup and more...

@shabbypenguin you may copy this to add it to the main post with it's formatting by using the quote feature and removing the quote tags.

 

[joeblowma]

@shabbypenguin "cannot check for software corruption"?

If that is the exact wording of it, I'm not seeing any 'cannot' message with relation to signatures in aboot or sbl (though I suppose it could be a image and not actual text?), though plenty of them with regards to not being able to load things like GPT or partitions. And yes shabbypenguin, before you say it I know resigning the bootloader is technically impossible (barring a leaked private key) - I just suspected the actual message is in boot.img rather than bootloader.

 

[avishah395]

If that is the exact wording of it, I'm not seeing any 'cannot' message with relation to signatures in aboot or sbl (though I suppose it could be a image and not actual text?), though plenty of them with regards to not being able to load things like GPT or partitions. And yes shabbypenguin, before you say it I know resigning the bootloader is technically impossible (barring a leaked private key) - I just suspected the actual message is in boot.img rather than bootloader.

The actual wording is "The software on this device cannot check for corruptions"

 

[joeblowma]

Definitely no sign of that phrase in the t-mo aboot/bootloader, just the "If you unlock the bootloader, you will be..." warning for when you do the unlock. I suppose bootloader could be chainloading another image like these other ones which I don't know what they are (tz for example) but I don't think its directly responsible for the message.

 

[shabbypenguin]

If that is the exact wording of it, I'm not seeing any 'cannot' message with relation to signatures in aboot or sbl (though I suppose it could be a image and not actual text?), though plenty of them with regards to not being able to load things like GPT or partitions. And yes shabbypenguin, before you say it I know resigning the bootloader is technically impossible (barring a leaked private key) - I just suspected the actual message is in boot.img rather than bootloader.

thats the info i got from autoprime, the last lg device i worked on was the lg optimus G so i defer my knowledge about how and why they do things to what he tells me. i know on moto's you can flash em and it's a separate partition that is a specially formatted image.

 

[joeblowma]

Ah I see it, some 25 images are in a munge of sorts called raw_resources.bin in the update which seem to be loaded by bootloader, "verifiedboot_red", "verifiedboot_yellow" and "verifiedboot_orange" (g.co/ABH has them rendered as well), among other images including the battery charging logo and even the 'factory reset' text lines. Yet another strike against my own bootloader, it only supports the red "your device is corrupt. It can't be trusted" image - good to know though, I was wondering where the factory reset text/binary was and it was indeed the bootloader all along.

So yeah, short of a private key being leaked or someone having a quantum computer at their disposal... probably stuck with the message if the bootloader is unlocked

 

[porear]

Any movement on the external SD card issue? I'm stymied with a full internal that I can't back up. Thanks!