Greetings,
I want to ask if there is any solution to fix inverted touch (position X) on screen on my Samsung Galaxy S6 [G920FXXS5EQL1].
With TWRP 3.3.1.0 I made backup of official Samsung Android Nougat 7.0 I have installed on my phone.
Then I wiped Dalvik / ART Cache, Cache, System and Data. Rebooted back to TWRP, downloaded LOS 17.1 UNOFFICIAL ROM and then put it into Internal Storage.
Started flashing this ROM, when flashing was completed I wiped Dalvik / ART Cache, then Rebooted to System. Everything was fine, until Setup screen.
When I clicked on Next, it clicked on Emergency call, I was confused so I restarted back to recovery TWRP but now even in TWRP the touch is inverted, so I wiped
again Dalvik / ART Cache, Cache, System and Data. Rebooted back to recovery TWRP and installed back backup. The problem still persists even on official Samsung Android Nougat 7.0.
Rebooted back to recovery TWRP and wiped Dalvik / ART Cache, Cache, System, Data and Internal Storage. Downloaded and flashed /e/ OS but still, touch on screen is inverted.
I already tried USSD/MMI code *#2663# from this thread on LOS and /e/ but on these ROMs, this doesn't work.
Is there any solution to fix this ?
Thank you
you probably flashed the wrong twrp. You will need to install stock rom and then reinstall touch firmware.
Thanks for advice.
It's already working. The official 3.3.1.0 TWRP for Samsung Galaxy S6 caused this inverted touch.
So I flashed original firware via Odin G920FXXS6ETJ6_G920FOXX6ETI6_G920FXXU6ERF6_HOME.tar.md5 (tried 18 different firmwares, only this one worked)
Reinstalled touch firmware in Samsung Test Menu.
I used this time unofficial twrp-3.5.2_9-0-zeroflte.img via Odin.
Then I flashed /e/ OS via TWRP and everything works like I wanted.
Related
Hi. Yesterday I succesdfully rooted my n8020 (galaxy note 10.1 LTE Swedish). Tho, when I tried to flash Sbiddens modded CM version, it failed. I wiped data/facto ry reset from CWM, wiped cache and Dalvik. Flashed CM and Gapps. Rebooted, only to get stuck at the blue-ring Cyanogenmod boot screen. Tried to redo all the steps in different orders, no succcess. Stillvstuck at boot.
Then came the puzzling part. I downloaded the original firmware from sammobile.com, and flashed it via Odin. It succeeded, bit whenbit booted in back to the standard rom, all my applications and all the data was intact! As I sevetal times wiped data/factory reset, I assumed thatevwrything would be gonw and that I'd have to install everythingnfrom scratch. Am I correct in assuming this, and may this be related to CM getting stuck at boot? Any hel greatly appreciated!
vargfloejt said:
Hi. Yesterday I succesdfully rooted my n8020 (galaxy note 10.1 LTE Swedish). Tho, when I tried to flash Sbiddens modded CM version, it failed. I wiped data/facto ry reset from CWM, wiped cache and Dalvik. Flashed CM and Gapps. Rebooted, only to get stuck at the blue-ring Cyanogenmod boot screen. Tried to redo all the steps in different orders, no succcess. Stillvstuck at boot.
Then came the puzzling part. I downloaded the original firmware from sammobile.com, and flashed it via Odin. It succeeded, bit whenbit booted in back to the standard rom, all my applications and all the data was intact! As I sevetal times wiped data/factory reset, I assumed thatevwrything would be gonw and that I'd have to install everythingnfrom scratch. Am I correct in assuming this, and may this be related to CM getting stuck at boot? Any hel greatly appreciated!
Click to expand...
Click to collapse
Bump
vargfloejt said:
Bump
Click to expand...
Click to collapse
I have seen something similar when I installed Cyanogenmod on a kindle fire, I had to do a factory reset after restoring back to stock firmware.
I would suggest that you try doing a factory reset after restoring factory firmware on your GNote.
Success with Philz recovery
Had the same problem loading onto my N8020.
In the end I used a different recovery and it worked first go.
Try using Phils recovery http://forum.xda-developers.com/showthread.php?t=2202714
Hi,
I was trying to install lineage os, I had TWRP 3.0.2. I booted to recovery, did factory reset, then wiped dalvik, system, data and cache. Then when i tried to flash os, i got error code 7. I downloaded latest TWRP-3.1.0 and flashed it to recovery, after which my phone is not going to recovery at all.
Please help me in this.
My bootloader is unlocked.
Using FlashTool 0.9.18.6, I flashed "Sony Xperia L C2105 15.3.A.1.17 Generic DE" - FTF, which I downloaded from:
https://forum.xda-developers.com/xperia-l/general/sony-xperia-l-flashable-ftfs-locked-t2560642
Downloaded CM11 from FreeXperia's thread, from that I extracted boot.img and using FlashTool flashed it.
Downloaded CM12.1 from Oliver's thread and moved it into my external sdcard. Using CWM, did a clean wipe (dalvik, cache, data and system), and flashed the zip.
ROM installed and was working fine.
Downloaded CM13 from Oliver's thread and moved it into my external sdcard.
Enabled USB debugging.
Downloaded TWRP 3.0.2-0, from:
https://dl.twrp.me/taoshan/twrp-3.0.2-0-taoshan.img.html
Rebooted into bootloader using adb. And flashed TWRP, using fastboot:
"fastboot flash boot twrp.img"
Rebooted into recovery. The interface was flickering non-stop and the left part was overlapping over the right part and vice-versa, but I managed to factory reset and wipe my dalvik, cache, data, system, sdcard and android secure.
Then I flashed CM13 from my external sdcard.
No errors.
Wiped dalvik, cache and my external sdcard.
Rebooted.
Bootloop.
Rebooted into CM Recovery.
Factory Reset and wiped cache.
Rebooted.
Bootloop.
I have also tested 7.x.x (CM14 and Resurrection Remix) and it also gets me in a bootloop until the battery reaches 0%.
The problem started with Beta 2 of CM13 (anything before it works fine), after I flashed it almost a year ago. I also made a post there at that time about my problem:
"I'm not certain if this is the right thread to ask, and I don't think this qualifies as a bug report, I'm just asking for some help as my phone is stuck on the boot logo forever until the battery runs out (from 90-100% to 0%).
I've previously used CM11, CM12.1 and the previous beta 1 of CM13, but after flashing beta 2 a couple days ago it's just stuck on trying to boot.
The recovery I'm using is TWRP 3.0.2. I wiped my phone completely(the system, sdcard, cache etc). After that I connected my phone to my PC, while on recovery, and copied the ROM zip and GAPPS zip to my external sdcard. I disconnected my phone from the PC. Flashed the ROM and after that GAPPS (Open GApps Platform: ARM / 6.0 / pico). The logs didn't show any error so I wiped the dalvik cache and rebooted the phone. The phone went into the boot logo and now is just stuck there, I waited ~5 hours and it still didn't fully boot after an hour or so the battery ran out. So I decided to do everything again, charging the phone to 100%, wiping the phone completely 10 times(for reasons) and flashing everything the same way(I also downloaded the ROM from a different mirror, and tested both zips for any errors), this time I left it overnight, keeping the charger connected and in the morning it was still stuck on the boot logo. The third time I tried a different GAPPS package(A-GAPPS) and the same result. Can anyone provide some help? Maybe I'm just missing something or being really stupid. I'm sorry for being such a bother."
https://forum.xda-developers.com/xperia-l/orig-development/rom-cyanogenmod-13-0-t3254779/page20
I made this thread in hope of finding out what's causing this. Any help is appreciated.
It's been almost a year and I still have this problem with newer ROMs. Does nobody have any suggestions, anything at all? Is more information required? I'd be happy to give/do anything*, if it would mean getting these ROMs working.
The only error I've noticed is that after flashing LineageOS 14.1, if I try a fully factory reset through the default "Android Recovery" it will fail and I'll get "E: format_volume: failed to open /persist/footer" (This doesn't happen if I do a factory reset through TWRP).
Hi,
I recently tried to install a custom rom (Resurrection Remix) on the latest EMUI version which resulted in my device not booting anymore.
After several tries I gave up and wanted to simply use stock with root.
I installed SuperSU, but that did not show up in the application menu.
After that I recovered system and boot from a recent full backup and installed magisk.
That resulted in the device not booting anymore at all. This condition stays now.
I then reinstalled the stock rom via dload method, with a factory reset after, but it then started to be stuck in the blue screen with the honor logo.
Is there anything I can do? TWRP is gone, I only get the stock EMUI recovery.
This happened to mee too. You should try a wipe data and cache from recovery, then reboot. It worked for me.
P.s i flashed a stock recovery don't know if TWRP will work the same, try.
After the dload update the stock recovery is installed again, I wiped data and cache already, but that didnt make it work too :/
EDIT: Found the error: The /data partition is unusable in it's current state (f2fs). Is F2FS the default filesystem for /data or do I need to change it to ext4 or something?
Background:
The boot-loop happened few days after installing the Arrow OS [Pie]. Below is the link from where I installed the same.
https://forum.xda-developers.com/oneplus-one/development/unofficial-arrow-os-bacon-t3836884
I've tried the following things till now:
1. Tried "Advanced Wipe" via TWRP (only dalvik cache and other cache)
2. Tried "Restore" the back up I had saved for old OS (RR Oreo OS)
3. Tried "Advanced Wipe" via TWRP (wiped everything including system and installed RR Oreo OS again)
4. Tried Flashing CM Stock ROM (cm-13.1.2-ZNH2KAS3P0-bacon-signed-fastboot_64GB) - Currently, my phone is on this ROM.
Please help me on this.