You could also leave the surprise on the first post.not bored but I left a surprise in your pm inbox
LOL good one!
testing was required firstYou could also leave the surprise on the first post.
We have download mode, not bootloader or fastboot mode... That's why it won't work.Why is reboot to bootloader disabled? Is it to avoid users to mess things up?
Why is reboot to bootloader disabled? Is it to avoid users to mess things up?
well it's not like we don't have them it'that they are locked down tighter than fort knoxWe have download mode, not bootloader or fastboot mode... That's why it won't work.
-VZW LG G2 VS980
I'll see if I still have an apk for an experimental Samsung s3 reboot app that the dev was able to boot directly into dl mode via the app. Think there would be a similarity?well it's not like we don't have them it'that they are locked down tighter than fort knox
also I've been trying to get reboot to download mode working but no luck
nah thats ok but you can try if you wantI'll see if I still have an apk for an experimental Samsung s3 reboot app that the dev was able to boot directly into dl mode via the app. Think there would be a similarity?
-VZW LG G2 VS980
yeah I never did anything with encryption so it probably isn't going to workUnfortunately twrp 2.6.3.3 or 2.7.0.0 cannot handle device encryption on gpad. After I encrypted my device and booted into twrp, there is not data partition. On my Nexus 4 I get a password prompt and then it mounts the data partition. On Gpad I cannot even tick the data partition in Mount-Options and I don't get a password prompt.
Thanks for trying to fix it, I am looking forward to act as guinea pig.yeah I never did anything with encryption so it probably isn't going to work
your the first person to ever mention anything about it so I just left it alone but I can look into making it work.
I think I need these tooMaybe one of these flags fixes encryption:
TW_INCLUDE_CRYPTO := true
TW_INCLUDE_JB_CRYPTO := true
Is because is not "footer" is "encrypt"I think I need these too
but finding the hex for FS_FLAGS is key I think
but I'm not sure cause I keep getting error can't locate footer
TW_CRYPTO_FS_FLAGS := "0x00000406"
TW_CRYPTO_KEY_LOC := "footer"
I built TWRP with encryption and don't have that error in the log. Anyway my data partition is not encrypted, so I cannot test it properly.I think I need these too
but finding the hex for FS_FLAGS is key I think
but I'm not sure cause I keep getting error can't locate footer
TW_CRYPTO_FS_FLAGS := "0x00000406"
TW_CRYPTO_KEY_LOC := "footer"
Thanks! I tried your build andI built TWRP with encryption and don't have that error in the log. Anyway my data partition is not encrypted, so I cannot test it properly.
The full stock 4.4.2 had an upgraded aboot that isn't Loki exploitable.(or if it is has not been included in loki_patch). Therefore the only method is to gain root with ioroot25 http://forum.xda-developers.com/showpost.php?p=48709232&postcount=869&nocache=1&z=7334539103321731Hi to all, there's a method to install TWRP on G Pad with stock Android 4.4.2 v50020a?
Thanks
Can't you just use flashify?The full stock 4.4.2 had an upgraded aboot that isn't Loki exploitable.(or if it is has not been included in loki_patch). Therefore the only method is to gain root with ioroot25 http://forum.xda-developers.com/showpost.php?p=48709232&postcount=869&nocache=1&z=7334539103321731
Then restore 4.2.2 aboot via dd, followed by installing a loki'd twrp image.