Database Develop

Troubleshooting, touch screen not working in TWRP

Hi everyone, so some mistakes have been made today. While playing around with substratum theme engine on my mix running lineage-os 14.1, i had uninstalled one of the themes and then decided to uninstall the app entirely, however after uninstall it didnt reset the theme, so i rebooted. While attempting to reboot it got stuck in a boot loop. At this point I plugged my phone into my pc and booted into twrp so i could access my files and get them off, however when attempting to boot into twrp i could not use the touch screen which is preventing me from re-flashing my rom. and so after troubleshooting for an hour or soi had all my files off of my device, so i decided to format the system partition. so now i have no rom flashed and a twrp that i cannot use due to lack of touchscreen, its temporarily bricked i guess. So my questions are; A. can i use an otg cable and a mouse to control twrp? B. Is there some way to directly flash a rom from adb or from the connected pc. Then I should also state that I have tried older/newer versions of twrp to try to get the touchscreen working, to no avail (currently running 3.1.1-0 lithium). Ive read that it may be touchscreen drivers or something that are mis-matched from the rom. the onlyt issue is that there is no rom, also ive heard that the touchscreen is at a kernel level so i may need to flash a new kernel to get it working. TBH im not going to do anything else so that i dont completely brick my phone. Thank you all in advance for helping out!

Please try this (older) TWRP by MrRaines: https://www.androidfilehost.com/?fid=673368273298927160
It's TWRP 3.0.2-0 based but has different kernel/driver that is more compatible with a varous bunch of ROMs.

You're a god, this is exactly what I needed, thanks!!!

raupe said:
Please try this (older) TWRP by MrRaines: https://www.androidfilehost.com/?fid=673368273298927160
It's TWRP 3.0.2-0 based but has different kernel/driver that is more compatible with a varous bunch of ROMs.
Click to expand...
Click to collapse
I LOVE you, spent hours trying to get recovery working. This was the only fix!
Thank you so much brother.

kanej2006 said:
I LOVE you, spent hours trying to get recovery working. This was the only fix!
Thank you so much brother.
Click to expand...
Click to collapse
Ok glad to read that it works.
Please keep in mind: the TWRP of MrRaines is an older one and is heavily modified.
ATM i'm trying to investigate what's the specific reason other TWRP versions are conflicting with touchscreen drivers on every new release of an stable or dev rom but MrRaines TWRP is still working ^^
The TWRP compatibility case has become even worse with the release of some Android 7.x / Nougat based ROMs - without an official kernel source release for Android 7 by Xiaomi (Android 6 kernel sources should have been released some weeks ago).
Could take a couple of days to find a reason and some more to find a solution...
... any help, tips and confidential information is very welcome @MrRaines @jcadduono

raupe said:
Ok glad to read that it works.
Please keep in mind: the TWRP of MrRaines is an older one and is heavily modified.
ATM i'm trying to investigate what's the specific reason other TWRP versions are conflicting with touchscreen drivers on every new release of an stable or dev rom but MrRaines TWRP is still working ^^
The TWRP compatibility case has become even worse with the release of some Android 7.x / Nougat based ROMs - without an official kernel source release for Android 7 by Xiaomi (Android 6 kernel sources should have been released some weeks ago).
Could take a couple of days to find a reason and some more to find a solution...
... any help, tips and confidential information is very welcome @MrRaines @jcadduono
Click to expand...
Click to collapse
Just see the kernel img, ramdisk and boot files/blobs

raupe said:
Ok glad to read that it works.
Please keep in mind: the TWRP of MrRaines is an older one and is heavily modified.
ATM i'm trying to investigate what's the specific reason other TWRP versions are conflicting with touchscreen drivers on every new release of an stable or dev rom but MrRaines TWRP is still working ^^
The TWRP compatibility case has become even worse with the release of some Android 7.x / Nougat based ROMs - without an official kernel source release for Android 7 by Xiaomi (Android 6 kernel sources should have been released some weeks ago).
Could take a couple of days to find a reason and some more to find a solution...
... any help, tips and confidential information is very welcome @MrRaines @jcadduono
Click to expand...
Click to collapse
Hmmm. I did try two or even three other versions of TWRP. The first two would not even flash giving me an error. The third worked but touch screen would not work. Final attempt was the one from MrRaines which worked perfect!

