Hello everybody,
I installed hydrogen today and since that moment I cant use my phone anymore. I get all the time ghost touches and cant use anything. Even restarting is difficult. I tried to Install Oxygen 3.0 still the same ghost touches.
Atm im downloading the stock rom and will try it again.
PS: in TWRP no ghost touches only when I boot any android version the ghost touches start.
pls help the OP2 is only 2 days old...
Suffering from the same, but after a screen replacement. In recivory no ghost touches
Did you try a "very" clean install in TWRP ?
Like Wipe > Advanced > All except Internal Storage
Then try to reinstall the Rom ( or OOS 2.2.1 / CM 13 or another ROM you want ^^ )
And be sure your TWRP's version is compatible with H2Os / OOs 3
I have now the stock rom on my phone and everything works well again.
I dont know what the problem was I deleted already EVERYTHING from my op2 but it didnt help
I must stay with the stock rom :/
hxh201 said:
I have now the stock rom on my phone and everything works well again.
I dont know what the problem was I deleted already EVERYTHING from my op2 but it didnt help
I must stay with the stock rom :/
Click to expand...
Click to collapse
What stock ROM have you installed? Can you share a link? Thanks
nosidefcp said:
Suffering from the same, but after a screen replacement. In recivory no ghost touches
Click to expand...
Click to collapse
Hi,
I have the same issue,
I've replaced my broken screen a week before.
Initially it worked fine but I started to have this problem now.
If you've solved the problem, please let me know!!
Related
So i just got a new moto g4 plus XT1642 (UK amazon version) and so of course the first thing i had to do was install a custom rom, so i followed a guide here to unlock it and install TWRP which went fine until i flashed a new firmware, I dont know if i somehow installed the wrong one but now it wont go past the "checking connection" screen on setup without crashing (sometimes it doesnt even get past the welcome language screen) I have tried flashing the stock firmware but it just does the same thing no matter which one i try (XT1642_ATHENE_MPJ24.139-48_cid50_subsidy-DEFAULT_CFC.xml.zip is the right one i think?)
If anyone could help me get back to marshmellow it started with then i promise i wont mess around with it again :3
Thanks for any help you can give.
Edit: Okay so I finally just went to do the thing i started out to do which was to install the Resurrection Remix rom (http://forum.xda-developers.com/moto-g4-plus/development/rom-resurrection-remix-n-5-8-0-t3507275) so I just thought that maybe if i got it installed it might fix what problems i was having and yeah sure enough i followed what i was supposed to flash first which was (Moto_G4_Plus_XT1643_ATHENE_MPJ24.139-63_Stock_Img) btw and then flashed Resurrection Remix and it just started working again, everything seems fine but I'm worried I might have broken something with all my puttering around with its inside ya know?
But the main thing is phone calls work, texts work, it rooted itself magically, can install unsigned apks and such, wifi works and so does the fingerprint sensor which i heard people were having issues with. So should i just not look for problems and enjoy it maybe? I'm glad i got it sorted im some fashion at least
So I HAVE now noticed that some apps seem to hang/crash sometimes, epecially games, not sure if it has to do with my puttering around though Is there anything I can do to check that everything is working ok? any programs that scan for errors or something?
Happy its working don't get me wrong but no issues would be best ^^
I've got your same model and I use this to get back to stock: XT1621-XT1622-XT1642_ATHENE_MPJ24.139-23.4_cid50_subsidy-DEFAULT_CFC.xml
If you're running rr and everything works you don't need to do anything just stick with it.
gabriwinter said:
I've got your same model and I use this to get back to stock: XT1621-XT1622-XT1642_ATHENE_MPJ24.139-23.4_cid50_subsidy-DEFAULT_CFC.xml
If you're running rr and everything works you don't need to do anything just stick with it.
Click to expand...
Click to collapse
Hey, thanks for the input, I did use that when i was having issues but it still caused that crashing at the connection screen issue sso i dont know why it would work for you and not me, perhaps i needed to get it to a working state before i could downgrade again? I dont really want to try it out now and see, the crashing issue seems to be infrequent so its possible its a different issue (software conflicts or ram overusage maybe?). I'll keep using it and see what issues develop
Plz help me!!!!
Im installing custom rom in sm core prime 360H via twrp but its shows error number7
How to fix it..???
Any one help me plz i need it
Probably your internal storage if full or something. Which ROM were you installing anyway?
rms112 said:
Probably your internal storage if full or something. Which ROM were you installing anyway?
Click to expand...
Click to collapse
I tried every custom rom but same issue
Error code 7
My phone storage is almost 70%free
Plz help me to solv this
Are you sure you're using ROM built ONLY for G360H? None of us faced that error. Also remember Roms made for other device won't work and you may hard brick your device.
See here for more.
https://forum.xda-developers.com/showthread.php?t=2522762
rms112 said:
Are you sure you're using ROM built ONLY for G360H? None of us faced that error. Also remember Roms made for other device won't work and you may hard brick your device.
See here for more.
https://forum.xda-developers.com/showthread.php?t=2522762
Click to expand...
Click to collapse
Yes in 100% sure its 360H stock rom
I also try ins and inu both stock rom but issue is same
Can u tell me which stock are you use
Bdw are you indian....? Because my English is lil bit week?
rms112 said:
Are you sure you're using ROM built ONLY for G360H? None of us faced that error. Also remember Roms made for other device won't work and you may hard brick your device.
See here for more.
https://forum.xda-developers.com/showthread.php?t=2522762
Click to expand...
Click to collapse
I use this method also which is given in link but same issue ?
Idk man. You should probably try flashing official stock firmware using Odin. Its really easy. Then flash twrp by dreamstar. And start flashing custom ROMs.
I was on stock of Saudi Arabia. But I never used it after we got various CM builds..
I am on RR 5.8.3 by hash now.
Thnx for ideas
my problem solved
Now Installed​ lineage 7.1
Bdw how to close this Thread ?
rms112 said:
Idk man. You should probably try flashing official stock firmware using Odin. Its really easy. Then flash twrp by dreamstar. And start flashing custom ROMs.
I was on stock of Saudi Arabia. But I never used it after we got various CM builds..
I am on RR 5.8.3 by hash now.
Click to expand...
Click to collapse
RR 5.8.3 working fine
I trywd this but home button and resent apps cnt shows
Any idea about it...
rms112 said:
Idk man. You should probably try flashing official stock firmware using Odin. Its really easy. Then flash twrp by dreamstar. And start flashing custom ROMs.
I was on stock of Saudi Arabia. But I never used it after we got various CM builds..
I am on RR 5.8.3 by hash now.
Click to expand...
Click to collapse
RR 5.8.3 working fine ??
I trywd this but home button and resent apps cnt shows
Any idea about it...
Works fine with me. RR beta 1 based on 7.1.2.
You should ask on that thread of ROM. Maybe hash can help you!
Good luck.
Help i'm not sure but i think i might have bricked my sm-g360h.
HELP I'M NOT SURE BUT I THINK I MIGHT HAVE BRICKED MY SM-G360H. When i had some issues with my phone, I used twrp to flash cyanogenmod 12 custom rom on my phone some two weeks ago and it flashed properly. After a number of issues, i decided i wanted to go back to the stock rom. so i downloaded the firmware from sammobile, installed odin and flashed it with odin. when the flashing was done successfully, my phone rebooted instead of giving me the screen of a newly launched phone it went to the home screen, and had a pattern lock screen and tried my pattern lock from when i was on cyanogenmod 12 and it unlocked it. and gave me the screen of a newly lauched phone but before i could continue with startup, it rebooted immediately and each time it get to the lock screen, it goes to the screen with the samsung logo after some few seconds and then come back to the lock screen please help what do i do?
PS: one of the issues i had that made me want to return to the stock rom was the fact that i couldn't change my screen lock to none or swipe after i decided to use pattern on the cyanogenmod
yemialabipurpose said:
HELP I'M NOT SURE BUT I THINK I MIGHT HAVE BRICKED MY SM-G360H. When i had some issues with my phone, I used twrp to flash cyanogenmod 12 custom rom on my phone some two weeks ago and it flashed properly. After a number of issues, i decided i wanted to go back to the stock rom. so i downloaded the firmware from sammobile, installed odin and flashed it with odin. when the flashing was done successfully, my phone rebooted instead of giving me the screen of a newly launched phone it went to the home screen, and had a pattern lock screen and tried my pattern lock from when i was on cyanogenmod 12 and it unlocked it. and gave me the screen of a newly lauched phone but before i could continue with startup, it rebooted immediately and each time it get to the lock screen, it goes to the screen with the samsung logo after some few seconds and then come back to the lock screen please help what do i do?
PS: one of the issues i had that made me want to return to the stock rom was the fact that i couldn't change my screen lock to none or swipe after i decided to use pattern on the cyanogenmod
Click to expand...
Click to collapse
Sounds like problem of dirty flash not hard brick.
Here's what you should do.
1) go to twrp recovery using power + vol up
2) wipe everything except storage
3) Flash cm 13 beta 5 or 6 ( the latest beta) or lineage OS or RR
4) if the problem still exists, then used Odin to flash stock ROM and repeat steps 1 to 3
Also don't use cm 12. Its EOF and you won't get any bug fixes and updates.
hi everyone.
i am having this wierd issue for a month or so, when i try to update RR rom.
after i flash the rom, i get the screen attached. screen seems for like 2 seconds, and goes this half black / half blue screen. screen is still responsive, i can receive calls and if i double tap anywhere, screen locks. there is no problem with screen on twrp or anything ( because sometimes after flashing the rom i dont get this screen, so i don't do anything else, except use it normally.) but today it happened without a reason, the phone was in my pocket when i took it out and saw the screen in this state.
i always flash by following the steps given. i know it is not hardware related. where is the problem? what do i need to do?
p.s. : when charging, blue part goes yellow.
thank you all, waiting for a solution
rukenau said:
hi everyone.
i am having this wierd issue for a month or so, when i try to update RR rom.
after i flash the rom, i get the screen attached. screen seems for like 2 seconds, and goes this half black / half blue screen. screen is still responsive, i can receive calls and if i double tap anywhere, screen locks. there is no problem with screen on twrp or anything ( because sometimes after flashing the rom i dont get this screen, so i don't do anything else, except use it normally.) but today it happened without a reason, the phone was in my pocket when i took it out and saw the screen in this state.
i always flash by following the steps given. i know it is not hardware related. where is the problem? what do i need to do?
p.s. : when charging, blue part goes yellow.
thank you all, waiting for a solution
Click to expand...
Click to collapse
First go to recovery and check that display problem present or not if not then flash any other custom rom or reflash rr
if you are unable to go to recovery then flash stock rom via odin it will fix every software related issue
and if flashing stock rom doesn't work then it may be hardware issue
You confirmed the model # in download mode? Tried using different version of TWRP?
I am facing same problem recently, did you find any solution ?
still no solution. this problem is not hardware related since i can use it perfectly now. i tried to flash (via twrp) RR-N-v5.8.5 exactly as described in op. rom boots, i can see the home screen for a brief moment but screen goes immediately black and blue. i can receive calls, lock and wake screen, that's all. then i have to restore everything. i am currently on hexagon rom v2.5 and no issues but i like RR.
again, this problem is not hw related. i follow all the steps again and again checking everything..
any ideas?
blue screen
rukenau said:
still no solution. this problem is not hardware related since i can use it perfectly now. i tried to flash (via twrp) RR-N-v5.8.5 exactly as described in op. rom boots, i can see the home screen for a brief moment but screen goes immediately black and blue. i can receive calls, lock and wake screen, that's all. then i have to restore everything. i am currently on hexagon rom v2.5 and no issues but i like RR.
again, this problem is not hw related. i follow all the steps again and again checking everything..
any ideas?
Click to expand...
Click to collapse
make a clean install and try a different kernel than pre installed one
maniwaraich said:
make a clean install and try a different kernel than pre installed one
Click to expand...
Click to collapse
clean install worked for a day or so, until i turned off ambient dislpay and restart. then it went blue&black again.
i tried a few kernels, some bootloaders and modems (including nordic) but problem persists.
i will try to get a logcat :/
In case anyone has the same problem: reboot to safe mode, go to settings, flip cover and turn off S-View flip cover.
Same issue un lineage og 15.0 and 15.1 on samsung galaxy S 5 mini G800F someone find a solution?
pierpa2 said:
Same issue un lineage og 15.0 and 15.1 on samsung galaxy S 5 mini G800F someone find a solution?
Click to expand...
Click to collapse
Read thread .
Flash stock rom and test .
But this is the Note 3 forum not your phones forum .
JJEgan said:
Read thread .
Flash stock rom and test .
But this is the Note 3 forum not your phones forum .
Click to expand...
Click to collapse
lareay flashed lots of time differents ROM sorry for the wrong forum but i can't find a solution.
Stock rom with oreo does not exist.
Solved turning off smart cover
Hi all,
I'm new to the device so I'm maybe doing something wrong but I don't think so. I got the device with a terribly cracked, I flashed Pixel Experience (Android 10) as it's what I've had on my Nexus 5x, everything was working fine so I proceeded to replace the screen. I replaced it with one from Aliexpress which seems legit.
The phone then wouldn't boot, or seemed not to boot. I saw the splash screen then a black screen. The system did boot as I could see the capacative keys light up and sounds working, I just couldn't see any image on the screen. After a while trying to flash other ROMs and other TWRP versions (at this point TWRP showed up as a black screen too) I found that the following solution solved my problem.
https://forum.xda-developers.com/mi-a1/how-to/solved-mi-a1-bootloop-t3973131
This is fine, I can use the stock ROM and update it to the latest version but cannot use any AOSP based ROMS and still cannot use any other recovery apart from the one used to solve the "bootloop".
Does anyone have any idea how I can solve this? I thought the screen was maybe a weird version that needed some additional drivers but the strange thing is that it works for the stock ROM.
Regards,
Simon
Hi:
simonkerr said:
Hi all,
I'm new to the device so I'm maybe doing something wrong but I don't think so. I got the device with a terribly cracked, I flashed Pixel Experience (Android 10) as it's what I've had on my Nexus 5x, everything was working fine so I proceeded to replace the screen. I replaced it with one from Aliexpress which seems legit.
The phone then wouldn't boot, or seemed not to boot. I saw the splash screen then a black screen. The system did boot as I could see the capacative keys light up and sounds working, I just couldn't see any image on the screen. After a while trying to flash other ROMs and other TWRP versions (at this point TWRP showed up as a black screen too) I found that the following solution solved my problem.
https://forum.xda-developers.com/mi-a1/how-to/solved-mi-a1-bootloop-t3973131
This is fine, I can use the stock ROM and update it to the latest version but cannot use any AOSP based ROMS and still cannot use any other recovery apart from the one used to solve the "bootloop".
Does anyone have any idea how I can solve this? I thought the screen was maybe a weird version that needed some additional drivers but the strange thing is that it works for the stock ROM.
Regards,
Simon
Click to expand...
Click to collapse
I'm in the same situation. I think these screens are not 100% compatible so it seems a hardware issue.
Maybe using vendor partition but i'm so stucked as you.
My phone can't hotboot any official recovery although i can boot flashed recovery only if i boot slot a not slot b.
Stock roms boot always using slot a but tried Lineage (thats uses slot b) and got always black screen.
I'll keep reading and trying to solve it.
Regards.
simonkerr said:
Hi all,
I'm new to the device so I'm maybe doing something wrong but I don't think so. I got the device with a terribly cracked, I flashed Pixel Experience (Android 10) as it's what I've had on my Nexus 5x, everything was working fine so I proceeded to replace the screen. I replaced it with one from Aliexpress which seems legit.
The phone then wouldn't boot, or seemed not to boot. I saw the splash screen then a black screen. The system did boot as I could see the capacative keys light up and sounds working, I just couldn't see any image on the screen. After a while trying to flash other ROMs and other TWRP versions (at this point TWRP showed up as a black screen too) I found that the following solution solved my problem.
https://forum.xda-developers.com/mi-a1/how-to/solved-mi-a1-bootloop-t3973131
This is fine, I can use the stock ROM and update it to the latest version but cannot use any AOSP based ROMS and still cannot use any other recovery apart from the one used to solve the "bootloop".
Does anyone have any idea how I can solve this? I thought the screen was maybe a weird version that needed some additional drivers but the strange thing is that it works for the stock ROM.
Regards,
Simon
Click to expand...
Click to collapse
Have you made any progress?
gsausalito said:
Have you made any progress?
Click to expand...
Click to collapse
Thanks for your interest but I've made no progress and actually given up on it. I'm sure the issue could be resolved by buying a new, more compatible screen but I'm not going to put any more money into the phone.
As far as the software solution goes, I've tried almost every combination of ROM + Kernel i can think of but the only thing that works is the stock ROM.
I'm going to close this thread as I don't think it's much use to anyone.
Regards
Sorry for posting here, but i am in the same and i noticed that flashing canting 4.9 kernel gives display for like 8 seconds after screen turns off. May it be a kernel config issue? if anyone in this forum could answer this i could try and change it. Also flashing stock kernel on custom rom solves the problem but makes other thing fail
Hello, I've got the same issue. Is there any solution ? Or, at least, any clue to work on it ?
EDIT: I finally done it!
with this kernel (OC) : https://forum.xda-developers.com/t/...rkernel-v3-1-nonoc-and-oc-12-11-2020.4186317/
And this rom : https://forum.xda-developers.com/t/rom-11-0-official-crdroid-7-1-tissot-13-11-2020.4195351/
I installed this kernel, cause you was saying it is probably a kernel issue, so I tried to look for most recent kernel.
And then, it worked, so I think you was right.
I can't be sure it will work with all ROM, but I think.
Hello Mi A1 friends.
So yesterday I decided to change my crack LCD screen and to my surprise the phone boots into Xiaomi Logo and then after that its just a black screen. Message and other notifcation sounds still come in which means that the phone mange to boot into home screen, just with nothing to display. At the time of changing screen, I am on stock kernel and Pixel Experience 10.
Gonna flash back to stock pie(9) rom and see how it goes from there.
Deezio said:
Hello, I've got the same issue. Is there any solution ? Or, at least, any clue to work on it ?
EDIT: I finally done it!
with this kernel (OC) : https://forum.xda-developers.com/t/...rkernel-v3-1-nonoc-and-oc-12-11-2020.4186317/
And this rom : https://forum.xda-developers.com/t/rom-11-0-official-crdroid-7-1-tissot-13-11-2020.4195351/
I installed this kernel, cause you was saying it is probably a kernel issue, so I tried to look for most recent kernel.
And then, it worked, so I think you was right.
I can't be sure it will work with all ROM, but I think.
Click to expand...
Click to collapse
Sry for reply to an old post, but how did you do it? How did you flash kernel when you can't enter twrp because of screen issues? I have exact the same problem, where stock rom works but everything else cause blank screen. Also can't boot to twrp - probably the same reason.
Hi, I hope you guys are doing good at these times.
I was trying to load a stable version of Lineage OS 16 on my MI A1. But, when I flashed TWRP 3.3 the touch screen was working but very weird. So I booted the phone out of TWRP and the issue persisted.
The issue is similar to what I found on these two threads:
https://forum.xda-developers.com/mi-a1/help/touch-t3769226
https://forum.xda-developers.com/mi-a1/help/touch-screen-haywired-twrp-t3922617
I tried booting stock N android (using this file "tissot_images_7.8.23_20170823.0000.00_7.1_61cf97d794.tgz" with MiFlash Tool but the issue still persisted on the touch screen.
If you guys have any ideas please let me know.
Thanks, and have a nice day.