Touch problem - Xiaomi Mi A1 Questions & Answers

I was using PIXEL EXPERIENCE 9.0. Then to update Rom i tried to install Twrp. I mistakenly booted nougat twrp from fastboot
Then after i noticed that i was trying nougat twrp instead of Oreo..i downloaded oreo twrp and booted...but when i tired to touch is was faulty..mean for suppose i triede to open mount menu it touch on Reboot in twrp.
Then i decided to flash stock rom.
I downloaded latest one and flashed but result was same... Touch problem...
PLEASE TELL.ME FIX

Related

Can't boot to recovery.

Phone is Lenovo A6000, not plus. I installed multiple TWRPs, 3.1.0 and 2.9 something.
I even installed CWM, still couldn't boot to the recovery.
Now, I know how to flash with fastboot, and I know how to boot. Booting doesn't work at all, it says "booting" and never finishes.
Flashing says "okay" and I reboot, do a reboot to recovery, and I get put into bootloader/fastboot.
Any help? I just bought the phone today, no one messed with it.
Edit: Nevermind. CWM installed. How do I install TWRP, so it works? Also, forgot to mention that the phone has the latest stock rom, 4.4.4.
Edit#2: While trying to install "TWRP-3.1.0-Lenovo-A6000.img",
I got an error.
"Can't open /tmp/update.zip (bad)"
"Installation aborted."
Edit#3: Same error with multiple TWRP images.
First of all the twrp 3.1.0 is meant for nougat roms. Since you are flashing that recovery on KitKat rom which it won't support. So first try updating phone to stock lollipop. Then flash twrp 2.8. then take a complete backup(most important) and save it on SD card. After that flash any rom you want. If you are flashing marshmallow or nougat rom then after flashing rom flash 3.1.0 twrp.
I have long ago (10 minutes after last edit) fixed the problem already by flashing stock firmware through some weird software, and then started updating to latest lollipop firmware, and then installed TWRP 3.1 and then installed RR android version 7.1.2. But, thank you for trying to help. I hereby ask a moderator to close the thread because the problem was resolved. Thank you.

Bootloops after flashing Magisk OOS 5.0.2

I've been getting bootloops after installing Magisk on my OnePlus 5 unlocked bootloader , rooted before at 4.5.15.
I directly updated it to 5.0.2 which resulted in many errors in the end had to flash it completely and then clean install the ROM .
The ROM works perfectly with almost no trouble.
I then flashed almost all Magisk versions I could get hold of (14.5,15.2,15.3,15.4(beta))
But none of them could get past the boot animation.
I've also flashed the no Verity mod file both before and after the flashing of Magisk nothing worked.
But everytime after all this I flash the Magisk uninstaller and I get easily get back to using the device but without root.
Anyone help me rooting this ?
The ROM has been downloaded from official OnePlus website and the twrp I'm using is the codeworkx version.
First do this then tell me how it went.
1. Boot to fastboot and flash twrp-3.2.1-0-universal-codeworkx-cheeseburger.img via command window, make sure you have adb installed on pc.
2. Then boot DIRECTLY to twrp.
3. Dirty flash OOS 5.0.2 over your current rom in twrp and then wipe dalvik and cache.
4. Then boot into fastboot DIRECTLY again and flash twrp-3.2.1-0-universal-codeworkx-cheeseburger.img again.
5. Boot into twrp directly and flash Magisk 15.2.zip
6. Finally boot into the system.
7. Optional: then you can go ahead and update Magisk via it's own flash tool.
I'm already on 5.0.2 so do I dirty flash it again?

TWRP Not working

Hi, I have a essential phone running Oreo 8.1, just recently I have rooted the phone with magisk v16 an twrp 3.2.1, I successfully flashed it with twrp but after the flash whenever I want to get into twrp it just freezes up on the mount data screen and I have to force reboot it, does anyone know a solution to this problem
Make sure you're following the exact steps from this post. Every step is crucial (except #3, because you have to disable your screen lock before booting twrp.
You shouldn't have to manually mount anything in TWRP either. The magisk installer might give you an error about mounting system but it doesn't seem to make any difference.
[QRCODE][/QRCODE]
yellk20 said:
Hi, I have a essential phone running Oreo 8.1, just recently I have rooted the phone with magisk v16 an twrp 3.2.1, I successfully flashed it with twrp but after the flash whenever I want to get into twrp it just freezes up on the mount data screen and I have to force reboot it, does anyone know a solution to this problem
Click to expand...
Click to collapse
You cannot have TWRP installed with 8.x.
TWRP is not compatible.
You must flash the original boot image, then install magisk.
TWRP cannot remain.
You will boot loop.
Please read the instructions on rooting carefully.
Ok thank you
Why can't TWRP replace recovery instead of boot?
RawSlugs said:
Why can't TWRP replace recovery instead of boot?
Click to expand...
Click to collapse
No one has created a bit image with TWRP as the recovery.
Sent from my PH-1 using XDA Labs
RawSlugs said:
Why can't TWRP replace recovery instead of boot?
Click to expand...
Click to collapse
Because the partition layout of the Essential does not have a recovery partition.
Recovery is contained in the boot image.
So to have TWRP resident/permanent, the boot image must be patched.
It has been done for 7.x, but sense 8.x is still beta, there is no official TWRP for Oreo.
Once Oreo is final, I expect we will get a TWRP that works.
The current limitation, means you can't flash without a computer handy.

TWRP Loop

Hi,
after flashing serveral custom roms (with open bootloader) via twrp (latest version), which btw worked perfectly till now, i suddenly produced a twrp loop. I tried to flash another custom rom, reinstall twrp, but no rom boots. Only twrp appears.
Because of this i can´t also open the port to flash a stock rom via QFIL. Is it possible in my situation to remove twrp and install stock recovery? I can´t find a corresponding img file.
Thanks!

no touch after flashing custom roms!

i'm running stock january frimware with no root or any thing and wanna flash aosip 9.0,when i flash twrp 3230 i have working touch . and when i flash jan_twrp_root.img based on daze one toturial i lose my touch in twrp so i decided to start instructions for installing custom roms with twrp 3.2.3.0 because i have touch on it. after flashing rom i flashed twrp-installer.zip and after rebooting to recovery i did not have touch to flash gapps and when i change to the another slot after flashing twrp installer i have twrp working so did it and change the active slot with fastboot after that in twrp < reboot< change slot to the other i mean were the rom installed and doing gapps and magisk.zip rebooting to the system but i do not have touch in system and can not do nothing in lets go screen. testing the process with RR and Aosip rom and having the same results.
any suggestion?tnx in advanced
Not to hijack but I have a bonestock phone that is neither rooted and the bootloader is locked. Had a bad screen, replaced with two different screens. Both turn on no issue but zero touch. Super frustrated, flashed latest OTA and nothing.
had this issue, i couldnt have touch on one rom but the others worked, i used the adb recommended in the stock rom files thread (think this was the problem for me) but i ended up reverting back to stock with magisk, the roms are stable but have some issues and i didnt find it a plus of having a rom with essential, i did installed helix engine for the app optimization

Categories

Resources