TWRP 3.2.1-0 not working

Hi Folks...
Got me an Samsumg Galaxy S3 GT-I9305.
I tried to install RR, so first step obviously was getting TWRP 3.2.1-0-i9305.img.tar.
Downloaded over at https://dl.twrp.me/i9305 the said version.
Installed with Odin V3 and everything came up clear but when i tried to boot into recovery i got stuck in Bootlogo
Playing around for a while i decided to install TWRP 3.0.2-1 which worked fine on first try.
Tried to flash the 3.2.1-0-i9305.img via TWRP gave me the error message "File is too big".
Can anyone confirm?

That version is too big for the recovery partition on our device.. Need someone to compress it to make it smaller to fit the partition size of the device.

I have the same problem with the last version TWRP 3.2.1.0.
When I push this one with Odin 3.12, all is sucess but when i reboot the device in custom recovery, it can't, it is stuck

S3 GT-I9305 Specific?
Lexington67 said:
Hi Folks...
Got me an Samsumg Galaxy S3 GT-I9305.
I tried to install RR, so first step obviously was getting TWRP 3.2.1-0-i9305.img.tar...
Click to expand...
Click to collapse
TWRP 3.2.1-0 works great on my S3 i9300, flashed from the external SD card so could you please edit your thread title and add: S3 GT-I9305?
Thanks!

curiousrom said:
TWRP 3.2.1-0 works great on my S3 i9300, flashed from the external SD card so could you please edit your thread title and add: S3 GT-I9305?
Thanks!
Click to expand...
Click to collapse
This thread is in the gt-i9305 help n troubleshooting section btw.. So there's nothing to edit. Correct me if im wrong.

Lexington67 said:
Can anyone confirm?
Click to expand...
Click to collapse
Confirmed also. Unable to use 3.2.1-0 for install/upgrade.
3.0.2-1 works fine, https://dl.twrp.me/i9305/twrp-3.0.2-1-i9305.img.html

Working 3.2.1-0 credit goes to @Option58 the one who compress it. Thank him. Enjoy guys.
https://androidfilehost.com/?fid=817906626617954564

Official TWRP 3.2.1-0 for i9305 Problem Reported to TeamWin TWRP
@Lexington67 @public3n3my @GouLt @mouth
I reported the problem to the TeamWin TWRP so other S3 i9305 users don't waste their time with this version:
Hello, several XDA i9305 users report here
that version TWRP 3.2.1-0 returns error: "File is too big".
https://forum.xda-developers.com/galaxy-s3/help-i9305/twrp-3-2-1-0-t3720311/
https://dl.twrp.me/i9305/
Click to expand...
Click to collapse
And they promptly replied:
Thanks for the report. I have removed it from the download section of twrp.me and disabled future builds until someone can fix the issue.
Click to expand...
Click to collapse
Awesome support from a non-profit open source community project IMO.
***

I'm working on my own TWRP device tree, based on official LineageOS repos, with the intention of getting official support for version 3.2.1-0. I'll create my own thread when my build is ready. According to TWRP's official page for the i9305, there is no current official maintainer.
Edit: I compiled a 3.2.1-0 build and created a separate thread: https://forum.xda-developers.com/galaxy-s3/development-i9305/recovery-twrp-3-2-1-0-t3741413

[Talk/Download] Android 10.0 for Samsung Galaxy S5

Good Morning/Evening ladies and gentlemen, boys and girls, this is a talk of Android 10.0 for Samsung Galaxy S5.
Yes, LineageOS 17 for klte is now here. In testing state.
Just talk, share and star this thread to see the updates.
Updates and download links moved. https://forum.xda-developers.com/ga...-samsung-galaxy-s5-talk-t3965502/post80268759

I hope someone out there could remember our old beloved S5 to work on the Android 10 Rom

