Database Users

[Q] Stuck in recovery boot loop...?

While using the PA Updater app to upgrade my rom, the app attempted to reboot into recovery to run an openrecovery script. While doing this, I believe it set my "reboot mode flag" to recovery.
The tablet boots with the Google screen and then shows the TWRP splash (I'm on version 2.6.0.0), then it reboots and starts again.
I am able to get to the bootloader, but even if I press start or recovery mode it reenters the boot loop trying to get into recovery. In the bootloader was where I saw the reboot mode flag set to recovery. Is there a way to use fastboot to remove that or am I just going to have to do a wipe with fastboot?

It happened to me once. I pushed the power button for 60 seconds as it supposed to do a kind of battery pull, and it worked.

HunterOrHunted said:
While using the PA Updater app to upgrade my rom, the app attempted to reboot into recovery to run an openrecovery script. While doing this, I believe it set my "reboot mode flag" to recovery.
The tablet boots with the Google screen and then shows the TWRP splash (I'm on version 2.6.0.0), then it reboots and starts again.
I am able to get to the bootloader, but even if I press start or recovery mode it reenters the boot loop trying to get into recovery. In the bootloader was where I saw the reboot mode flag set to recovery. Is there a way to use fastboot to remove that or am I just going to have to do a wipe with fastboot?
Click to expand...
Click to collapse
same thing just happened to me... tried Factory Reset and TWRP ran an Open Recovery Script and boom... boot loop... TWRP screen pops up and then goes to loop...
tried pressing powerbutton but no use...
any workaround for this???

Lordificated said:
same thing just happened to me... tried Factory Reset and TWRP ran an Open Recovery Script and boom... boot loop... TWRP screen pops up and then goes to loop...
tried pressing powerbutton but no use...
any workaround for this???
Click to expand...
Click to collapse
I've done this twice to my nexus now and I think I found a reliable way to restore to running condition. YMMV
1)Boot the nexus into fastboot (power and both volume keys) when you power up.
2)Attach your usb cable from the PC (or MAC I guess, dont have one to try)
3)start WUG Nexxus Root Toolkit. 'Launch' advanced utilities.
4)Test your fastboot with Quick tools. check the button at Fastboot-Bootloader and click 'List Devices' if the box that pops up is empty then fastboot isn't working (I can't help you there and it must be working to continue).
5)If fastboot shows a device then go to "Boot Temporary" and click 'Custom Recovery'.
6)I selected 'Touch TWRP' but CMW may work as well. This will reboot you into (temp)TWRP and from there you can force a reboot that will reset the 'Recovery' flag that has locked your bootloader.
7)Give it a few minutes (be patient for 5 minutes) and hopefully you reboot to where you were prior to this mess.
Long time lurker and couldn't fix my fails without everyone here.
Thanks to all.
Bill

