Somehow I've messed up my recovery and it won't boot anymore. The phone boots up just fine, but not into recovery mode. When I try and go into recovery mode, the blue text "Recovery Booting" shows, sits for about 5-10 seconds, then boots up the regular system (currently the latest cyanogenmod M6 release).
I've tried flashing different recoveries using Odin 3.09 and 1.85, but both of them fail with "Odin Fail (auth)". On the screen it says "odin secure check recovery failed". I've also tried flashing different recoveries through ROM Manager and GooManager, both of which claim they flashed successfully, but still won't boot into recovery. The phone is still rooted, is there any way I can get a working recovery back??
hi,
my S4 i9500 won't boot.
i have tried loading several versions of stock roms, recoveries and non-stock roms.
all stock roms fail in odin, and i get "unsupported dev_type" error on the device.
other non-stock roms install with no error, but the device won't boot after reboot.
finally, out of frustration and recklessness, i guess i used an S4 boot loader fix wihch loaded successfully from odin.
unfoutunatly, after rebooting the device, boot message sais GT-I9505 instead of GT-I9500. turns out it was a 9505 boot loader fix.
is there anything i can do to bring my device back to life??
currently, device won't boot to recovery (blue "recovery booting" on top left corner of screen), won't boot to system, but can enter download mode, and be identified by odin.
update: i also tried flashing stock rom with pit file. in this case i get "secure check fail : pit" error message on the device
thanks!!
bontuser said:
hi,
my S4 i9500 won't boot.
i have tried loading several versions of stock roms, recoveries and non-stock roms.
all stock roms fail in odin, and i get "unsupported dev_type" error on the device.
other non-stock roms install with no error, but the device won't boot after reboot.
finally, out of frustration and recklessness, i guess i used an S4 boot loader fix wihch loaded successfully from odin.
unfoutunatly, after rebooting the device, boot message sais GT-I9505 instead of GT-I9500. turns out it was a 9505 boot loader fix.
is there anything i can do to bring my device back to life??
currently, device won't boot to recovery (blue "recovery booting" on top left corner of screen), won't boot to system, but can enter download mode, and be identified by odin.
update: i also tried flashing stock rom with pit file. in this case i get "secure check fail : pit" error message on the device
thanks!!
Click to expand...
Click to collapse
if you dont want to be on stock rom then try flashing a custom recovery by odin eg philz touch link here and then just flash it via recovery and you will be able to boot into recovery and then you can just flash a custom rom.
if you dont want to install custom rom do a clean wipe and try flashing the stock rom again
hope it hepled .
Hit thanks if it helped.
Kushan02 said:
if you dont want to be on stock rom then try flashing a custom recovery by odin eg philz touch and then just flash it via recovery and you will be able to boot into recovery and then you can just flash a custom rom.
if you dont want to install custom rom do a clean wipe and try flashing the stock rom again
hope it hepled .
Hit thanks if it helped.
Click to expand...
Click to collapse
hi, thanks for your help.
as mentioned in my original post,i tried loading custom recovery - both twrp and wcm, but can't enter recovery mode in bothe cases
bontuser said:
hi,
my S4 i9500 won't boot.
i have tried loading several versions of stock roms, recoveries and non-stock roms.
all stock roms fail in odin, and i get "unsupported dev_type" error on the device.
other non-stock roms install with no error, but the device won't boot after reboot.
finally, out of frustration and recklessness, i guess i used an S4 boot loader fix wihch loaded successfully from odin.
unfoutunatly, after rebooting the device, boot message sais GT-I9505 instead of GT-I9500. turns out it was a 9505 boot loader fix.
is there anything i can do to bring my device back to life??
currently, device won't boot to recovery (blue "recovery booting" on top left corner of screen), won't boot to system, but can enter download mode, and be identified by odin.
update: i also tried flashing stock rom with pit file. in this case i get "secure check fail : pit" error message on the device
thanks!!
Click to expand...
Click to collapse
Hi mate,
Flash a stock rom with odin , who knows what happen when you flashed the boot fix plus all the custom rom
Easiest way out is flash stock start from beginning
follow this thread:
http://forum.xda-developers.com/showthread.php?t=2265477
bontuser said:
hi, thanks for your help.
as mentioned in my original post,i tried loading custom recovery - both twrp and wcm, but can't enter recovery mode in bothe cases
Click to expand...
Click to collapse
okay so try flashing the philz touch recovery via odin in download mode and see if it works it will probably work
link here - https://www.androidfilehost.com/?fid=95864024717069687
and bro please hit thanks button.
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?
Hi, i have a sm-n910f galaxy note 4 that is stuck on boot, the samsung logo appears and get stucked. If i try to boot the recovery i get stucked too whith the logo and the msg that say "recovery booting...". I have tryed to flash stock roms throught odin (with autoreboot unticked, factory reset ticked, with pit and without pit) i have tested samsung firmware rom (N910FXXS1DQC3) and the rom that besoeasy suggested on that thread. If i flash twrp i get stuck on the screen "Recovery: is not seandroid enforcing set warranty bit recovery" and the phone starts vibrate and autoreboot if not stucked. Any suggestions?
Greetings
I had the same problem with TWRP, flash TWRP, untick auto reboot. flash TWRP, remove battery and charger. boot into recovery again. that will work. sorry for my English