Database Info

Phone is not power up?

I flashed cwm recovery over TWRP from this link below . now phone is not power on?
http://androidhost.org/hUhuh
Any suggestion. :crying:

sanrajbhar said:
I flashed cwm recovery over TWRP from this link below . now phone is not power on?
http://androidhost.org/hUhuh
Any suggestion. :crying:
Click to expand...
Click to collapse
Press volume down while powering on. Does the bootloader appear? If it does, use
Code:
fastboot flash recovery NAMEOFTWRPIMAGE.img
Code:
fastboot boot NAMEOFTWRPIMAGE.img
Backup your data, reboot to bootloader and flash stock ROM before proceeding to flash a custom ROM (or try flashing the custom one directly).

xMotoDA said:
Press volume down while powering on. Does the bootloader appear? If it does, use
Code:
fastboot flash recovery NAMEOFTWRPIMAGE.img
Code:
fastboot boot NAMEOFTWRPIMAGE.img
Backup your data, reboot to bootloader and flash stock ROM before proceeding to flash a custom ROM (or try flashing the custom one directly).
Click to expand...
Click to collapse
I tried volume down with power button but it does not working, no bootloader or sceen on. can I assume now nothing can be done.
My phone was rooted and installed with AOSP rom .

sanrajbhar said:
I tried volume down with power button but it does not working, no bootloader or sceen on. can I assume now nothing can be done.
My phone was rooted and installed with AOSP rom .
Click to expand...
Click to collapse
I have a similar issue, as my phone also cannot turn on and I have TWRP recovery.
I had rooted my phone with SuperSU and unlocked the bootloader via motorola's tool. But then due to SafetyNet, apps such as Snapchat wouldn't work (cant log in), and I couldn't download Netflix (totally a huge issue).
So I decided to try switching to Magisk instead, as I heard that uses systemless root that doesnt trip Safety Net. While uninstalling SuperSU (using the built in feature for full removal), I was able to uninstall SuperSU and unroot my phone, but was not able to restore the stock boot image in the process. It was at this point I made a NANdroid backup in case I stuffed anything up.
Because of this, I was unable to flash Magisk via the TWRP recovery, so I downloaded a previous version of the firmware from January to flash back to from here. After flashing this and also wiping the user data, my phone booted up fine and worked, and appeared to be in normal condition.
However, then I elected to download and install the firmware update. This all went well, and was installing, until just at the end of the process, when the phone turned off. It had over 60% battery at the time.
At this point in time I'm still unable to get it to boot up, even into recovery or fastboot mode, so I cant really do anything, or restore my NANdroid backup.
If I plug it into my laptop, and hold the power + volume button down for a period of time, I can hear the USB connected tone (Windows 10), which then switches to a disconnected tone and a "USB device malfunctioned" error message pops up.
I tried leaving it unplugged all of last night just in case it was stuck in a boot loop or something so the screen couldn't display anything, in order to flatten the battery, but obviously I couldn't tell any difference. I'm currently now trying to have it plugged into power for an extended period of time just in case it is actually just flat. The current condition is just a black screen as if there was no power at all, with no lights or anything, regardless of a charger being connected, with the buttons not doing anything (I've attempted holding down the power and volume down buttons together for at least 2 minutes to no effect)
Any help would be greatly appreciated.
My specs: Moto G Turbo (2015), model XT1557, running Android 6.0.1. Can't remember exactly, but it previously had the latest firmware available before I tried flashing the January firmware.

J4 plus (J415GB) bricked

Is there anyone here facing same with my situation? today i bricked my J4 plus, Dunno if its hard bricked or soft brick, I can't enter to download mode and system restore anymore. Im just trying to get oreo back because i fell little laggy on my current os (pie). I went to samsung service center and they told to use JTAG to get it fix but its too expensive for me to pay hundreds buck for this.
Thank you

its not bricked. your battery is full drained. i had the same problem and how i fixed!!! i presed all 3 buttons and put usb cable to my pc and my phone. it goes like bootloop starts and shuts. you will wait with pressed buttons from 5 to 10 mins depend how low is your battery. and finaly will go to download mode and you can flash it then!!!

