Database Info

Can't Root Galaxy S5 Stuck At Blue Bar

TLDR;
Trying to install custom recovery with odin auto-reboot checked off so stock doesnt replace odin says PASS I disconnect the phone but in downloading mode the blue bar is full and the phone doesn't want to shut down. I remove the battery and try to boot into custom philz-recovery it gets stuck in samsung logo. But functions perfectly on normal boot. I reset the whole phone and try the cf-auto-root method and the phone gets stuck in samsung logo now not even booting up normally. So i reset the whole phone again with odin and firmware from sammobile now sitting with a stock android and knox warranty ticked without having a root.
(Sorry for the long post I've tried to provide as much info as I can) So I have a Samsung Galaxy S5 exact model number SM-G900H. And I'm trying to root it. I go into download mode than I launch Odin and check off Auto-Reboot so it won't boot up and the stock recovery replaces the custom I'm trying to install, I connect the phone it says its connected than I select AP and than choose philz-recovery (latest version) and start it. So the Odin finishes its work says "PASS" in green letters. I disconnect the phone but on S5 the blue bar is full and it does not want to shut down (if the auto-reboot is checked it just reboots and it doesn't even want to boot into stock recovery just stuck on samsung logo) I've waited a good hour and still nothing. So I pull out the battery for it to shut down and than I straight try to boot into recovery and it just gets stuck on samsung logo and the blue letters don't even show up. Before rooting the recovery worked and I factory resetted the device before so samsungs knox does't interrupt with its not-being-able-to-boot-into-recovery-if-you-dont-know-the-password-to-the-samsung-account. And I'm now sitting here now with knox warranty ticked and not even rooted BUT I CAN STILL USE THE PHONE PERFECTLY WITHOUT TRYING TO BOOT INTO RECOVERY JUST BOOTS UP NORMALLY. So what I do than is reset the phones firmware with Odin from sammobile. Ok stock android. Than I try the Cf-auto root method with Odin. No luck phone just doesn't even boot up. So I reset the phone again same method. Ok stock android again. Sitting here reading through google for 8 hours 5 of thise spent on xda. STILL NO LUCK. So I hope someone can resolve the issue. I can't provide any pictures as I just rage closed my computer and didn't take pics. And if I install cynogenmod with heimdall is it going to be rooted (i know you don't need a root to do that) and can someone provide a guide to that heimdall cynogenmod install method?

My S7 Duos is totally unresponsive, black screen but blue LED is on

I had my phone just sitting on a wireless charger this morning and had been there for about 15-30 minutes. I noticed it was rebooting, odd I thought? I took it off and then realized it was going into a boot loop. I gave it a soft reset and then it would turn on and stay on for about 10 seconds before boot looping again. I again gave it a soft reset after a couple loops and now it seems to totally dead, as the title implies.
No button combination has worked and I've held them all down for well over 30 seconds each. I've tried plugging it into my PC and haven't gotten any response that way. The blue LED is on so I know it's not dead...I think? To make matters worse, I bought this phone off Craigslist about 5 months ago and it's the Exynos version so I definitely can't get any kind of warranty on it. I'm hoping someone has had this problem and can help or just has some advice. Thanks everyone.
EDIT: To keep this updated, I have been able to get into Odin Mode and have tried to flash stock firmware. Odin says everything went fine but the phone hangs up at the Samsung Galaxy S7 logo. I'm unable to boot into recovery mode and I've even tried to reinstall TWRP with Odin and that has not worked.

Seen the LED only problem before, waiting for the battery to drain and the phone to turn off seems to be the only known cure atm
Once it does, connect the charger for 15 mins, then boot directly into recovery and clear caches to try fix the bootloop, possible it may need factory resetting / clean flash of stock ROM
Using the MicroUSB > USB white adapter, you may be able to connect a power hungry USB peripheral to the phone to drain the battery faster, I use a USB desktop fan, but some people report it not working when it is stuck in this LED loop and have just had to wait it out

Thanks for that advice, I'll let it drain over night. However, I have been able to get it to boot into Odin Mode and Odin v.3 recognized it. I flashed the stock firmware but upon rebooting nothing happened and now it gets stuck at the Samsung logo screen. I can still get it back into Odin mode, which I believe will be the fastest way to kill the battery, but I find it odd that I can get into that but not recovery? I am rooted and have TWRP installed, if that matters at all.

If you can get into Download (ODIN) mode, then letting the battery drain probably won't help, that only seems to help when the phone is completely stuck with nothing but the LED working
Make sure you flash CSC (Not HOME_CSC) along with the other 3 sections of the ROM, using ODIN 3.12.3, that should factory reset the phone after the flash
If you successfully flashed stock with ODIN already, you are no longer rooted and do not have TWRP installed, flashing stock with ODIN replaces all that with stock

I updated Odin and once again tried to flash the 4 parts, making sure I used the right CSC file, but I'm still getting hung up at the Samsung Galaxy S7 logo. Do you have a suggestion as to which region's firmware I should use? I have been trying the Australia one from SamMobile's site.
EDIT: And to clarify, I have the G930FD(the duos one).

jonny727272 said:
I updated Odin and once again tried to flash the 4 parts, making sure I used the right CSC file, but I'm still getting hung up at the Samsung Galaxy S7 logo. Do you have a suggestion as to which region's firmware I should use? I have been trying the Australia one from SamMobile's site.
EDIT: And to clarify, I have the G930FD(the duos one).
Click to expand...
Click to collapse
Any region would work, and the F firmware works for the FD too

Having various problems trying to flash my S7 out of a boot loop

Had it for 3 years now, it first looped in October 2017, broke all the sensors but has otherwise been working fine since. I also rooted it about 7 months ago in case that makes any difference with recovery. During both of these loops I have been unable to reliably get into recovery/download mode. I left it alone for an hour earlier today and came back to find that it was somehow in Odin/download mode with the text in the top left but still on the boot screen. So I plugged it into my computer, it was detected and then I flashed it with the correct G930T firmware and home csc. Got the success message in Odin and it seemed to be working but it was just stuck on the boot screen now. So now I've just been trying to flash it again with the other csc but it has been failing for a lot of different reasons and I don't know what any of them mean. I did manage to get it to power on a lot more reliably and into download mode, but still having problems. The biggest problem is when I get to either the download screen or warning screen, the screen suddenly gets all glitchy and I can't do anything. Whenever that happens it also shuts off after 10 seconds. This also happened on the Smart Switch emergency recovery screen when I cancelled a stalled flash and then tried to flash it again from that screen. I've also gotten errors when trying to flash from the download/boot screen. The ones I can remember are "unsupport dev_type", "secure check fail : tz eMMC write fail : tz" and "secure check fail : hyp eMMC write fail : hyp". I can't even find anything else on these errors and have no idea what they mean. I also have no idea how it is getting into Odin mode on the boot screen but so far that is the only way I have been able to do anything since I can't get into download mode the proper way. Lastly I tried to check in Smart Switch to recover it but it says the device is unsupported and there is nothing in emergency recovery.

Operation Ivy said:
Had it for 3 years now, it first looped in October 2017, broke all the sensors but has otherwise been working fine since. I also rooted it about 7 months ago in case that makes any difference with recovery. During both of these loops I have been unable to reliably get into recovery/download mode. I left it alone for an hour earlier today and came back to find that it was somehow in Odin/download mode with the text in the top left but still on the boot screen. So I plugged it into my computer, it was detected and then I flashed it with the correct G930T firmware and home csc. Got the success message in Odin and it seemed to be working but it was just stuck on the boot screen now. So now I've just been trying to flash it again with the other csc but it has been failing for a lot of different reasons and I don't know what any of them mean. I did manage to get it to power on a lot more reliably and into download mode, but still having problems. The biggest problem is when I get to either the download screen or warning screen, the screen suddenly gets all glitchy and I can't do anything. Whenever that happens it also shuts off after 10 seconds. This also happened on the Smart Switch emergency recovery screen when I cancelled a stalled flash and then tried to flash it again from that screen. I've also gotten errors when trying to flash from the download/boot screen. The ones I can remember are "unsupport dev_type", "secure check fail : tz eMMC write fail : tz" and "secure check fail : hyp eMMC write fail : hyp". I can't even find anything else on these errors and have no idea what they mean. I also have no idea how it is getting into Odin mode on the boot screen but so far that is the only way I have been able to do anything since I can't get into download mode the proper way. Lastly I tried to check in Smart Switch to recover it but it says the device is unsupported and there is nothing in emergency recovery.
Click to expand...
Click to collapse
When you flash with Odin tick "'re partition" in Odin options.
When "pass" appears disconnect phone from pc. Force reboot by holding home+volume down+power.
As soon as screen goes black press volume up while keeping home and power pressed. When recovery menu appears choose wipe / factory reset. Then reboot.
What is obviously very important is you are flashing the correct firmware for the device in the first place.

Rooter S8+ after months suddenly stuck on teamwin (twrp) logo splashscreen

Hi All,
I'm enjoying my first rooted phone for some months now. It's a s8+ with android 12.
But today out of nowhere my phone crashed and now i'm stuck on the teamwin logo page (3.5.2_9-0)
What i've tried:
Using odin again to install the exact same version from my downloads folder again. But this doesn't do a thing
Install a new twrp version from it's website. But then the samsung s8+ logo comes up, and the phone seems to restart immediately and ends in a loop.
I have no clue what to do and trying to search what i have to do but can't find anything but what i've done already.
This is my first rooted phone, so a bit of a noob.
edit: i've tried other versions, but it seems that only 3.5.2_9-0 gets through the samsung logo, but not further then the teamwin logo)n
And in can still enter download mode.
The logo seems to go away for a second every minute

At the moment i followed this tutorial (in januari)

My phone was 4 years old, i guess i'll buy a new one. Perhaps someone can tell me if i can reach my files. Most is backupped correctly but my signal (messenger) backup seems to be backuped to my phone itself instead of the SD card

Stuck on TWRP's "teamwin" loading screen after years of working normally and no changes

Hello, I've been using this phone for more than a few years now. Reflashed the system a few times over the years and was currently on Ivan_Meler's amazing LineageOS 18.
I saw that a bug on his 19.1 version I was experiencing was potentially fixed, so I started preparing to switch to that.
First order of business was going to recovery and doing a full backup, I had gone into recovery not too long ago.
Except I got boot looped instantly.
The current situation is:
- Model is SM-G930F
- The device is rooted
- Device will not stay turned off, if I force turn off with volume down + power it reboots instead
- Device is able to get into download mode and it seems to work normally
- Device will always boot to recovery, except when I ask to boot to download mode by volume down + power + home (not sure if there is a button combination for specifically booting to system, lmk If there is)
Things I already tried:
- Letting the battery run out completely to hopefully clear some cache -> Device tries to boot to recovery as soon as I plug the charger in
- Using ADB during the stuck splash screen -> Device eventually gets recognized by windows but it throws the generic "Your USB device malfunctioned" error, ADB doesn`t recognize it.
- Rebooting by launching a harmless command in Heimdell -> Device reboots but nothing else changes, still stuck.
- Letting battery run out at different stages, like in the stuck teamwin splashscreen, in the warning message before download mode and in download mode -> nothing changes
Additional information from the moment I tried to get to recovery and got stuck:
- I fat fingered "reboot" instead of turning off the phone, so I just held down volume up + home to get into recovery (I had already done this successfully before).
- My phone has USB debugging turned on
- My phone was plugged to my PC in USB Tethering mode when I tried to get to recovery
- My phone was set to use USB Tethering mode by default when plugged via USB, because I use that function a lot.
- My PC had the ADB server running, but was not actively running anything on device at the time.
I remember having been stuck in this same situation before and being able to recover it without losing data. But I have no recollection of how I did it.
If there was a way to make my phone stop trying to reboot and just turn off, im sure that
I would be able to boot into system, because i dont see how anything could've gotten messed up there since the phone rebooted normally and wasn`t reflashed or anythng
I really didn't want to have to wipe it, since my last full backup was a few months ago.
Do you guys have any suggestions? I was thinking of trying to flash back the exact same TWRP version through Odin, without flashing anything else. And seeing if that fixes it since the version is shown in the teamwin loading screen, would that be safe?

Hi, any progress ? I'm in the very similar situation, but flashing the same TWRP with Odin didn't help and I'm still stuck on TWRP logo. And adb doesn't see the device (neither when I'm in download mode nor when I'm on TWRP logo)

Is the device softbricked?
Try Frp HiJacker
All Samsung Frp HiJacker by Hagard (2017)
All Samsung FRP HiJacker 2017 latest updated tool.This tool 100% working and tested. FRP HiJacker V1.0 Features: * Remove Samsung FRP 2017 in Download Mode (No More Combination Files and No more tricks) * Softbrick fixer *Phone...
forum.xda-developers.com
Had similar problems myself