[Q] My Touch Screen doesn't work on recovery. - Galaxy S 4 Active Q&A, Help & Troubleshooting

Hi, everyone. I bought a used Galaxy S4 Active a week ago and works like a charm (except for the display, it shows burns like a AMOLED Screen over time, mostly on the borders), and the first thing i did was try to install custom recovery (Philz Touch Recovery). Everything went fine except that my touch screen doesn't respond in Recovery Mode (I try with TWRP 3.0.2 by jcadduono also). This is weird because i have no problem with touch or anything in normal boot. Can you help me? I think this is not the original screen and that's why i'm getting that weird burns on the LCD.

same to me twrp doesn't even work on my s4Active and showing lcd burn too

Try to flash TWRP by jcadduono. If it doesn't work there, you should replace your digitizer/screen

you can use a mouse via otg cable , it works on twrp 3.0.2

Related

CWM works, but Android wont boot after.

Tried to change the cover of the phone, but I did not go trough with it.
So I screwed it back together, and now Android wont boot, the screen just goes black after a few seconds. The screen works, the buttons work, it's only the OS that wont boot.
Anyone seen this before?
Solved, got the phone mounted in CWM, and Rooted a new rom

M7 doens't boot with replacement display

Hi everyone,
I have a weird issue with my M7.
It fell down and now the glas is cracked, but everthing is still working fine. Now I wanted to replace the screen and I bought a new display+touchscreen.
The weird thing now happens: when I connect the new display the phoen won't boot (just using the flexcable for the display is enough ... touch doesn't matter). It gets stuck directly after the bootlogo.
I can access the bootloader, but not the recovery or the system. When I reconnect the old display everything is working fine.
At first I thought that the new display might be defective and I sent it back. Now I got a new one from another seller and I have the same issue again.
I tried it with newest twrp and cwm recovery + CM11 and the stock firmware via Guru Reset M7 2.24.161.1
Any ideas?
Edit:
Just recognized that the device seems to boot, but the screen is just black (background light on) ... well at least I was able to reboot the device via adb (stock 4.2.2)

[Q] data rescue (water damage) with TWRP?

Hello everybody,
I have an S3 Mini here that was in the water. I disassembled and dried it - but the display is not ok: It flickers, sometimes off, sometimes very dark and wrong colours. All buttons and the USB plug work.
So i thought about uploading TWRP with ODIN and boot into it (hoping that when TWRP is running, i cann access the file system). When i start it normal, it shows the unlock screen, but because i cannot touch i cannot unlock it.
I launched ODIN, downloaded the TWRP here from the forum, and i can flash it - but i cannot boot into the recovery. When i try it - the first samsung logo just stays and nothing happens anymore. Is there some more to do / may i have missed something ?
Or is there a different way to access the data?

Xperia Z3+ E6553 - strange issues, i wanna help