HunterOrHunted said:
While using the PA Updater app to upgrade my rom, the app attempted to reboot into recovery to run an openrecovery script. While doing this, I believe it set my "reboot mode flag" to recovery.
The tablet boots with the Google screen and then shows the TWRP splash (I'm on version 2.6.0.0), then it reboots and starts again.
I am able to get to the bootloader, but even if I press start or recovery mode it reenters the boot loop trying to get into recovery. In the bootloader was where I saw the reboot mode flag set to recovery. Is there a way to use fastboot to remove that or am I just going to have to do a wipe with fastboot?
Click to expand...
Click to collapse
I had the same thing happen to me (though i updated from stock 4.4 to 4.4.2 [and i had twrp installed]). I tried reflashing to stock recovery and a few other things but same problem, it kept booting me into stock recovery. I know this is going to sound crazy, even stupid, but just letting it sit there for 5 minutes (at the stock recovery screen) let it work... I was searching for more things to try and it just started booting.... Checking the bootloader again showed the reboot mode flag set to none.

zeroedout420 said:
I had the same thing happen to me (though i updated from stock 4.4 to 4.4.2 [and i had twrp installed]). I tried reflashing to stock recovery and a few other things but same problem, it kept booting me into stock recovery. I know this is going to sound crazy, even stupid, but just letting it sit there for 5 minutes (at the stock recovery screen) let it work... I was searching for more things to try and it just started booting.... Checking the bootloader again showed the reboot mode flag set to none.
Click to expand...
Click to collapse
I guess mine worked because I was still on stock bootloader and adding TWRP was an important key but the 5 minutes seems to be the solution after all the rest.

recovery boot loop:- Is coz, one of your partitions would be facing problems while mounting.. So Wipe the Partition and Format it with Ext-2 file format. and reboot the Mobile. Then it'll stops rebooting.

Do you have a Samsung device?
Be warned - there is no such thing as fastboot mode for most Samsung Galaxy devices - you'll be wasting your time doing this and typing "fastboot devices" for many hours!
If you have problems with your recovery, it works to just reflash the CF-autoroot kit, which happens to flash the cache partition too. My problem was similar to the OP's - a bootloop with TWRP's obviously buggy OpenRecoveryScript, which was installing a ZIP file over and over again.
If you flash the CF-autoroot specific to your device, TWRP will be gone, but the phone will boot normally again - with all your data on it - hooray!
Then you install TWRP or CWM recovery as you did originally.
Stay away from OpenRecoveryScripts! I'll be installing a ZIP file in the traditional, manual way from now on, from an external SD card so I can remove the card if I get another TWRP boot loop.

carltasmania said:
Be warned - there is no such thing as fastboot mode for most Samsung Galaxy devices - you'll be wasting your time doing this and typing "fastboot devices" for many hours!
If you have problems with your recovery, it works to just reflash the CF-autoroot kit, which happens to flash the cache partition too. My problem was similar to the OP's - a bootloop with TWRP's obviously buggy OpenRecoveryScript, which was installing a ZIP file over and over again.
If you flash the CF-autoroot specific to your device, TWRP will be gone, but the phone will boot normally again - with all your data on it - hooray!
Then you install TWRP or CWM recovery as you did originally.
Stay away from OpenRecoveryScripts! I'll be installing a ZIP file in the traditional, manual way from now on, from an external SD card so I can remove the card if I get another TWRP boot loop.
Click to expand...
Click to collapse
How do you install cf-autoroot when stuck in a boot loop with samsung galaxy S device if there is no fastboot?

My phone is stuck in bootloop too. It shows Twrp at the starting and then restarts. What am i supposed to do? I need help ASAP please

[Q] Trouble installing recovery via Odin

Hi all. Could use some help. Not sure which step I am missing. I followed the Philz Touch instructions below and flashed the MD5 recovery package with Odin. First with the "Auto Reboot" option ticked, then without. Odin says successful but I can't seem to get it to boot into recovery. Am I using the wrong three buttons? When I tried it just came up the battery charging logo.
Should I not have "F. Reset Time" ticked?
boot into download mode
start odin3 and configure it as in picture below
connect phone in download mode to PC via USB
press start to flash the tar.md5 package
normally, phone should auto-reboot into recovery.
If it reboots into main system and your recovery remains stock, repeat above steps and untick "autoreboot" in odin. Once flash is done, keep pressing the 3 buttons combo to for a reboot into recovery.You should see the new CWM
when in recovery, if you choose option "reboot system now" and you get "yes - disable flash recovery", select that option to avoid stock recovery overwriting cwm

Anyone? Can someone simply verify the 3-button reboot sequence?
I have a newly rooted Sprint GS4 which I updated to MF9 before rooting. I used Odin 1.85 to root it. I am now looking to install a custom recovery and kernel and eventually experiment with some different ROMs. I decided to go with the PHILZ Touch CWM based recovery and flashed the correct tar.md5 file based on his instructions listed here... http://forum.xda-developers.com/showpost.php?p=39433857&postcount=4. However, I am running into the issues that he addresses regarding the phone auto-rebooting back into the main system and not into the newly installed recovery. I did as he said and un-checked the "auto reboot" option and tried again a couple times. Once it seemed to get stuck on the downloading screen when i unplugged the device after successful install via Odin, then I tried the same leaving the phone plugged into the computer and it seemed to get stuck on the battery charging logo. I am deftly afraid of bricking this thing so I was hoping someone who's done this can explain exactly which step I am missing. Thanks very much and thanks for the noob thread.

jbb2388 said:
Anyone? Can someone simply verify the 3-button reboot sequence?
Click to expand...
Click to collapse
With the phone powered off, press and hold the power and volume up buttons, and when the phone vibrates, release the power button but not the volume button. You should get a screen saying booting recovery, followed by the recovery ROM.

angiest said:
With the phone powered off, press and hold the power and volume up buttons, and when the phone vibrates, release the power button but not the volume button. You should get a screen saying booting recovery, followed by the recovery ROM.
Click to expand...
Click to collapse
Geez, I thought I had tried that multiple times but it just worked finally!!! Thanks angie! Finally into the recovery and performing a nandroid backup as we speak.

Samsung Galaxy S5 SM-G900F 5.0 stuck during root

This is not the first time i root an android device but it is the first time im doing it on an S5, nonetheless I am pretty much stuck right now.
I tried to install CF-Auto-Root-klte-kltexx-smg900f.tar using Odin from here, it installed with no problems, but when the phone restarted I get:
RECOVERY BOOTING
RECOVERY IS NOT SEANDROID ENFORCING
Set Warranty Bit: recovery
and then it shuts down.
I tried to enter recovery mode by doing power+vol up+menu but nothing happens ?
Can anyone help ?
EDIT: ok, so I did manage to get it running again by flashing openrecovery-twrp-2.8.5.0-gt-klte. This got me past the "Recovery is not seandroid...", but all in all I still didn't manage to get root access...

I passed through a similar situation , all u have to do once u've got the recovery is get the SuperSU flashable zip and flash it and ur done
Here is a direct link : https://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip?retrieve_file=1

This happened to me also. I am running XXU1BOJ1 . I flashed twrp-2.8.7.0-klte.img and even though it solved getting stuck at recovery, my phone still boots into the standard recovery instead of TWRP when pressing VOLUP+Home+Power. Anyone got ideas?

xmun said:
This happened to me also. I am running XXU1BOJ1 . I flashed twrp-2.8.7.0-klte.img and even though it solved getting stuck at recovery, my phone still boots into the standard recovery instead of TWRP when pressing VOLUP+Home+Power. Anyone got ideas?
Click to expand...
Click to collapse
You don't flash .img - you flash .tar

*Detection* said:
You don't flash .img - you flash .tar
Click to expand...
Click to collapse
I did flash .img.tar actually. Still no effect - boots to regular recovery. Can't figure this out...

i get in the same situation...why still rebooting in original recovery?
i installed this one CF-Auto-Root-klte-kltexx-smg900f.tar with odin with succes but still have
RECOVERY BOOTING
RECOVERY IS NOT SEANDROID ENFORCING
Set Warranty Bit: recovery
then when i boot i get a black screen with all application error....the only way to get it back working was to wipe factory reset in original recovery.
what can i do to get it working so i can install custom roms?
thx in avance

seaskyways said:
I passed through a similar situation , all u have to do once u've got the recovery is get the SuperSU flashable zip and flash it and ur done
Here is a direct link : https://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip?retrieve_file=1
Click to expand...
Click to collapse
I can't seem to get the coustom recovery installed, and after some digging i found this :
manubhargav said:
Actually the problem was that custom recovery(twrp here) was not installed at all, that above mentioned error occurs when you try to install SuperSU.zip from stock recovery<3e>.
This happens because when you flash custom recovery from Odin and allow it to reboot on its own, Samsung's recovery checking script checks if a custom recovery is present and overrides.
To bypass that check you need to take your battery out as soon as the recovery is flashed by Odin ( and before the phone reboots).
As soon as the Odin says PASS you should be ready to take out the battery which will stop it from rebooting,
put back the battery and enter recovery mode directly by pressing and holding Volume Up, Home and Power keys at the same time.
Release all three buttons when Samsung Galaxy S5 screen flickers and the main screen of Recovery mode appears.
This will avoid script checking and will let you to custom recovery directly,there you can install SuperSU or any other zip.
Click to expand...
Click to collapse
The thing is, when i try to do that, and then get into recovery i get
Could not do normal boot.
ODIN MODE.
Any help ? Please ? The bloatware is driving me nuts :crying:

VL4DST3R said:
I can't seem to get the coustom recovery installed, and after some digging i found this :
The thing is, when i try to do that, and then get into recovery i get
Could not do normal boot.
ODIN MODE.
Any help ? Please ? The bloatware is driving me nuts :crying:
Click to expand...
Click to collapse
Maybe your phone is not recognized in Download Mode as corresponding drivers may not be properly installed. So Computer is not able to recognize the phone when in Downlaod mode. Install SM Bus Controllers drivers from Intel from Official driver source.
After setting-up you'll be able to flash TWRP and boot into recovery mode.
---------- Post added at 05:36 AM ---------- Previous post was at 05:32 AM ----------
xmun said:
This happened to me also. I am running XXU1BOJ1 . I flashed twrp-2.8.7.0-klte.img and even though it solved getting stuck at recovery, my phone still boots into the standard recovery instead of TWRP when pressing VOLUP+Home+Power. Anyone got ideas?
Click to expand...
Click to collapse
Actually the problem of custom recovery (TWRPhere) not installed at all, stock recovery<3e> persists after reboot because when you flash custom recovery from Odin and allow it to reboot on its own, Samsung's recovery checking script checks if a custom recovery is present and overrides.
To bypass that check you need to take your battery out as soon as the recovery is flashed by Odin ( and before the phone reboots).
As soon as the Odin says PASS you should be ready to take out the battery which will stop it from rebooting,
Put back the battery and enter recovery mode directly by pressing and holding Volume Up, Home and Power keys at the same time.
Release all three buttons when Samsung Galaxy S5 screen flickers and the main screen of Recovery mode appears.
This will avoid script checking and will let you to custom recovery directly,there you can install SuperSU or any other zip.

manubhargav said:
Maybe your phone is not recognized in Download Mode as corresponding drivers may not be properly installed. So Computer is not able to recognize the phone when in Downlaod mode. Install SM Bus Controllers drivers from Intel from Official driver source.
After setting-up you'll be able to flash TWRP and boot into recovery mode.
Actually the problem of custom recovery (TWRPhere) not installed at all, stock recovery<3e> persists after reboot because when you flash custom recovery from Odin and allow it to reboot on its own, Samsung's recovery checking script checks if a custom recovery is present and overrides.
To bypass that check you need to take your battery out as soon as the recovery is flashed by Odin ( and before the phone reboots).
As soon as the Odin says PASS you should be ready to take out the battery which will stop it from rebooting,
Put back the battery and enter recovery mode directly by pressing and holding Volume Up, Home and Power keys at the same time.
Release all three buttons when Samsung Galaxy S5 screen flickers and the main screen of Recovery mode appears.
This will avoid script checking and will let you to custom recovery directly,there you can install SuperSU or any other zip.
Click to expand...
Click to collapse
The drivers are installed, and Odin sees my phone just fine, also the thing with removing the battery before it restats leads me to the error i mentioned above...

VL4DST3R said:
The drivers are installed, and Odin sees my phone just fine, also the thing with removing the battery before it restats leads me to the error i mentioned above...
Click to expand...
Click to collapse
Ah, So the problem you're facing is NOT getting into recovery mode
There are 2 ways to solve the problem, (1st -> flashing recovery.tar again, 2nd-> flashing stock firmware)
First method:
Enter "Download Mode" by holding down "Volume Down"+ "Home" + "Power" button.
Flash recovery.img again and check if it boots into recovery this time.
Sometimes this may not work and you may need to try flashing firmware
Second method:
Download Firmware from here
Open odin in your PC
Enter "Download mode"
Connect the device to PC using USB
Flash the PDA, BL, AP, CSC etc.
Alternatively, You can flash the firmware using SmartSwitch

manubhargav said:
Ah, So the problem you're facing is NOT getting into recovery mode
Click to expand...
Click to collapse
Oh but it is! That's exactly my problem. Look, here are the 3 outcomes I get regarding the whole recovery menu thing:
Go into the default recovery menu - cant install SuperSU but at least it works.
Install twrp and remove the battery after it finishes transfering and wants to restart, at which point when I go into recovery I get the above error (Could not do normal boot. ODIN MODE.)
Install twrp and let it restart by itself and after it is done, go into recovery only to find it is back to the default one.

VL4DST3R said:
Oh but it is! That's exactly my problem. Look, here are the 3 outcomes I get regarding the whole recovery menu thing:
Go into the default recovery menu - cant install SuperSU but at least it works.
Install twrp and remove the battery after it finishes transfering and wants to restart, at which point when I go into recovery I get the above error (Could not do normal boot. ODIN MODE.)
Install twrp and let it restart by itself and after it is done, go into recovery only to find it is back to the default one.
Click to expand...
Click to collapse
Which Kernel version are you in? Which TWRP version did you try? Install other custom recoveries? On locked bootloader?

Ok, I tried CWM and nothing changed, i get the default recovery menu...
Doing the shut down before it restarts gets me "recovery is not seandorid enforcing"

VL4DST3R said:
Ok, I tried CWM and nothing changed, i get the default recovery menu...
Doing the shut down before it restarts gets me "recovery is not seandorid enforcing"
Click to expand...
Click to collapse
Turn OFF Auto-Reboot option in ODIN and flash the recovery.tar and remove battery and directly boot into recovery mode.
Go into a working custom recovery (CWM or TWRP) and flash SuperSU.zip from the recovery and reboot with ("Fix permissions" if there is such an option, otherwise simply reboot).

manubhargav said:
Turn OFF Auto-Reboot option in ODIN and flash the recovery.tar and remove battery and directly boot into recovery mode.
Go into a working custom recovery (CWM or TWRP) and flash SuperSU.zip from the recovery and reboot with ("Fix permissions" if there is such an option, otherwise simply reboot).
Click to expand...
Click to collapse
Tried that already, and as I said, I can't get a custom recovery working, it either resets to the default one or I get the "recovery is not seandorid enforcing" error.

VL4DST3R said:
Tried that already, and as I said, I can't get a custom recovery working, it either resets to the default one or I get the "recovery is not seandorid enforcing" error.
Click to expand...
Click to collapse
1)
Ah use latest twrp 2.8.70
Ah use latest supersu beta 2.52
Quick download cm12.1 nightly and flash it.
Boot Rom and go into settings/aboutphone/ click build number rapidly.
Developer settings should appear, then go into developers options/ click on "root access" and enable it.
---- now test if its working . however....
2)
If its not working, take yourself back into twrp and flash that supersu beta.
----now test again. However ....
3)
If it doesn't work again .
go back to stock 5.0 rom>>> put twrp on >>> and flash DAT supersu .
now test ya rom again. However.........
4)
If it dont work again ..
go back to stock 4.4 rom>>> put twrp on>>> and flash a random supersu.
now test ya rom again. However.....
5)
if that doesn't work again,
Go back to stock rom through (odin) and restart the process from the top .
btw the "recovery is not seandorid enforcing" is normal . not an error.

