Database Users

Problem with my S4 GT-i9500 (Stuck in boot mode, bricked)

Hello.
I own a Samsung Galaxy S4 GT-i9500. I tried to downgrade from Lollipop to KitKat using Odin but I messed up in the process of doing so. Now my phone won’t turn on at all unless plugged into the PC via USB cable. When I plug it in, my PC doesn’t recognize it and an error message with a caution sign flashes on the screen. When I try to go into boot mode (holding the Power button + volume down + home) the menu shows up, but when I try to enter the boot mode it doesn’t respond. The only way I can get into the boot mode is when I remove the battery and immediately press the down volume.
Does anyone know what I can do here? Thank you.

nooguy94 said:
Hello.
I own a Samsung Galaxy S4 GT-i9500. I tried to downgrade from Lollipop to KitKat using Odin but I messed up in the process of doing so. Now my phone won’t turn on at all unless plugged into the PC via USB cable. When I plug it in, my PC doesn’t recognize it and an error message with a caution sign flashes on the screen. When I try to go into boot mode (holding the Power button + volume down + home) the menu shows up, but when I try to enter the boot mode it doesn’t respond. The only way I can get into the boot mode is when I remove the battery and immediately press the down volume.
Does anyone know what I can do here? Thank you.
Click to expand...
Click to collapse
Hi,
Do you mean Download Mode?
Could you try to enter Download Mode with battery removed and flash again your firmware with ODIN? Let me know.
Sent from my ASUS_Z00AD

krasCGQ said:
Hi,
Do you mean Download Mode?
Could you try to enter Download Mode with battery removed and flash again your firmware with ODIN? Let me know.
Sent from my ASUS_Z00AD
Click to expand...
Click to collapse
Yeah sorry, I meant download mode.
I've tried that method before but to no avail. My phone is currently at the repair shop, hopefully the pros can find a solution to it.
Thanks for the reply

Please helpppp!!

So today i root my Samsung S7 edge(SM-G9350F) and after that i try to flash Xposed framework and it didn't work. Now my phone stuck at Samsung logo screen and when i try to enter recovery mode and download mode, there's a red text on top saying KERNEL IS NOT SEANDROID ENFORCING. I want to fix it by flashi
ng custom ROM with ODIN but i cant enter the download mode. Should i try to go to Samsung counter?but i just rooted my phone. Is it okay since they cant see it through the download mode?
PLS HELPPPPP
www s33 postimg org/ybfxuw14f/20160602_204744.jpg (replace empty space with .)

Kernel is not seandroid enfororcing is commonly shown after root... thats not the problem here. Try holding vol down + power button + home button, this should take you to download mode. Try it again, make sure your phone is completely turned off for 20 seconds before entering download mode.

shazore said:
Kernel is not seandroid enfororcing is commonly shown after root... thats not the problem here. Try holding vol down + power button + home button, this should take you to download mode. Try it again, make sure your phone is completely turned off for 20 seconds before entering download mode.
Click to expand...
Click to collapse
I cant enter the download mode, when i try to enter the download mode it just keep restarting to the screen where it showing Kernel is not seandroid enforcing.

Lsoikc said:
I cant enter the download mode, when i try to enter the download mode it just keep restarting to the screen where it showing Kernel is not seandroid enforcing.
Click to expand...
Click to collapse
Did you completely turn off your device for 20 seconds before entering into download mode ?

OMG THANKSS, I couldn't turn off my phone so I let my phone drain my battery until its dead. Thanks anyway its really help:good:

Did I just hard brick my phone?

I was on efficient rom 3.3 and wanted to update to 3.4 but I was on some older versions of bootloader and modem so I wanted to update them first before moving to efficient rom 3.4. So I downloaded the BPHJ BL and CP for 935F, opened Odin and successfully flashed the files from download mode, it said the flash was successful and the phone attempted to reboot (as it normally does after an Odin flash), and now it's stuck at the Samsung logo with a red "recovery is not seandroid enforcing" in upper left corner. I try to boot into download mode by volume up+power+home button, the phone tries to do it but it gets stuck again at the same screen. If I plug my phone to the PC now, Odin doesn't even recognize it, it doesn't say added or anything, it's like the phone is not even connected.
I know I flashed the correct files because they are for the 935F (exynos international - my phone).
How the hell did this happen? Is the phone dead? Can I try anything else?

You have to get into download mode, otherwise it's normal that ODIN doesn't see anything.
Keep trying to get into DL mode. I've read several times here that people had the same problems with getting into DL mode while being stuck in a bootloop, but eventually succeeded after a lot of tries.

MisterKanister said:
You have to get into download mode, otherwise it's normal that ODIN doesn't see anything.
Keep trying to get into DL mode. I've read several times here that people had the same problems with getting into DL mode while being stuck in a bootloop, but eventually succeeded after a lot of tries.
Click to expand...
Click to collapse
I try to but it's just not working. I press vol up + power + home, the screen goes black for a second and then the Samsung logo appears again with the same error.

