Post Reply
Question

Flashed CWM, but still Stock Recovery?

21st May 2014, 03:57 AM   |  #1  
OP Senior Member
Flag Cave Creek
Thanks Meter: 35
 
648 posts
Join Date:Joined: Apr 2011
More
So I followed this guide to return to stock about a year ago: http://forum.xda-developers.com/show....php?t=2301259

I have since then remained on the stock ROM, but stayed on MDK. I am rooted as well, but never flashed a custom recovery.

Anyways I downloaded ROM Manager and flashed CWM Touch and it said it was succesful. However, when I reboot to recovery it is still the stock bootloader?

I am sure it is something stupid, as I have been away from all this stuff for quite a while now.
21st May 2014, 04:14 AM   |  #2  
joshm.1219's Avatar
Senior Member
Flag Philadelphia
Thanks Meter: 1,388
 
3,241 posts
Join Date:Joined: May 2013
More
Rom manager won't work for our phone. You can use goo manager to install twrp or flashify to install either recovery

Sent from my SCH-I545 using Tapatalk
The Following User Says Thank You to joshm.1219 For This Useful Post: [ View ]
21st May 2014, 04:15 AM   |  #3  
OP Senior Member
Flag Cave Creek
Thanks Meter: 35
 
648 posts
Join Date:Joined: Apr 2011
More
Quote:
Originally Posted by joshm.1219

Rom manager won't work for our phone. You can use goo manager to install twrp or flashify to install either recovery

Sent from my SCH-I545 using Tapatalk

Woah...that is weird...it has always worked in the past? What happened?
21st May 2014, 04:20 AM   |  #4  
joshm.1219's Avatar
Senior Member
Flag Philadelphia
Thanks Meter: 1,388
 
3,241 posts
Join Date:Joined: May 2013
More
Quote:
Originally Posted by CC268

Woah...that is weird...it has always worked in the past? What happened?

Verizon happened. Well they've always made their phone manufacturers lock the bootloaders but with the Qualcomm Snapdragons, we haven't been able to get a true bootloader unlock. In fact, you're very lucky you kept your phone on MDK firmware. There's a small majority of us that did that and we're the only ones with an "exploited" bootloader, the 6 firmwares since MDK all have locked bootloaders.

Basically we use a "loki" exploit to make the system think our bootloader is unlocked, even though it really isn't. That's why ROM manager won't work, you need a loki'd version of CWM, not just the normal version.
The Following 2 Users Say Thank You to joshm.1219 For This Useful Post: [ View ]
21st May 2014, 04:28 AM   |  #5  
OP Senior Member
Flag Cave Creek
Thanks Meter: 35
 
648 posts
Join Date:Joined: Apr 2011
More
Quote:
Originally Posted by joshm.1219

Verizon happened. Well they've always made their phone manufacturers lock the bootloaders but with the Qualcomm Snapdragons, we haven't been able to get a true bootloader unlock. In fact, you're very lucky you kept your phone on MDK firmware. There's a small majority of us that did that and we're the only ones with an "exploited" bootloader, the 6 firmwares since MDK all have locked bootloaders.

Basically we use a "loki" exploit to make the system think our bootloader is unlocked, even though it really isn't. That's why ROM manager won't work, you need a loki'd version of CWM, not just the normal version.

Ahh gotcha, while I don't really do the custom ROMs or kernels anymore I guess I am glad I stayed on MDK. Now a days I just stay on the Stock ROM, but still rooted with custom recovery.

Thanks for your help.
The Following User Says Thank You to CC268 For This Useful Post: [ View ]
Post Reply Subscribe to Thread
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes


Top Threads in Verizon Samsung Galaxy S 4 Q&A, Help & Troubleshooting by ThreadRank