GeniusisHere said:
1)
Ah use latest twrp 2.8.70
Ah use latest supersu beta 2.52
Quick download cm12.1 nightly and flash it.
---- now test if its working . however....
2)
----now test again. However ....
3)
If it doesn't work again .
now test ya rom again. However.........
4)
If it dont work again ..
now test ya rom again. However.....
5)
if that doesn't work again, .
Click to expand...
Click to collapse
First of all holy **** what an answer... let's SLOW DOWN a bit first, shall we ?
Secondly you lost me from step 1, I don't want CyanogenMod, I want the default Samsung 5.0 with TouchWiz (contrary to popular belief I actually like it).
Also I would really like to know (from someone that actually knows why this happens) why is it reverting to default recovery and how can I stop it from doing so ? manubhargav had an interesting idea, but sadly it doesn't work for everyone (as someone else mentioned on that other post)

So I'm guessing no one knows the answer to my problem considering almost a moth has passed...

I know that in kitkat the answer was to turn off / disable 'Reactivation Lock' (located under settings>>security and unchecking the box)........
I had heard that Samsung had removed that option in lollipop, but it might be worth checking......it has/had to be disabled BEFORE attempting to flash anything......
http://i.imgur.com/rVnFwJM.jpg

keithross39 said:
I know that in kitkat the answer was to turn off / disable 'Reactivation Lock' (located under settings>>security and unchecking the box)........
I had heard that Samsung had removed that option in lollipop, but it might be worth checking......it has/had to be disabled BEFORE attempting to flash anything......
http://i.imgur.com/rVnFwJM.jpg
Click to expand...
Click to collapse
RL is still there with LP too