also i think u have to reflash through twrp the no-verity-opt-encript 2.1 zip. when flash different bootloader.
Sent from my SM-G935F using XDA-Developers mobile app

lvnatic said:
I try to but it's just not working. I press vol up + power + home, the screen goes black for a second and then the Samsung logo appears again with the same error.
Click to expand...
Click to collapse
Download mode is vol DOWN + power + home.
New bootloader also required newest version of TWRP.
So after going into download mode flash the newest TWRP and that's it!.
Sent from my SM-G935F using Tapatalk

NonXtreme said:
Download mode is vol DOWN + power + home.
New bootloader also required newest version of TWRP.
So after going into download mode flash the newest TWRP and that's it!.
Sent from my SM-G935F using Tapatalk
Click to expand...
Click to collapse
Yes the vol up was a mistake, I know up is for recovery and down for download mode. I tried booting into download mode and I still can't do it. I opened this up in the efficient rom thread and yes, I ran into this problem because I wasn't aware I needed the latest twrp version.
Anyway, I try booting into download mode by vol down+power+home and it doesn't work. I try vol dow+power and as soon as the screen goes black I keep holding on the home button as well, without releasing vol down and power. Still not working. The screen goes but instead of booting into download mode it goes back to the Samsung logo with the seandroid enforcing error. This is the first time I can't boot into download mode.

lvnatic said:
Yes the vol up was a mistake, I know up is for recovery and down for download mode. I tried booting into download mode and I still can't do it. I opened this up in the efficient rom thread and yes, I ran into this problem because I wasn't aware I needed the latest twrp version.
Anyway, I try booting into download mode by vol down+power+home and it doesn't work. I try vol dow+power and as soon as the screen goes black I keep holding on the home button as well, without releasing vol down and power. Still not working. The screen goes but instead of booting into download mode it goes back to the Samsung logo with the seandroid enforcing error. This is the first time I can't boot into download mode.
Click to expand...
Click to collapse
Have you try holding vol down+home+power without release them until the download mode come up?
What I mean is that you don't need to wait for screen to go black. Just holding the button combo and phone will automatically reboot and go into download mode.
Sent from my SM-G935F using Tapatalk

NonXtreme said:
Have you try holding vol down+home+power without release them until the download mode come up?
What I mean is that you don't need to wait for screen to go black. Just holding the button combo and phone will automatically reboot and go into download mode.
Sent from my SM-G935F using Tapatalk
Click to expand...
Click to collapse
Yes, that's how I usually do it. It doesn't work. I'm thinking of going with the phone for a warranty repair but I'm worried that red seandroid enforcing error will raise questions about root. I booted into download mode a lot of times before, I know how to do it, it just doesn't work.

lvnatic said:
Yes, that's how I usually do it. It doesn't work. I'm thinking of going with the phone for a warranty repair but I'm worried that red seandroid enforcing error will raise questions about root. I booted into download mode a lot of times before, I know how to do it, it just doesn't work.
Click to expand...
Click to collapse
You're not hard bricked or you wouldn't have any thing showing on your screen.
First hold the power and volume down buttons only til it black screens then as soon as it does hold buttons for download Mode. It sometimes takes many times.
I've also read quite a few people let the phone die then plug it in to charge and then hold the buttons for download Mode.
That's how a friend of mine got his in download Mode.
"And on that bombshell!"
Sent from my Echoe powered AEL Driven G935F

s7freak said:
You're not hard bricked or you wouldn't have any thing showing on your screen.
First hold the power and volume down buttons only til it black screens then as soon as it does hold buttons for download Mode. It sometimes takes many times.
I've also read quite a few people let the phone die then plug it in to charge and then hold the buttons for download Mode.
That's how a friend of mine got his in download Mode.
"And on that bombshell!"
Sent from my Echoe powered AEL Driven G935F
Click to expand...
Click to collapse
Yeah I was thinking of that as well. Thanks.

Out of curiosity, if I go at Samsung now in this state, they will know for sure that the phone was rooted? Can I imply something like I tried updating with Samsung kies and now it's stuck?

lvnatic said:
Out of curiosity, if I go at Samsung now in this state, they will know for sure that the phone was rooted? Can I imply something like I tried updating with Samsung kies and now it's stuck?
Click to expand...
Click to collapse
seandroid enforcing error means the device can't load the security policy cuz u voided warranty
you could always say something like your kid was playing with it and it went into a bootloop or that there was an OTA update and it stoped midway and now your phone wont boot up hope for the best if they decline u goto another store to have it replaced/fixed some ppl arent knowledgeable about voiding warranty and issue a replacement

