Hello,
I´ve got a problem with my Samsung Galaxy S5
The History:
I bought a Samsung Galaxy S5 SM-G900f from Ebay with a Software Problem. The seller said, he try to flash a Custom Room like Cyanogenmod, he don´t know which)
The flash failed (i don´t know why). Now the S5 have a brick.
I tried so much, but i can´t repair it, pls help me.
The Problem is:
I can not start the Recovery Menü to flash a new Custom room. Always i tried to start the Menü, there is just a text "recovery Booting", then the phone restarts after round about 10 sec.
So even if i tried to start the S5 normally without recovery Menü, it´s just the Samsung Galaxy S5 Logo power by Android, then the phone restarts all the time.
The only thing i can do is start the download mode.
Things i tried:
- Firmware installation about Kies (pass, but still the Same Problem)
-Firmware Installation about Odin (pass, but still the same Problem)
- CF-Autoroot flashing (pass) then i tried to flash a recovery like PhilZ but then when i tried to open the recovery it`s "Recovery is not seandroid enforcing" Set Warranty bit
I tried so many firmwares but still the same Problem. Now it is installed Lollipop 5.0 G900FXXU1BOI3_G900FDBT1BOI1_G900FXXU1BOI3_HOME
There is no chance to repair it over ADB oder Fastboot, cause USB-debugging is disabled
Maybe you can help me and help me to stop spend all my time for this phone, cause im interested to know how i can repair it.
flash twrp from odin
then sideload a rom
install the rom
tell me if it works
.
I tried to install twrp 2.7.0.0-klte with odin. It´s pass, but when i tried to boot into Recovery he said "recovery is not seandroid enforce" Set Warranty bit: recovery
Pls help me i´ve got no idea more
Try this hold on (power volume up and home) then do not release until recovery mode boot
sh4dow6oy said:
flash twrp from odin
then sideload a rom
install the rom
tell me if it works
Click to expand...
Click to collapse
I tried to install twrp 2.7.0.0-klte with odin. It´s pass, but when i tried to boot into Recovery he said "recovery is not seandroid enforce" Set Warranty bit: recovery
Pls help me i´ve got no idea more
With some of the newer LP based firmwares, twrp 2.8.7.0 klte is the only version that works.....
Other than that, you might find it necessary to odin back to KitKat (flashing a pit file too) and try 'towelrooting' your device.......
BE WARNED.......If you *do* flash a pit file, make sure it's the CORRECT pit for your device.....In some cases, flashing the wrong pit will permanently kill a device.
http://i.imgur.com/rVnFwJM.jpg
So i had try it.
1.)hold on ( volume up and home) then do not release until recovery mode boot
--> The phone always restart no recovery is possible
2.) I try to install on LP the TWRP 2.8.7.0 Still the Same error "recovery is not seandroid enforce" Set Warranty bit: recovery
Before i root the device with CF-Autoroot and it´s pass
3.) I downgrade to 4.4.2 with a full package of Firmware with CSC,BL,AP,CP and a pit file.
The downgrade pass, when the phone starts it says recovery booting in blue script, then the phone restarts. I can´t intstall towelroot, cause the system is not booting, so i´d tried to install CF-Autoroot (pass) and then also the TWRP 2.7.0.0 pass but not booting and then 2.8.0.0.
But still the same "recovery is not seandroid enforce" Set Warranty bit: recovery
If you got a pass on your KK flash, you have a stock recovery......
Have you tried booting into that recovery and wiping cache and factory resetting? It is necessary to do this when downgrading......
http://i.imgur.com/rVnFwJM.jpg
Yes it was a KK stock recovery.
I tried to boot in this recovery, but when the phone starts it says recovery booting in blue script, then the phone restarts after a few seconds.
It´s not possible to wipe cache or make a factory reset, cause the recovery is not booting. That´s my problem. Also when i have flash the stock firmware i tried to go into the recovery but when the phone starts it says recovery booting in blue script, then the phone restarts after a few seconds. ( 4.4.2 and 5.0)
I´can´t flash a custom rom cause the recovery is not booting. I´ve no idea
Are you attempting the 3 button combination from powered off to get into recovery?........
@'detection' does the OP's situation sound familiar?.....
http://i.imgur.com/rVnFwJM.jpg
Very familiar -
https://dl.twrp.me/klte/
Flash TWRP 2.8.7.0 .TAR (Do not unzip) with ODIN 3.10.7 - in Download mode (Volume Down & Home & Power)
It will say "recovery is not seandroid enforce" Set Warranty bit" at the top when you boot into recovery, give it a few seconds and you should see the TWRP blue splash screen, and then recovery should load up
Then flash a custom ROM from TWRP
--
If that all still fails, try flashing the PIT file for the G900F along with a Stock ROM
http://forum.xda-developers.com/attachment.php?attachmentid=2721101&d=1399024091
Extract this one so it is .PIT, and add it to ODINs PIT section
If that still fails, try flashing just the PIT file with ODIN, and then the TWRP 2.8.7.0 with ODIN and see if you can get in that way
Or PIT and TWRP together
Try a combination until you get back in
Also try different versions of TWRP from 3.07 up to 3.10.7
keithross39 said:
Are you attempting the 3 button combination from powered off to get into recovery?........
@'detection' does the OP's situation sound familiar?.....
Yes i did, than the it happen what i wrote upside
What do you mean with "@'detection' does the OP's situation sound familiar?....."
Click to expand...
Click to collapse
It sounds familiar because it's happened to many other people recently too, although TWRP usually fixes it
Follow my instructions above
No chance guys,
i´d tried to install all TWRP which i found once in 5.0 and also i tried to install on 4.4.2. But always the same mistake. (recovery is not se.....)
Now i´ve tried to install CWM-Recovery and now there is no mistake like upside. Now in blue "recovery booting" and in yellow set warranty bit: recovery
But the recovery is not booting, the phone always make a restart. I´d also tried to install the recovery without auto-reboot in odin. But no help.
I don´t understand, cause when i flash a Stock Firmware, the recovery menu ,in my opinion, it have to start, but it doesn´t. Maybe i have anexpensive paper weight now
I search the internet to install a Custom room over Odin, but i don´t find any results, so i think it is not possible.
Do you have more ideas? Pls help. Thanks
I have the exact same problem, some are calling it the Black Screen of Death (with the blue led flicker). This is what happened to me:
0) had TWRP + latest 12.1 Cyanogenmod
1) installed the alpha 13 Cyanogenmod, which worked, more-or-less...
2) lost access to TWRP recovery, did not lose access to download
3) tried every single type of black magic from XDA (Kies, pit files, bootloader files, etc)
4) now it turns on, the LED turns blue and slowly, slowly flickers, but the screen is blank. At some point it plays the Samsung boot sound
Any help will be enormously appreciated.
check PM
bowzee said:
I have the exact same problem, some are calling it the Black Screen of Death (with the blue led flicker). This is what happened to me:
0) had TWRP + latest 12.1 Cyanogenmod
1) installed the alpha 13 Cyanogenmod, which worked, more-or-less...
2) lost access to TWRP recovery, did not lose access to download
3) tried every single type of black magic from XDA (Kies, pit files, bootloader files, etc)
4) now it turns on, the LED turns blue and slowly, slowly flickers, but the screen is blank. At some point it plays the Samsung boot sound
Any help will be enormously appreciated.
Click to expand...
Click to collapse
Another idea?
Joda899 said:
Another idea?
Click to expand...
Click to collapse
Ithink you should try re instal original firmware using odin and get ur warranty back then fix it on samsung
I found a trick that seems to help slightly, until an actual solution is published. During a misbehave episode, assuming that something shows up (which is not always the case):
1) press <power + home + vol-down> until the download thing shows up
2) press <up-arrow> so that it actually gets into download mode
3) press <power> until the screen turns off and immediately release (otherwise it will try to reboot); this makes it stay off
4) let it "rest" for a certain period of time (could be 5 minutes or more)
5) back to normal
Did u root your device vai CF auto root? Did it work?
Heya
I followed a guide to download odin and CF auto Root-k3g-k3gxx-smg900h. I installed odin, booted into download and loaded the cf autoroot.
It takes a while before going to blue "RESET" and then my phone keeps showing the samsung logo.
After 2min Odin shows a green "PASS".
However I'm now stuck with a phone that won't boot and keeps showing the samsung logo.
I have tried the advice given in http://forum.xda-developers.com/showthread.php?t=2725939
Any advice would be appreciated.
After flashing with Odin did your recovery boot and do its thing, or did your phone reboot and just hanged on the Samsung screen? If the latter occurred, try repeat the entire Odin process again.
Heya.
I repeated the process, but while it says "Blue Reset" it's still sits at the samsung logo. The only way to then reboot is to take the battery out and put it back in. Then when I press vol up+pwr+home; nothing happens except the logo. No recovery mode.
The only thing that I seem to have access to is the Downloading.
Xi41 said:
Heya.
I repeated the process, but while it says "Blue Reset" it's still sits at the samsung logo. The only way to then reboot is to take the battery out and put it back in. Then when I press vol up+pwr+home; nothing happens except the logo. No recovery mode.
The only thing that I seem to have access to is the Downloading.
Click to expand...
Click to collapse
Flash stock ROM again with ODIN
Don't use CF AR to root again, some phones just brick like that
Flash TWRP recovery, then SuperSU from TWRP instead
Hello,
I decided to try and root my phone yesterday in order to use flux and the AdAway for my Samsung Galaxy Note 3 SM-N9007. However when i used Odin instead of saying "Pass" it was saying "Reset". As it was my first time doing anything like this, I unplugged my phone which seemed to have been the wrong move. My phone would vibrate once or twice and then reboot to show me the Samsung logo and the words "Recovery is not Seandroid forcing". It would show that screen for approximately 2 seconds where it turns off and repeats the process. Whilst off for that period of time I cannot enter recovery mode. However I can enter the download mode (vol. down + power). I have researched a bit on what to do however I am still a bit unsure.
*It seems the main problem is I can not enter recovery mode at all. As the logo shows it just turns off instantly and then turns back on getting stuck in a loop.
What I gathered online.
- Download the stock firmware for it. (The file I'm downloading is roughly 1.3 gb)
- Load the file the same way I tried to root the phone.
Is this correct? Could I get some assistance please?
Thank you
I have managed to resolve the error by loading in the stock firmware with Odin.
Heize_July said:
I have managed to resolve the error by loading in the stock firmware with Odin.
Click to expand...
Click to collapse
Just so you know, it's normal for the message: "Recovery is not Seandroid forcing" to appear when you root the phone.
Also, if you unplugged the phone after it said "Pass", then theoretically you shouldn't have a problem.
So the steps for a successful root would be:
1. Flash stock
2. Flash custom recovery (TWRP)
3. Flash superSU.zip file from custom recovery
And you should now be rooted
ShaDisNX255 said:
Just so you know, it's normal for the message: "Recovery is not Seandroid forcing" to appear when you root the phone.
Also, if you unplugged the phone after it said "Pass", then theoretically you shouldn't have a problem.
So the steps for a successful root would be:
1. Flash stock
2. Flash custom recovery (TWRP)
3. Flash superSU.zip file from custom recovery
And you should now be rooted
Click to expand...
Click to collapse
Yea I made the mistake of choosing the wrong CFRoot file. The one I installed was for Android version 4.3 whereas my device was 5.0. After retrying I manged to get the root to work. Thanks anyways!
As the title says I tried to root my phone and got into this situation. I followed a video from TheUnlockr
I put my phone into developer mode and the OEM unlock.
I completed the Odin3 boot img using Samsung_G935x_QC_Rooted_BOOT.TAR file that I got from XDA developers. It said it passed
Afterwords I'm stuck in the reboot loop. I can get into the the teal custom OS download screen as well as the recovery booting screen that does the "Installing system update" animation and I get a "No Command" screen with a dead Android, after a bit it lets me into the Android Recovery screen. I've tried Reboot system now, no go, reboot to bootloader no joy that goes to the "Downloading... Do not turn off target" message.
I believe my bootloader got gorked with the rooted boot.
How can I get back to just a usable OS? I've downloaded the stock firmware from Sammobile but that's taking 2-3 hours. Am I just until that finishes downloading?
Yeah, wait until file finishes and than of course flash with odin. Sometimes Sammobile is slow, you may try downloading firmware from uptodato.com (if you've fast internet connection).
Hi All,
Got a S5 G900I here that's doing my head in! Stuck in the infamous bootloop at the Samsung logo.
I have been a long time reader of these forums and have prior experience from flashing Samsung phones but this one is driving me mad!
I can put the phone into Download mode without an issue, phone is detected in Odin and I can flash any firmware I try to it (Have tried original 4.4.2 , 5.0 and latest 6.0.1 firmwares from SamMobile). Odin goes through the entire process, reports as "Pass" but then the device goes straight back into the reboot loop and will never fully boot up.
I can also use Odin to push TWRP / CWM / PhilzTouch recoveries, however the device will never boot into the recovery partition. I get the blue "Recovery Booting" message briefly, then the device bootloops again.
Does anyone have any further suggestions to try and get this phone operational again?
I have tried multiple versions of Odin, multiple firmware versions, different computers, different USB cables, different USB ports etc.
I look forward to hearing back from you
Try this :
1. Make sure flash latest recovery with latest ODIN version. Check the official website.
2. Do not let your phone restart after flash recovery with ODIN. Un-check auto reboot on option tab in ODIN. After PASS flash recovery disconnect USB cable then ummm ... I do not know what about your phone .. Mine G900D, I just just pull the battery then I plug it again lol ..: D
3. It should be able to get into recovery after that. If not, it means the recovery type does not match your phone.
andra.soul.catcher said:
1. Make sure flash latest recovery with latest ODIN version. Check the official website.
2. Do not let your phone restart after flash recovery with ODIN. Un-check auto reboot on option tab in ODIN. After PASS flash recovery disconnect USB cable then ummm ... I do not know what about your phone .. Mine G900D, I just just pull the battery then I plug it again lol ..: D
3. It should be able to get into recovery after that. If not, it means the recovery type does not match your phone.
Click to expand...
Click to collapse
Have tried latest stock recovery and latest TWRP recovery using latest ODIN v3.13.1 as well as ODIN v3.09 and v3.10 - No difference whether I uncheck or check auto reboot either
Phone still stuck in a constant reboot loop and never gets to recovery
AS93 said:
Have tried latest stock recovery and latest TWRP recovery using latest ODIN v3.13.1 as well as ODIN v3.09 and v3.10 - No difference whether I uncheck or check auto reboot either
Phone still stuck in a constant reboot loop and never gets to recovery
Click to expand...
Click to collapse
It is important to turn off the phone right after flash recovery on the download screen. I mean really off rather than reboot. unplug the battery do not turn off with the power button. Because when rebooted, recovery will automatically return to stock .. so the recovery you just installed will be erased again. if stock recovery inside is broken you will get bootloop. if it is done and still can not enter recovery .. huum .. I am afraid if it's a hardware problem .. because it's easier to find a suitable recovery than its firmware. if recovery can not be in flash .... it's a long way to go ..
By the way, sorry for ask .. you release the power button when it says "recovery booting" with blue text.. right ..? while continuing to hold the volume up..?
andra.soul.catcher said:
It is important to turn off the phone right after flash recovery on the download screen. I mean really off rather than reboot. unplug the battery do not turn off with the power button. Because when rebooted, recovery will automatically return to stock .. so the recovery you just installed will be erased again. if stock recovery inside is broken you will get bootloop. if it is done and still can not enter recovery .. huum .. I am afraid if it's a hardware problem .. because it's easier to find a suitable recovery than its firmware. if recovery can not be in flash .... it's a long way to go ..
By the way, sorry for ask .. you release the power button when it says "recovery booting" with blue text.. right ..? while continuing to hold the volume up..?
Click to expand...
Click to collapse
Thanks for the quick reply.
Yes when I am booting into recovery mode and can see the blue text "Recovery Booting" in the corner of the screen I let go of the power button - device still boot loops.
Have flashed recovery then removed battery - still cannot get it into recovery.
I have seen some Samsungs have hardware issues with their NAND chips but in these cases there are a lot of errors relating to NAND displayed on the screen when I've seen it be a hardware issue. None of these appear on this phone - convinced it has something to do with software.
I found these threads - exactly the same issue as me, and at the end it says they fixed it by flashing a specific bootloader however I have a G900I and the phone in this thread was a G900F
https://forum.xda-developers.com/galaxy-s5/help/bricked-s5-sm-g900f-boot-to-recovery-t3280926/
https://forum.xda-developers.com/galaxy-s5/help/samsung-s5-sm-g900f-stock-flash-caused-t3771105
https://forum.xda-developers.com/galaxy-s5/help/bricked-s5-sm-g900f-boot-to-recovery-t3280926
Have tried countless different versions of ODIN / recovery / stock firmware , including the "service firmware with the separate files G900IDVU1BOE1_CL4826466_QB4839040_REV00_user_low_ship_MULTI_CERT"