And I pretty much hope developers take their time on Android 9 before they jump to 10. Android 8 for S5 is one to skip, because the development stopped to early. Android 9 should be bugfree and with all the good features of before, if possible as smooth as Android 7. Make the foundation solid before going on, so I'm pretty happy that there is no major work on Android 10 for S5 right now. Starting the development in half a year would be more than early enough. Please don't repeat the cycle of Android 8 for S5 ever again, coming up fast and being skipped as fast.

MysteryIII said:
And I pretty much hope developers take their time on Android 9 before they jump to 10. Android 8 for S5 is one to skip, because the development stopped to early. Android 9 should be bugfree and with all the good features of before, if possible as smooth as Android 7. Make the foundation solid before going on, so I'm pretty happy that there is no major work on Android 10 for S5 right now. Starting the development in half a year would be more than early enough. Please don't repeat the cycle of Android 8 for S5 ever again, coming up fast and being skipped as fast.
Click to expand...
Click to collapse
Unfortunately, LineageOS 17 has been out unofficially to some devices. Lucky tho, klte wasn't on the list.

OfficialJohnGL4 said:
Unfortunately, LineageOS 17 has been out unofficially to some devices. Lucky tho, klte wasn't on the list.
Click to expand...
Click to collapse
Android 8 was the one with significant changes that took a lot of time to get working. 9 and 10 are more like 8.2 and 8.3. I wouldn't expect LineageOS 17 to be significantly less stable.
Also, please don't link to that site, OP. It's nothing but clickbait, spam, and fake news.

Couchy said:
Android 8 was the one with significant changes that took a lot of time to get working. 9 and 10 are more like 8.2 and 8.3. I wouldn't expect LineageOS 17 to be significantly less stable.
Also, please don't link to that site, OP. It's nothing but clickbait, spam, and fake news.
Click to expand...
Click to collapse
Actually it isn't. This photo explains it.
If you don't believe me then check it yourself.
(Kind of offtopic) Also in OnePlus 6 forums of XDA LineageOS 17 has been released for it (unofficially).
In conclusion, fake news? Nope.
I also included that it needs to wait. No devs can do it instantly when the development has begun.

Updates on Android 10 ROMs for Samsung Galaxy S5s:
13/9/19: LineageOS 17 is ready for some devices, unofficially, Expect to have LineageOS 17 to be on Samsung Galaxy S5 Soon.
19/9/19: HavocOS just release official Android 10 ROM. The first official Android 10 custom ROM. As S5 is supported. It will happen soon. (A month I think?)
28/10/19: First unofficial LineageOS 17 klte has released.
Android 10 ROMs:
https://www.cyanogenmods.org/download-lineageos-17/#SAMSUNG
(Samsung Galaxy S5 users need to wait)
Raynelfss said:
You can actually boot Note 3's LineageOS 17.1 builds on the S5, reportedly. I tried that yesterday and I can confirm it works. But obviously it has a whole lot of bugs so it is not recommended to do it.
Click to expand...
Click to collapse
https://forum.xda-developers.com/galaxy-note-3/development/rom-lineageos-17-0-t3971019
Couchy said:
Let's make it (un)official:
https://forum.xda-developers.com/galaxy-s5/unified-development/rom-lineageos-17-0-klte-t3992419
Click to expand...
Click to collapse
Android 10 Kernels:
[Empty, I think we should wait a little longer]

@OfficialJohnGL4
you should edit your opening post and put all the information there. :good:
This would be much easier for the people to get all the information about Q for S5
just a suggestion.
regards

j1gga84 said:
@OfficialJohnGL4
you should edit your opening post and put all the information there. :good:
This would be much easier for the people to get all the information about Q for S5
just a suggestion.
regards
Click to expand...
Click to collapse
Thanks, but I am afraid that words limit is the issue, so yeah. If there is not issue, I will edit the text to just "Moved back to top". Thanks.

Reserved
As of now, still waiting for Android 10.
Project Mainline is the reason, which means that ROM developers won't have to update Security Patches if they want to.

You can actually boot Note 3's LineageOS 17 builds on the S5, reportedly. I tried that yesterday and I can confirm it works. But obviously it has a whole lot of bugs so it is not recommended to do it.

Now kind of off topic, but I just open up a thread about Treble for S5, if any devs wanna see it then link here:
https://forum.xda-developers.com/galaxy-s5/general/dev-talk-treble-klte-t3972763

