Hi guys,
i have an old ASUS MeMOPad FHD10 LTE, which i am trying to use LineageOS with.
TLDR: suddenly no Touch input in TWRP Recovery AND LineageOS 15.1/16 after it worked at first, OTG cable with mouse/keyboard input as workaround, in stock ROM the touch input IS working without problems
I unlocked the bootloader, did a backup of stock recovery img, flashed TWRP v3.2.3-0 for [Asus_ME302KL][DUMA] (from here). I rebooted to TWRP and made a NANDROID backup and flashed LineageOS ROM 15.1 (from here)
Everything worked perfectly fine until here, i booted up LineageOS 15.1 successfully, then i tried to flash mindthegapps (from here), i noticed too late this was the 64bit Version and ofc it bugged out to hell.
I then wiped data/cache and flashed 15.1 ROM and this time i used opengapps full package for 8.1 and flashed it directly after, but on reboot LineageOS 15.1 got stuck (just rebooted after 20min loading screen).
Then after a few more steps and tinkering, including trying out Lineage 16 for ME302KL, at one point the touch input in TWRP stopped responding on entering recovery. Multiple restarts didn't help. I didn't do anything other then flashing ROMs and wiping data/cache (at some point /system too).
I plugged in an USB Mouse with OTG and was able to navigate and flash back the stock ROM from nandroid backup, the touch input worked just fine!
Then i rebooted into TWRP, still no touch. I flashed LineageOS 15.1 ROM, and to my shocking, also no touch input after booting up. Flashing back stock ROM did get it back to working again. I even flashed back the stock recovery IMG and re-flashed TWRP again, still no luck.
What else is there, that i can try?
I was thinking of fastboot erase/format in bootloader, which partitions do i have to delete for a FULL reset, since flashing back stock recovery/rom didn't help?
Got touch input working with twrp-3.1.1-0-duma (older version), proceeded to flash Lineage 14.1 for MeMOPAD10 FHD... still no touch input there.. im so confused, any help?
Got touch working now with AOSP Extended ROM: https://forum.xda-developers.com/android/general/rom-aosp-extended-v4-4-t3637692
For now i'll stick to that.. but why does it break on LineageOS?
Hi, May i know how you unlocked the boot loader? for me the .apk downloaded from ASUS is not working. it always says "An unkown error occurs, which may be a network connection issue. please wait and try again later".
is there any other way to unlock the bootloader? appreciate your response.
Hello, may I ask how you unlocked the boot loader?
Related
Hi! I've been messing with my phone for a while and have it rooted and Bumpd with TWRP and I recently decided to switch back from the unofficial CM12 to the system backup I made before flashing CM. After I restored it, it wanted to install a sprint update and said it would reboot to install it, stupidly I pressed "okay" and didn't realize that it probably wouldn't install correctly with TWRP and not the original recovery. Now every time I restart the phone it boots into recovery (I assume because it wants to install the update). I have tried to boot it into download to reinstall the stock firmware but it still boots into recovery. Any help or ideas would be greatly appreciated!
Go here follow instructions http://forum.xda-developers.com/showthread.php?p=55367233
Have a great day! from my LG G3
Hi there, i'm writing this in hopes of someone reading it who give me some pointers.
i was running for the last years on CM 10.2.1 but i thought it was time for an update. update to CM 11.2 worked but my installed apps were making some weird troubles so i decided to do a factory reset and there my trouble started.
i flashed to boot.img in fastboot, cleared cache with fastboot cmd
format \system, \data, \cache and of course dalvik
flashed rom CM 11.2 (from official cyanogenmod site) via recovery sideload
rebooted and as my thread title says was stuck on CM boot sequence
i tried different CM roms, but always the same result. system wont end the bootup.
i even suspected a problem with CMW v6.0.4.8 and flashed TWRP from the CM 12.1 thread here in the forum.
so in short i can flash boot.img, recovery, different roms but in the end can't get it to work.
i would really appreciate some hints what i could do differently or maybe were i go wrong.
if you need more info i'm happy to supply them to you.
Thanks in advance.
solved by installing a TWRP backup and boot.img what i found on a german android site.
i was also able after that to install CM 12.1 unofficial and its running now. but i'm totally stumped what caused this weird problem to begin with. doesn't really matter now, i'm relieved it worked in the end.
Installed TWRP twrp-3.1.0-1-lt02ltetmo.img on Samsung Galaxy Tab 3 SM-T217S using Heimdall 1.4.0. Eventually will install LineageOS but as a first step wanted to successfully install TWRP. Have zero experience with all this besides occasional casual usage on an old tablet with the stock KitKat install.
First thing to note to anyone else trying to install a ROM on a Samsung Glaxy Tab 3 SM-T217S. twrp-3.1.0-1-lt02ltetmo.img works. twrp-3.1.1-0-lt02ltetmo.img causes an endless reboot. If accidentally install twrp-3.1.1-0-lt02ltetmo.img use Heimdall to install twrp-3.1.0-1-lt02ltetmo.img.
So TWRP installed okay. Now the device boots into TWRP. How can TWRP be set to boot back "into" the KitKat Android that is currently installed? LUKS encryption (or whatever LUKS/dm-crypt derivative Android uses) is used but assume this shouldn't be an issue since /boot ins't encrypted with LUKS/dm-crypt.
Decided to forget trying to boot old rom and install LineageOS. Assumed (wrongly, maybe?) that TWRP was a bootloader like grub that could easily load standard rom with LUKS/dm-crypt.
Couldn't use TWRP to wipe /data or other partitions due to encryption. TWRP can however just reformat which worked. Than used "adb sideload" to install LineageOS and OpenGApps. About OpenGApps. Used the "aroma" variant which allows choice of which apps to install. The touch screen and home/ back buttons do not work for proceeding with the OpenGApps install. Have to kinda use the volume and power buttons to make and select options during the install. Never really figured out how to make choices so just installed the "pico" (minimal) variant of OpenGApps which installed fine.
Installing LineageOS was absolutely worth it to anyone else thinking about doing so.
Hello everyone,
My phone has a small issue. It was running under lineage 15.1 and after an update never restarted correctly (bootloop).
The first thing I tried to do is going to twrp to restore a backup, but when in twrp, touchscreen does not work. It also doesn't work in eRecovery.
I saw somewhere on the forums that a boot.img flash was required, so I tried flashing a save I did a while ago, with no luck.
Also tried older and newer versions of twrp.
Can anyone help me ?
Hello!
Yesterday, after succesfuly installing the modified VBmeta image and flashing TWRP, i ended up wiping my OS accidentaly.
Trying to take advantage of the situtation, i searched some custom roms to install, and found the Lineage OS 18.0 Thread on the Galaxy a10 custom roms. I wiped the required caches, and flashed the OS, Magisk and Gapps (NikGapps) in this order.
However, my phone won't boot anymore. It shows the first samsung screen (warning me that i'm not using a official firmware), then the screen warning that the bootloader is unlocked, and then the phone just goes black screen indefinitely. I can force restart with power + volume down, but can't access recovery or download mode by any means, as it just goes black when i try. PC won't recognize the phone as well, giving me no way to install scatter firmware of any sorts.
Is there anyway to save my phone?
Hello! If you still have issues, I have the same phone. The problem was the custom rom I was trying to install (LineageOS). Crdroid booted up just fine.