I don't know what happened. but it looks like my phone is now stuck while I went to reboot into recovery.
The screen is frozen and displpays the following:
Recovery booting......
Recovery is not seandroid enforcing
set warranty bit: recovery
it just stays there.
I took out the battery to turn it off, and power it back on. It boots to the same screen display.
I just did a back up just last week.
I am been using a custom rom (wicked version 5) for a long time in Note 3. This is the first time I had this issue. I think (hope not) that the phone is bricked.
How do I fix this? any suggestion will be appreciated. Thank you in advance
Have you tried re-installing recovery (CWM, TWRP) via Odin (assuming you can get into download mode)?
Related
ok so i had posted lat night where for what ever reason after being rooted and having wicked rom running after doing a nandroid back up phone wouldn't go past boot screen. every time i try to go to recovery it shows samsung boot screen and see on top that it is going into recovery mode. after like 2 seconds it reboots and goes back to boot screen. i was able to get into download mode and flashed stock rom in odin. every things works fine as far as that. one strange thing is the phone sd card is pretty much full. i have done a factory reset every thing was back to normal. once again phone memory is full. i have loaded the root file on my ext sd card. load a recovery through odin. that works fine. still won't go into recovery. how can i fix this issue. i really just want the stock rom with recovery and root so i can run a few programs that require root. also how much extra space should i have on the phone memory after loading stock rom back up. any help would be greatly appreciated. btw this is not my first time having a rooted and custom rom phone. i had all that working on my htc amaze 4g.
probablecauz69 said:
ok so i had posted lat night where for what ever reason after being rooted and having wicked rom running after doing a nandroid back up phone wouldn't go past boot screen. every time i try to go to recovery it shows samsung boot screen and see on top that it is going into recovery mode. after like 2 seconds it reboots and goes back to boot screen. i was able to get into download mode and flashed stock rom in odin. every things works fine as far as that. one strange thing is the phone sd card is pretty much full. i have done a factory reset every thing was back to normal. once again phone memory is full. i have loaded the root file on my ext sd card. load a recovery through odin. that works fine. still won't go into recovery. how can i fix this issue. i really just want the stock rom with recovery and root so i can run a few programs that require root. also how much extra space should i have on the phone memory after loading stock rom back up. any help would be greatly appreciated. btw this is not my first time having a rooted and custom rom phone. i had all that working on my htc amaze 4g.
Click to expand...
Click to collapse
Just press and hold volume down + power and once the blue letters " booting in recovery mode" show up let go you will be in recovery mode
rudyp9 said:
Just press and hold volume down + power and once the blue letters " booting in recovery mode" show up let go you will be in recovery mode
Click to expand...
Click to collapse
lol wow. don't know how that worked. every time before when i wanted to get into recovery i held it until it actually went into recovery. thanks:good:
My phone is verizon s4 sch-i545 when I try to boot up in recovery mode it shows booting in recovery but it just boots up normally .I wanted to do a factory reset but the factory reset just restarts my phone and when I try to get into recovery mode for a hard reset I cant boot into recovery mode. I don't know what to do
For recovery, try holding down the volume up, home and power button. Once the phone starts to boot, release the power button only. Keep pressing the volume up and home button. When you see the dead android, release all buttons.
Rahimwahid said:
My phone is verizon s4 sch-i545 when I try to boot up in recovery mode it shows booting in recovery but it just boots up normally .I wanted to do a factory reset but the factory reset just restarts my phone and when I try to get into recovery mode for a hard reset I cant boot into recovery mode. I don't know what to do
Click to expand...
Click to collapse
Odin stock firmware.
probablecauz69 said:
ok so i had posted lat night where for what ever reason after being rooted and having wicked rom running after doing a nandroid back up phone wouldn't go past boot screen. every time i try to go to recovery it shows samsung boot screen and see on top that it is going into recovery mode. after like 2 seconds it reboots and goes back to boot screen. i was able to get into download mode and flashed stock rom in odin. every things works fine as far as that. one strange thing is the phone sd card is pretty much full. i have done a factory reset every thing was back to normal. once again phone memory is full. i have loaded the root file on my ext sd card. load a recovery through odin. that works fine. still won't go into recovery. how can i fix this issue. i really just want the stock rom with recovery and root so i can run a few programs that require root. also how much extra space should i have on the phone memory after loading stock rom back up. any help would be greatly appreciated. btw this is not my first time having a rooted and custom rom phone. i had all that working on my htc amaze 4g.
Click to expand...
Click to collapse
Try rooting your phone and then you may install flashify app and reflashed your recovery. For more info visit - youtu.be/dUb7oISR6wA
my video where I hv solves this problem
Hi XDA Forums,
I have a problem with my Note 2 for some reason.
Let me explain you what is wrong with my Note 2
I was sitting down and watching a movie, my phone was right next to me, The phone randomly turned off and after couple of second it had turned back on. It had showed the first every screen when you turn it on "Samsung Galaxy Note 2 N7100". Now from there it keeps on looping the same screen over and over again.
I had done some research before opening this thread, I saw that some people said I should try factory resetting it from the recovery mode, I then tried going on the recovery mode, it was not successful, it had showed me the same "Samsung Galaxy Note 2 N7100" screen and then repeated to boot loop it self again, I tried going on the recovery a couple of times but it didn't let me go on it.
Next I had then downloaded the 4.1.2 Official Firmware from SamMobile to flash it to stock again, I had then tried going on the Download Mode, It goes to the screen for Download Mode, but when I try pressing up to continue from the warning message it had then rebooted it itself and made it self stuck on the screen again.
Basically, my phone is stuck on boot loop, It does not let me access the recovery mode and it also does not let me access download mode.
ROM Using: Tigra_RomV3 4.3 Based ROM
Kernel Used: The Kernel which comes with the ROM or Stock, I didn't change the kernel myself.
If there is a internal problem does that mean I wont get help from the Warranty because the phone was rooted?
hello,
just try to use the jig, it should work...
use it so your phone will be in download mode, then flash your rom
Do you NANDROID backup? Maybe you may restore it by custom recovery.
Second, remove the battery first for a while and retry to access the RECOVERY and DOWNLOAD mode. If not, try the suggestion up there.
I screwed up.
I wanted to install a new custom mod after purchasing a new SM-P605. I rooted my device, and searched for a while on how to install a custom recovery (TWRP). I downloaded ODIN and flashed it a couple of times but it didn't work, I kept getting a "recovery is not seandroid enforcing" and the screen freezes.
Then I tried Rashr's flash tool to install TWRP for me, and afterwards selected "boot into recovery".
Now i'm stuck in the same screen, but whenever I tried to restart, i get back to it, and can't get back in the system.
What can I do?
I'm unfortunately stuck in a very similar situation.
I was updating the firmware on my tablet to 4.4.2 downloaded off Sammy mobile, uploading using Odin. I've done this dozens of times since my S2 which was 12 handsets and 6 Android tablets ago. This time, about a third of the way through the process hung for a few minutes then the device restarted without warning and now its stuck in a loop where it starts normally
http://imgur.com/MTwiE5V [1]
Then says
RECOVERY BOOTING...
RECOVERY IS NOT SEANDROID ENFORCING
Set Warranty Bit : recovery.
Then this
http://imgur.com/Ua1nmhi [2]
and stays on that screen for short periods before rebooting and starting the above again.
Thanks in advance for any tips or help you guys can provide!
SleepyDonald said:
I screwed up.
I wanted to install a new custom mod after purchasing a new SM-P605. I rooted my device, and searched for a while on how to install a custom recovery (TWRP). I downloaded ODIN and flashed it a couple of times but it didn't work, I kept getting a "recovery is not seandroid enforcing" and the screen freezes.
Then I tried Rashr's flash tool to install TWRP for me, and afterwards selected "boot into recovery".
Now i'm stuck in the same screen, but whenever I tried to restart, i get back to it, and can't get back in the system.
What can I do?
Click to expand...
Click to collapse
Have tried factory reset/clear cache/clear dalvik?
shayind4 said:
Have tried factory reset/clear cache/clear dalvik?
Click to expand...
Click to collapse
Thanks, but it turns out the solution to my problem was simple. I took it to the place I got it from and the guy just pressed power, vol and menu button long enough until it rebooted. I'm quite a noob it seems.
I'm not sure if it will help you Nationalmaverick, because my problem was slightly different.
Hey!
I was trying to find this problem all around, but no luck. So I'm setting up new thread. Hope not to get redundant
A never rooted S4 mini died for no reason. In the morning we found it powered off and it couldn't be charged, other battery didn't help, nothing.
Long story short I managed to wake it up after complete dissassemble and playing with the battery connectors.
Now it starts up, but after the Samsung Logo it reboots = boot loop.
When I try to enter recovery, it tries to enter (I can see the blue "recovery booting"), but reboots immediately again.
The only thing that works is Download Mode.
So I used Odin to flash all CWM, PhilZ and TWRP subsequently. I got a bit further: in recovery mode it says "No command", then the usual "# MANUAL MODE #" etc and after few seconds it reboots again. So I still can't use recovery.
Does this all mean that the internal SD is fried?
I just need to recover the photos, that's all...
Thanks!
Marek
personic said:
Hey!
I was trying to find this problem all around, but no luck. So I'm setting up new thread. Hope not to get redundant
A never rooted S4 mini died for no reason. In the morning we found it powered off and it couldn't be charged, other battery didn't help, nothing.
Long story short I managed to wake it up after complete dissassemble and playing with the battery connectors.
Now it starts up, but after the Samsung Logo it reboots = boot loop.
When I try to enter recovery, it tries to enter (I can see the blue "recovery booting"), but reboots immediately again.
The only thing that works is Download Mode.
So I used Odin to flash all CWM, PhilZ and TWRP subsequently. I got a bit further: in recovery mode it says "No command", then the usual "# MANUAL MODE #" etc and after few seconds it reboots again. So I still can't use recovery.
Does this all mean that the internal SD is fried?
I just need to recover the photos, that's all...
Thanks!
Marek
Click to expand...
Click to collapse
Same problem with mine I can get in to download mode but recovery mode just says recovery booting then it turns off and back on again in the same loop ie it boots samsung screen then turns off then back on again and so on, I've tried CWM and TWRP odin says everything is good, but i get the same recovery booting and the loop again!
anything else i can try?
thanks
Hello everyone,
My phone (S4 mini GT-I9195) decided all of a sudden to stop working. I couldn't boot it, charge it, nothing but a black screen. After some research on the world wide web, I came to the conclusion that it might be "bricked", as the cool kids call it. I came upon a guide on this website that seemed promising: https://forum.xda-developers.com/showthread.php?t=2600869
I followed the instructions, found a debrick.img corresponding to my GT-I9195, put it on a sd card and managed to boot the phone.
Next was entering Download mode and flash with a stock firmware via Odin (v3.09). I used a 4.4.2 firmware I found on Sammobile (I9195XXUCNK4_I9195QXZCOA1_XEF) corresponding to my region and phone.
Everything went fine with Odin, I waited until it said "PASS!" and rebooted the phone.
The next step was to enter Recovery mode, and that's where I have a problem. I use the combination "Volume up + Home + Power" to enter it, it vibrates once, shows me the Samsung logo (+ model) with "Recovery booting...." written in blue on the top left corner, I release all the buttons, and after a few seconds, it goes to a black screen, it vibrates twice and reboot on the Samsung logo, but without the "Recovery booting..." message on top left corner. After that, it enters a bootloop that only ends when I remove the battery.
So, I can never enter the recovery mode (I tried multiple times, with different methods, such as releasing only the power button, but to no avail) and cannot complete the debrick guide. I tried different stock firmwares but always with the same result.
Did I do something wrong? What can I do differently to enter recovery mode? Should I prepare the funeral for my phone?
Thank you in advance for your answers.
You should try flashing cwm with odin, then formating your system partition, if you can externally put a rom on your memory card then do so, after that install that rom on your phone, if that doesn't work then try flashing your stock firmware after you had done everything...Of course I don't know if any of this will work because I haven't run into a issue like this before, though one time my recovery was blocked and flashing cwm on it fixed it, instead of flashing stock firmware I went for cyanogenmod (now lineage os) so it might work for you, who knows.
Well, first of all, thank you for your leads.
Secondly, as you suggested, I tried flashing with Odin, with CMW (6.0.4.6 and 6.0.5.1). It went smoothly in Download mode, I get the green PASS!, but just as before, when it reboots in Recovery mode, it doesn't go beyond the blue "Recovery booting...." step, instead, the dreaded bootloop begins.
I also tried flashing with TWRP (3.0.2.0), but unfortunately no change...
And without any custom recovery, I cannot try the lineage os.
I'm begining to feel the end ^^
paupiette said:
Well, first of all, thank you for your leads.
Secondly, as you suggested, I tried flashing with Odin, with CMW (6.0.4.6 and 6.0.5.1). It went smoothly in Download mode, I get the green PASS!, but just as before, when it reboots in Recovery mode, it doesn't go beyond the blue "Recovery booting...." step, instead, the dreaded bootloop begins.
I also tried flashing with TWRP (3.0.2.0), but unfortunately no change...
And without any custom recovery, I cannot try the lineage os.
I'm begining to feel the end ^^
Click to expand...
Click to collapse
I have TWRP on my mini. When I first flashed TWRP (3.0.2.1) via Odin, I had to manually boot into recovery by holding VolUp+Home+Power as soon as I see PASS!, BEFORE the phone automatically reboots.
I have to try this a couple times to get TWRP to stick. From what I read, if you let the phone boot automatically after flashing from Odin, it will automatically overwrite the new flash with stock Samsung recover (which is bad in your case.) So you have to interrupt this by a manual reboot before the phone does its thing. If you are successful, you should boot directly into TWRP on the manual reboot. From then on TWRP will overwrite the stock recovery and you will be good to go.
I find the timing of this manual reboot a bit tricky on the phone. Do it too soon, and the TWRP was not flashed, a second too late, and the phone boots to stock. I had to try that a few times to get it right. Basically, be ready with the buttons and press it the instant you see PASS! So maybe you can try flashing TWRP again before giving up.
I have encountered the same problems today. After waking up, my phone (S4 Mini) told me an update (17 MB) was available. Happy about still getting updates, I started the process and the telephone rebooted. When returning ten minutes later it was all dark and wouldn't respond to any button combination. After working through a lot of threads and forums, trying to fix the problem, I managed to get a debrick image for the phone as well as the right firmware from Sammobile (which is astonishingly the same one that paupiette uses, though I'm from Germany, but the phone seems to have a French regional code).
At first I wasn't able to get to the Download Mode, instead my phone always told me this while denying my attempts to flash it:
BOOTE RECOVERY MODE
CHECK BOOT PARTITIONS..
COPY FROM T-FLASH..
BOOT RECOVERY..
WRITE 139008 sectors..
FLASH WRITE FAILURE
ddi: mmc_read failed
ODIN MODE
PRODUCT NAME: GT-I9195
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
KNOX KERNEL LOCK: 0x0
KNOX WARRANTY VOID: 0x0
CSB-CONFIG-LSB: 0x30
BOOTLOADER RPSWREV: 2
WRITE PROTECTION: Enable
Nothing seemed to work and some other topics on different forums blamed the internal flash chip (eMMC) to be the cause for all the trouble. I gave up on my phone, loosening the skrews on the back to get a look on the board. Before ripping apart the last bits, I tried to start the Download Mode one more time, so I put in the battery and hold the three buttons. Et voilà - the phone came up with that white booting screen. It was looping this process over and over as paupiette had allready described. I managed to start the Download Mode and flash with Odin3 (v3.12). A green "PASS!" told be, it worked until it began to enter the loop of rebooting again unable to enter the Recovery Menu.
So close but yet so far away from what I want.
Any new ideas or suggestions?