Database Info

Can boot in download mode but no recovery

Greetings,
When I was flashing via odin stock rom somehow it got stuck on setup connection and I had to close it. Since then the tablet wouldnt boot into recovery mode and wont boot at all. It goes to first samsung logo and gets blank. I tried flashing stock roms even with options repartition via odin in download mode but no luck.
Any insights people?

hardik_hrc said:
Greetings,
When I was flashing via odin stock rom somehow it got stuck on setup connection and I had to close it. Since then the tablet wouldnt boot into recovery mode and wont boot at all. It goes to first samsung logo and gets blank. I tried flashing stock roms even with options repartition via odin in download mode but no luck.
Any insights people?
Click to expand...
Click to collapse
I have this same problem. Bump.

Hey guys, I only suggest the following, cause I had the same problem after flashing via odin.
In fact it happened to me more than once since I forgot the solution after a while ...
Make sure you unplug the USB cable from your tablet before trying to get into recovery mode.
That did it for me both times - once with my S4 and just recently with my Tab 2...

Is my N8013 completely dead?

I have a sinking feeling that the same failure that killed my first tablet, an HP Touchpad (NAND Lock/Failure) has killed my Galaxy Note N8013. All was fine until a few days ago. I was running TWRP 2..8.0.1. and alternating between CM12.1 and BliisRom with no problems. I connected it to charge overnight and went to bed. The next morning it was stuck on the CM12.1 boot animation. It would never boot, just run the animation until the battery drained. I can put it in download mode and it appears to successfully flash stock/custom roms/recoveries (I've tried them all) but as soon as it reboots it goes back to the CM boot animation. If I try to put in recovery (power + Volume up) the TWRP splash screen appears but quickly disappears and is replaced by CM boot animation. Since I can't get into recovery is there another way to do a factory reset/wipe? Any ideas or suggestions?

DaElderGeek said:
I have a sinking feeling that the same failure that killed my first tablet, an HP Touchpad (NAND Lock/Failure) has killed my Galaxy Note N8013. All was fine until a few days ago. I was running TWRP 2..8.0.1. and alternating between CM12.1 and BliisRom with no problems. I connected it to charge overnight and went to bed. The next morning it was stuck on the CM12.1 boot animation. It would never boot, just run the animation until the battery drained. I can put it in download mode and it appears to successfully flash stock/custom roms/recoveries (I've tried them all) but as soon as it reboots it goes back to the CM boot animation. If I try to put in recovery (power + Volume up) the TWRP splash screen appears but quickly disappears and is replaced by CM boot animation. Since I can't get into recovery is there another way to do a factory reset/wipe? Any ideas or suggestions?
Click to expand...
Click to collapse
did you tryed with odin or abd, try to flash newest twrp from the site and flash it via odin3.

Pupskartoffel said:
did you tryed with odin or abd, try to flash newest twrp from the site and flash it via odin3.
Click to expand...
Click to collapse
Only with Odin. My understanding is that ADB isn't available if you can't boot into recovery. I haven't found anyway to make it boot into recovery.

Reflash/recovery
Have you tryed to flash twrp 2.8.7.0 or cwm or, try to reflash the boot.img.
Sorry for bad english i'm only 12

HELP! Bootloop after flashing TWRP

Hey folks,
my S10e (G970F) is bootlooping after flashing TWRP via Odin. The flashing process via Odin did PASS and I could enter TWRP afterwards because the file "Encryption_Disabler" needed to be installed while still in TWRP but I messed up since I've forgot to put that very specific file to the internal storage before and my PC doesn't seem to mount the S10e after being in recovery mode (TWRP). I was cursing myself and in a fit of distress I decided to reboot the S10e into system and that was when it doesn't boot past the SAMSUNG booting screen anymore. I'm stuck with bootlooping.
As for now, I can enter the download mode , my bootloader is unlocked and I'm back on stock recovery but the device deprives itself from booting up which resulted in a never ending bootloop. And let me tell you, bootlooping can cause extremely distress and you feel like sighing every other seconds because it keeps messing with your brain.
Can you guys help me out here? Thanks for your efforts!

I've managed to fix it myself. YAY! I'm happy!

cocolish said:
I've managed to fix it myself. YAY! I'm happy!
Click to expand...
Click to collapse
Can you elaborate on how you fixed it for anyone else going through the same problems?

I flashed stock Firmware via Odin. After it boots up I proceed with this guide
https://forum.xda-developers.com/showpost.php?p=79411681&postcount=9
https://topjohnwu.github.io/Magisk/install.html#samsung-system-as-root
And it works perfectly fine!

i got bootloop after flash twrp, keys combination doesnt work
do u have idea?
https://drive.google.c…L_rWhxJkkNA2YV9TU/view

SM-A750FN (Sam. a7 2018) TWRP not loading

Hello, my problem is that I flash "Twrp_3.2.3-1_a750.tar" with ODIN in order to try and root my SM-A750FN device.
After I flash it and ODIN sais PASS, I get out of download mode and immediatly enter recovery mode. At that point the teamwin logo flashes on the screen and then the phone shuts down. The phone boots up again, tries to go into recovery mode again at which point it goes into a kind of bootloop to teamwin logo and after a few tries it just stays closed, doesnt take anymore commands (dl, recovery, etc.) and starts to heat up like he is still bootlooping just doesnt show on the screen. I let the battery drain, i go into download mode and install stock firmware. I know long story.
SHORT STORY: SM-A750FN wont go into TWRP recovery, when i try to go to recovery mode it bootloops to TWRP logo. I would like to solve this in order to root it.
I specify that i have changed the firmware(rom) on the device, the original one worked with TWRP, I tried the latest firmware I could find for two separete regions and both have the same behavior.
Thanks in advance!

Re-flash the original ROM to get rid off of the failed TWRP installation.

Hello, thanks for the answear. Do you have any idea where to get the original rom from? I dont have it anymore as i din't make a back-up before flashing the ones that i got from the internet. I already tried to flash 2 stock roms from the internet and they dont seem to work with twrp.

Request it from OEM / Carrier.
BTW: It's NOT the installed ROM that doesn't work with TWRP but it's TWRP that doesn't work with installed ROM. Take note that TWRP rewrites portions of installed ROM.

I see, so I should request it from Samsung? Also thanks for you answears, i think i'll try atleast one older ROM for my phone, maybe TWRP will work with that. Thanks!

Question How to fix bootloop on Poco X3 Pro

My Poco X3 Pro was running in Pixel experience plus custom ROM. My pixel experience recovery was gone. so i installed TWRP recovery. but my phone got stuck in bootloop while installing magisk via TWRP then I tried to flash MIUI 14 fastboot rom using mi flash tool but failed again and again. I also tried to flash directly using platform tools. but it doesn't work. after then I flashed Pixel experience recovery via fastboot and then installed Pixel experience ROM this time my phone started. but when I power off the device and tried to on it again it stuck in bootloop. then I again installed Pixel experience ROM and turned my phone on. but I'm afraid that if I turn off my phone will again stuck in the bootloop. how can I fix this?

Shahriar566 said:
My Poco X3 Pro was running in Pixel experience plus custom ROM. My pixel experience recovery was gone. so i installed TWRP recovery. but my phone got stuck in bootloop while installing magisk via TWRP then I tried to flash MIUI 14 fastboot rom using mi flash tool but failed again and again. I also tried to flash directly using platform tools. but it doesn't work. after then I flashed Pixel experience recovery via fastboot and then installed Pixel experience ROM this time my phone started. but when I power off the device and tried to on it again it stuck in bootloop. then I again installed Pixel experience ROM and turned my phone on. but I'm afraid that if I turn off my phone will again stuck in the bootloop. how can I fix this?
Click to expand...
Click to collapse
Pixel with magisk and modules?

No I was just installing magisk via TWRP

try installing magisk via image patching, works for me everytime. Magisk creator himself warn against using TWRP to flash magisk.zip

I was asking how to fix bootloop. My device is on but if I power off it will go to bootloop again then I will have to flash Pixel experience again. My problem is bootloop not installing magisk

Shahriar566 said:
I was asking how to fix bootloop. My device is on but if I power off it will go to bootloop again then I will have to flash Pixel experience again. My problem is bootloop not installing magisk
Click to expand...
Click to collapse
Tried flash official MIUI recovery ROM with TWRP?

Tried official MIUI fastboot rom not recovery

Shahriar566 said:
Tried official MIUI fastboot rom not recovery
Click to expand...
Click to collapse
Put the fastboot ROM in C drive directly, then go into the folder, find the "flash_all.bat" to flash it under fastboot mode.
Don't use Mi-Flash.
Can try the recovery flashing method with TWRP.
Check if you still got mobile SIM card working, with the original intact IMEI.

I tried "flash_all.bat" but after clicking it runs for 1 sec then disappear

Shahriar566 said:
I tried "flash_all.bat" but after clicking it runs for 1 sec then disappear
Click to expand...
Click to collapse
Rename the folder name shorter, like "ROM."
Phone needs to be in Fastboot mode, before running that flash_all.bat.
There could be some issue connecting your phone with the PC. Could be driver issue, permission issue, AMD CPU issue and/or other reasons.
Try TWRP to flash the recovery ROM would be easier.
Remember to "Format data" in TWRP.

Yeah I know the rules . I did it several times with no issue . And I have all the drivers installed in the PC.
Actually I'm afraid of power off the phone cuz if I power off it will go to the bootloop again then I again have flash pixel experience.
I just want to know does this ever happen that my phone is totally ok and if I power off it will go to bootloop?

Shahriar566 said:
Yeah I know the rules . I did it several times with no issue . And I have all the drivers installed in the PC.
Actually I'm afraid of power off the phone cuz if I power off it will go to the bootloop again then I again have flash pixel experience.
I just want to know does this ever happen that my phone is totally ok and if I power off it will go to bootloop?
Click to expand...
Click to collapse
This had happened to me rarely that the phone failed to start, stuck on the booting logo and self-boot again, then it booted correctly on the 2nd boot.
Don't know if your phone is totally ok or not, since there are cases that had the CPU ball issues. To make sure, it's better to find Xiaomi/Redmi/Poco official repair center and or customer service.
Even if the phone is out of warranty, could still ask for a phone hardware checkup, with some fee needed.

Thanks for the advice
pl1992aw said:
This had happened to me rarely that the phone failed to start, stuck on the booting logo and self-boot again, then it booted correctly on the 2nd boot.
Don't know if your phone is totally ok or not, since there are cases that had the CPU ball issues. To make sure, it's better to find Xiaomi/Redmi/Poco official repair center and or customer service.
Even if the phone is out of warranty, could still ask for a phone hardware checkup, with some fee needed.
Click to expand...
Click to collapse
Actually today I rebooted my device and it went to bootloop but after showing it's boot logo 3 or 4 times it started.
What do you think about it?

Shahriar566 said:
Actually today I rebooted my device and it went to bootloop but after showing it's boot logo 3 or 4 times it started.
What do you think about it?
Click to expand...
Click to collapse
Unknown reason. Don't know if it's ROM issue or hardware issue.
Can try downgrade to old firmware versions.
Can also try older ROM versions.