Touch doesn't work in TWRP, Renovate ROM but work in stock ROM - Samsung Galaxy S8+ Questions & Answers

So I installed Renovate Rom 13.0 three days back and today suddenly the touch stopped working. I had to use my mouse to browse through my phone and found that I lost root in my phone as well. So I guessed this has something to do with the screen being unresponsive.
I uninstalled substratum completely with all the overlays and rebooted my phone and the touch was working fine again. Next, I tried to open the recovery mode from the power menu in order to flash supersu, the did boot into recovery into TWRP instead it booted the system and the touch became unresponsive again.
I decided to reset my phone, tried the button combination to go to the recovery mode, the notification lighted up as blue but it didn't take me to TWRP instead rebooted the system. So I assumed the TWRP was somehow gone/ corrupted or whatever so my only rescue was to flash the stock firmware via Odin. I flashed the stock Oreo firmware and the touch was working again.
Now when I finally thought the problem was fixed and decided to flash TWRP again to root and flash custom ROM, the flashed TWRP and the touch again stopped working in TWRP. Now before doing anything further and trying to figure out whats wrong, I want you guys to help me out with this problem.
This is a really strange problem which I have never encountered with any of the phones I have ever owned.

Related

[Q] Stuck in recovery loop, LG Spectrum

Phone: LG Spectrum
ROM: Cyanogen 10.1 3 or something
CWM: 6.0.4.7
I was in the process of manually installing CWM Touch via Rashr Flash Tool to replace an old 6.0.1.1 non-touch version i had on it before, and when I successfully got it installed, the app asked if I wanted to reboot into recovery. So I pressed yes, and it did.
Unfortunately, it never seemed to remove it afterwards because after every single reboot, it kept going back to recovery, not loading the android OS.
I've tried the following with no success:
Clearing data factory reset
Clearing cache
Clearing Dalvik cache
Full restore to V6 stock
Full restore to Cyanogen (I made a backup when I first got to CWM Touch)
This is the current behavior of my phone:
When powered on, it will display the LG logo, then it will flicker to black and then fade in the LG logo again, 5 seconds later recovery boots. If phone was off and you insert USB cable to charge, the LG logo appears, but the battery mode sort of screen never comes after. Its just stays at the LG logo, and never turns off the display.
It will keep rebooting to recovery no matter if I even tell the recovery to reboot to bootloader.
I don't know exactly how the bootup structure is for androids but the only thing I can think of that may be the issue is the recovery itself if it wasn't the app that caused this. It just doesn't make sense that after a full restore, it would still have an issue, other than the recovery itself, UNLESS there is some secret boot instruction file that's stuck with a "Reboot_to_Recovery = 1" parameter.
Since this thing is stuck in a recovery boot, how would I be able to manually, without OS access, reflash another version of CWM on the device? Or if there's another possible way to fix this, please help me.
Maybe the ROM hasn't flashed on your phone properly .try again with a clean flash. may help
HiT Thank$ If HelPed
I believe this is independent of the ROM. I had noticed in preparing to flash a new ROM that instead of restarting to the OS, it restarted to the recovery. I didn't take much note of this, but it was clear that this problem began when I flashed the new recovery. Also, the fact that I had used 2 seperate, very different restores (full restores) with no success means that it couldn't have been the ROM.
My only probably clue right now is that the recovery is to blame (which is weird since CWM notes 6.0.4.7 as compatible with LG Spectrum. I had 6.0.1.1 before with no issue). I have no idea how to change this recovery however, given that I can't even boot the OS at all, and there doesn't seem to be a "flash recovery' option in recovery (which is kinda annoying).

Wierd Bootloop-Problem when flashing TWRP

