Hello,
I have a Samsung Galaxy S4 (i9505) with a strange behavior (ghost touch, mainly). Anyway, I have installed a dozen of custom ROMs (even reinstalling the stock ones) with no success.
I've noticed that no matter what ROM was currently installed, I've got the same TSP values (when running *#2663# code):
Phone's TSP FW version: SYB0085C
Part's TSP FW version: SYB0085C
Config TSP FW Version: SGH-I337_SY_0608
TSP checksum data: NA
(btw, I actually have an i-9505 model but it prints SGH-I337 , as above)
Looks like the phone software was messed up by the former owner (or by a regular update).
I've tried to wipe/format all the partitions (I'm using TWRP recovery) but the TSP firmware is still there (as the TWRP itself uses the touch screen input only).
How to actually get rid of the current TSP firmware (complete wipe/remove) so I could install another version from scratch (along with a custom ROM or such)?
Does the recovery software (TWRP) use a custom (embedded) TSP firmware? (though I got the same ghost touches in TWRP, too).
Thank you in advance for any help.
I've just installed (downgrading) another TWRP version (hoping for a non-touch driven interface - with no luck).
Anyway, while testing the new recovery interface I've noticed that the ghost touches almost disappeared (and they were present in the recovery mode, too).
After restarting the phone, I've noticed the same reduction in ghost touches (though they're still "alive") but I wonder what could have been the influence of the new (actually, older) version of TWRP on touch screen firmware (or touch screen behavior, for that matter)?
Does the recovery software (TWRP) use it's own touch screen firmware and did it actually rewrite the former TSP firmware version?
Any ideas, please?
I've made some progress on chasing the TSP firmware.
I found that the "apnhlos" (by-name) partition is mounted as /firmware during regular operation (but was not mounted during recovery). Hence I have mounted it then I found out its content:
Code:
keymaste.b00 q6.b00 skmm_ta.b03 tima_key.b03 tima_pkm.b03 vidc.b03
keymaste.b01 q6.b01 skmm_ta.mdt tima_key.mdt tima_pkm.mdt vidc.mdt
keymaste.b02 q6.b03 tima_atn.b00 tima_lkm.b00 tzapps.b00 wcnss.b00
keymaste.b03 q6.b04 tima_atn.b01 tima_lkm.b01 tzapps.b01 wcnss.b01
keymaste.mdt q6.b05 tima_atn.b02 tima_lkm.b02 tzapps.b02 wcnss.b02
mc_v2.b00 q6.b06 tima_atn.b03 tima_lkm.b03 tzapps.b03 wcnss.b04
mc_v2.b01 q6.mdt tima_atn.mdt tima_lkm.mdt tzapps.mdt wcnss.b05
mc_v2.b02 skmm_ta.b00 tima_key.b00 tima_pkm.b00 vidc.b00 wcnss.mdt
mc_v2.b03 skmm_ta.b01 tima_key.b01 tima_pkm.b01 vidc.b01
mc_v2.mdt skmm_ta.b02 tima_key.b02 tima_pkm.b02 vidc.b02
Now that's the true challenge: which one is the TSP firmware (if any)?!
Any help, please?
I'm in the twilight zone, really.. I've tried to delete the whole content of "apnhlos" aka "/firmware" aka "/dev/block/mmcblk0p1" while in recovery mode, it shows an empty partition but after reboote the whole content is back!
I've even tried to format it (mkfs.vfat /dev/block/mmcblk0p1), it looks empty afterwards but then again, the data is back after reboot.
Now I really need some help.. how to actually get rid of that partition content?
Any help, please? I'm running out of ideas..
Meanwhile, my sensor hub (software) has broken, too (no sensor is working nor detected) hence I need to reflash that sensorhub firmware too.
I've tried the "*#2663#" method but it fails when I'm trying to update SENSORHUB.
I've flashed a lot of stock ROMs (using Heimdall tool) but no one seems to change the TSP or SENSORHUB firmware.
Are they stored on kenrnel or something?
Hi guys,
Still no luck on my quest of replacing my phone's touch screen driver.
I found the location of the driver (/sys/bus/i2c/drivers/synaptics_rmi4_i2c) but I don't know how to disable it (for testing purpose only) or how to actually replace it.
For instance, does anyone know how to disable (or unbind de touch screen device from the aforementioned driver) using an adb (shell) command?
Related
(Feel free to move this thread to anywhere where it belongs, if it's an issue. And sorry for my non-native english).
Good night for everyone,
To make it short:
- I bought an LG G2 D802 from amazon.com (description says it's a factory unlocked phone).
- Tried to install a modified kitkat rom.
- The phone bricked into fastboot mode, but then I could repair the download mode and installed a Hong Kong (without noticing it and messed up the phone, because I'm form Venezuela and it went to a Locked state) stock firmware. But couldn't repair the recovery mode.
- When the phone booted it had an apparent screen calibration problem, where it doesn't respond accurately to touch, but going to the sensor->calibrate sensor option from settings menu didn't fix the problem at all. So I think it's something related to the Android system files (partitions maybe?) and not the settings or S/W at all.
- Installed an Open kitkat firmware hoping that it would fix the issue, but with no result. It correctly changed the S/W, but the screen problem persisted.
Some ideas that I have (but haven't found any propper methot to fix the phone) are:
1. If it applies: repairing the Android system files, to fix the touchscreen problem.
2. Rooting the phone and installing the best Recovery Mode to fix the phone.
3. Wiping the phone to blank.
4. Install a correct S/W from zero.
5. Hoping that it works
If it's possible doing it from a pc software or command line (connected to the phone obviously) I think it would be the easier solution, but don't know how to do it.
I would be really grateful with anyone who reads this and can help me fixing this...
Thanks.
I hope someone has some experience of this problem, I will do my best to explain in some detail.
It is as out of the box currently running version 4.0.4 firmware.
The history, initially stock firmware version 4.0.3 was running, the USB was a little loose, so I swapped the complete pcb with another S2 I have with a faulty display, to make things a bit more complicated I also put in a 2Gb SD card, when I rebooted the problem appeared, on pressing the power button to wake up, the screen comes on to the lock screen in dimmed mode, and it will stay like it for anything from 5 to 15 seconds, then the screen will go to full brilliance and the screen can be unlocked.
What I have tried, removed and rebooted with sd card removed, swapped back the original USB pcb, and swapped back again as the problem remained, also upgraded to firmware version 4.0.4, that is more or less where I am now, the problem remains.
Have tried researching but unable to find anything relating to this problem, do you have any ideas?
Update:
After further reading, it appears the original firmware may have been customised, because I was not able to get Kies to connect with the device and the CSC was stated as 'unknown', which from what I have read indicates a custom ROM.
Having flashed the stock firmware , on the recovery menu I get still the message #Manual Mode# Appling Multi CSC.... Applied the CSC code: XEU Successfully applied multi CSC, which was also present with original firmware but it never actually applied the code as it stated CSC 'unknown'. but I can now connect with Kies and the CSC code is stated as I9100XEULPA.
Is it normal to get this message at the recovery menu?
Is it a symptom of the same lock screen delay issue?
Solved
I spent 6 weeks trying to fix this, the most aggravating of problems are sometimes very easy to cure when you know the answer!
Disable auto brightness, easy, your long wake up delay has now gone.
Let me know if it helped you.:good:
I tried to change the internal partitions because by default only 1GB is available for apps, this failed horrible with the provided app (HK Rom Editor) and caused a bootloop.
Afterwards I re-flashed the phone with firmwares which I found on Needrom, that worked fine but the touchscreen is totally misaligned doesn't matter which one I use. If I press for example the top part the phone thinks that I'm touching the middle, it does work fine its just totally wrong calibrated. I can't check if anything else isn't working.
Model: THL 4440, 4GB
Android: 4.2.2
Has someone any idea how I can fix this issue? Do I need a different stock firmware?
Someone told me that I deleted/overwrote my touchscreen calibration files, is there any way how I can identify the chip or get proper files for the THL 4400?
Hi There,
My Main Issue:
I have a Samsung Galaxy S6 Edge SM-G925F, with a cracked screen, at 15% battery life the display is not usable, although anything after 25% it becomes usable and brightness levels from 60%~100% the device and screen is usable.
BIG issues:
Recovery Mode [Display Dead - But Active in Recovery Mode]
Download Mode [Display Dead - But Active]
Boot Screen and logo [Nothing but one flash on cracked side] - indicates OS boot
Work a rounds:
Watched YT videos of people in recovery and basically counted my way to wiping cache and dalvic etc [which worked once]
FIRMWARE Issues:
Samsung_SM-G925F_(G925FXXU6ESA1_G925FOJV6ESB1_South_Africa_v7.0)_by_(FirmwareOS.com) - Size: 1.9GB | Works But unable to boot
SM-G925F_1_20180530094301_nsue7o1m55_fac - Size: 4.9GB | Works but when installed only 16Gb assigned feels like the wrong firmware or dual sim or possible double os with backdoor
XFV-G925FXXU5EQL2-20180111184000 - Does not work without alterations.
Odin Version Used: 3.10, 3.10.6, 3.10.7, 13.14
1. When installing Samsung_SM-G925F_(G925FXXU6ESA1_G925FOJV6ESB1_South_Africa_v7.0)_by_(FirmwareOS.com) using odin, it completes with success although its unable to boot into the startup screen. (Most likely stuck on boot logo but unable to see).
2. When installing SM-G925F_1_20180530094301_nsue7o1m55_fac using odin, it completes and is able to boot and setup the device. My main issue is that this OS is double the size weird in app apps and the OS Storage is at 16GB and not 32GB.
Work Around:
I installed SM-G925F_1_20180530094301_nsue7o1m55_fac then at bootscreen entered download mode again and installed Samsung_SM-G925F_(G925FXXU6ESA1_G925FOJV6ESB1_South_Africa_v7.0)_by_(FirmwareOS.com), That installs with success and boots it sorts out the weird apps and works smoothly, only problem is now that storage is at 16GB and not 32GB still.
I have got XFV-G925FXXU5EQL2-20180111184000 working and installable although it is not worth the effort as the OS itself is missing major .com files.
I messed around to the point where i got it to 32GB although i flashed it to get to the working non sketchy size firmware Samsung_SM-G925F_(G925FXXU6ESA1_G925FOJV6ESB1_South_Africa_v7.0)_by_(FirmwareOS.com).
My Final Points:
Started googling how to build my own android rom, turns out that route is going to including a steep learning curve and a fast data connection.
Remembered XDA back when i used android 5 years ago and i must say this is a darn cool upgrade to XDA , tried to find a firmware failed
Found Linage OS, realized i cannot install that due to no sd card and no screen visibility in recovery mode.
Is there anyone with free time and the available tools required to create a proper bootable image for the SM-G925F perhaps stock 7.1 rom, or help me piece together a working one using multiple other firmwares.
Been mixing around with the images, then simply recreating the md5 files and the final combined.md5 would be used as the trial and error img.
Mission:
Trying to get this baby back up and running so that i could actually utlise it by installing linux etc as i do not need a screen to VNC or SSH
Thanks in advance
UPDATE:
New Firmware found:
ISSUES: Able to install although displays 16GB of storage still.
I was unable to install in stand alone from download as Odin got stuck at meta-data/foto.zip
After removing the meta-data i then remade the .tar.md5 and installed it using Odin
It was a success up until i checked the storage and it was incorrect. I then went to Settings and found those weird looking settings "Apps" setting doubled .
Link : SM-G925F_XFV_G925FXXS6ETK3_G925FXFV6ESE1_G925FXXU6ESE3_G925FXXS6ETK3
EDIT:
Currently Going to give this one a try
G925FXXS6ETJ4_G925FOJV6ETJ1_PAK-Droidhelper.com.zip
Will update with results
UPDATE: Did not work.
Going to fiddle with number 2 as that one happened to pick up 32GB on one install.
Found a New Firmware:
XSG-G925FXXU6ERD3-20180515181713
Going to give this one a try.
Will post an update
UPDATE: Did not work
Long story short....eh.....?!!
My Samsung Galaxy A10 (SM-A105FN) got wet during a rainy bikeride! At first it still worked - but then started to show a yellow triangle with exclamation point (charging problem?), restarting and ending up in Android Recovery (the one with only three options - Try again, Factory data reset and View recovery logs) saying Can't load Android system, Reboot Recovery Cause is: Unable to disable quotas on dev/block/platform because system/bin/tune2fs is missing.
So, not able to get into system and turn on USB debugging etc...
Current stock firmware PDA: A105FNXXU6BUC3 (Android 10)
Tried to install new firmware via Apply update from ADB and SD card but both failed saying Failed: Out of memory.
With Odin I got PASS! flashing BL+AP+CP+HOME_CSC with latest stock fimware PDA: A105FNXXS7CVB1 (Android 11) - but still in Recovery loop now saying Reboot Recovery Cause is: [set_policy_failed / data/app]
The phone is not rooted nor bootloader unlocked.
I don't care about the phone (budget) - but I really do need my own data back!!
Is there a way without losing data? TWRP??
Jan
In trying to be helpful, all I can do is point you to this thread where I personally organized in one place over 200 similar threads (almost) exactly like yours (where all had an unresponsive screen - but most were due to being dropped).
What is the best XDA solution to control Android on the PC & recover data over Wi-Fi when the user suddenly has an unresponsive broken screen?
GalaxyA325G said:
In trying to be helpful, all I can do is point you to this thread where I personally organized in one place over 200 similar threads (almost) exactly like yours (where all had an unresponsive screen - but most were due to being dropped).
What is the best XDA solution to control Android on the PC & recover data over Wi-Fi when the user suddenly has an unresponsive broken screen?
Click to expand...
Click to collapse
Thanks GalaxyA325G!
I'll dig into that thread!!
Probably - or, definitely - I'm screwed....!!!
also TWRP supports MTP