search

fakemanoan / TWRP-Releases

TWRP release page
0 stars 0 forks source link

Touch not working (SM-G925P) #1

Open SaqinNoor opened 1 month ago

SaqinNoor commented 1 month ago

Flashed the image, rebooted into TWRP, but touch seems to not be working at all. I know zeroltespr or SM-G925P is not supported, but it's not that different from SM-G925I, right? Like, there might be SIM related problems, but the hardware is not different enough to bork touch. If unable to provide support, could anyone guide me somewhere else, any other build of TWRP, that could let me install fakemanoan's LineageOS 20 ROM? I claim all responsibilities for damage to my device. I'm f***ing around and finding out. I am technically flashing firmware designed for one model on another unsupported model. However, I still expect some kind of help. Thanks.

fakemanoan commented 1 month ago

Can you confirm a few things for me.

Did you flash the S6 edge TWRP? Did you have problems with your previous TWRP (if you previously installed an older TWRP)? Does the device respond to adb commands (adb shell)? Do you have an issue using https://drive.google.com/drive/folders/1gAlPsZIkYM-XYWu-JWJCDgwJ-60h0Ss2 these builds?

SaqinNoor commented 1 month ago

Did you flash the S6 edge TWRP?

Yeah, I may be an idiot but not that big of an idiot to flash the flat variant's builds :p

Did you have problems with your previous TWRP (if you previously installed an older TWRP)?

Nope, I reflashed TWRP from the official site (version 3.3 or something I believe) and it worked fine with flashing CrDroid, backing up, and restoring backups.

Does the device respond to adb commands (adb shell)?

Yeah, it works fine when I use fastboot or when I delete system apps using adb.

Do you have an issue using https://drive.google.com/drive/folders/1gAlPsZIkYM-XYWu-JWJCDgwJ-60h0Ss2 these builds?

I don't know, but I'll try within the next 3 days.

Thank you so much for your support, even though I'm running unsupported hardware.

fakemanoan commented 1 month ago

Sorry for any confusion, but TWRP can accept adb commands (I think you were referring to android 13 specifically and not the recovery). Can you get an adb shell in TWRP?

The reason is to see if TWRP is non-responsive in general or if its just touch input.

thanks :)

SaqinNoor commented 1 month ago

Oh sorry, I misunderstood your question there. I'll retry later and notify. Although I think TWRP does respond, since the screen turns off by itself, and by that point I'm completely locked out, since unlocking the screen requires a swipe.

SaqinNoor commented 1 month ago

Sorry for the 3 days of absence, but I'm back TWRP responds to ADB commands Used the builds from the Google Drive linked above, but same problem

I would like to wrap this issue up and close it, since I'm not really interested in custom ROMs and do not have a reason to use TWRP anymore. However, I do want this bug to be fixed for the people running into the same problem and/or me looking to run custom ROMs again since using Android 7 really is a nightmare for running recent apps :)

SaqinNoor commented 1 month ago

Hello, no replies in a while... The current state of the stock ROM has really made it necessary to upgrade to Android 12/13. I would appreciate it if we could troubleshoot and fix this soon.

fakemanoan commented 1 month ago

Weird. Does TWRP 3.3.1.0 (the one on the official TWRP site) also have this issue? This wouldn't work long term for Android 12+, but would be interesting to see.

I would like to help dig into this but I am a bit busy IRL so time is at a bit of a premium. I will try to help when I can though

SaqinNoor commented 1 month ago

"Does TWRP 3.3.1.0 (the one on the official TWRP site) also have this issue?"

No 😭

"I would like to help dig into this but I am a bit busy IRL so time is at a bit of a premium."

Ah okay no problem, I'll wait patiently.

SaqinNoor commented 1 month ago

I would like to clarify a few things about the phone:

1) Screen and body is original from a Japanese model from the carrier "au". Unsure of the specific model, will have to Google.

2) Replaced the entire logic board a few months ago, with the logic board belonging to a Sprint zeroltespr.

SaqinNoor commented 3 weeks ago

Man you there? I've been waiting for so long to flash A12 but I simply can't because of this issue. I can't wait anymore 😭

fakemanoan commented 3 weeks ago

Still looking into it. Seems like non-working touch is an issue on these devices historically on other AOSP ROMs. Might need some different firmware files/kernel issue. Doing a TWRP refresh soon for Note 5/S6 Edge+, so I'll try again then.

Also its worth noting - even if I fix TWRP and you manage to sideload, I believe Sprint, ATT and Verizon use a Qualcomm modem, whereas other models use Samsungs own Shannon modem, due to CDMA support being better on QC. This is not supported in my ROM, and would require a lot of work to get it functioning properly.

Never say never, but it probably won't get support soon.

SaqinNoor commented 3 weeks ago

Seems like non-working touch is an issue on these devices historically on other AOSP ROMs.

Doing a TWRP refresh soon for Note 5/S6 Edge+, so I'll try again then.

Alright then. Take it easy :-)

Other models use Samsungs own Shannon modem, due to CDMA support being better on QC. This is not supported in my ROM, and would require a lot of work to get it functioning properly.

Shot myself in the foot by doing the logic board replacement. I live in Asia and use GSM, so I never had to bother with CDMA. Do you think the entire modem be broken? Or will only CDMA not work and GSM might?

fakemanoan commented 3 weeks ago

It isnt a question of CDMA vs GSM, rather just getting the modem to work at all. The qualcomm modem and samsung modem are completely incompatible with one another, and since I don't own a QC S6, it wont be easy to get it going. Doesn't look like any developer has released a Qualcomm S6 AOSP ROM either, so idk it probably wont happen any time soon.