Trouble flashing TWRP

Hi, everyone.
I have a galaxy s8 SM-G950FD. I have once flashed TWRP and rooted the device successfully.
Then I tried to install a custom ROM but I got bootloop.
After that, I flash official ROM to unbrick my device. But since then, whenever I tried to flash TWRP again I got this message "Verification failed unable to restart your device the integrity verification has failed. You need to reset your device to factory default settings. This will erase all your data."
My device is still working fine but I want to try to flash a new ROM (even if I may brick my device forever). I don't know what to do. Can you guys give me some advice ?
Thank you!

It's quite a simple fix I think: You need to make a backup of the Data partition and then do a wipe using TWRP. This happens because TWRP cannot handle Samsung's Encryption; the only way to bypass this problem is by formatting once again.

MikeTheTechSavvy said:
It's quite a simple fix I think: You need to make a backup of the Data partition and then do a wipe using TWRP. This happens because TWRP cannot handle Samsung's Encryption; the only way to bypass this problem is by formatting once again.
Click to expand...
Click to collapse
But I cannot boot into TWRP. How can I do that ?

If you're stuck in the bootloop you should press the force reboot key combination: Power Down + Home + Power. After the device restarts switch the Volume Down key for the Volume Up key right after the screen goes blank. That should get you into TWRP (if it's correctly installed), otherwise directly into the stock recovery.

