Related
Hello everyone!
I have been experiencing a strange issue with almost all the Marshmallow ROMs currently in the development section. The Phone boots, Setup Wizard runs, and in between, the screen freezes/hangs and after 5-10 seconds the phone reboots. Again the setup wizard runs and even if i'm able to complete the wizard, the phone frequently hangs and then reboots.
I had been running Paranoid Android 5.1 ROM before flashing the Marshmallow ROM and this strange issue suddenly started. I have tried to flash stock rom and then flash twrp, then flash the ROM, even wiped everything several times. Still the same issue persists. This is really getting annoying as i have tried 3-4 different ROMs and 2 GApps and still the screen freezes and then phone reboots.
And this happens only on Marshmallow ROMs as i again have currently installed Chroma 5.1.1 ROM and its running smoothly. I am beginning to think of it to be a hardware issue. Can anyone help me solve this?
imrock0 said:
Hello everyone!
I have been experiencing a strange issue with almost all the Marshmallow ROMs currently in the development section. The Phone boots, Setup Wizard runs, and in between, the screen freezes/hangs and after 5-10 seconds the phone reboots. Again the setup wizard runs and even if i'm able to complete the wizard, the phone frequently hangs and then reboots.
I had been running Paranoid Android 5.1 ROM before flashing the Marshmallow ROM and this strange issue suddenly started. I have tried to flash stock rom and then flash twrp, then flash the ROM, even wiped everything several times. Still the same issue persists. This is really getting annoying as i have tried 3-4 different ROMs and 2 GApps and still the screen freezes and then phone reboots.
And this happens only on Marshmallow ROMs as i again have currently installed Chroma 5.1.1 ROM and its running smoothly. I am beginning to think of it to be a hardware issue. Can anyone help me solve this?
Click to expand...
Click to collapse
Flash Frank ROM, Flash Tuxi Gapps from Frank's OP, no one is having any issues now. Also don't forget to do a factory reset if you can even the Internal data.
sidnoit22 said:
Flash Frank ROM, Flash Tuxi Gapps from Frank's OP, no one is having any issues now. Also don't forget to do a factory reset if you can even the Internal data.
Click to expand...
Click to collapse
I have done factory reset several times. Even flashed stock via fastboot multiple times. Done the exact same steps you mentioned. Its not only with Frank ROM actually, i tried another Marshmallow ROM and the same thing happened again.
How is it that Lollipop ROMs are running smooth and Marshmallow ROMs are crashing?
imrock0 said:
I have done factory reset several times. Even flashed stock via fastboot multiple times. Done the exact same steps you mentioned. Its not only with Frank ROM actually, i tried another Marshmallow ROM and the same thing happened again.
How is it that Lollipop ROMs are running smooth and Marshmallow ROMs are crashing?
Click to expand...
Click to collapse
seems like it's Gapps/ ROM problem (with setup wizard)
this my only suggestions:
1. try to flash Frank's M without Gapps > reboot normaly
if this worked, then it's related to Gapps issue...
if it still remains, then
2. Flash ROM, Gapps, wipe, etc.
after that back to home of TWRP > Mount > Mount system > back > Advanced > File manager > go to /system/priv-app
search for folder name related to Setup wizard/ Google setup wizard (NOT GooglePartnerSetup) > delete it > reboot
3. fingercrossed it will bring you to home screen without any problem...
good luck then :fingers-crossed:
yayakuya said:
seems like it's Gapps/ ROM problem (with setup wizard)
this my only suggestions:
1. try to flash Frank's M without Gapps > reboot normaly
if this worked, then it's related to Gapps issue...
if it still remains, then
2. Flash ROM, Gapps, wipe, etc.
after that back to home of TWRP > Mount > Mount system > back > Advanced > File manager > go to /system/priv-app
search for folder name related to Setup wizard/ Google setup wizard (NOT GooglePartnerSetup) > delete it > reboot
3. fingercrossed it will bring you to home screen without any problem...
good luck then :fingers-crossed:
Click to expand...
Click to collapse
Thanks i'll try this out when i get back home. Although i did try flashing just the ROM to see if GApps were causing the issue. Without GApps, the phone booted to the homescreen, but then after 5-10 mins would reboot itself. I don't know may be it has got something to do with temperature? Because i've noticed that the phone becomes very hot when it first boots up on a new ROM(i know its normal for it to get hot). But when i used the phone on a Marshmallow ROM when the phone was NOT hot, it went on pretty well for 20-30 mins and then again rebooted.
yayakuya said:
seems like it's Gapps/ ROM problem (with setup wizard)
this my only suggestions:
1. try to flash Frank's M without Gapps > reboot normaly
if this worked, then it's related to Gapps issue...
if it still remains, then
2. Flash ROM, Gapps, wipe, etc.
after that back to home of TWRP > Mount > Mount system > back > Advanced > File manager > go to /system/priv-app
search for folder name related to Setup wizard/ Google setup wizard (NOT GooglePartnerSetup) > delete it > reboot
3. fingercrossed it will bring you to home screen without any problem...
good luck then :fingers-crossed:
Click to expand...
Click to collapse
Here's another update. I tried the new Chroma Marshmallow ROM and it too had the same issue. The phone hangs/freezes randomly and then reboots. After trying so many ROMs, i think the issue is with hardware itself. None other has reported this issue, nor could i find it anywhere else. I guess i can say that my(and only my) nexus 4 is not compatible with Marshmallow officially and unofficially.
I don't know what kernel Frank's uses but you could always try to flash an alternate kernel. I haven't taken the jump to Marshmallow yet, but it seems TaUrUs and hellsCore support M (I currently use hellsCore with stock L).
bjb2 said:
I don't know what kernel Frank's uses but you could always try to flash an alternate kernel. I haven't taken the jump to Marshmallow yet, but it seems TaUrUs and hellsCore support M (I currently use hellsCore with stock L).
Click to expand...
Click to collapse
I'll try another kernel and ping back.
Probably lacked boot the system before you install GApps.
imrock0 said:
I'll try another kernel and ping back.
Click to expand...
Click to collapse
The FC of Setup Wizard is discussed in the ROM thread of Chroma.
You can try this because it is advised by the Dev of Chroma and supported by many others and I have succeeded with this.
Flash stock L and boot up.
Boot into TWRP (make sure you have the latest) and factory reset.
Flash Chroma 1/11/2015 and Bank's Gapps without boot/reboot in between and no wipe afterwards.
Reboot.
---------- Post added at 07:03 PM ---------- Previous post was at 07:00 PM ----------
webg3brasil said:
Probably lacked boot the system before you install GApps.
Click to expand...
Click to collapse
At least for Chroma, that is a wrong approach. No boot between ROM and Gapps flash.
Make sure you have permissions granted to all of the apps. I had similar issues, and had to do with Location and apps making calls to GPS. Would cause a reboot, and not just a force close. Try amending the Location settings as well. All else fails, capture a logcat.
Everyone thanks for your time!
I found the solution. bjb2's suggestion did the trick. I flashed TaUrUs-Mallow Kernel after Frank Marshmallow ROM and everything seems fine now. Have been running Marshmallow since a day without any issues. Still it's curious why the stock kernel gave such errors.
Thanks everyone again for your suggestions and help
DELETED-- If you face the same problem (No sensors working), flash the following file through TWRP. It is attached to the end of the post.
https://forum.xda-developers.com/showpost.php?p=71360979&postcount=2717
Are you on a custom ROM and have flashed a different kernel?
Please provide more details.
--DELETED--
PATAboy said:
Hello everyone, my sensors have been failing since last saturday.
---Info: ---
*Phone: G4 Plus - xt1641 - 32GB Dual Sim
*OS: Lineage OS 14.1 1st May Nightly Update
*Kernel: (I think it was installed when sensors started failling) ElementalX Kernel 1.05 for Lineage OS
(As of now,12 of may, 8 Hours and a half after this was posted) V. 1.06 for Lineage is installed. Still not working
Never had a problem with any of them
***Problem: Sensors not working (Accelerometer , Gyroscope, Light and Proximity Sensors, Headphones Detection)
Cant get readings from Sensor Data Apps
Cause: Theres no apparent cause. Phone never fell to floor nor nothing like that. It happened after playing a game. No overheating while playing.
**Actions taken:
-Re-Flashed Lineage OS many times, with no succes (Wiped everything but sdcard and usb otg)(With and without ElemntalX)
NO SUCCES
-Flashed Stock Rom, with sensors working momentarily. They worked for 30 secs after one day of the Stock Rom install. Didnt work after that. Reflashed Stock, didnt work. (I believe that ElementalX was installed, version 1.04 for Stock Rom)
MOMENTARY SUCCES
-Flashed Lineage,
NO SUCCES
-Tried using ADB to execute:
*Sensor.qcom
* and sensorsevice
From /system/bin/
NO SUCCES
-Erased hmac.key (the only file) from /data/system/sensor_service
NO SUCCES
I grabbed a logcat, but I'll grab one from boot, so Im not uploading this one.
Click to expand...
Click to collapse
Look for SensorHub-N.zip and flash it in TWRP. This should be flashed after flashing ElementalX Kernel.
--DELETED--
--DELETED--
PATAboy said:
Do you know where to get it? I dont seem to find anything
Click to expand...
Click to collapse
You'll find a TWRP flashable sensorhub firmware zip file here: https://forum.xda-developers.com/showpost.php?p=71360979&postcount=2717
By the way, with flashing the stock ROM, have you flashed/updated your device to Nougat at any point, before flashing Lineage OS?
--DELETED--
PATAboy said:
Yes, when I updated from MM to Nougat, i Flashed Nougat stock rom with fastboot to update it. The I used it for a while, till I found Resurrection Remix. No problems. But I wanted to try CyanogenMod. I ended knowing that Lineage was kinda the new Cyanogen, so I installed it. No problems for about a month and a half.
Also, do i need to reflash lineage and the kernel with it, or just reflash kernel and then sensorhub-n.zip??
Click to expand...
Click to collapse
Hmm, then that's odd sensors have failed when you've been running with no issue.
Don't think you have to reflash L-OS or the kernel, flash the sensorhub in TWRP (you may wish to wipe cache/Dalvik) and reboot - the sensorhub firmware should flash into /etc/firmware. You could re-flash the kernel if you wanted to.
--DELETED--
PATAboy said:
Hello everyone, my sensors have been failing since last saturday.
---Info: ---
*Phone: G4 Plus - xt1641 - 32GB Dual Sim
*OS: Lineage OS 14.1 1st May Nightly Update
*Kernel: (I think it was installed when sensors started failling) ElementalX Kernel 1.05 for Lineage OS
(As of now,12 of may, 8 Hours and a half after this was posted) V. 1.06 for Lineage is installed. Still not working
Never had a problem with any of them
***Problem: Sensors not working (Accelerometer , Gyroscope, Light and Proximity Sensors, Headphones Detection)
Cant get readings from Sensor Data Apps
Cause: Theres no apparent cause. Phone never fell to floor nor nothing like that. It happened after playing a game. No overheating while playing.
**Actions taken:
-Re-Flashed Lineage OS many times, with no succes (Wiped everything but sdcard and usb otg)(With and without ElemntalX)
NO SUCCES
-Flashed Stock Rom, with sensors working momentarily. They worked for 30 secs after one day of the Stock Rom install. Didnt work after that. Reflashed Stock, didnt work. (I believe that ElementalX was installed, version 1.04 for Stock Rom)
MOMENTARY SUCCES
-Flashed Lineage,
NO SUCCES
-Tried using ADB to execute:
*Sensor.qcom
* and sensorsevice
From /system/bin/
NO SUCCES
-Erased hmac.key (the only file) from /data/system/sensor_service
NO SUCCES
I grabbed a logcat, but I'll grab one from boot, so Im not uploading this one.
Click to expand...
Click to collapse
Well it is for xt1643 but should work for u too. See the instructions n u will have a customer service rom flash at ur home. It should definitely solve ur problem
---------- Post added at 09:58 AM ---------- Previous post was at 09:57 AM ----------
DgnrtnX said:
Well it is for xt1643 but should work for u too. See the instructions n u will have a customer service rom flash at ur home. It should definitely solve ur problem
Click to expand...
Click to collapse
https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1643-updated-signed-t3460695
Hello Guys.
Im in dire need of help actually. Ive recently rooted my galaxy grand 2 running 4.4.2 KK and set it up with twrp v3.1.
yet im having the issue when i install a custom rom.
1.) Cyanogenmod - MM
When i install the rom, it installs and and on 1st reboot it optimizes all the apps yet gets stuck on "starting apps". when i force restarted it, it boots till the welcome screen to select the language but then the touch screen stops responding but its not stuck as pressing the power button turns off the screen and back on and also on long press reboot options appear , which on the other hand responds to touch. so im guessing its not the touch screen issue? but then ive noticed that apps also crash while im on the welcome screen.
2. Resurrection remix - MM
Same issue yet this passes the starting apps screen and goes to the home screen directly but only to be found that the screen isnt responding.
this is very weird because of all the phones ive installed custom rom on, this is the first case im having such trouble.
could it be because knox is installed? i tried getting rid of it from the stock rom but everytime i try that i cant boot back up because it gets stuck at the samsung logo.
can some one help me quick because this is really irritating.
Thanks.
Maybe its realy screen problem... did the touch screen works on twrp
fire_onCA said:
Maybe its realy screen problem... did the touch screen works on twrp
Click to expand...
Click to collapse
Yes It Does. Its not the screen issue because on stock rom everything works properly.
Im guessing somethings interrupting with the OS, causing the apps to crash.
aymanabdulla said:
Hello Guys.
Im in dire need of help actually. Ive recently rooted my galaxy grand 2 running 4.4.2 KK and set it up with twrp v3.1.
yet im having the issue when i install a custom rom.
1.) Cyanogenmod - MM
When i install the rom, it installs and and on 1st reboot it optimizes all the apps yet gets stuck on "starting apps". when i force restarted it, it boots till the welcome screen to select the language but then the touch screen stops responding but its not stuck as pressing the power button turns off the screen and back on and also on long press reboot options appear , which on the other hand responds to touch. so im guessing its not the touch screen issue? but then ive noticed that apps also crash while im on the welcome screen.
2. Resurrection remix - MM
Same issue yet this passes the starting apps screen and goes to the home screen directly but only to be found that the screen isnt responding.
this is very weird because of all the phones ive installed custom rom on, this is the first case im having such trouble.
could it be because knox is installed? i tried getting rid of it from the stock rom but everytime i try that i cant boot back up because it gets stuck at the samsung logo.
can some one help me quick because this is really irritating.
Thanks.
Click to expand...
Click to collapse
Flash twrp 3.0.0 (over your existing twrp 3.1). Just copy the twrp.zip to your root directory of internal storage and flash using twrp 3.1. Maybe that will help because it helped me.
mfaisal98 said:
Flash twrp 3.0.0 (over your existing twrp 3.1). Just copy the twrp.zip to your root directory of internal storage and flash using twrp 3.1. Maybe that will help because it helped me.
Click to expand...
Click to collapse
but I've already tried that! I started off with 3.0 and when that didn't work I moved to 3.1!
I also noticed I get a small message on top when. I start the phone with the Samsung logo saying that something isn't seandroid when I install a custom room but it isn't like an error or something.
Could the issue be with the kernal?
Or should I try cwm recovery now?
aymanabdulla said:
but I've already tried that! I started off with 3.0 and when that didn't work I moved to 3.1!
I also noticed I get a small message on top when. I start the phone with the Samsung logo saying that something isn't seandroid when I install a custom room but it isn't like an error or something.
Could the issue be with the kernal?
Or should I try cwm recovery now?
Click to expand...
Click to collapse
If you get some error message on boot while there is the Samsung logo then there is something wrong! Now you should:
1. Flash the stock rom (to correct that error message on boot)
2. Flash recovery
3. Root (SuperSU 2.82)
4. Continue with the installation (thru twrp 3.0.0) of 6.0.1 but before that:
(a) Factory reset
(b) Wipe data
(c) Wipe cache
(d) Wipe dalvik cache)
(e) DO NOT WIPE THE SYSTEM!
Goog luck
I suggest flashing the stock 4.4.2 ROM via Odin and then start everything from scratch. Currently facing the same problem after flashing the Ressurection Remix M 5.7.4.
mfaisal98 said:
If you get some error message on boot while there is the Samsung logo then there is something wrong! Now you should:
1. Flash the stock rom (to correct that error message on boot)
2. Flash recovery
3. Root (SuperSU 2.82)
4. Continue with the installation (thru twrp 3.0.0) of 6.0.1 but before that:
(a) Factory reset
(b) Wipe data
(c) Wipe cache
(d) Wipe dalvik cache)
(e) DO NOT WIPE THE SYSTEM!
Goog luck
Click to expand...
Click to collapse
Its not actually an error message but a small notice on the top left corner.
When I restore my official rom back the message is normally gone.
But I will try again with ur advice again because I always wipe system before flashing the rom so it could be causing the issue.
Thanks I'll let u know what happens
kaiserfakinaway said:
I suggest flashing the stock 4.4.2 ROM via Odin and then start everything from scratch. Currently facing the same problem after flashing the Ressurection Remix M 5.7.4.
Click to expand...
Click to collapse
I did do that. I have the official stock rom running now since RR and cyanogenmod isn't responding.
aymanabdulla said:
I did do that. I have the official stock ROM running now since RR and CyanogenMod isn't responding.
Click to expand...
Click to collapse
Have you tried flashing RR or CM13 after flashing the stock ROM?
and could you give me the full name of the stock ROM?
aymanabdulla said:
Hello Guys.
Im in dire need of help actually. Ive recently rooted my galaxy grand 2 running 4.4.2 KK and set it up with twrp v3.1.
yet im having the issue when i install a custom rom.
1.) Cyanogenmod - MM
When i install the rom, it installs and and on 1st reboot it optimizes all the apps yet gets stuck on "starting apps". when i force restarted it, it boots till the welcome screen to select the language but then the touch screen stops responding but its not stuck as pressing the power button turns off the screen and back on and also on long press reboot options appear , which on the other hand responds to touch. so im guessing its not the touch screen issue? but then ive noticed that apps also crash while im on the welcome screen.
2. Resurrection remix - MM
Same issue yet this passes the starting apps screen and goes to the home screen directly but only to be found that the screen isnt responding.
this is very weird because of all the phones ive installed custom rom on, this is the first case im having such trouble.
could it be because knox is installed? i tried getting rid of it from the stock rom but everytime i try that i cant boot back up because it gets stuck at the samsung logo.
can some one help me quick because this is really irritating.
Thanks.
Click to expand...
Click to collapse
Did you flashed the vendor.zip provided after flashing the rom?If not,then it is the cause of that problem
kaiserfakinaway said:
Have you tried flashing RR or CM13 after flashing the stock ROM?
and could you give me the full name of the stock ROM?
Click to expand...
Click to collapse
Yes, thats what i did.
G7102DDUBNK1_G7102ODDBNK1_G7102DDUBNK1_HOME.tar.md5 this was the file name. it works fine i guess, had some issues with the sim as the phone keeps on asking to reboot but no other issues.
Subhashis said:
Did you flashed the vendor.zip provided after flashing the rom?If not,then it is the cause of that problem
Click to expand...
Click to collapse
Yes i did. as well as the front cam + patch fix. i flashed both yet still the same issue.
mfaisal98 said:
If you get some error message on boot while there is the Samsung logo then there is something wrong! Now you should:
1. Flash the stock rom (to correct that error message on boot)
2. Flash recovery
3. Root (SuperSU 2.82)
4. Continue with the installation (thru twrp 3.0.0) of 6.0.1 but before that:
(a) Factory reset
(b) Wipe data
(c) Wipe cache
(d) Wipe dalvik cache)
(e) DO NOT WIPE THE SYSTEM!
Goog luck
Click to expand...
Click to collapse
Ok i tried this with the steps u have told me. still no luck
i went to twrp opened wipe, wiped dalvik cache, cache, internal storage and data. but not the system.
same issue. also the small message which comes in the top left corner is
"Kernal is not seandroid enforcing" red colour font
"set warranty bit : kernal" yellow colour font
why is this shown?
should i try cwm?
So I have been trying various ROMs and found out that this problem only exists on MM ROMs. RR-M and CM13 both starts but system stops responding completely. But RR-N and CM14.1/12.1/12 are working flawlessly.
---------- Post added at 08:05 AM ---------- Previous post was at 08:03 AM ----------
aymanabdulla said:
Ok i tried this with the steps u have told me. still no luck
i went to twrp opened wipe, wiped dalvik cache, cache, internal storage and data. but not the system.
same issue. also the small message which comes in the top left corner is
"Kernal is not seandroid enforcing" red colour font
"set warranty bit : kernal" yellow colour font
why is this shown?
should i try cwm?
Click to expand...
Click to collapse
That small message is not a problem. It is showing because the kernel is not selinux enforcing.
kaiserfakinaway said:
So I have been trying various ROMs and found out that this problem only exists on MM ROMs. RR-M and CM13 both starts but system stops responding completely. But RR-N and CM14.1/12.1/12 are working flawlessly.
---------- Post added at 08:05 AM ---------- Previous post was at 08:03 AM ----------
That small message is not a problem. It is showing because the kernel is not selinux enforcing.
Click to expand...
Click to collapse
Why Doesnt any one else have this problem?
oh is it? what about lineage os 13.1 running MM?
Fine i have put cm12.1 for download, will flash it and let u know what happened.
Fingers Crossed
kaiserfakinaway said:
So I have been trying various ROMs and found out that this problem only exists on MM ROMs. RR-M and CM13 both starts but system stops responding completely. But RR-N and CM14.1/12.1/12 are working flawlessly.
---------- Post added at 08:05 AM ---------- Previous post was at 08:03 AM ----------
That small message is not a problem. It is showing because the kernel is not selinux enforcing.
Click to expand...
Click to collapse
Thank You So MUCH.....
The issue was with the MM roms, because cm12.1 seems to be working perfectly, although not the camera. could someone tell me what about that now?
what now should we close this thread or figure out why MM isnt working on this device? Kernal Issue?
Could someone also check if the Lineage os with MM works or not?
Thanks again.
aymanabdulla said:
Thank You So MUCH.....
The issue was with the MM roms, because cm12.1 seems to be working perfectly, although not the camera. could someone tell me what about that now?
what now should we close this thread or figure out why MM isnt working on this device? Kernal Issue?
Could someone also check if the Lineage os with MM works or not?
Thanks again.
Click to expand...
Click to collapse
Have you tried any TW MM ports like J7 Hybrid MM Heavily Debloated Port or [ROM][6.0.1][TW][Electron Rom][Version 1] or [ROM][6.0.1][TW] JSERROM Version 3.1 [BETA][ms013g]?
kaiserfakinaway said:
Have you tried any TW MM ports like J7 Hybrid MM Heavily Debloated Port or [ROM][6.0.1][TW][Electron Rom][Version 1] or [ROM][6.0.1][TW] JSERROM Version 3.1 [BETA][ms013g]?
Click to expand...
Click to collapse
Nope, all of them have camera issues too.
but im sure there will be a fix for this, since its running LOLLIPOP.
I'll let u know.
aymanabdulla said:
Thank You So MUCH.....
The issue was with the MM roms, because cm12.1 seems to be working perfectly, although not the camera. could someone tell me what about that now?
what now should we close this thread or figure out why MM isnt working on this device? Kernal Issue?
Could someone also check if the Lineage os with MM works or not?
Thanks again.
Click to expand...
Click to collapse
Might not be a kernel issue because I have also tried with this custom kernel [KERNEL][5.x/TW/6.x]Infected Kernel R4[15-05-2016] and still the same.
after booting deadman twrp 3.1.1 on los 16.1, touch of my phone is not working, even in twrp..
afte that I flash stock oreo via MI flash tool.. but no result, same problem, touch wrong.. like mad, ,
any fix there >???
please some one help me... plz
I think you should select clean flash again while flashing rom through mi flash tool!
Facing same problem, clean flash did not help. Please reply.
I had the same problem with a new Mi A1. After installing twrp and flashing LineageOS the touch screen didn't work correctly. When touching it, sometimes it would respond in the wrong spot. Most touches were unresponsive. Booting back to twrp had the same problem. When I flashed stock Oreo with MiFlash it still was broken.
I managed to fix it doing the following (files available on androidfilehost from a user named edwaine):
1. Download MiFlash2017-7-20-0.zip which seems to be the latest version
2. Download the latest official Nougat ROM (not Oreo)
tissot_images_7.12.19_20171219.0000.00_7.1_d39fa89aaf.tgz
3. Put the phone in fastboot mode by holding power + volume down
4. Did a "clean all and lock" with MiFlash 2017.7.20.0
After this my phone booted to a black screen for a few minutes and then showed the initial setup with a working touch screen. I believe the initial problem was caused by not properly upgrading to Oreo. I didn't even check the stock firmware when it arrived, because I didn't think there were any issues just flashing newer firmware. I will now try to upgrade properly.
I hope this helps someone.
Bro, how about upgrade to Oreo? Is the touch still fixed?
Fewome said:
I had the same problem with a new Mi A1. After installing twrp and flashing LineageOS the touch screen didn't work correctly. When touching it, sometimes it would respond in the wrong spot. Most touches were unresponsive. Booting back to twrp had the same problem. When I flashed stock Oreo with MiFlash it still was broken.
I managed to fix it doing the following (files available on androidfilehost from a user named edwaine):
1. Download MiFlash2017-7-20-0.zip which seems to be the latest version
2. Download the latest official Nougat ROM (not Oreo)
tissot_images_7.12.19_20171219.0000.00_7.1_d39fa89aaf.tgz
3. Put the phone in fastboot mode by holding power + volume down
4. Did a "clean all and lock" with MiFlash 2017.7.20.0
After this my phone booted to a black screen for a few minutes and then showed the initial setup with a working touch screen. I believe the initial problem was caused by not properly upgrading to Oreo. I didn't even check the stock firmware when it arrived, because I didn't think there were any issues just flashing newer firmware. I will now try to upgrade properly.
I hope this helps someone.
Click to expand...
Click to collapse
Faced the same problem. I played with the firmware and stopped working the touchscreen. This tip rolled back to 7.1,2 helped. The phone began to work.
I updated it after the initial configuration and connection to the network, the phone itself downloaded the update and installed it. Updated to 8.1.0.
Thank you so much for sharing!
Hi, touch, fingerprint and capacitive buttons stopped working after I installed Pixel experience ROM, I rolled back to 7.1.2 using Mi flash tool according to your suggestion (same versions of Miflash and ROM as suggested by you). Still the problem isnt solved, please help.
meet4300 said:
Hi, touch, fingerprint and capacitive buttons stopped working after I installed Pixel experience ROM, I rolled back to 7.1.2 using Mi flash tool according to your suggestion (same versions of Miflash and ROM as suggested by you). Still the problem isnt solved, please help.
Click to expand...
Click to collapse
same problem how did you solved it ?
As my phone was in warranty, I was able to get it solved by replacing motherboard. Booting older versions of TWRP can get the touch working, this is suggestion is still to be tested. Try your luck if you can sort it out. In Pixel experience rom, there is an option of double tap to wake. I think thats the reason this fuss is all about. I think due to a different manufacturer, maybe our screens won't support it.
For those who still did not get touch working after installing stock nougat just unlock bootloader and boot twrp 3.2.1 (strictly never flash it...just hot boot it..... it's the reason ur touch got malfunctioning...)and reboot voila!...ur touch is restored
I still can't seem to get it to work.
Tried nougat and two oreo version but the issue remains.
The touchscreen does work after I boot the device but does not work after it wennt to sleep/lock screen.
The screen does also not work inside twrp
i also tried to install a custom rom via adb shell and twrp but the zip fails (9.0 and lineage)
I hope someone could help me
diocore said:
I still can't seem to get it to work.
Tried nougat and two oreo version but the issue remains.
The touchscreen does work after I boot the device but does not work after it wennt to sleep/lock screen.
The screen does also not work inside twrp
i also tried to install a custom rom via adb shell and twrp but the zip fails (9.0 and lineage)
I hope someone could help me
Click to expand...
Click to collapse
Disable DT2W and voila, fixed.
I don't know what the problem is, but I know how to "fix" it.
diocore said:
I still can't seem to get it to work.
Tried nougat and two oreo version but the issue remains.
The touchscreen does work after I boot the device but does not work after it wennt to sleep/lock screen.
The screen does also not work inside twrp
i also tried to install a custom rom via adb shell and twrp but the zip fails (9.0 and lineage)
I hope someone could help me
Click to expand...
Click to collapse
Same problem. Did you make any progress?
leodoct said:
Same problem. Did you make any progress?
Click to expand...
Click to collapse
I'm in trouble too. Tried Nougat, but didn't work. Any other ideas?
Edit: now I can't reflash anything from Nougat. It just says "Device is locked"
mikla90 said:
I'm in trouble too. Tried Nougat, but didn't work. Any other ideas?
Edit: now I can't reflash anything from Nougat. It just says "Device is locked"
Click to expand...
Click to collapse
Well i found a solution for my case. The problem for me was the version of platform tools i used to lock-unlock boot-loader, boot the system and running any commands install HAL3 etc..
Every installation i did (firmwares, from nougat to oreo and last to pie) was executed with the platform tools latest windows version that boot.img had (14,888KB) size.
The version that my touch screen began to work again is the platform tools r.28.0.1.windows that had the boot.img (34,928KB) size.
When i booted the phone in fastboot mode, i opened platform tools r.28.0.1.windows and run the command "fastboot boot boot.img" the phone rebooted and the touch was working again I think that the boot.img file of this version is the correct to boot the phone normally.
Hope this helps....
fewome said:
i had the same problem with a new mi a1. After installing twrp and flashing lineageos the touch screen didn't work correctly. When touching it, sometimes it would respond in the wrong spot. Most touches were unresponsive. Booting back to twrp had the same problem. When i flashed stock oreo with miflash it still was broken.
I managed to fix it doing the following (files available on androidfilehost from a user named edwaine):
1. Download miflash2017-7-20-0.zip which seems to be the latest version
2. Download the latest official nougat rom (not oreo)
tissot_images_7.12.19_20171219.0000.00_7.1_d39fa89aaf.tgz
3. Put the phone in fastboot mode by holding power + volume down
4. Did a "clean all and lock" with miflash 2017.7.20.0
after this my phone booted to a black screen for a few minutes and then showed the initial setup with a working touch screen. I believe the initial problem was caused by not properly upgrading to oreo. I didn't even check the stock firmware when it arrived, because i didn't think there were any issues just flashing newer firmware. I will now try to upgrade properly.
I hope this helps someone.
Click to expand...
Click to collapse
thank you sooooo much dude u saved my ********ing assssss!
ash roxx said:
For those who still did not get touch working after installing stock nougat just unlock bootloader and boot twrp 3.2.1 (strictly never flash it...just hot boot it..... it's the reason ur touch got malfunctioning...)and reboot voila!...ur touch is restored
Click to expand...
Click to collapse
Thank You .. You are a lifesaver
:good:
Mi A1 touch responds somewhere on screen
Fewome said:
I had the same problem with a new Mi A1. After installing twrp and flashing LineageOS the touch screen didn't work correctly. When touching it, sometimes it would respond in the wrong spot. Most touches were unresponsive. Booting back to twrp had the same problem. When I flashed stock Oreo with MiFlash it still was broken.
I managed to fix it doing the following (files available on androidfilehost from a user named edwaine):
1. Download MiFlash2017-7-20-0.zip which seems to be the latest version
2. Download the latest official Nougat ROM (not Oreo)
tissot_images_7.12.19_20171219.0000.00_7.1_d39fa89aaf.tgz
3. Put the phone in fastboot mode by holding power + volume down
4. Did a "clean all and lock" with MiFlash 2017.7.20.0
After this my phone booted to a black screen for a few minutes and then showed the initial setup with a working touch screen. I believe the initial problem was caused by not properly upgrading to Oreo. I didn't even check the stock firmware when it arrived, because I didn't think there were any issues just flashing newer firmware. I will now try to upgrade properly.
I hope this helps someone.
Click to expand...
Click to collapse
packpunk said:
Bro, how about upgrade to Oreo? Is the touch still fixed?
Click to expand...
Click to collapse
Please let me know if someone have solution. PLZ PLZ PLZ
I flashed latest rom pie/ oreo/naughut...but no luck.
I also hotboot recovery start but still touch lagging.
Plesae let me know if there is any solution.
Dear Xda Members I have Problem with my MI A1
I downgrade it to 7.1
Aflter Flashing clean all and relock its with MI flasher tool, My touch Screen misbehave, I try nought and oreo firmware (above mentions also) but problem cant solve
Please help me
Thanks
[if you install this firmware and make clean and relock so you need to unlock bootloader for OTA update]
Thanks You very much Dear your solution is working well.
I downgrade my cell for some reson from pie, when I clean Install and relock I face touch problem, I try manay official firmware but all wrost,
Then I try your shearing mathod, LOL WoW Its worked, I install this firmware then OTA 8.1 and then OTA 9.0 and then AOSP Ex on my cell now its worked fine!
Fewome said:
I had the same problem with a new Mi A1. After installing twrp and flashing LineageOS the touch screen didn't work correctly. When touching it, sometimes it would respond in the wrong spot. Most touches were unresponsive. Booting back to twrp had the same problem. When I flashed stock Oreo with MiFlash it still was broken.
I managed to fix it doing the following (files available on androidfilehost from a user named edwaine):
1. Download MiFlash2017-7-20-0.zip which seems to be the latest version
2. Download the latest official Nougat ROM (not Oreo)
tissot_images_7.12.19_20171219.0000.00_7.1_d39fa89aaf.tgz
3. Put the phone in fastboot mode by holding power + volume down
4. Did a "clean all and lock" with MiFlash 2017.7.20.0
After this my phone booted to a black screen for a few minutes and then showed the initial setup with a working touch screen. I believe the initial problem was caused by not properly upgrading to Oreo. I didn't even check the stock firmware when it arrived, because I didn't think there were any issues just flashing newer firmware. I will now try to upgrade properly.
I hope this helps someone.
Click to expand...
Click to collapse
Hi everyone,
To flash the last rom (nightly ) of LineageOS ( in Oreo,from the 2 february), i had to put the firmware 5.1.7. After flash this firmware i was able to flash the ROM but it makes my phone extremely slow and with screen issues (i can still use the tactile but the screen doesnt follow).
I restored but the problem stills then i put le last stable ROM from Oneplus on android pie (9.0.3). It is a bit better (still really slow) and after a moment i get now like a white noise (same as on TV but with color moreover) by wink ( was more and more often on Google Maps), I had to reboot cause i couldnt use more my phone.
Thanks you in advance !
Ps : I've got TWRP from siankatabg and i'm not rooted , if you want me to send log tell me how pls.
Up :good:
When you were flashing did you used this instructions?
https://forum.xda-developers.com/oneplus-5/how-to/official-oxygenos-4-5-2-7-1-1-ota-t3627003
Flash codework's TWRP for Pie. After that reboot into recovery, wipe everything down and use clean flash instructions for your OTA. It should be able to fix any issue you were having. If not let me know.
Yes i followed the clean flash way (it didn't resolve my issue) but my issue occured before i flash pie, when i flashed lineageOS 15.1 with the firmware 5.1.7 required (which i flashed too). A restoration didnt change that issue.
I tried with the TWRP from codework but it doesnt recognise my internal stockage.
Thanks of your time.
Raidenne said:
Yes i followed the clean flash way (it didn't resolve my issue) but my issue occured before i flash pie, when i flashed lineageOS 15.1 with the firmware 5.1.7 required (which i flashed too). A restoration didnt change that issue.
I tried with the TWRP from codework but it doesnt recognise my internal stockage.
Thanks of your time.
Click to expand...
Click to collapse
Hi, try wiping everything down with the new TWRP, after that reboot into recovery once more. Install last normal working OOS to see if that helps you. If not maybe it is hardware issue? Let me know once you wiped and installed the last working OOS on it.
I have installed multiple roms and firmware updates on my device with codework's TWRP and never had big issue like this. In my opinion best option for you to trace your steps back to the last working version of your os and try learning what might have gone wrong.
Ebeninyo said:
Hi, try wiping everything down with the new TWRP, after that reboot into recovery once more. Install last normal working OOS to see if that helps you. If not maybe it is hardware issue? Let me know once you wiped and installed the last working OOS on it.
I have installed multiple roms and firmware updates on my device with codework's TWRP and never had big issue like this. In my opinion best option for you to trace your steps back to the last working version of your os and try learning what might have gone wrong.
Click to expand...
Click to collapse
My issues seem gone since few weeks with the last OTA (it very rarely happens now). I don't know what caused that even if i use my backup.
Thanks for your support !