102skysx said:
seandroid enforcing error means the device can't load the security policy cuz u voided warranty
you could always say something like your kid was playing with it and it went into a bootloop or that there was an OTA update and it stoped midway and now your phone wont boot up hope for the best if they decline u goto another store to have it replaced/fixed some ppl arent knowledgeable about voiding warranty and issue a replacement
Click to expand...
Click to collapse
Thanks for the reply. The battery finally discharged completely and turned off the device. So from the powered off state I managed to boot into download mode from the first try. Flashed the latest twrp and everything is working fine. Topic can be closed

"Recovery booting" blue color when power on SM-G7102 Duos original photos attached.

"Recovery booting" blue color when power on SM-G7102 Duos original photos attached.
Dear Tech's,
Unable to attach photos.
youtu.be/cUOViT5W7fg
This phone was given with issue from my friend. Is it fixable ? ( I really don't know what version of rom flashed before.)
When power on - Getting "recovery booting..." in blue color on top left after that next screen is "effacement en cours..."
after that no luck same screens when ever i try to power on.
tried many things, no luck.
Tried the below guidance too.
Samsung Sm-G7102 Soft Unbrick Tested Firmware + Downgrade From 4.4.2 Guide
Note:This file Only fix Bootloop issues ,Always Booting in recovery mode, after update to 4.4.2 hang Logo Only recovery mode.
Firmware Flashing Method:
* Put Mobile in Download Mode By Holding Vol dwn + Home + Pwr
* Cnnt vit pc using Usb
* Run Odin
* Select File in PDA
* Uncheck Auto Boot in Odin (Important This Step )
* Click Start
* After Flash complete Disconnect yur mobile Remove battery Wait for 20
Insert Battery Pwr ON yur Mobile
* If downgraded From 4.4.2 Hard rest it Mobile should Boot
* After flash Hard reset it if not Booted
Note:Tested on 2 Devices Worked Fine nd IMEI also fine
Firmware Download From Here Android 4.3
G7102ZTUANG2_ZZTANG2_BRI_Taiwan_4.3.zip [Credit Tsar3000]
Odin Flasher
no luck... still the same.
Kindly help to unbrick

take it to local repair shop and get the power button changed
I had the same issue and it was solved after I got power button changed

balooney55 said:
take it to local repair shop and get the power button changed
I had the same issue and it was solved after I got power button changed
Click to expand...
Click to collapse
Dear Balooney,
You damn sure that the issue is with the power button ?
Lemme know how to post pictures in this... so that i can post the original pictures.
This website doesn't allow me to post pictures and external links.

Well I had the same issue for almost a week the phone it self booted to twrp and when I hit reboot it gave a blue screen and the again to twrp and again and again
My issue was fixed after a power button replace

balooney55 said:
Well I had the same issue for almost a week the phone it self booted to twrp and when I hit reboot it gave a blue screen and the again to twrp and again and again
My issue was fixed after a power button replace
Click to expand...
Click to collapse
Anyways my issue is different like getting power on and getting recovery booting in the top left in blue color but i screen android logo after that saying erasing in progress.

Must be a hardware glitch I guess get it inspected at a service center or local repair shop

balooney55 said:
Must be a hardware glitch I guess get it inspected at a service center or local repair shop
Click to expand...
Click to collapse
ok thanks for your replies...

Still in recovery booting.... blue color text.
Any savvy here to solve this issue.
Odin mode
product name: Sm-g7102
current binary: Samsung official
system status: Official
qualcomm secure boot: Enable (csb)
Rp swrev: S2, t2, r2, a2, p2 udc start
I am able to flash roms ... but still no booting only possible to go download mode. Tried flashing twrp aswell no luck.

Has anyone able to solve this "Recovery booting.." issue... im facing this now.

SM-T377A recovery

Hi Folks -
Bricked my Tab - go me..
At present it's sitting at the "An error has occurred Use the Emergency Recovery function in the Smart Switch Software" screen.
What have I done:
Reload ROM -
Odin sees device - starts transfer Errors at first bar (I've since learned it may not be possible due to version of Tab or vendor lock )
Fine - i'll follow the on screen advice:
Loaded Smart Switch - " Device not recognized"
- Reloaded drivers still not recognized
Fine I'll talk to Samsung support:
Out of warranty, you can ship it to us, we'll see what we can do. How much? Depends..
Ok - I'll do a hard reset: -
Hold Power + Volume up + Home = no effect
Hold Power + Volume down + home = get's to the download screen
Hold Power + Volume Down + home - when screen goes black push volume up (holding the other 2) just goes back to the 'there was an error screen"
I've looked through forums and posts tried all the hints/tricks, etc.. It's stuck between the Download Screen and the you done wrong screen.
ODIN MODE
Product Name: SM-T377A
Current Binary: Samsung Official
System Status: Official
FAP Lock: ON
Secure Download: Enabled
KNOW Warrenty Void: 0
AP Software Rev: B:3 K:1 S:2
Anything I've missed? Any trick for recovery mode that might get me to the menu?
As always - thank you community for being awesome..
Best,
MG