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.
Related
Hi,
I've attempted the JB update
http://forum.xda-developers.com/showthread.php?t=1737899..
fastboot flash boot boot.img etc.. which said all was well..
But now find that my phone will not boot up, doesn't get past the Google and unlock screen.
I've tried all combinations of volume buttons, I can get to the fasboot menu where I can choose either Recovery Mode, Power Off, Start or Restart bootloader.
None of these appear to do anything, recovery goes to the google a screen followed by an Android on it's back with an exclamation mark over it.. then goes to the Google and unlocked icon screen and stays there...
I fear my phone is bricked... Please help..
bevnet said:
Hi,
I've attempted the JB update
http://forum.xda-developers.com/showthread.php?t=1737899..
fastboot flash boot boot.img etc.. which said all was well..
But now find that my phone will not boot up, doesn't get past the Google and unlock screen.
I've tried all combinations of volume buttons, I can get to the fasboot menu where I can choose either Recovery Mode, Power Off, Start or Restart bootloader.
None of these appear to do anything, recovery goes to the google a screen followed by an Android on it's back with an exclamation mark over it.. then goes to the Google and unlocked icon screen and stays there...
I fear my phone is bricked... Please help..
Click to expand...
Click to collapse
1.) Your phone is far from bricked at all. You have access to the boot loader (i.e. the screen with the options). The recovery you're seeing is stock recovery. All you need to do is go into boot loader and fastboot flash recovername (CWM) and you will have your custom recovery back to wipe data and reinstall a rom or restore a nandroid backup
Mine is doing the same thing, weird thing is, it was working since yesterday on jellybean, it just randomly froze this morning and and now won't boot..
im currently at work so i don't have admin rights to do a fastboot flash..
any idea why it would randomly stop working when i havn't flashed anything on it besides the jb rom?
Sorted..
Thanks for the comments.. yeah i was over-reacting a bit there..
I downloaded the Galaxy Nexus Toolkit, got a stock rom form gopogle, flashed it.. back to normal, well, it will be after i restore the CWM backup i took.. phew..
Thanks again
Ian.
Still stuck
I'm also stuck in the same situation(google with the unlock screen). I fear I'm a little more stuck. I also can see the recovery/restartbootloader screen. However, everything I try still comes back to that same google screen and gets hung up. Need some help!
this has happened twice today and i think it from using volume+
Steelbully said:
I'm also stuck in the same situation(google with the unlock screen). I fear I'm a little more stuck. I also can see the recovery/restartbootloader screen. However, everything I try still comes back to that same google screen and gets hung up. Need some help!
Click to expand...
Click to collapse
Boot into recovery, wipe cache, Reboot
Hey guys
A friend of mine was flashing his Galaxy Note 3 GT-P5200 and it suddenly froze, then it restarted.
Now at every restart, it's stuck in a recovery loop.
I can still access donwload mode, and I've tried flashing several firmwares with Odin but it still reboots directly to the recovery mode and restarts.
I've tried flashing different recoveries, but it still reboots every time.
Is it hard bricked ?
If it is, what are the solutions ?
Thank you
hamidv2 said:
Hey guys
A friend of mine was flashing his Galaxy Note 3 GT-P5200 and it suddenly froze, then it restarted.
Now at every restart, it's stuck in a recovery loop.
I can still access donwload mode, and I've tried flashing several firmwares with Odin but it still reboots directly to the recovery mode and restarts.
I've tried flashing different recoveries, but it still reboots every time.
Is it hard bricked ?
If it is, what are the solutions ?
Thank you
Click to expand...
Click to collapse
If it stays in recovery mode long enough to perform a cache wipe, try that. Then a full data wipe/factory reset. If you can't get that to work, then I have no other ideas. You did flash a full firmware package in Odin, correct?
gr8nole said:
If it stays in recovery mode long enough to perform a cache wipe, try that. Then a full data wipe/factory reset. If you can't get that to work, then I have no other ideas. You did flash a full firmware package in Odin, correct?
Click to expand...
Click to collapse
Unfortunately it doesn't stay on the recovery mode even half a second.
It restarts right away.
And yeah, I've flashed the correct files again and again but the problem persists.
I guess it just went to electronics heaven ...
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 guys,
Thank you for reading, any help is appreciated.
My device was running the latest release of CM13 (cm-13.0-20160418-SNAPSHOT-ZNH0EAO2NK-serrano3gxx) and TWRP v3.0.2-1
So yesterday afternoon my phone randomly shutdown and I was unable to get it turned back on until this morning.
However though when i did manage to get it powered on after hours of failed tries it was stuck on the Samsung boot screen.
I've since tried to access the TWRP Recovery (Pwr + Vol Up + Home) but it sticks on the TWRP slash screen and then attempts to reboot normally (which as i said stick on the Samsung boot screen).
I also tried re-installing TWRP via Odin and it appears to be installing properly and successfully but when i attempt to access TWRP it again sticks on the splash screen,
I've also tried installing CWM Record via odin and that also appears to be installing properly and successfully but when I attempt to access the recovery I am yet again greeted with the TWRP Slash Screen which has lead me to believe something is going wrong.
Any ideas or suggestions as to what may be going on here ?
Thanks in advance, any help is appreciated.
Hey again guys,
I have tried installing stock rom via Odin, It says Pass but nothing at all seems to be changing.
I'm beginning to think Odin may really not be working at all or something is wrong with the phone
Update: I tried flashing TWRP recovery via Heimdall and it appears to have completed successfully saying "RECOVERY upload successful" but when i reboot immediately after into Recovery mode it still sticks at the TWRP 3.0.0-0 Splash Screen then attempts to reboot normally which as mentioned earlier also sticks on samsung slash screen
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?