Bricked my J4+
Can someone help me with a bricked J4+?
I wanted to install TWRP, I followed the guide to the letter on how to install TWRP.
After successfully flashing TWRP 3.2.3-0 and flashing RMM bypass zip (without booting to the OS) I also performed a Wipe Cache in TWRP.
I booted to the Samsung OS and the system overall felt laggy.
I performed a Factory Reset, still the system felt laggy.
I decided to use Odin and install the Samsung factory system (thus go back to Samsung OS).
I booted successfully and decided to give TWRP 3.2.3-0 another chance.
Odin resulted in FAIL when trying to flash with the following error: Can't open the specified file (line: 1892)
I tried different versions of Odin (from last to previous ones), different USB ports, I even tried another PC but no success.
I performed another factory reset and now the phone is hard bricked I guess because it will power on...try to get in stock recovery and Erase...and then power off. I can't get to download mode or stock recovery.
Any help I would highly appreciate it.
Thanks.

FL0R1AN said:
Can someone help me with a bricked J4+?
I wanted to install TWRP, I followed the guide to the letter on how to install TWRP.
After successfully flashing TWRP 3.2.3-0 and flashing RMM bypass zip (without booting to the OS) I also performed a Wipe Cache in TWRP.
I booted to the Samsung OS and the system overall felt laggy.
I performed a Factory Reset, still the system felt laggy.
I decided to use Odin and install the Samsung factory system (thus go back to Samsung OS).
I booted successfully and decided to give TWRP 3.2.3-0 another chance.
Odin resulted in FAIL when trying to flash with the following error: Can't open the specified file (line: 1892)
I tried different versions of Odin (from last to previous ones), different USB ports, I even tried another PC but no success.
I performed another factory reset and now the phone is hard bricked I guess because it will power on...try to get in stock recovery and Erase...and then power off. I can't get to download mode or stock recovery.
Any help I would highly appreciate it.
Thanks.
Click to expand...
Click to collapse
you didnt follow guide from letter to letter. is obviuosly you didnt do all you need to do. if you in pie update you need to flash twrp (you did) then NEED to format data(go to wipe choose format data(not wipe data,cache) write yes and swipe to format data.this step is important.then go to recovery again and flash pie patched boot.img and oreo enforcing.zip,then RMM bypass,and then you can do boot up your device.thanks.

rudi021 said:
you didnt follow guide from letter to letter. is obviuosly you didnt do all you need to do. if you in pie update you need to flash twrp (you did) then NEED to format data(go to wipe choose format data(not wipe data,cache) write yes and swipe to format data.this step is important.then go to recovery again and flash pie patched boot.img and oreo enforcing.zip,then RMM bypass,and then you can do boot up your device.thanks.
Click to expand...
Click to collapse
The part where I had to format the data...I have missed that. Thanks for pointing it out.
I took the phone to a repair shop because it is hard bricked and it needs jtag to unbrick it.
As soon as I have it back I will try again to install TWRP.
Thanks for the help, I appreciate it.

FL0R1AN said:
The part where I had to format the data...I have missed that. Thanks for pointing it out.
I took the phone to a repair shop because it is hard bricked and it needs jtag to unbrick it.
As soon as I have it back I will try again to install TWRP.
Thanks for the help, I appreciate it.
Click to expand...
Click to collapse
no need to thanks.btw if your device is unlocked you cant be bricked.just flash firmware you want and thats it.btw your device must be unlock to do this stuff(twrp,gsi,etc....) btw you can have read my guide for flashing gsi on samsung j4+.https://forum.xda-developers.com/galaxy-j4+/how-to/how-to-flash-gsi-genericsystemimage-to-t3942554.
if you have any question be free to ask.i will help you if i can.

rudi021 said:
no need to thanks.btw if your device is unlocked you cant be bricked.just flash firmware you want and thats it.btw your device must be unlock to do this stuff(twrp,gsi,etc....) btw you can have read my guide for flashing gsi on samsung j4+.https://forum.xda-developers.com/galaxy-j4+/how-to/how-to-flash-gsi-genericsystemimage-to-t3942554.
if you have any question be free to ask.i will help you if i can.
Click to expand...
Click to collapse
This is a phone from work and I did toggle EOM unlock and USB debugging in order to flash TWRP.
I did not enter any password, face unlock, pattern or sign in to google....nothing of the sort. As soon as I opened the phone from the box tried to install TWRP knowing it will erase everything after TWRP installation. I really hate Samsung UI and wanted to try Lineage OS or another custom ROM which is not laggy like ONE UI.
After installing TWRP the phone became very laggy (obviously I did not perform a format data...my bad) I did use Odin and flashed the corresponding firmware of the phone and it did that successfully.
I tried to give TWRP another shot by flashing it again but I was getting a FAIL in Odin with the following error: Can't open the specified file (line: 1892)
After this I tried to flash again the same Samsung firmware but kept getting the same FAIL and the same error: Can't open the specified file (line: 1892)
I have tried all versions of Odin but the same FAIL and same error.
Now I can't even get into Download mode or Samsung recovery mode.
I press Volume Up + Volume Down and insert the micro USB cable....the phone takes at least 10 seconds to power up (Samsung logo) and then I see a blue screen with Android robot trying to perform an Erase and then fails and the phone powers off immediately.
As soon as I get the phone I will check your link on XDA and try a GSI ROM.
Which one do you recommend...this is a work phone, all I care about is speed and fluidity and it has to be a daily driver.

FL0R1AN said:
This is a phone from work and I did toggle EOM unlock and USB debugging in order to flash TWRP.
I did not enter any password, face unlock, pattern or sign in to google....nothing of the sort. As soon as I opened the phone from the box tried to install TWRP knowing it will erase everything after TWRP installation. I really hate Samsung UI and wanted to try Lineage OS or another custom ROM which is not laggy like ONE UI.
After installing TWRP the phone became very laggy (obviously I did not perform a format data...my bad) I did use Odin and flashed the corresponding firmware of the phone and it did that successfully.
I tried to give TWRP another shot by flashing it again but I was getting a FAIL in Odin with the following error: Can't open the specified file (line: 1892)
After this I tried to flash again the same Samsung firmware but kept getting the same FAIL and the same error: Can't open the specified file (line: 1892)
I have tried all versions of Odin but the same FAIL and same error.
Now I can't even get into Download mode or Samsung recovery mode.
I press Volume Up + Volume Down and insert the micro USB cable....the phone takes at least 10 seconds to power up (Samsung logo) and then I see a blue screen with Android robot trying to perform an Erase and then fails and the phone powers off immediately.
As soon as I get the phone I will check your link on XDA and try a GSI ROM.
Which one do you recommend...this is a work phone, all I care about is speed and fluidity and it has to be a daily driver.
Click to expand...
Click to collapse
1. two possible mistake. 1.after you try flash firmware dont check user data,just check AP,BL,CP,CSC and flash firmware.2.no need to try old odin. all new firmware is work on new odin.just need to know what to checked to flash. about gsi all is good but i like Havoc OS, Lineage OS 16, RR,almost all.again you are welcome to ask help if you want.:good:

rudi021 said:
1. two possible mistake. 1.after you try flash firmware dont check user data,just check AP,BL,CP,CSC and flash firmware.2.no need to try old odin. all new firmware is work on new odin.just need to know what to checked to flash. about gsi all is good but i like Havoc OS, Lineage OS 16, RR,almost all.again you are welcome to ask help if you want.:good:
Click to expand...
Click to collapse
Hmmm I did check USER DATA. So that bricked my device. Thanks for letting me know.

FL0R1AN said:
Hmmm I did check USER DATA. So that bricked my device. Thanks for letting me know.
Click to expand...
Click to collapse
yeeeahhh. i am knowing that in hard way. you can check user data only if you have ORIGINAL firmware and not rooted phone(mean twrp),if you have rooted(twrp) then flash with or without user data. some firmwares on web can flash with user data, some cant.anyway as i say you can always ask for help.i will gladly help if i can. good luck.

rudi021 said:
yeeeahhh. i am knowing that in hard way. you can check user data only if you have ORIGINAL firmware and not rooted phone(mean twrp),if you have rooted(twrp) then flash with or without user data. some firmwares on web can flash with user data, some cant.anyway as i say you can always ask for help.i will gladly help if i can. good luck.
Click to expand...
Click to collapse
Thanks. I will wait for the phone to be unbricked and then will try TWRP again.

Can i install gsi rom if the phone is in oneui?

FL0R1AN said:
I press Volume Up + Volume Down and insert the micro USB cable....the phone takes at least 10 seconds to power up (Samsung logo) and then I see a blue screen with Android robot trying to perform an Erase and then fails and the phone powers off immediately .
Click to expand...
Click to collapse
What you're describing are symptoms of a flat battery and a direct boot to recovery.
To boot to download mode plug in the USB cable first then hold vol up, vol down and power until download mode appears.
There is absolutely no way TWRP caused the lag. TWRP runs in its own minimal OS environment and has no effect on a booted android OS whatsoever.
Lastly your device wasn't hard bricked, a device that powers on even if it doesn't boot is only soft bricked.
Usually recoverable using the right procedure.

ashyx said:
What you're describing are symptoms of a flat battery and a direct boot to recovery.
To boot to download mode plug in the USB cable first then hold vol up, vol down and power until download mode appears.
There is absolutely no way TWRP caused the lag. TWRP runs in its own minimal OS environment and has no effect on a booted android OS whatsoever.
Lastly your device wasn't hard bricked, a device that powers on even if it doesn't boot is only soft bricked.
Usually recoverable using the right procedure.
Click to expand...
Click to collapse
I managed to boot into the Revovery and perform a factory reset, now the phone booted normally.
I will try and install TWRP.
When these strange things happened the device had over 80% battery...at least that's what it showed on screen.
Now I see that indeed it was flat 0% and you were right to point out that this is a flat battery problem.
Thanks for the help I really appreciate it.

FL0R1AN said:
I managed to boot into the Revovery and perform a factory reset, now the phone booted normally.
I will try and install TWRP.
When these strange things happened the device had over 80% battery...at least that's what it showed on screen.
Now I see that indeed it was flat 0% and you were right to point out that this is a flat battery problem.
Thanks for the help I really appreciate it.
Click to expand...
Click to collapse
well like i told you it is not problem of twrp.but as senior member ashyx told in answer today device cant be hard bricked.just flash firmware and device will boot as normal. btw keep battery full

rudi021 said:
well like i told you it is not problem of twrp.but as senior member ashyx told in answer today device cant be hard bricked.just flash firmware and device will boot as normal. btw keep battery full
Click to expand...
Click to collapse
Yes Thanks. I am at 100% battery. Can I ask a few questions on how to install TWRP?
I am on Android 9.x.x PIE.
Install TWRP and immediately force reboot to recovery.
Flash the RMM bypass.
Format data
Boot to Samsung OS.
Is this procedure correct?
Thanks.

FL0R1AN said:
Yes Thanks. I am at 100% battery. Can I ask a few questions on how to install TWRP?
I am on Android 9.x.x PIE.
Install TWRP and immediately force reboot to recovery.
Flash the RMM bypass.
Format data
Boot to Samsung OS.
Is this procedure correct?
Thanks.
Click to expand...
Click to collapse
install twrp(in odin option uncheck Auto Reboot) ,format data reboot to recovery,flash oreo enforcing.zip,flash RMM,flash magisk(newest) then reboot.

rudi021 said:
install twrp,format data,flash oreo enforcing.zip,flash RMM,flash magisk(newest) then reboot.
Click to expand...
Click to collapse
Got it, Thanks.

FL0R1AN said:
Yes Thanks. I am at 100% battery. Can I ask a few questions on how to install TWRP?
I am on Android 9.x.x PIE.
Install TWRP and immediately force reboot to recovery.
Flash the RMM bypass.
Format data
Boot to Samsung OS.
Is this procedure correct?
Thanks.
Click to expand...
Click to collapse
It's correct, but if you want access to the data partition in twrp you need to also install the encryption patch.
You will also need to either install magisk or some other patch that disables dmverity.

ashyx said:
It's correct, but if you want access to the data partition in twrp you need to also install the encryption patch.
You will also need to either install magisk or some other patch that disables dmverity.
Click to expand...
Click to collapse
Got it, Thanks

N8010 - stuck at downloading mode

Hi, after flashing TWRP update from TWRP itself I am now stuck at download mode.
I can access downloading mode using Power + Volume down
I cannot boot into twrp using Power + Volume up, this brings download mode up.
I cannot boot into system, this results in the same behavior as previous situation.
The main problem is that for a long time my cable or port is not working correctly. I can charge tablet but the data transfer is not established. I cannot say if it is caused by cable or port but I think it is the port itself - other reduction does not work as well. Thanks to this I cannot easily flash recovery back.
So I am looking for other solutions than buying new port board/cable and replacing it. SD card is currently the only one interface working. I am asking if there is possibility to flash recovery/stock via sd card - maybe some files detected right after entering download mode, i. e. recovery.img.
Other possibility would be to get adb over wifi working.
Thank you.

Hi,
does the flash process even start when you try it with odin or heimdall?
Once recovery boot is triggered, it will alway's try to boot into.
You could try to:
heimdall print-pit
If this is succesfull, you may can boot into system and then flash a new twrp with root rights.

html6405 said:
Hi,
does the flash process even start when you try it with odin or heimdall?
Once recovery boot is triggered, it will alway's try to boot into.
You could try to:
heimdall print-pit
If this is succesfull, you may can boot into system and then flash a new twrp with root rights.
Click to expand...
Click to collapse
Hi,
my problem is that my cable (probably charging port) is not working (it does charge but does not transfer data) so I cannot do flash via cable.
I flashed twrp update using twrp. I do not understand however why I cannot boot into system or does bootloader need working recovery?
Here I am sending two pics:
1. boot into download mode directly using Power + Volume Down - https://pasteboard.co/JU4sQdr.jpg
2. standard reboot or Power + Volume up - https://pasteboard.co/JU4t6gR.jpg
Is I get somehow to system, I can flash recovery easily as I have rooted device.

Development [UNOFFICIAL][EXPERIMENT] TWRP for Galaxy Tab S7 FE

This is an unofficial and experimental build of TWRP which was tested on the Samsung Galaxy Tab S7 FE (SM-T735) model only.
I used TWRP Samsung Galaxy Tab S7+ 5G device tree by ianmacd and modified it.
MTP doesn't work at the moment.
If you flash a GSI, be sure to wipe the metadata partition along with the data partition.
You might need to flash the neutralized vbmeta image.
Installing TWRP: Flash both files with Odin in the AP slot.
Kernel Source (I used the kernel which was in the stock recovery)
Device Tree Source
As always, be sure to backup your data in case something goes wrong.
Edit: I apologize to everyone for taking 1 year to update this thread.
Disclaimer:
No guarantees that everything would work. I am not responsible for any damages caused from this.

Thank You for your contribution, I hope to see a stable TWRP or other recovery

Will this work with T733?

mcgomfer said:
Will this work with T733?
Click to expand...
Click to collapse
Read the description again, slowly.

Sorry to ask such a noob question but how do I download and install this? Ive got my tab s7 fe rooted with magisk on stock rom and Im far from new to flashing recoveries and roms, but there is no zip to flash or anything, how do I use it?

Hi, My bro.
Can this be used to install GSI?

billy996 said:
Hi, My bro.
Can this be used to install GSI?
Click to expand...
Click to collapse
Hello,
Yes, you can install a GSI with this, I've flashed the AOSP GSI and it worked as intended.

BDog21 said:
Sorry to ask such a noob question but how do I download and install this? Ive got my tab s7 fe rooted with magisk on stock rom and Im far from new to flashing recoveries and roms, but there is no zip to flash or anything, how do I use it?
Click to expand...
Click to collapse
Hello,
I've updated the post with the files added.

dhruv22592 said:
Hello,
I've updated the post with the files added.
Click to expand...
Click to collapse
Can you flash these together by putting the vbmeta in userdata and TWRP in AP?

lewmur said:
Can you flash these together by putting the vbmeta in userdata and TWRP in AP?
Click to expand...
Click to collapse
Hello,
How I had flashed these files on my tab was by flashing them one by one. Alternatively, you can flash vbmeta in the USERDATA slot.

dhruv22592 said:
Hello,
How I had flashed these files on my tab was by flashing them one by one. Alternatively, you can flash vbmeta in the USERDATA slot.
Click to expand...
Click to collapse
Doing both at the same time doesn't work. Bootloop. Had to flash stock and start from scratch to get it working again. Then I flashed vbmeta which then required a factory reset. Did minimal setup and then flashed TWRP but couldn't get it to boot to recovery so TWRP got overwritten. I unchecked auto reboot in Odin prior to flash and when it finished held power and vol down till screen blanked and then switch to vol up. But when it reached the screen saying to push power to continue it didn't continue until I finally released vol up. Then it booted system instead of recovery. I held vol up for several minutes before finally releasing it.

lewmur said:
Doing both at the same time doesn't work. Bootloop. Had to flash stock and start from scratch to get it working again. Then I flashed vbmeta which then required a factory reset. Did minimal setup and then flashed TWRP but couldn't get it to boot to recovery so TWRP got overwritten. I unchecked auto reboot in Odin prior to flash and when it finished held power and vol down till screen blanked and then switch to vol up. But when it reached the screen saying to push power to continue it didn't continue until I finally released vol up. Then it booted system instead of recovery. I held vol up for several minutes before finally releasing it.
Click to expand...
Click to collapse
Hello,
This requires a factory reset.
I apologize that i was not clear before but the steps i did were:
1. Reboot my tablet to download mode with adb using "adb reboot download"
2. Flash twrp in the AP slot
3. Then the tab complains about using a custom recovery, force reboot the tab and immediately boot to download mode (by holding both volume buttons and the power button)
4. Then flash vbmeta in the AP slot.
5. Finally, when the tablet automatically reboots, immediately hold the Vol Up+Power button to boot into twrp.

dhruv22592 said:
This requires a factory reset.
I apologize that i was not clear before but the steps i did were:
1. Reboot my tablet to download mode with adb using "adb reboot download"
2. Flash twrp in the AP slot
3. Then the tab complains about using a custom recovery, force reboot the tab and immediately boot to download mode (by holding both volume buttons and the power button)
4. Then flash vbmeta in the AP slot.
Click to expand...
Click to collapse
Tried that. Still wouldn't boot to recovery.

lewmur said:
Tried that. Still wouldn't boot to recovery.
Click to expand...
Click to collapse
Hello,
Which model are you using?
It might slightly differ in the specs, if the model is SM-T733, I would suggest you try this version of TWRP instead.

dhruv22592 said:
Hello,
Which model are you using it might slightly differ in the specs, if the model is SM-T733, I would suggest you try this version of TWRP instead.
Click to expand...
Click to collapse
Sorry, this was meant for another post.

The CPU of SM-T735 is Snapdragon 750G, and the CPU of SM-T733 is Snapdragon 778G.
Does anyone test this TWRP on SM-T733 to run?

dhruv22592 said:
Hello,
This requires a factory reset.
I apologize that i was not clear before but the steps i did were:
1. Reboot my tablet to download mode with adb using "adb reboot download"
2. Flash twrp in the AP slot
3. Then the tab complains about using a custom recovery, force reboot the tab and immediately boot to download mode (by holding both volume buttons and the power button)
4. Then flash vbmeta in the AP slot.
5. Finally, when the tablet automatically reboots, immediately hold the Vol Up+Power button to boot into twrp.
Click to expand...
Click to collapse
after I flash TWRP in step 2 and reboot into download mode. The tablet prompts me to unlock the bootloader again. And as a result, I can't get into TWRP. Please assist thank you

billy996 said:
The CPU of SM-T735 is Snapdragon 750G, and the CPU of SM-T733 is Snapdragon 778G.
Does anyone test this TWRP on SM-T733 to run?
Click to expand...
Click to collapse
did you have any luck getting into TWRP?

dhruv22592 said:
Hello,
This requires a factory reset.
I apologize that i was not clear before but the steps i did were:
1. Reboot my tablet to download mode with adb using "adb reboot download"
2. Flash twrp in the AP slot
3. Then the tab complains about using a custom recovery, force reboot the tab and immediately boot to download mode (by holding both volume buttons and the power button)
4. Then flash vbmeta in the AP slot.
5. Finally, when the tablet automatically reboots, immediately hold the Vol Up+Power button to boot into twrp.
Click to expand...
Click to collapse
Did you ever get TWRP to work? If so, what stock version were you running? I'm thinking I can't get TWRP to run because I'm running the latest update out right now.

mdewii23 said:
Did you ever get TWRP to work? If so, what stock version were you running? I'm thinking I can't get TWRP to run because I'm running the latest update out right now.
Click to expand...
Click to collapse
AFAIK, the ONLY TWRP to work was for the T735 and it was experimental. So far, I'm happy with rooted stock. My performance and battery life seem to be great, so there isn't much pressure to improve with a custom ROM. So long as rooting is possible, you can do your own de-bloating.

A problem that I think there’s no solution for

I decided to give this rom a try and I needed to flash TWRP but apparently it wasn’t the right version or something. But what happened is, before I flash twrp via Odin I don’t why I wasn’t able to enter download mode by pressing [VOL - and POWER]. I was able to do it through bootloader option in the standard recovery, so I did, but twrp didn’t run correctly, its home page shows glitches then the phone turns off and boot by it self again to the glitched twrp screen and keeps doing this over and over till the battery dies, and whatever I tried to press nothing happens, it’s like trying to wake a phone that doesn’t have any recovery or download mode.
Is there anything I can do?
I live in Damascus, Syria, so it’s impossible to reach samsung customers care because of the sanctions :/
Sorry for my bad English

Moe.n said:
I decided to give this rom a try and I needed to flash TWRP but apparently it wasn’t the right version or something. (...)
Click to expand...
Click to collapse
Can you provide a link to the manual with which you flash TWRP?
Without that, it's hard to understand why you can't access download mode.

ze7zez said:
Can you provide a link to the manual with which you flash TWRP?
Without that, it's hard to understand why you can't access download mode.
Click to expand...
Click to collapse
Actually I wasn’t able to enter download mode in the usual way [VOLdown and POWER]. I think this happened after the last firmware I used, I noticed something isnt right because It has so many bugs but I kept using it for a year because I was afraid to break the phone permanently. But now when I took the risk I entered download mode through bootloader option.
Here the twrp I tried to flash
[RECOVERY][ROOT]TWRP 3.2.3-1 Galaxy A7 2018/A750
Unofficial release -TWRP recovery for the Galaxy A7 2018 - SM-A750F EXYNOS 7885 TWRP 3.2.3-0 Released Aug 6, 2018 TWRP 3.2.3-0 is out now for most currently supported devices. What's new in 3.2.3-0: * Fix automatic installing of OTA zips on...
forum.xda-developers.com

Why are you trying to start DOWNLOAD mode via two buttons VOL DOWN and POWER, when the TWRP flashing manual says to press three buttons?
Code:
1. Put your device in DOWNLOAD mode.
(Hold POWER + VOL DOWN + VOL UP)
Re-flash TWRP exactly as instructed but without RMM.

Moe.n said:
I decided to give this rom a try and I needed to flash TWRP but apparently it wasn’t the right version or something. But what happened is, before I flash twrp via Odin I don’t why I wasn’t able to enter download mode by pressing [VOL - and POWER]. I was able to do it through bootloader option in the standard recovery, so I did, but twrp didn’t run correctly, its home page shows glitches then the phone turns off and boot by it self again to the glitched twrp screen and keeps doing this over and over till the battery dies, and whatever I tried to press nothing happens, it’s like trying to wake a phone that doesn’t have any recovery or download mode.
Is there anything I can do?
I live in Damascus, Syria, so it’s impossible to reach samsung customers care because of the sanctions :/
Sorry for my bad English
Click to expand...
Click to collapse
the problem is not the twrp in that thread, but probably your stock firmware(if you are using one) because if your current firmware is from 2021 and so on.. then flashing a custom recovery will give you a glitching twrp so try doing this tutorial first https://forum.xda-developers.com/t/updated-september-2022-how-to-root-a7-2018.4488289/#post-87528089 before flashing twrp in your phone, just download the firmware for your device dated dec 2020 or last firmware update in 2020 then extract it.. then flash the bl_file(just the bl file of that 2020 firmware) to your phone then try flashing twrp again to your phone by following the instructions in the thread you posted here.

in case you have followed the full tutorial in that link I put up there, then you probably have a phone that can be modified because of bl_file from 2020 and a latest security patch(if you followed the ful tutorialsin that link up there), and in case you want to root your phone then follow the tutorials here https://forum.xda-developers.com/t/guide-how-to-root-galaxy-a7-2018.4318969/ then before you put a lock screen and make your finger print and face detection work you have to patch this module in magisk manager https://forum.xda-developers.com/t/guide-passing-safetynet.4318941/ to avoid being locked, because if you root your phone without patching the safety net will lead you into a loop.