MikeTheTechSavvy said:
It's quite a simple fix I think: You need to make a backup of the Data partition and then do a wipe using TWRP. This happens because TWRP cannot handle Samsung's Encryption; the only way to bypass this problem is by formatting once again.
Click to expand...
Click to collapse
MikeTheTechSavvy said:
If you're stuck in the bootloop you should press the force reboot key combination: Power Down + Home + Power. After the device restarts switch the Volume Down key for the Volume Up key right after the screen goes blank. That should get you into TWRP (if it's correctly installed), otherwise directly into the stock recovery.
Click to expand...
Click to collapse
I cant flash/get into TWRP. I tried to boot into stock recovery and do a system wipe/factory reset. Then I flash TWRP again but nothing seem to happen. I tried to boot into recovery and it get me to the stock recovery not TWRP.I did unlock OEM, used Odinv3.12, twrp-3.1.1-2-dreamlte.img.tar.

I had the same issue.
After Odin has flashed the Recovery it performs an auto reboot (if checked in Odin). So at this reboot hold Vol up + Home + Power as soon the screen goes of. You need to be quick. Then it should boot into TWRP.

True, Samsung's stock recovery is very persistent lately and if you tick the auto-reboot you have to be very fast in switching to Recovery mode combo.
Otherwise you can choose not to tick auto-reboot, force restart the device after the TWRP flashing was successful and immediately switch to the Recovery combo.
Here you go: two ways of doing this.

