Sony to Extend its AOSP Program to Other Devices

Sony will be offering its users the possibility to use AOSP ROMs as an alternative to the … more

Project Ara Smartphone Will Run Modified Android L with Hot Swapping

Project Ara is a very exciting topic–both for hardware and … more

Streamline Android Theme Customization with Graphic Porter

I dont have a custom theme on my Android phone, and the reason for this is because … more

Boost the Brightness of Your Sony Xperia Z1’s LED

I think the last time anyone has ever used a physical torch to find their earphones, … more
Post Reply

How I unlocked a Bell Galaxy S4 on 4.4.2

10th July 2014, 09:16 AM   |  #1  
OP Junior Member
Thanks Meter: 0
 
2 posts
Join Date:Joined: Aug 2013
My brother gave me his Bell locked Galaxy S4 today, so I've spent the day trying to unlock it to use on Rogers. After much reading of posts here, I managed to get it unlocked as follows:

I am no expert, though I am experienced with rooting and such. The following steps describe what I did to unlock my phone. I am not sure if all of these steps are necessary but they did work. Since I am not an expert, there is no point asking me questions if you have any problems, since I will not be able to help. Of course, some of these steps can void warranty, and could brick your phone if done improperly. I am not responsible for anything bad that happens.

1) Download and flash stock Columbia 4.2.2 rom with Odin (i used 3.09)
2) Root with CF-Auto Root
3) Flash Clockwork Mod (I use Caboomi's img2tar for this)
4) Get rid of KNOX by "installing" DE-KNOX zip in CWM (DE-SAMSUNGNIZER_KNOX_REMOVAL_SCRIPT_V2.0)
5) Download Chainfire's RegionLock Away, install and run
6) Restart and success!
7) Finally, I flashed the current (4.4.2) firmware of the provider I switched to (Rogers), as I was having problems with the phone and some other things. This seems to be operating properly now.



Note: I was able to install 4.2.2 rom even though I was unable to downgrade to 4.3. (Fail to flash aboot like many people get) I assume this is because the 4.2.2 rom does not modify aboot. Also, Chainfire states the RegionLock Away only works for the Note 3, however many people have used it successfully on the S4 as well. It did not work for me on 4.4.2, so I'm guessing either installing 4.2.2, or removing KNOX, or both got it to work.

I hope this helps some people. If it does, thank the developers who made everything above!
16th July 2014, 09:40 PM   |  #2  
Psykologikal's Avatar
Senior Member
Thanks Meter: 16
 
116 posts
Join Date:Joined: Feb 2012
What firmware where you on when u began? 4.4.2? Or earlier?

Sent from my SGH-I337M using XDA Free mobile app
20th July 2014, 06:45 AM   |  #3  
Member
Thanks Meter: 5
 
61 posts
Join Date:Joined: Jan 2011
More
I don't think KNOX affects the sim locking and unlocking. I know for sure that RegionLockAway works in 4.2.2 because I downgraded my phone to that rom and unlocked it...without doing any of the KNOX related stuff.

I think this method you are using trips the KNOX fuse when you downgrade from KitKat.
20th July 2014, 05:47 PM   |  #4  
Psykologikal's Avatar
Senior Member
Thanks Meter: 16
 
116 posts
Join Date:Joined: Feb 2012
OK but how did u downgrade? I don't care about the Knox flag mine is tripped I just want to get back to 4.2 so I can use real custom Roms. Everything I have seen suggests you cannot downgrade

Sent from my SGH-I337M using XDA Free mobile app
20th July 2014, 08:19 PM   |  #5  
Member
Thanks Meter: 5
 
61 posts
Join Date:Joined: Jan 2011
More
Quote:
Originally Posted by Psykologikal

OK but how did u downgrade? I don't care about the Knox flag mine is tripped I just want to get back to 4.2 so I can use real custom Roms. Everything I have seen suggests you cannot downgrade

Sent from my SGH-I337M using XDA Free mobile app

I downgraded to 4.2.2 by simply using ODIN. This process will trip the fuse. The trick in getting it to work is to clear all of the leftover files from 4.4.2 after the flash. You can't boot directly into the system after the flash. You have to go into recovery mode and do a factory reset. If you don't do this, the system wouldn't boot as what everyone is finding.
21st July 2014, 03:25 PM   |  #6  
Psykologikal's Avatar
Senior Member
Thanks Meter: 16
 
116 posts
Join Date:Joined: Feb 2012
So do I need to do a nand erase or something? Or just regular flash then boot into recovery factory reset then flash again? Cuz I would love to get back to 4.2 and start flashing custom Roms agaib

Sent from my SGH-I337M using XDA Free mobile app
21st July 2014, 08:01 PM   |  #7  
Member
Thanks Meter: 5
 
61 posts
Join Date:Joined: Jan 2011
More
Quote:
Originally Posted by Psykologikal

So do I need to do a nand erase or something? Or just regular flash then boot into recovery factory reset then flash again? Cuz I would love to get back to 4.2 and start flashing custom Roms agaib

Sent from my SGH-I337M using XDA Free mobile app

Just a simple factory reset should do.
11th August 2014, 03:42 AM   |  #8  
Junior Member
Flag Drummondville
Thanks Meter: 2
 
13 posts
Join Date:Joined: Jan 2011
So nothing for 4.4.2 directly? We have to downgrade? Thanks

Post Reply Subscribe to Thread
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes


Top Threads in AT&T Samsung Galaxy S 4 General by ThreadRank