If someone is interested to try the LineageOS GSI image, then here it is for A-only device:
LineageOS 17 A-only GSI: https://github.com/ZJRDroid/firmwar...s/LineageOS-17.0-Aonly-10-20190912-GSI.img.7z
Zygote fix v2: https://www.cyanogenmods.org/downloads/zygotefix-v2-for-android-10/
Permissiver v5: https://www.cyanogenmods.org/downloads/permissiver-v5-for-android-10-gsi/
IMPORTANT:
Backup every partition and keep it in a safe place before making any changes to your phone.
- Extract the above GSI compressed zip file where you will get system.img and vbmeta.img
- Wipe every partition except vendor and internal memory. IMPORTANT: Most likely Galaxy S5 won't have a vendor partition. Even if it has, don't wipe vendor partition.
- Flash the images via TWRP or fastboot utility.
- Once done, boot into TWRP and flash the Permissiver v5 and Zygote fix v2 zip files.
Try to boot and see if you are able to boot into LineageOS 17?
Let me know!

shibaa987 said:
If someone is interested to try the LineageOS GSI image, then here it is for A-only device:
LineageOS 17 A-only GSI: https://github.com/ZJRDroid/firmwar...s/LineageOS-17.0-Aonly-10-20190912-GSI.img.7z
Zygote fix v2: https://www.cyanogenmods.org/downloads/zygotefix-v2-for-android-10/
Permissiver v5: https://www.cyanogenmods.org/downloads/permissiver-v5-for-android-10-gsi/
IMPORTANT:
Backup every partition and keep it in a safe place before making any changes to your phone.
- Extract the above GSI compressed zip file where you will get system.img and vbmeta.img
- Wipe every partition except vendor and internal memory. IMPORTANT: Most likely Galaxy S5 won't have a vendor partition. Even if it has, don't wipe vendor partition.
- Flash the images via TWRP or fastboot utility.
- Once done, boot into TWRP and flash the Permissiver v5 and Zygote fix v2 zip files.
Try to boot and see if you are able to boot into LineageOS 17?
Let me know!
Click to expand...
Click to collapse
SM-G900I
Advanced wiped Dalvik / ART Cashe, System, Data and Cashe.
I did NOT wipe Internal Storage
Attempted to flash image (checked boot partition)
Result was "Size of image is larger than target device"
How does one determine an "A" only device?
Any ideas??

pmduper said:
SM-G900I
Advanced wiped Dalvik / ART Cashe, System, Data and Cashe.
I did NOT wipe Internal Storage
Attempted to flash image (checked boot partition)
Result was "Size of image is larger than target device"
How does one determine an "A" only device?
Any ideas??
Click to expand...
Click to collapse
What were the options you had for installation of IMG.

Samsung Galaxy S5 doesn't have treble yet, at least for now.
Any devs who want to try porting treble to S5 could try to use the GSI, but however no devs wanted to try it.

LokifiedMee said:
What were the options you had for installation of IMG.
Click to expand...
Click to collapse
Boot or recovery option

Raynelfss said:
You can actually boot Note 3's LineageOS 17.1 builds on the S5, reportedly. I tried that yesterday and I can confirm it works. But obviously it has a whole lot of bugs so it is not recommended to do it.
Click to expand...
Click to collapse
how do you do this? I tried and it didn't work maybe I didn't do it right.

ItsMeToby said:
how do you do this? I tried and it didn't work maybe I didn't do it right.
Click to expand...
Click to collapse
You have to use a modified boot.IMG. Also, you need to modify the updater script from the file. But don't worry, you shouldn't even try that.

ItsMeToby said:
how do you do this? I tried and it didn't work maybe I didn't do it right.
Click to expand...
Click to collapse
I also tried but i think you have to fool your recovery a little bit.

General EXYNOS S21 series - TWRP and root