Hey Guys,
so i got a wierd bootloop problem and for now i didn't find any solution here on xda or somewhere else,
not even a thread where someone has the same problem.
I'll try to give you as much information as possible in a chronological order.
First of all I got the international model (G920F).
So like 2-3 months ago everything was fine, my phone was rooted, got TWRP working and was flashing Roms with no problem what so ever. TW-Roms like Noble Rom and also AOSP/Lineage OS.
One day I wanted to flash UltImAtE NoUgAt A8 Port and that is where the trouble began, dont think it has something to do with the rom but maybe it helps.
So i flashed the Rom(wiped everything except int. storage), flashing was no problem but it didnt boot.
I know first boot always takes some time but after about 20-30 min I forced a reboot (Power+Vol. Down for 7sec).
After that the phone got into a Bootloop(always rebooted into the "first bootingscreen")
I let this process happen for about 15 min. and then tried to enter TWRP via hitting the buttons between the boots which didn't work. I then did "force" a reboot(Power + Vol. Down) which strangely resulted in one final reboot and turning the phone off after the first bootscreen.
So with the phone finally turned off I was able to boot into TWRP and reflashed the rom but the result was the same.
I did the same procedure again to get into TWRP and flashed the Stock Deodexed TW Rom, flashing worked but then the Phone directly rebooted into TWRP. Rebooting out of TWRP or booting the phone from beeing shut down both resulting into booting to TWRP.
So to get my Phone working again I had to flash stock ROM which in my case is G920FXXU5EQDF_G920FDBT5EQD1_G920FXXU5EQCD via Odin.
That worked but of course root and TWRP were gone so I then flashed TWRP via Odin(both newest Versions at that point)
aaaaaand phone straightly booted into TWRP again all the time. I tried different combinations of older versions of both twrp and odin but the result always was the same.
So at the moment I am on Stock, the phone works which is nice but i really wanna get TWRP working again and i have no idea what to do.
I hope someone can help me with that.
Cheers Guys
MuTec said:
Hey Guys,
so i got a wierd bootloop problem and for now i didn't find any solution here on xda or somewhere else,
not even a thread where someone has the same problem.
I'll try to give you as much information as possible in a chronological order.
First of all I got the international model (G920F).
So like 2-3 months ago everything was fine, my phone was rooted, got TWRP working and was flashing Roms with no problem what so ever. TW-Roms like Noble Rom and also AOSP/Lineage OS.
One day I wanted to flash UltImAtE NoUgAt A8 Port and that is where the trouble began, dont think it has something to do with the rom but maybe it helps.
So i flashed the Rom(wiped everything except int. storage), flashing was no problem but it didnt boot.
I know first boot always takes some time but after about 20-30 min I forced a reboot (Power+Vol. Down for 7sec).
After that the phone got into a Bootloop(always rebooted into the "first bootingscreen")
I let this process happen for about 15 min. and then tried to enter TWRP via hitting the buttons between the boots which didn't work. I then did "force" a reboot(Power + Vol. Down) which strangely resulted in one final reboot and turning the phone off after the first bootscreen.
So with the phone finally turned off I was able to boot into TWRP and reflashed the rom but the result was the same.
I did the same procedure again to get into TWRP and flashed the Stock Deodexed TW Rom, flashing worked but then the Phone directly rebooted into TWRP. Rebooting out of TWRP or booting the phone from beeing shut down both resulting into booting to TWRP.
So to get my Phone working again I had to flash stock ROM which in my case is G920FXXU5EQDF_G920FDBT5EQD1_G920FXXU5EQCD via Odin.
That worked but of course root and TWRP were gone so I then flashed TWRP via Odin(both newest Versions at that point)
aaaaaand phone straightly booted into TWRP again all the time. I tried different combinations of older versions of both twrp and odin but the result always was the same.
So at the moment I am on Stock, the phone works which is nice but i really wanna get TWRP working again and i have no idea what to do.
I hope someone can help me with that.
Cheers Guys
Click to expand...
Click to collapse
You do know that if you flash TWRP, you need to use a kernel that has dm-verity disabled or you need to be rooted. Flash TWRP then Flash Magisk through TWRP
U99Dev said:
You do know that if you flash TWRP, you need to use a kernel that has dm-verity disabled or you need to be rooted. Flash TWRP then Flash Magisk through TWRP
Click to expand...
Click to collapse
As it seems I did not, good thing that its written right at the TWRP download page...
Can't remember doing this when I installed TWRP first but as it seems I did.
Everything is working fine, just flashed Nexus OS and it booted.
Thank you so much dude