If you dont want to see all my story, go down 2 see the base of my problem and second question.
Hello, i recently bought this phone in last week, used, for fifty euros and it had 32.3.A.2.33 firmware, and please remember WHITE boot screen.
It havent bootloader unlocked.
For some hours of using, it runs fine, except display, seems to be changed by amateur person, sometimes bad touch sensitivity, but i turned on glove mode and no problem. No lags, camera working, every thing - no problem so far.
And then problem began - after restart for sim change, phone boot animation was very slow, and some display flickering. When it booted, system was very slow, display had very slow reactions, i thinked it was GPU or software problem. After some minutes it itself rebooted, 2 red blinks and then booted very fast.
I tried some restarts, 2 of 5 was this problem.
I tried unlock bootloader, and install TWRP, because i think this isnt GPU problem, if 3 times booted and works flawlessly for HOURS !
Okay, bootloader unlocked, twrp installed, i searching for some roms, but phone have very bad community on XDA, i downloaded 3 roms:
AOSCP 3.5.1 - works flawlessly, no display flickering or something, some bugs like camera with bad quality photos, but after restarts, no display flickering or lag and this is important. But no boot screen (pure black boot screen)
Ressurection Remix 5.8.5 - Android 7.1 - after restart it HAD flickering and lag, something similar like first stock rom, 2 of 5 boots... Not very bad but yes. Very good rom.
LineageOS 14.1 - EVERY BOOT HAD THIS PROBLEM. LAGS, DISPLAY FLICKERING, RESTART AND 2 RED BLINKS.
So i installed again AOSCP 3.5.1 and no problem, only camera.
My not intelligent head was a plan - i prove a downgrade. To 28.0.A.4.8 - stock android 5.0.2. Phone gets black boot screen, and EVERY boot had this problem. Lags, scuttering, flickering... But it booted. I try restart, but no difference. 5 of 5 boots had this problem.
I have installed again nougat rom but not like first, but 32.4.A.1.54. After start flashing with flashtool - report an error with boot_delivery.xml - so i checked exclude bootbundle - no problem with flash. Restarted.
Phone had a BLACK BOOT SCREEN - i looking, because nougat sony roms has a white boot screen.
First boot without Sim card - no lags anytime. It has restarted itself, because i wanted to add sim card.
After reboot, every reboot had this problem.
I tried flash with fastboot twrp like first - https://forum.xda-developers.com/xperia-z4/development/twrp-twrp-3-1-1-z3-z4-t3862684
After fastboot reboot - phone has 2 red blinks and not turning on. I put cable out and i trying to turn on it, but it only vibrates 3 times and nothing. Boot or something, i thinked it is dead, but FOR TODAY im able to get into flash mode and bootloader.
I skip some 5 days with trying with flashtool LP, MM and NOUGAT roms, FLASHING TWRP, Sony companion is unusable, because i unlocked bootloader... My phone (or fifty euros) is in holy phucking s+++ in 2 days of using.
Okay, only twrp what i can boot normally is 2.8.7.0 recovery by old 5.0.2 android Z-ROM https://forum.xda-developers.com/xperia-z4/development/zrom-custom-rom-z3-e6553-28-0-8-251-t3206005
For questions, i tried both this stock firmware and custom rom, rare thing is boot normally, but after restart, no difference.
I tried flash again first stock rom 32.3.A.2.33, no difference, but BLACK BOOT SCREEN aside of white.
One but only one different 3.0.0.0 twrp what im able to flash, only into FOTAKernel or RECOVERY not boot partition, because RED blinks and nothing, but this twrp is from sumire (z5):
https://forum.xda-developers.com/crossdevice-dev/sony/twrp-3-1-0-z5-z5c-z5p-t3571050.
I founded this argument by flashing and aoscp rom and error: This is for (ivy), your device is sumire.
I think i can change update_script - there i changed every ivy to sumire.
Installed with this twrp flawlessly, flashed magisk, reboot.
Again Red blinks...
Now what im able FUNCTIONAL only - flash 2.8.7.0 (too with display flickering and , but this twrp is ONLY for install Z-ROM, other roms like aoscp and RR i cant install because error E1004: cannot install system boot image.
And other twrps i can flash only to boot (kernel) partition, but red blinks or boot again into this 2.8.7.0 recovery.
I am making with Sony, and i had in the hands SO MANY phones , so many from them for repair, from different brands for 7 years, no problem with flashing so far (i thinked i am unstoppable :victory: ), and this is my 2nd phuckedup phone for whole 7 years (first was LG G6) and i wanna help, because i have working flash and bootloader, but i havent an idea what next, because some (80 percent) threads havent functional download links for NO SUPPORT or something, but this is absurd. Like my issue, but this is real. For example: i have Xperia SP for 6 years, with stable recently updated (30.9) LOS 15.1 and Xperia S (recent nAOSP 8.1) for 7 years, flashed anything, anything, anything... Downgraded, upgraded... And no problem for today. Reliable phones as... SP is my primary phone (for 6 years) and S for testing. I wanted something from sony but more performance - functional for 2 days. And karma is here - in xda.
Recently i put it into wall charger, it booted into that 2.8.7.0 recovery and it had 94° and it still breaths ! And really it was very hot ! Normally it had less than 60°.
If i flash through fastboot mentioned newer twrp 3.1.1, 3.0.2, 3.2.3 or other mentioned, what non-functioning there, after that red led blinks, it will go to (green) flash mode.
The main problem is: I am able to go into flashmode and fastboot, i can boot system, but (now) i am able to flash only one old recovery, where i CANT install and boot for example aoscp rom or other rom without problems (black screen, then red blinks, then green flash mode). Original software - lags, display scuttering, graphic artifacts but rare thing is going flawlessly, so i think isnt gpu problem. I need real help. I need this phone and i think it can be recovered. I can send anything from this phone (logs or videos), what would be helpful.
After factory reset + system format, in that old recovery, i have in internal storage (sdcard) folder with name 0. Everything cleaned, but this folder remains.
So there is second question, someone experienced with this issue ?
Problem with aoscp fixed. Very luckely, but no problem now !
I had an version of flashtool, 0.9.18.6, maybe i havent problems, because i had older phones from sony (my fault) and newer versions i have experience, cant found .ftf with older firmware.
An error, what i had in older flashtool when i trying to flash both nougat and marshmallow roms - entry (0000084F)parsing error boot_delivery, which means an program for boot.
I doing an very bad thing - check exclude bootbundle and flash was without errors, but this is reason, why i havent an white screen in nougat and marshmallow and amount of recoveries i cant flash so i cant flash an rom.
What i do is install an 0.9.23.1 version of flashtool (because i have an x86 notebook and today versions dont support x86, only x64)
Downloaded orange PL 32.2.a.5.11 (marshmallow official stock rom) from XperiFirm and it flashed bootbundle without problems !
I restarted it - WHITE BOOT SCREEN and HOORAY ! But lags, display scuttering and things, what i writed here, was here, also after itself restart - 3 red blinks. So after 3rd reboot i take cable, plugged in with volume +, fastboot flash boot 3.1.1.0 recovery and it worked.
Flashed AOSCP, magisk and booted without problems, no lags, no display scuttering and etc.
I am very glad i fix my problem, but an question still, why in official firmware or some custom roms (except AOSCP) i had this problems with lags, graphic artifacts, scuttering and reboot in random time with 3 red blinks ? On EVERY official firmware
Hint for you
If you have problem like me, every custom rom making problems, use boot image from aoscp https://androidfilehost.com/?w=files&flid=143620
I am not maintainer of this rom, i want only help others, if your device lags or graphic issues.
Maybe you get bootloop, but with this boot image i havent experienced after every reboot any problem with mentioned lags or again flashing twrp.
Still question for E6553
I tried almost all roms for this device and every other roms have problem with mentioned.
After flash and restart, every boot have problem with display flickering, lags and very, very slow reactions.
Even with every official firmware.
AOSCP is ONLY FUNCTIONAL SYSTEM FOR MY DEVICE ! But it have some bugs, like automatic brightness, bluetooth turning off, nfc not working, accelerometer or little bit heat and idle battery drain (it is fixed by GlassCanon LXT magisk mod) or screen does not turn off when i call, but never this boot problem.
One thing what i see, aoscp havent boot logo from sony and when i get out boot.img from this rom and put it into other custom roms (like LineageOS 14.1, crDroid or RR) and reboot it, no lags, no display flickering, pretty fast boot animation, but bootloop, so this boot.img is proprietary.
I tried from androidfilehost download aosp ota, but error 7 in twrp and when i change this in updater-script, then error 6.
Next what i tried from aosp - fastboot flash system.img - and i cant install it, because this file is big - around 1.2gb.
I am in corner with this phone and i wanna help, what more i should do for stable system or fix bugs in this rom.
Thanks

Mi 8 dipper Touch not Working -> Unplug display from motherboard and back in.

Hi everyone, i Have mi 8 global running latest miui 12 official.
I've never modded it before the issue and it was locked bootloader.
Here's the story:
After a screen replacement all was working well until i first shut down the phone and then when i booted it again the touch screen didn't work at all. I could perfectly see the images but touch didn't work and booting in recovery had the same issue.
How i managed to make the touch work:
1) Boot the Phone in System or Twrp
2) While booted unplug the display connector from motherboard and plug it back in
3) Touch works perfectly until i power off the device (and then it doesn't work again)
Also:
I tried various fastboot flashes and i found out NO MIUI Rom Fix the issue, except for this one (i didn't try custom roms): dipper_global_images_V9.6.7.0.OEAMIFD_20180903.0000.00_8.1_global_5671a55800.tgz
But:
-If i boot into System the touch works everytime perfectly even if i shut down the phone and boot it again.
-If i boot into Recovery (TWRP) the touch won't work so i need to unplug and re-plug the display connector to make it work, but after shut down it doesn't work again (it still works everytime in System).
Also:
I'm currently running this rom and i have random reboots (which never happened with miui 12).
Any help would be appreciated, thanks

Categories

Resources