As some of you know s21 source is out, it is possible to build custom recovery and obtain root.
Actually ordinary magisk root method is not working for us: patched boot image does not boot...no old method is working.
I asked a skilled developer, @afaneh92 (he already made custom twrp for galaxy phones in past) to help us but at present he does not have the phone so what he builds is actually tested just by me.
WHAT WE NEED
- many alpha tester (if many people help us we can test things almost intanctaneily)
- some good ideas from other skilled developers
- someone who can make a "BOUNTY" so we can encourage development
I have made a telegram group forstarting this adventure and to share real time our progresses.
https://t.me/joinchat/H7UFBxjpms2aubmO
devs and testers u are welcome!

Work in progress...

Nobody knows how to make a bounty?

Nobody interested?

Im interested just not sure how to help...ive tried everything on sm-996B.. have joined the chat..

any progress?

Samsung Galaxy S21Ultra Exynos stuck on bootscreen (21407) (21408) · Issue #3808 · topjohnwu/Magisk
Hello, I'm on a new Samsung Galaxy S21Ultra (Exynos) FW: G998BXXU1AUAC , which is unrooted but Knox tripped. Its not possible for me to boot the device properly after patching the usual files. Magi...
github.com

Root is near guys!

How come? Any Source?

TWRP working for samsung s21 ultra exynos users
credit - PAUL

How is the process?

I've tried to flash it: error vbmeta - had to flash original recovery.img again to boot the device again

bhammler said:
I've tried to flash it: error vbmeta - had to flash original recovery.img again to boot the device again
Click to expand...
Click to collapse
I think you need to use this:

A600G andriod 11 gsi

Looking for A600G andriod 11 gsi's stable enough please

John072021 said:
Looking for A600G andriod 11 gsi's stable enough please
Click to expand...
Click to collapse
If you're able to install TWRP, you should be able to run any GSI you want.
I have written a guide here but it is your responsibility to know what you are doing.

Read also that thread, there are at least two guides for A600X:
Question about lack of A6 ROMs
After spending a couple of weeks searching for LineageOS for the A6 (not A6+), I've discovered that there's very little support for this device. Why is this?
forum.xda-developers.com

It work thankyo

I'ved been using it for a day now so far so good

Using this guide for a600g
Post in thread 'Question about lack of A6 ROMs' https://forum.xda-developers.com/t/question-about-lack-of-a6-roms.4399123/post-86381773

By the way I used andriod 10
I used twrp 3.6.0 not (3.6.2)not stable and after format data then install fox via twrp and repeated the format data, reboot recovery
And after that I flashed rmm and multi Samsung disabler( tried to boot to Samsung stock but failed)so, I installed gsi by this guide Post in thread 'Question about lack of A6 ROMs' https://forum.xda-developers.com/t/question-about-lack-of-a6-roms.4399123/post-86381773

nqnxev said:
Read also that thread, there are at least two guides for A600X:
Question about lack of A6 ROMs
After spending a couple of weeks searching for LineageOS for the A6 (not A6+), I've discovered that there's very little support for this device. Why is this?
forum.xda-developers.com
Click to expand...
Click to collapse
Hey brother just to ask what os ur using right now?

Lineage 18 r mod when playing games while playing it just freeze and make a sound like its over use how to fix?

John072021 said:
Lineage 18 r mod when playing games while playing it just freeze and make a sound like its over use how to fix?
Click to expand...
Click to collapse
It's hard to say, try maybe flashing different kernel at first, and if it won't help ten play with different GSI's from the list:
Generic System Image (GSI) list
Notes about tinkering with Android Project Treble. Contribute to phhusson/treble_experimentations development by creating an account on GitHub.
github.com
Choose arm32_binder64 vndklite images as always.
John072021 said:
Hey brother just to ask what os ur using right now?
Click to expand...
Click to collapse
Stock + H-Kernel, because I'm using SmartView.

Is it ok to flash andriod 13?

John072021 said:
Is it ok to flash andriod 13?
Click to expand...
Click to collapse
You can try. but don't use old custom recovery, because Android 12+ can cause recovery bootloop. Try with this OrangeFox. Such GSI gives no guarantee of proper work on that A600X vendor.

Brother how to flash H kernel on stock?

John072021 said:
Brother how to flash H kernel on stock?
Click to expand...
Click to collapse
As usual - in custom recovery (flash as boot image).

Working on andriod 10?

Sure, works perfectly.