Phone bootloops only if Magisk is not installed

Hey, I recently got my Poco X3 NFC. I unlocked the bootloader, flashed a custom ROM and recovery, everything seemed fine. After installing Magisk (flashing the new "apk") from TWRP recovery, everything went fine too. Later I decided to switch to another ROM and I did a FULL wipe of pretty much everything except the stuff necessary to run the phone. I then flashed the new ROM and it got stuck at the yellow POCO screen, powered by Android and the padlock. I then rebooted back to TWRP and flashed the apk again, the phone booted with no problems whatsoever. The "Uninstall Magisk" button in the manager was completely broken, complete uninstall did nothing. I decided to uninstall it again from TWRP using the apk and renaming it to uninstall.zip. It successfully uninstalled, and after booting the same thing happened. Just stuck at the POCO screen. Then I flashed Magisk again, and it booted fine. I can't get my phone Magisk-free without it bootlooping. I tried flashing the stock boot.img, the ROM's boot.img, pretty much everything and nothing worked. Anyone knows what's happening?
same problem with samsung galaxy s8, and now it got worse on me after trying new rom, now my phone is stuck at recovery and doesn't work at all even the samsung repair center said the motherboard should be REPLACED, so I would recommend that you choose the most stable rom and keep it and stop changing your phone software or it will ne soft bricked like mine !
Alright, thanks. I guess I'll just keep the current ROM with Magisk. It'd be nice to have a phone booting without it though.

Lenovo Tab 4 10 plus 30 second boot loop

How can in get out of this boot loop, any advice, answers, help appreciated?
As background my Lenovo Tab 4 10 plus (stock 7.1 rom) had a failed SD card so I replaced the card and factory reset and thought I would try TWRP, Linageos 17.1 with magisk and relevent gapps - this all worked fine other than a Skype issue. I then found an 18.1 rom and tried that and this is where it seems to have gone wrong I set it up in the same ways as the 17.1 rom but with Andriod 11 gapps to suit, did a factory reset and 30 seocnds in I got the boot loop.
To fix it I tried going back to the 17.1 rom set-up that had worked but this then boot looped even with a full recovery reset. I have gone back to the stock rom backup in TWRP again with a recovery reset same boot loop. I have even used the Lenovo recovery tool to EDL mode flash a newly downloaded stock rom and it's still boot looping. I can only think that the 18.1 andriod 11 rom changed something fundimental but I can't find what?
Further I have another problem, the EDL flash worked but it locked the bootloader, however as I can't get in to Andriod with the boot loops, I can't switch ADB mode on so I can't unlock the bootloader to get TWRP up again.
So is there a way to start ADB without access to develeoper settings maybe through fastboot or recovery which I can get in to? Unlock the bootloader without ADB? Does anyone know why after the 18.1 Andriod 11 based rom, I have this continous boot loop?
I have a tb-x704f wich was totally caught in a boot loop, but I manisched to get back to working stock.
I was running firmware s000056 when I flashed twrp without backing up anything. I thought I never would have to go back to nougat, but standby time on lineage os was just not good for me, as I only use my tablet maybe half an hour a day, and I had to charge several times a week nevertheless.
So I tried to get back to stock and awesome standby time.
It was not easy bootloop after bootloop.
Tried Lenovo rescue and smart assistant multiple times, factory reset before and after flash, without SD card inserted etc, but bootloop.
Tried flashing the rom downloaded from the rescue tool with qfil but same result.
I then tried flashing the files with miflash 2016.08.30.0 still the same rom as I thought it had to be s000056. Miflash stopped halfway with some kind of error.
I then downloaded a stock rom from lenovo-forums.ru http://lenovo-forums.ru/topic/24135-lenovo-tab4-a10-plus-proshivka-tb-x704f_s000037_170703_row_qfil/
from the link in the discussion in the bottom of the site.
I had twrp still so from there I got into terminal and wrote "reboot edl" to get into emergency download mode and then flashed away. I presume that I could just as well had gotten in to edl mode by pressing vol+ and vol- simultaneously and then connected to PC holding those to buttons pressed. When the tablet was finished it was off, so I started going to recovery and wipeed cache and did a factory reset. Then booted and instead of bootloop it showed the Lenovo screen with a progress bar underneath. I successfully booted and took a update and then i am back to stock s000056.
The rom I got from lenovo-forums.ru stated it was only for EU and wi-fi model only. I am in Denmark and my tablet is WiFi only.
I think chances for success is greater using miflash than other tools when recovering from bootloop, but then again I don't know. Maybe I could just have flashed the s000037 rom with qfil or maybe I was just lucky, who knows.
But this what worked for me.
I hope this can help someone as I could not with the help of god find any useful help regarding this problem.
pallep said:
I hope this can help someone as I could not with the help of god find any useful help regarding this problem.
Click to expand...
Click to collapse
Thanks kind man You helped finish my struggle!
The only thing I want to add is that the ROM from the original link is no longer available, so I found the correct ROM using Google from the original filename here https://firmware247.com/lenovo-tab4-a10-plus-tb-x704f-firmware/

