[Development] Qualcomm (QLM) Auto TWRP recovery porter by Team Hovatek
[Development] Qualcomm (QLM) Auto TWRP recovery porter by Team Hovatek
(11-06-2019, 09:19 PM)tek3195 First and foremost, Thank You Team Hovatek for great work on an extremely tough concept. Android recoveries are nowhere close to a one-size-fits-all type of deal. Really impressive work. Almost worked well. Huawei Mediapad T3 8. Android 7.0 using version 1.1 of the recovery porter caused a build.prop from an LG phone running Android 6.0 to be placed into my recovery. Needless to say that didn't turn out very well. Checked the scripts and patches in tool and that LG build prop is what is in there. I'm not sure but it seems to me that it should be removed a.s.a.p. Whether it was not edited properly due to my particular device or whatever reason the entire thing wound up in my recovery may be, I can't find any logical reason to have a Marshmallow anything in a tool that only specs support for Nougat and Oreo. Other than that it was off a little bit in the recovery.fstab but it was fairly easy to edit. So now my question is How do I fix file name associations? What I mean is in the File Manager everything is correct but under the Install Directory they appear to be some kind of code that makes no sense. Sorry I said files but it is actually the folders. Once I blindly click one of them the folders and files beyond it are readable. Also settings do not survive a reboot and are back to default every time when entering recovery. So, folder names and settings, any thoughts on those two issues ?
(11-06-2019, 09:19 PM)tek3195 First and foremost, Thank You Team Hovatek for great work on an extremely tough concept. Android recoveries are nowhere close to a one-size-fits-all type of deal. Really impressive work. Almost worked well. Huawei Mediapad T3 8. Android 7.0 using version 1.1 of the recovery porter caused a build.prop from an LG phone running Android 6.0 to be placed into my recovery. Needless to say that didn't turn out very well. Checked the scripts and patches in tool and that LG build prop is what is in there. I'm not sure but it seems to me that it should be removed a.s.a.p. Whether it was not edited properly due to my particular device or whatever reason the entire thing wound up in my recovery may be, I can't find any logical reason to have a Marshmallow anything in a tool that only specs support for Nougat and Oreo. Other than that it was off a little bit in the recovery.fstab but it was fairly easy to edit. So now my question is How do I fix file name associations? What I mean is in the File Manager everything is correct but under the Install Directory they appear to be some kind of code that makes no sense. Sorry I said files but it is actually the folders. Once I blindly click one of them the folders and files beyond it are readable. Also settings do not survive a reboot and are back to default every time when entering recovery. So, folder names and settings, any thoughts on those two issues ?
(09-09-2019, 04:43 AM)Reepzvan @Hovatek Team. Guys can you remake the 1.2 version of this that allows the lollipop version to be ported also, & by the way i use this thing last night but no success on my Lenovo a2020a40
(09-09-2019, 01:54 PM)nawazawan i hope so if team hovatek can dot, they even dont know how to deal with build properties.They can pull this off i know just take some time GO GUYS! GO HOVATEK TEAM!
they are using old ANDROID IMAGE KITCHEN inside.
may be their team should also search the net.
Good Luck Hovatek
(09-09-2019, 01:54 PM)nawazawan i hope so if team hovatek can dot, they even dont know how to deal with build properties.
they are using old ANDROID IMAGE KITCHEN inside.
may be their team should also search the net.
Good Luck Hovatek
(09-09-2019, 01:54 PM)nawazawan i hope so if team hovatek can dot, they even dont know how to deal with build properties.
they are using old ANDROID IMAGE KITCHEN inside.
may be their team should also search the net.
Good Luck Hovatek