Database Users

Cannot access recovery also flash stock rom via odin

Hi everybody. First of all sorry for my bad english. I just got a new i9500 galaxy S4 and I would like to flash a cyanogenmod rom. So i flashed twrp recovery via odin v3.09 with the "PASS" success message. But when when i tried to boot the phone in recovery mode it gets stuck on black screen samsung start up logo with the message "recovery booting..." in the top left corner of the screen. I've decided to flash a stock rom thinking it will solve it. But when i tried to flash with odin i got a fail message in odin and a "unsupport dev_type" red message on the phone screen. Now I cannot access the recovery but normal boot and download mode work with no problem. And I also cannot flash a stock rom via odin.
Help me. I really need to flash custom rom

Samsung Galaxy S5 SM-G900F No Recovery Mode always restart Brick

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?

Samsung Galaxy S5 SM-G900F 5.0 stuck during root

This is not the first time i root an android device but it is the first time im doing it on an S5, nonetheless I am pretty much stuck right now.
I tried to install CF-Auto-Root-klte-kltexx-smg900f.tar using Odin from here, it installed with no problems, but when the phone restarted I get:
RECOVERY BOOTING
RECOVERY IS NOT SEANDROID ENFORCING
Set Warranty Bit: recovery
and then it shuts down.
I tried to enter recovery mode by doing power+vol up+menu but nothing happens ?
Can anyone help ?
EDIT: ok, so I did manage to get it running again by flashing openrecovery-twrp-2.8.5.0-gt-klte. This got me past the "Recovery is not seandroid...", but all in all I still didn't manage to get root access...

I passed through a similar situation , all u have to do once u've got the recovery is get the SuperSU flashable zip and flash it and ur done
Here is a direct link : https://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip?retrieve_file=1

This happened to me also. I am running XXU1BOJ1 . I flashed twrp-2.8.7.0-klte.img and even though it solved getting stuck at recovery, my phone still boots into the standard recovery instead of TWRP when pressing VOLUP+Home+Power. Anyone got ideas?

xmun said:
This happened to me also. I am running XXU1BOJ1 . I flashed twrp-2.8.7.0-klte.img and even though it solved getting stuck at recovery, my phone still boots into the standard recovery instead of TWRP when pressing VOLUP+Home+Power. Anyone got ideas?
Click to expand...
Click to collapse
You don't flash .img - you flash .tar

*Detection* said:
You don't flash .img - you flash .tar
Click to expand...
Click to collapse
I did flash .img.tar actually. Still no effect - boots to regular recovery. Can't figure this out...

i get in the same situation...why still rebooting in original recovery?
i installed this one CF-Auto-Root-klte-kltexx-smg900f.tar with odin with succes but still have
RECOVERY BOOTING
RECOVERY IS NOT SEANDROID ENFORCING
Set Warranty Bit: recovery
then when i boot i get a black screen with all application error....the only way to get it back working was to wipe factory reset in original recovery.
what can i do to get it working so i can install custom roms?
thx in avance

seaskyways said:
I passed through a similar situation , all u have to do once u've got the recovery is get the SuperSU flashable zip and flash it and ur done
Here is a direct link : https://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip?retrieve_file=1
Click to expand...
Click to collapse
I can't seem to get the coustom recovery installed, and after some digging i found this :
manubhargav said:
Actually the problem was that custom recovery(twrp here) was not installed at all, that above mentioned error occurs when you try to install SuperSU.zip from stock recovery<3e>.
This happens because when you flash custom recovery from Odin and allow it to reboot on its own, Samsung's recovery checking script checks if a custom recovery is present and overrides.
To bypass that check you need to take your battery out as soon as the recovery is flashed by Odin ( and before the phone reboots).
As soon as the Odin says PASS you should be ready to take out the battery which will stop it from rebooting,
put back the battery and enter recovery mode directly by pressing and holding Volume Up, Home and Power keys at the same time.
Release all three buttons when Samsung Galaxy S5 screen flickers and the main screen of Recovery mode appears.
This will avoid script checking and will let you to custom recovery directly,there you can install SuperSU or any other zip.
Click to expand...
Click to collapse
The thing is, when i try to do that, and then get into recovery i get
Could not do normal boot.
ODIN MODE.
Any help ? Please ? The bloatware is driving me nuts :crying:

VL4DST3R said:
I can't seem to get the coustom recovery installed, and after some digging i found this :
The thing is, when i try to do that, and then get into recovery i get
Could not do normal boot.
ODIN MODE.
Any help ? Please ? The bloatware is driving me nuts :crying:
Click to expand...
Click to collapse
Maybe your phone is not recognized in Download Mode as corresponding drivers may not be properly installed. So Computer is not able to recognize the phone when in Downlaod mode. Install SM Bus Controllers drivers from Intel from Official driver source.
After setting-up you'll be able to flash TWRP and boot into recovery mode.
---------- Post added at 05:36 AM ---------- Previous post was at 05:32 AM ----------
xmun said:
This happened to me also. I am running XXU1BOJ1 . I flashed twrp-2.8.7.0-klte.img and even though it solved getting stuck at recovery, my phone still boots into the standard recovery instead of TWRP when pressing VOLUP+Home+Power. Anyone got ideas?
Click to expand...
Click to collapse
Actually the problem of custom recovery (TWRPhere) not installed at all, stock recovery<3e> persists after reboot because when you flash custom recovery from Odin and allow it to reboot on its own, Samsung's recovery checking script checks if a custom recovery is present and overrides.
To bypass that check you need to take your battery out as soon as the recovery is flashed by Odin ( and before the phone reboots).
As soon as the Odin says PASS you should be ready to take out the battery which will stop it from rebooting,
Put back the battery and enter recovery mode directly by pressing and holding Volume Up, Home and Power keys at the same time.
Release all three buttons when Samsung Galaxy S5 screen flickers and the main screen of Recovery mode appears.
This will avoid script checking and will let you to custom recovery directly,there you can install SuperSU or any other zip.

manubhargav said:
Maybe your phone is not recognized in Download Mode as corresponding drivers may not be properly installed. So Computer is not able to recognize the phone when in Downlaod mode. Install SM Bus Controllers drivers from Intel from Official driver source.
After setting-up you'll be able to flash TWRP and boot into recovery mode.
Actually the problem of custom recovery (TWRPhere) not installed at all, stock recovery<3e> persists after reboot because when you flash custom recovery from Odin and allow it to reboot on its own, Samsung's recovery checking script checks if a custom recovery is present and overrides.
To bypass that check you need to take your battery out as soon as the recovery is flashed by Odin ( and before the phone reboots).
As soon as the Odin says PASS you should be ready to take out the battery which will stop it from rebooting,
Put back the battery and enter recovery mode directly by pressing and holding Volume Up, Home and Power keys at the same time.
Release all three buttons when Samsung Galaxy S5 screen flickers and the main screen of Recovery mode appears.
This will avoid script checking and will let you to custom recovery directly,there you can install SuperSU or any other zip.
Click to expand...
Click to collapse
The drivers are installed, and Odin sees my phone just fine, also the thing with removing the battery before it restats leads me to the error i mentioned above...

VL4DST3R said:
The drivers are installed, and Odin sees my phone just fine, also the thing with removing the battery before it restats leads me to the error i mentioned above...
Click to expand...
Click to collapse
Ah, So the problem you're facing is NOT getting into recovery mode
There are 2 ways to solve the problem, (1st -> flashing recovery.tar again, 2nd-> flashing stock firmware)
First method:
Enter "Download Mode" by holding down "Volume Down"+ "Home" + "Power" button.
Flash recovery.img again and check if it boots into recovery this time.
Sometimes this may not work and you may need to try flashing firmware
Second method:
Download Firmware from here
Open odin in your PC
Enter "Download mode"
Connect the device to PC using USB
Flash the PDA, BL, AP, CSC etc.
Alternatively, You can flash the firmware using SmartSwitch

manubhargav said:
Ah, So the problem you're facing is NOT getting into recovery mode
Click to expand...
Click to collapse
Oh but it is! That's exactly my problem. Look, here are the 3 outcomes I get regarding the whole recovery menu thing:
Go into the default recovery menu - cant install SuperSU but at least it works.
Install twrp and remove the battery after it finishes transfering and wants to restart, at which point when I go into recovery I get the above error (Could not do normal boot. ODIN MODE.)
Install twrp and let it restart by itself and after it is done, go into recovery only to find it is back to the default one.

VL4DST3R said:
Oh but it is! That's exactly my problem. Look, here are the 3 outcomes I get regarding the whole recovery menu thing:
Go into the default recovery menu - cant install SuperSU but at least it works.
Install twrp and remove the battery after it finishes transfering and wants to restart, at which point when I go into recovery I get the above error (Could not do normal boot. ODIN MODE.)
Install twrp and let it restart by itself and after it is done, go into recovery only to find it is back to the default one.
Click to expand...
Click to collapse
Which Kernel version are you in? Which TWRP version did you try? Install other custom recoveries? On locked bootloader?

Ok, I tried CWM and nothing changed, i get the default recovery menu...
Doing the shut down before it restarts gets me "recovery is not seandorid enforcing"

VL4DST3R said:
Ok, I tried CWM and nothing changed, i get the default recovery menu...
Doing the shut down before it restarts gets me "recovery is not seandorid enforcing"
Click to expand...
Click to collapse
Turn OFF Auto-Reboot option in ODIN and flash the recovery.tar and remove battery and directly boot into recovery mode.
Go into a working custom recovery (CWM or TWRP) and flash SuperSU.zip from the recovery and reboot with ("Fix permissions" if there is such an option, otherwise simply reboot).