Samsung J7 Pro Soft Brick after Oreo 8.1 update (no root)

Hi everyone...
Two days ago, and a few hours after installing the 8.1 update, my mom's J7 touchscreen was unresponsive, including the power button. It ran out of battery, and after I restarted it this morning, it goes to recovery mode after it tries installing system update and the No command screen is displayed.
I've searched on the web for hours and hours for solutions but none of them have worked, most probably because it requires the phone to be connected to the PC, and my PC (Windows 10) isn't even seeing the phone via USB (can't use ODIN nor ADB). BTW, the debug option most probably wasn't turned on prior to soft brick.
Phone Info:
SM-J730G J730GDXS5BRK1
No root
Error on recovery screen (the SD card has been taken out):
======================================
#fail to open recovery_cause(No such file or directory)#
#Reboot Recovery Cause is [UNKNOWN]#
No Support SINGLE-SKU
File-Based OTA
Supported API: 3
E:unknown volume for path [/odm]
E:unknown volume for path [/vendor]
E:unknown volume for path [/odm]
E:unknown volume for path [/vendor]
# MANUAL MODE v1.0.0#
Successfully verified dmverity hash tree
=======================================
Additional info: As I've mentioned, the power button isn't responsive, so I press the volume down button to choose the recovery options. I've tried all recovery options except for:
Wipe data / factory reset, as the phone data isn't backed up (mom doesn't want to lose the personal data as much as possible)
Apply update from ADB
Apply update from SD card
All other options are looping back to the recovery screen after installing system update screen.
Lastly, in recovery, there's an option at the bottom that states "Lacking storage booting". I'm sure that would mean something to someone reading this that would help solve the issue.
An OS downgrade or same 8.1 fix is preferred, as long as the phone data is intact. Any and all help would be much appreciated.

Try "Emergency Software Recovery" feature in Samsung Smart Switch for PC.
It could be a hardware issue as well. Clean your USB charging port with a brush and a drop of alcohol. Then dry with a hair drier.

