Bought an Australian model galaxy S4 off ebay which was stuck at Samsung Logo with a hope I can unbrick it.
I have tried to flash with an official firmware twice. ODIN confirmed flashing Passed. But the phone still could not boot pass Samsung logo with model number.
+ Pressed volume up + Home + power button to enter into recovery mode but the phone still stuck at recovery mode with blue text "recovery booting ". Have tried to take battery out and redo few times. . All I can do is go to download mode to flash official firmware again. However I do not want to mess thing up as I have tried twice without success.
Please help me out if you have any idea how to fix it. I am much appreciate.
I am not sure if it will help or not but you can try flashing TWRP via Odin and then boot into that one (maybe recovery is corrupted as well?)
Clear cache / dalvik cache from TWRP and try booting to system again
magnavn76 said:
Bought an Australian model galaxy S4 off ebay which was stuck at Samsung Logo with a hope I can unbrick it.
I have tried to flash with an official firmware twice. ODIN confirmed flashing Passed. But the phone still could not boot pass Samsung logo with model number.
+ Pressed volume up + Home + power button to enter into recovery mode but the phone still stuck at recovery mode with blue text "recovery booting ". Have tried to take battery out and redo few times. . All I can do is go to download mode to flash official firmware again. However I do not want to mess thing up as I have tried twice without success.
Please help me out if you have any idea how to fix it. I am much appreciate.
Click to expand...
Click to collapse
Good idea of @th3cr0w.
I will add: It's important know what firmware had before you start to flash things. I supose you don't know it. What you can do is:
1. Flash TWRP recovery in DOWNLOAD MODE via ODIN unticking "Auto reboot". Take out the battery when the process finish. Wait 30 sec. and push it in again.
2. Boot in TWRP and wipe all (Wipe -> Advanced Wipe -> Select system, data, cache and dalvik cache).
3. Reboot in DOWNLOAD MODE and now yes, flash the firmware you wish via ODIN normally.
Same happens with my Galaxy s3 while ago, Problem was the EMMC chip was corrupted, And the problem was solved after replacing it from a local shop.
Joku1981 said:
Good idea of @th3cr0w.
I will add: It's important know what firmware had before you start to flash things. I supose you don't know it. What you can do is:
1. Flash TWRP recovery in DOWNLOAD MODE via ODIN unticking "Auto reboot". Take out the battery when the process finish. Wait 30 sec. and push it in again.
2. Boot in TWRP and wipe all (Wipe -> Advanced Wipe -> Select system, data, cache and dalvik cache).
3. Reboot in DOWNLOAD MODE and now yes, flash the firmware you wish via ODIN normally.
Click to expand...
Click to collapse
Thanks for your and TH3cr0w's suggestion. I will try it tonight and let you guys know. Hope I will fix it. A quick question before I do, once I install TWRP it is anyway I can remove it and reinstall official receovery?
I am using this firmware:
PDA I9505XXUGNH6
CSC I9505XSAGNH1
i have tried to install TWRP with this file twrp-2.8.6.0-jfltexx.tar 9.9M. However my phone still stuck and can not boot into recovery. up the top of screen i have following messages:
Recovery booting...
RECOVERY IS NOT SEANDROID ENFORCING
Set Warranty Bit : recovery
Have i done anything wrong? Thanks
What you're seeing is normal, but recovery not installing isn't. I know you don't want to try it again, but flash your stock ROM through Odin. Do it this time with the following changes:
Add a PIT file (easily found on the forum).
Make sure "Re-partition" is selected.
The combination of the PIT file and the re-partition function should wipe the S4's internal storage and partition it properly. If there is no physical damage to the internal storage you should then be able to boot into the device. Otherwise you may have no choice but to have this beast repaired.
Related
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?
hey guys! first post but I have been lurking here and there before registering.
Sorry if this is the wrong section to post this in. I am trying to root my note 4 and I installed TWRP using Odin. Now when I go into recovery mode to flash SuperSu, it says "no command" with the android guy laying on the floor. I tried the factory reset option and I installed TWRP again but still same problem. I can still load my phone and use it as usual but now I can't go into recovery mode with TWRP and flash supersu to root it. Anyone know how I can fix this problem? Any help would be appreciated.
No one knows?
kratos0605 said:
hey guys! first post but I have been lurking here and there before registering.
Sorry if this is the wrong section to post this in. I am trying to root my note 4 and I installed TWRP using Odin. Now when I go into recovery mode to flash SuperSu, it says "no command" with the android guy laying on the floor. I tried the factory reset option and I installed TWRP again but still same problem. I can still load my phone and use it as usual but now I can't go into recovery mode with TWRP and flash supersu to root it. Anyone know how I can fix this problem? Any help would be appreciated.
Click to expand...
Click to collapse
What is the model number of your Note 4? When you are at the "no command" screen, try holding the volume up button and then press the power button to take you to recovery. I'd that doesn't work try holding the power button and tapping the volume up button quickly and release all buttons and see if it allows yoj to access recovery. I'd these do not work keep trying different button combinations. I'd you still cannot access the recovery menu you may have to Odin the factory firmware and start over. Let me know what happens.
Sent from my Nexus 6 using XDA-Developers mobile app
none of those button combinations work. I will install stock firmware on it again and see if that fixes the recovery.
I had this problem in the past, I think the problem was that when I was installing TWRP via Odin that I had not powered off the phone so it looked like it installed but actually didn't, try taking out the battery and then boot into recovery or download mode whatever it is that is used for Odin and install again
kratos0605 said:
none of those button combinations work. I will install stock firmware on it again and see if that fixes the recovery.
Click to expand...
Click to collapse
If you cannot get into recovery with any button combination boot to download mode and use Odin to flash all 4 files of the factory firmware. That will give you a fresh start. Let me know how it goes.
Sent from my Nexus 6 using XDA-Developers mobile app
Same here
After holding volume up+middle button+power bar
I get into recovery mode but right after recovery mode it goes into “installing system update….” and then “No command” shows up and after that I get the following message and options:
Android system recovery
Volume up/down to move highlight;
power button to select.
reboot system now
apply update from ADB
apply update from external storage
apply update from cache
wipe/data/factory reset
wipe cache partition
reboot to bootloader
power down
View recovery logs
Enable cp logging
Disable cp logging
and at the bottom in yellow it says;
# MANUAL MODE #
— Appling Multi-CSC…
Applied the CSC-code : GLW
Successfully applied multi-CSC.
Any sort of help would be appreciated, thank you.
amk58 said:
Same here
After holding volume up+middle button+power bar
I get into recovery mode but right after recovery mode it goes into â??installing system updateâ?¦.â? and then â??No commandâ? shows up and after that I get the following message and options:
Android system recovery
Volume up/down to move highlight;
power button to select.
reboot system now
apply update from ADB
apply update from external storage
apply update from cache
wipe/data/factory reset
wipe cache partition
reboot to bootloader
power down
View recovery logs
Enable cp logging
Disable cp logging
and at the bottom in yellow it says;
# MANUAL MODE #
â?? Appling Multi-CSCâ?¦
Applied the CSC-code : GLW
Successfully applied multi-CSC.
Any sort of help would be appreciated, thank you.
Click to expand...
Click to collapse
Use the VOLUME UP/DOWN BUTTONS to scroll to WIPE DATA/FACTORY RESET and let it do its thing. When it's done select REBOOT SYSTEM NOW.
Tell me what that does.
fast69mopar said:
Use the VOLUME UP/DOWN BUTTONS to scroll to WIPE DATA/FACTORY RESET and let it do its thing. When it's done select REBOOT SYSTEM NOW.
Tell me what that does.
Click to expand...
Click to collapse
but this will erase all my data from the phone
Yes it will but it is the most likely way out of your bootloop. Before you wipe, connect your device to your PC and boot to recovery. Once your PC recognizes your device internal storage, transfer everything that you can think of.
Sent from my Nexus 6 using XDA-Developers mobile app
fast69mopar said:
Yes it will but it is the most likely way out of your bootloop. Before you wipe, connect your device to your PC and boot to recovery. Once your PC recognizes your device internal storage, transfer everything that you can think of.
Click to expand...
Click to collapse
I'm not in bootloop
My phone is working normally.
I'm trying to root my note 4 N910H (Android 6.0.1 Marshmallow) device
I flashed TWRP recovery using Odin
now I need to boot into TWRP recovery so I can to Flash SuperSu.zip downloaded in my device
what is happening after holding volume up+middle button+power bar
I should expect a menu with install option so I can flash the SuperSUfile in the device internal memory, instead this is happening:
it goes into “installing system update….” and then “No command” shows up and after that I get the following message and options:
Android system recovery
Volume up/down to move highlight;
power button to select.
reboot system now
apply update from ADB
apply update from external storage
apply update from cache
wipe/data/factory reset
wipe cache partition
reboot to bootloader
power down
View recovery logs
Enable cp logging
Disable cp logging
and at the bottom in yellow it says;
# MANUAL MODE #
— Appling Multi-CSC…
Applied the CSC-code : GLW
Successfully applied multi-CSC.
Click to expand...
Click to collapse
If i choose reboot system, the phone will work fine, but I need a way to access TWRP recovery so I can to Flash SuperSu
amk58 said:
I'm not in bootloop
My phone is working normally.
I'm trying to root my note 4 N910H (Android 6.0.1 Marshmallow) device
I flashed TWRP recovery using Odin
now I need to boot into TWRP recovery so I can to Flash SuperSu.zip downloaded in my device
what is happening after holding volume up+middle button+power bar
I should expect a menu with install option so I can flash the SuperSUfile in the device internal memory, instead this is happening:
If i choose reboot system, the phone will work fine, but I need a way to access TWRP recovery so I can to Flash SuperSu
Click to expand...
Click to collapse
That looks like TWRP didn't stick when you flashed it using Odin. Try a different version of Odin and flash TWRP.
Sent from my Nexus 6 using XDA-Developers mobile app
kratos0605 said:
hey guys! first post but I have been lurking here and there before registering.
Sorry if this is the wrong section to post this in. I am trying to root my note 4 and I installed TWRP using Odin. Now when I go into recovery mode to flash SuperSu, it says "no command" with the android guy laying on the floor. I tried the factory reset option and I installed TWRP again but still same problem. I can still load my phone and use it as usual but now I can't go into recovery mode with TWRP and flash supersu to root it. Anyone know how I can fix this problem? Any help would be appreciated.
Click to expand...
Click to collapse
So idk if you've gotten it fixed, but what worked for me was: I had been turning on the phone after odin did its thing, and that caused the oem recovery to reinstall itself. So instead of letting odin auto boot be ready to push the volume up button to put it into twrp recovery. I had to remove my battery to keep it from booting fully.
We need to try another time flash. Conditions - old Odin 3.06, configured to remove reboot.
swhockey347 said:
So idk if you've gotten it fixed, but what worked for me was: I had been turning on the phone after odin did its thing, and that caused the oem recovery to reinstall itself. So instead of letting odin auto boot be ready to push the volume up button to put it into twrp recovery. I had to remove my battery to keep it from booting fully.
Click to expand...
Click to collapse
thanks you saved me lot of time today !!!
Thanks - this helped me too
i have same problem
my phone is samsung j2lte
have you try untick /uncheck the "auto reboot" option on odin app. instead reboot manually after flashing twrp??
my problem not solved either
Thank you. This helped me too.
kratos0605 said:
hey guys! first post but I have been lurking here and there before registering.
Sorry if this is the wrong section to post this in. I am trying to root my note 4 and I installed TWRP using Odin. Now when I go into recovery mode to flash SuperSu, it says "no command" with the android guy laying on the floor. I tried the factory reset option and I installed TWRP again but still same problem. I can still load my phone and use it as usual but now I can't go into recovery mode with TWRP and flash supersu to root it. Anyone know how I can fix this problem? Any help would be appreciated.
Click to expand...
Click to collapse
In ODIN go to 'options' and uncheck 'auto-reboot', then flash TWRP. When it's done, it won't reboot, just pull the battery for several seconds, reinsert it and boot into TWRP Recovery.
Enjoy!
When I try to flash any thing it gets stuck on boot.img
I just flashed TWRP for the first time but it comes up with "Unmodified System Partition" but touchscreen doesn't work for some reason so I cant select anything. I tried removing the battery and rebooting my phone (Galaxy S4 19505) But it just boots back into recovery for TWRP in the "Unmodified System Partition" . Please Help, thanks.
Edit: Should I delete the TWRP disk image from my pc? (My phone also keeps vibrating while turned off). I have also noticed that there is a non physical home back and menue button, did I download the wrong version? I used the TWRP app to download and flash the image.
Hi,
Download the latest image or tar from here: https://dl.twrp.me/jfltexx/ and flash it with either Odin or Heimdall.
Not quite sure about the notice, is it on the screen that asks you if you want to keep the system partition read-only? Then you either need to swipe or click ok.
Normally flashing a recovery should not produce the problems you are describing, did you only flash the recovery?
Long story short - when using wifi my s7 edge started to restart several times until it got to boot loop. I tried various things, enter and exit download mode, factory reset, partition cache clear, nothing helped. I tried to flash stock firmware several times (different versions) but it didn't help. I can go to recovery and download mode, odin recognizes the device and passes the flashing, however it does not boot. Always stuck on "galaxy s7 edge" screen.
Do you guys have any idea what could I do? I was thinking about installing twrp, however will I be able to install it if the setting in developers setting "OEM unlock" was not enabled?
heofizzy said:
Long story short - when using wifi my s7 edge started to restart several times until it got to boot loop. I tried various things, enter and exit download mode, factory reset, partition cache clear, nothing helped. I tried to flash stock firmware several times (different versions) but it didn't help. I can go to recovery and download mode, odin recognizes the device and passes the flashing, however it does not boot. Always stuck on "galaxy s7 edge" screen.
Do you guys have any idea what could I do? I was thinking about installing twrp, however will I be able to install it if the setting in developers setting "OEM unlock" was not enabled?
Click to expand...
Click to collapse
Hello,
You don't have to worry, your phone isn't broken, i flash roms every day so i'm very familiar with does kind of "Errors". I'm here to assist you.
So without the OEM Unlock option enabled your phone won't be able to boot to recovery neither system if you flash a custom rom, flashing the stock firmware via Odin is the only way so try does steps:
1. Download stock firmware for your model from sammobile.
2. Extract the files and place them in the correct tab.
3. Disable auto-reboot in option panel.
4. Soon after it finish flashing, long press volume down and power button until screen turns off, then quickly press volume up, home button and power button.
5. Phone should now boot to recovery from which you have to do a factory reset and wipe cache/data.
6. Restart system.
Phone should boot just fine now, it might take 5 minutes for the first boot, if you're stuck for more than 5 minutes i would kindly ask you to take a picture of your log in recovery.
If you manage to boot the phone go to developer settings and enable OEM unlock then you can flash TWRP and from TWRP a custom rom.
If you have questions and still need help, feel free to pm me for anything, i'm here to help you!
Grettings,
SwitchDeath
So I took it to the service, it was a faulty motherboard.
I have same issue with my s7 edge, but with AT&T version (G935A). I couldn't find the firmware from sammobile as previous instruction from SwitchDeath. Do I have any other option to download the firmware from other source? Nothing seem to work for me from all other forum instructions and downloads, it just stuck in "galaxy s7 edge" screen on and off and not reboot at all. Please help!
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"