TWRP crashing, stuck in recovery bootloop

For the last couple years I've been following this process to retain root using the TWRP A/B Retention Script and installing Magisk to the inactive slot after OTA and everything been fine and dandy. However, after the last time I performed this process Magisk would immediately crash when I tried to launch its app. Upon investigating I noticed that the file it downloaded for flashing was suspiciously small, so I suspect it flashed a corrupted file. I had already successfully rebooted my phone several times after the OTA, so I figured it was just Magisk that got corrupted and TWRP must be fine. I recently tried to reboot into recovery and discovered that TWRP is broken too. My phone briefly flashes the TWRP logo before the screen goes black and it tries to reboot into recovery again.
I've been able to get into fastboot by simultaneously holding down the power button and both volume buttons. However, none of the options in fastboot actually get my anywhere. Choosing start, recovery mode, or power off just get me back into the TWRP bootloop, and restart bootloader obviously just keeps me in fastboot.
I assume I need to reflash TWRP and Magisk, but I'm not sure how to go about that. Can someone point me in the right direction? Thanks.
This is how I proceeded:
Downloaded the latest TWRP image (twrp-3.6.2_11-0-guacamole.img) from here: https://dl.twrp.me/guacamole/
Verified the md5sum to ensure the download wasn't corrupted.
fastboot boot twrp-3.6.2_11-0-guacamole.img
In TWRP, Advanced > Flash Current TWRP
Now I have a working recovery, but I still can't boot into my system. When I go to Reboot > System in TWRP it just boots back into recovery.
I enabled MTP in TWRP and copied off all the data I cared about, then used the "Flash Factory Images" option in the TOOL ALL IN ONE to flash 9.5.13-GM21AA-OnePlus7ProOxygen_21.O.16_OTA_016_all_1908281716_b2bb5-FASTBOOT.zip. I tried it without checking the box to erase everything, hoping I could keep my data, but that didn't work. With that box checked though I was able to boot again, but I cannot turn on WiFi for some reason. I'm hoping the OTA will fix that issue. Does anyone know how to get WiFi working again or why it may have stopped working?
altayh said:
I cannot turn on WiFi for some reason. I'm hoping the OTA will fix that issue.
Click to expand...
Click to collapse
Fortunately enough the first OTA did indeed solve the WiFi issue. Now I've applied all of the OTAs and finally have my phone in a proper working state again.

Categories

Resources