manubhargav said:
Turn OFF Auto-Reboot option in ODIN and flash the recovery.tar and remove battery and directly boot into recovery mode.
Go into a working custom recovery (CWM or TWRP) and flash SuperSU.zip from the recovery and reboot with ("Fix permissions" if there is such an option, otherwise simply reboot).
Click to expand...
Click to collapse
Tried that already, and as I said, I can't get a custom recovery working, it either resets to the default one or I get the "recovery is not seandorid enforcing" error.

VL4DST3R said:
Tried that already, and as I said, I can't get a custom recovery working, it either resets to the default one or I get the "recovery is not seandorid enforcing" error.
Click to expand...
Click to collapse
1)
Ah use latest twrp 2.8.70
Ah use latest supersu beta 2.52
Quick download cm12.1 nightly and flash it.
Boot Rom and go into settings/aboutphone/ click build number rapidly.
Developer settings should appear, then go into developers options/ click on "root access" and enable it.
---- now test if its working . however....
2)
If its not working, take yourself back into twrp and flash that supersu beta.
----now test again. However ....
3)
If it doesn't work again .
go back to stock 5.0 rom>>> put twrp on >>> and flash DAT supersu .
now test ya rom again. However.........
4)
If it dont work again ..
go back to stock 4.4 rom>>> put twrp on>>> and flash a random supersu.
now test ya rom again. However.....
5)
if that doesn't work again,
Go back to stock rom through (odin) and restart the process from the top .
btw the "recovery is not seandorid enforcing" is normal . not an error.

GeniusisHere said:
1)
Ah use latest twrp 2.8.70
Ah use latest supersu beta 2.52
Quick download cm12.1 nightly and flash it.
---- now test if its working . however....
2)
----now test again. However ....
3)
If it doesn't work again .
now test ya rom again. However.........
4)
If it dont work again ..
now test ya rom again. However.....
5)
if that doesn't work again, .
Click to expand...
Click to collapse
First of all holy **** what an answer... let's SLOW DOWN a bit first, shall we ?
Secondly you lost me from step 1, I don't want CyanogenMod, I want the default Samsung 5.0 with TouchWiz (contrary to popular belief I actually like it).
Also I would really like to know (from someone that actually knows why this happens) why is it reverting to default recovery and how can I stop it from doing so ? manubhargav had an interesting idea, but sadly it doesn't work for everyone (as someone else mentioned on that other post)

So I'm guessing no one knows the answer to my problem considering almost a moth has passed...

I know that in kitkat the answer was to turn off / disable 'Reactivation Lock' (located under settings>>security and unchecking the box)........
I had heard that Samsung had removed that option in lollipop, but it might be worth checking......it has/had to be disabled BEFORE attempting to flash anything......
http://i.imgur.com/rVnFwJM.jpg

keithross39 said:
I know that in kitkat the answer was to turn off / disable 'Reactivation Lock' (located under settings>>security and unchecking the box)........
I had heard that Samsung had removed that option in lollipop, but it might be worth checking......it has/had to be disabled BEFORE attempting to flash anything......
http://i.imgur.com/rVnFwJM.jpg
Click to expand...
Click to collapse
RL is still there with LP too

gt-i9505 stuck at bootloader-dead recovery?

Hi guys! I have an gt-i9505 that suddenly shuted down with a crash image (the image was blured ... Like old tv when the signal wasn't very good) and when i tried to turn on the phone it get stuck at "samsung galaxy s4 ..." and i can't access the recovery ... It sais "recovery booting...." but it stops at this point and stais like that forever
If i shut it down and put it on charge the batery shows up with a lightening mark in it but no animation or percent
Fortunatly download mode is available and i flashed a new custom recovery (cwm) the odin said everything was fine but still the recovery isn't accessable . tried also flashing a stock rom but same problem no accessable recovery and the phone is still stuck at s4 logo ...
Any help?

A stock ROM from sammobile.com is flashed in download mode, not recovery mode so it doesn't matter if the phone has no recovery installed.

audit13 said:
A stock ROM from sammobile.com is flashed in download mode, not recovery mode so it doesn't matter if the phone has no recovery installed.
Click to expand...
Click to collapse
I know that but why it can't boot then? Ans what about recovery, Flaahing a stock rom gives you a stock recovery but the phone can't get into any recovery...
Can this be a hardware problem?

You flashed a stock ROM with pit?

audit13 said:
You flashed a stock ROM with pit?
Click to expand...
Click to collapse
No, i don't know how to do it, a link with some installation tips and downloads would be more than thankfull
...............................................................
I flashed cwm recovery again with odin and I got into recovery , wiped data and cache but when I restarted the phone it got stuck again at bootloader and now I can't access the recovery again.... I think that volume up and power buttons are broken somehow...
Flashed again the stock rom , same problem , nothing changed...
A few ideas would be great!

I'm pretty sure it's a hardware problem. The phone doesn't simply shut down for no reason, unless some hardware part was failing.

Sounds like the same problem I have (https://forum.xda-developers.com/galaxy-s4/help/s4-boot-i9505-t3529543)
I would also be interested in how to install stock ROM with pit.

S5 G900I Recovery Bootloop - Cannot get into any recovery mode?

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"