Attend XDA's Second Annual Developer Conference, XDA:DevCon 2014!
5,781,370 Members 37,321 Now Online
XDA Developers Android and Mobile Development Forum

[Q] Recovery bootloop Galaxy s5

Tip us?
 
luisjo2k
Old
#1  
Junior Member - OP
Thanks Meter 0
Posts: 4
Join Date: Jun 2010
Default [Q] Recovery bootloop Galaxy s5

I tried to install the CWM Recovery using Odin. Device gets stuck in BootLoop with......

1. RECOVERY BOOTING (in blue),
2. RECOVERY IS NOT SEANDROID ENFORCING (red)
3. Set Warranty Bit: recovery (yellow)

Cant Boot in download mode
It isnt recognized by the pc, odin or kies

Havet find a clear answer in previous posts. Any help?
 
knoxrents
Old
#2  
Junior Member
Thanks Meter 0
Posts: 5
Join Date: Nov 2010
Quote:
Originally Posted by luisjo2k View Post
I tried to install the CWM Recovery using Odin. Device gets stuck in BootLoop with......

1. RECOVERY BOOTING (in blue),
2. RECOVERY IS NOT SEANDROID ENFORCING (red)
3. Set Warranty Bit: recovery (yellow)

Cant Boot in download mode
It isnt recognized by the pc, odin or kies

Havet find a clear answer in previous posts. Any help?
I am in this situation right now as well after flashing CWM recovery via ODIN. Hopefully someone has an answer. Did you find anything?
 
babygau
Old
#3  
Senior Member
Thanks Meter 202
Posts: 526
Join Date: Jun 2011
Location: Melbourne
Try to overwrite your recovery with Philz Touch. It's working perfect for G900 variants so far:

Philz Touch Recovery Download
Please click THANKS button on the left instead of just saying if you find my post useful for you ,

Sent from my Galaxy S5 using Tapatalk Pro

Device: Galaxy S5 G900I
ROM: XtreStoLite ROM by @edgarf28
Kernel: KT Kernel by @ktoonsez with modified ktoonsifized v2 profile
The Following User Says Thank You to babygau For This Useful Post: [ Click to Expand ]
 
knoxrents
Old
#4  
Junior Member
Thanks Meter 0
Posts: 5
Join Date: Nov 2010
Quote:
Originally Posted by babygau View Post
Try to overwrite your recovery with Philz Touch. It's working perfect for G900 variants so
I was finally able to get the phone into download mode by pulling the battery so I just pushed TWRP to it to fix the CWM issues. I'll check out Philz Touch as well though. Thanks.
 
babygau
Old
#5  
Senior Member
Thanks Meter 202
Posts: 526
Join Date: Jun 2011
Location: Melbourne
Quote:
Originally Posted by knoxrents View Post
I was finally able to get the phone into download mode by pulling the battery so I just pushed TWRP to it to fix the CWM issues. I'll check out Philz Touch as well though. Thanks.
Great!

IMO, Philz Touch is more beatiful and more functional than TWRP
Please click THANKS button on the left instead of just saying if you find my post useful for you ,

Sent from my Galaxy S5 using Tapatalk Pro

Device: Galaxy S5 G900I
ROM: XtreStoLite ROM by @edgarf28
Kernel: KT Kernel by @ktoonsez with modified ktoonsifized v2 profile
 
jeemer
Old
#6  
Junior Member
Thanks Meter 0
Posts: 11
Join Date: Jun 2012
Hi guys - I had this same issue today. I'd also installed CWM and tried to go into recovery mode via ROM Manager when it happened.

Looked around and after finding this thread I managed to flash with Philz Touch and got it to boot. Managed to get it into recovery mode and run this new Philz Touch version of CWM and do a backup. However just before it got into CWM it still came up with:

1. RECOVERY BOOTING (in blue),
2. RECOVERY IS NOT SEANDROID ENFORCING (red)
3. Set Warranty Bit: recovery (yellow)

Then loaded into CWM whereas before flashing Philz it was just looping. Is there a way I can stop it from coming up with this?
 
knoxrents
Old
#7  
Junior Member
Thanks Meter 0
Posts: 5
Join Date: Nov 2010
Quote:
Originally Posted by jeemer View Post
Hi guys - I had this same issue today. I'd also installed CWM and tried to go into recovery mode via ROM Manager when it happened.

Looked around and after finding this thread I managed to flash with Philz Touch and got it to boot. Managed to get it into recovery mode and run this new Philz Touch version of CWM and do a backup. However just before it got into CWM it still came up with:

1. RECOVERY BOOTING (in blue),
2. RECOVERY IS NOT SEANDROID ENFORCING (red)
3. Set Warranty Bit: recovery (yellow)

Then loaded into CWM whereas before flashing Philz it was just looping. Is there a way I can stop it from coming up with this?
I'm using TWRP and the same thing comes up. It only comes up for a few seconds so I just don't worry about it. With CWM recovery, it was locked on that screen.

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes


Give Your Android Wear Device a Lock Screen with Lockable

Without a doubt,Android Wear is one of the most frequently talked abouttopics of … more

Forums Added for the LG G Watch R and Samsung Gear S

A little over a week ago, LG “inadvertently” let the world know about the … more

Secrecy App Goes Open Source, New LG Android Wear Device! – XDA Developer TV

Secrecy encryption app goes open source! That and much … more

Pushbullet Updated with SMS Send Ability

Pushbullet is one of thoseapplications that every Android lover should have installed on his or … more