Good evening, have you tried installing the latest version of the firmware by odin?
If not, try this.
probably its touch stopped working after the update because it was not original (already it has been changed) or it can be other cases ..
if you still can not install the newest firmware downloaded from the sammobile site you can do the second procedure.
Such you will find in this same forum.
In it you use the pc miracle box application and downgrade to 7.1.
this is the title of the post.
follow all procedures.
and it will be all right.
Fix Touch does not work on Samsung J7 Pro (J730G, J730GM) when updating Android 8.1
https://forum.xda-developers.com/ga...ix-touch-samsung-j7-pro-j730g-j730gm-t3850177
PS: Putting it into download mode: Turn the device on by holding the volume down buttons + Home + Power

Thank you. I've tried 3 times now as I am getting stuck at II. Flash TWRP and fix rom. After I flash the nougat rom via TWRP, phone reboots and the logos keep on looping. Either I am doing something wrong or I'm missing a step, or the zip is not working for my mom's phone.

Marius.Banderas said:
Thank you. I've tried 3 times now as I am getting stuck at II. Flash TWRP and fix rom. After I flash the nougat rom via TWRP, phone reboots and the logos keep on looping. Either I am doing something wrong or I'm missing a step, or the zip is not working for my mom's phone.
Click to expand...
Click to collapse
Then when you get to step II open the twrp and go into settings and uncheck the prompt option to install supersu if it is checked. whenever you do something in twrp uncheck this option. I do not know if this will be your problem but this always happens to me, if not clear at the time of restart the cell phone is in the loop screen exactly because of this option.

Cloud1245 said:
Then when you get to step II open the twrp and go into settings and uncheck the prompt option to install supersu if it is checked. whenever you do something in twrp uncheck this option. I do not know if this will be your problem but this always happens to me, if not clear at the time of restart the cell phone is in the loop screen exactly because of this option.
Click to expand...
Click to collapse
Checked TWRP Settings and there's no option / tickbox for supersu. I think one thing that I'm doing wrong is that I'm formatting data in TWRP during the wipe process instead of just sliding it to restore factory settings. I will try again later today after work.
Also, one thing I've noticed after flashing TWRP is that I have to enter recovery mode twice - the first time, it goes to the No command error screen then goes to stock recovery. Only after a reboot in the stock recovery would the phone enter TWRP recovery.

Marius.Banderas said:
Checked TWRP Settings and there's no option / tickbox for supersu. I think one thing that I'm doing wrong is that I'm formatting data in TWRP during the wipe process instead of just sliding it to restore factory settings. I will try again later today after work.
Also, one thing I've noticed after flashing TWRP is that I have to enter recovery mode twice - the first time, it goes to the No command error screen then goes to stock recovery. Only after a reboot in the stock recovery would the phone enter TWRP recovery.
Click to expand...
Click to collapse
Just one more thing. In tutorials on how to install twrp. when you enter twrp the first thing you should do is format the data. then install the rmm state prenormal and bypass files and only then install magisk or a custom rom.
---------- Post added at 11:10 PM ---------- Previous post was at 11:05 PM ----------
Cloud1245 said:
Just one more thing. In tutorials on how to install twrp. when you enter twrp the first thing you should do is format the data. then install the rmm state prenormal and bypass files and only then install magisk or a custom rom.
Click to expand...
Click to collapse
https://youtu.be/UOACi_sUDQY
do only steps 1, 4, 5, 6, 7, and 8 of the video description.
Will be all right!

Marius.Banderas said:
Thank you. I've tried 3 times now as I am getting stuck at II. Flash TWRP and fix rom. After I flash the nougat rom via TWRP, phone reboots and the logos keep on looping. Either I am doing something wrong or I'm missing a step, or the zip is not working for my mom's phone.
Click to expand...
Click to collapse
Before trying to flash TWRP, first flash a full stock firmware and make sure your can at least boot all the way up to the main screen.
Once that works, only then try to flash any custom recovery or custom rom.

Same prob
I've just faced the same problem a few days after my update as well. Did you figure out how to get it back to normal? Thank you!

uz91 said:
I've just faced the same problem a few days after my update as well. Did you figure out how to get it back to normal? Thank you!
Click to expand...
Click to collapse
that is a drk error
you can modification the stock firmware with 7z program
1. open your stock firmware go to AP file
2. click rename than erase the (.md5)
3. extarct the file
4. find (system) file
5. make a (.tar) file with (7z) program with the that system file
6. flash
7. done