I got an unlock code from cellunlocker.net (a site I've used a few times in the past) for my rooted stock-rom S6 Edge from Bell Canada.
When I try to use the code, the message says Unlock Unsuccessful.
Reading the details of the unlock code email, it says unlocking might not work if the phone has been "rooted and/or custom rom installed".
Surely rooting cannot mean one cannot sim unlock it after.... or does it?!?!?
Sometimes rooted phones actually dont unlock. Ive seen people have this problem before. If you Odin back to stock and try unlock should work no problem. From there you can feel free to root and such again with it unlocked no problem.
nookie1916 said:
Sometimes rooted phones actually dont unlock. Ive seen people have this problem before. If you Odin back to stock and try unlock should work no problem. From there you can feel free to root and such again with it unlocked no problem.
Click to expand...
Click to collapse
+1
Experienced something similar myself with my S5 using Cellunlocker.net on rogers. I changed my runtime to ART and it set my binary status to custom. For some reason, changing the Runtime from dalvik to ART on my S5 set my status to custom and prevented any OTA, so I said what tha heck, i'll just root it and trick my status to get OTA, then I wanted to unlock it but it didnt work. I restored to stock after seeing it suggested on XDA, input code and it worked, was able to re-root after without any other issues. Not sure if it's the actual root or the custom status that blocked the unlock though but I think both set the status to custom.
Related
Hey Guys,
I own a Samsung Galaxy S4 from Verizon and have followed the guide on how to root it posted on the forums. For a while things were good. My phone booted up with the correct loading screen and my device detected that I was on an official kernel. Now for reasons I'm not sure of, my phone is saying that the kernel is custom and the lock icon has returned when I restart or cold boot my phone. I'm not running custom firm ware, I'm running a stock Verizion kernel. I tried to delete SuperUser, but it isn't installed. My binaries for SuperSU are up-to-date. I'm still rooted, but I would like to get rid of the unlock icon when I boot up and I would like to get the system to recognize that this is an official kernel.
Also ES File Explorer is unable to mount r/w privilages on my phone in order to delete busybox and su so that I could try to re-root the phone again. Any help would be appreciated, thanks!!
Theres no way so far to get rid of it. Mine actually goes back and for between custom and official all the time. Maybe when the bootloader gets unlocked it will do away with it, but until then it does no harm. So if you want to root, that's the price we pay.
sneekerpimpz said:
Theres no way so far to get rid of it. Mine actually goes back and for between custom and official all the time. Maybe when the bootloader gets unlocked it will do away with it, but until then it does no harm. So if you want to root, that's the price we pay.
Click to expand...
Click to collapse
Most of the time mine is gone. Maybe once a week I might see it.
sneekerpimpz said:
Theres no way so far to get rid of it. Mine actually goes back and for between custom and official all the time. Maybe when the bootloader gets unlocked it will do away with it, but until then it does no harm. So if you want to root, that's the price we pay.
Click to expand...
Click to collapse
So I managed to get rid of it. I'm not sure if it's permanent, but here's what I did. I couldn't delete the stuff in the root directory (and this was before I found solid explorer which has better root access programming than es does). So I did a factory reset and found that that worked for a while, but then I noticed that downloading Triangle Away seemed to be causing the problem because the lock icon returned after I installed it and gave it root access. So I deleted it and chose the 'unroot' option from the list of options in supersu. Then I re-rooted the phone using the guide. Now the lock icon hasn't returned, and the device status under the about phone menu says that my firmware is the official one. Another thing I noticed is that I'm running an older version of busybox (version 1.17.1 I think, as installed by motochopper).
Again I'm not sure what I did differently, or changed as a result of my method, but it seems to have worked. Perhaps someone with more development knowledge can let me know what's happened for my own personal information.
Has anyone tried Towelroot on the S4 NC5 build?
Is this going to unlock the bootloader?
Sent from my SCH-I545 using Tapatalk
This is root method....no it will NOT unlock boot loader
And yes I have used it on my wife's phone it works great..
There is a thepread on it in general section...
sambrooke said:
Has anyone tried Towelroot on the S4 NC5 build?
Is this going to unlock the bootloader?
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
Works perfectly.
sambrooke said:
Has anyone tried Towelroot on the S4 NC5 build?
Is this going to unlock the bootloader?
Click to expand...
Click to collapse
We really seem to have failed in helping people to understand this, as Towelroot users are now bricking phones right and left by people who root bootloader locked phones then use Goo Manager and the like to try to flash custom recovery and fail.
If your bootloader is locked, you can't flash custom recovery or custom kernel. It doesn't matter if you're rooted or not.
"CUSTOM" Software
Does anyone know if the triggers the "Custom" and the unlocked padlock when rebooting?
seadooman said:
Does anyone know if the triggers the "Custom" and the unlocked padlock when rebooting?
Click to expand...
Click to collapse
It DOES trigger the Custom padlock. With root access you can install Xposed Framework and one of modules allows you to reset that back to Original boot screen.
I think triangle away will work also. I haven't tried yet, but removed the custom screen with the mk2 build after that was rooted with saferoot.
http://forum.xda-developers.com/galaxy-s2/orig-development/2014-01-15-triangleaway-v3-26-t1494114
Sent from my IdeaPad U410 using Tapatalk
Lost "HI Galaxy Funtion"
Not sure if its related but I lost the handsfree "HI Galaxy" , Get the cannot connect to servers error. Anyone experience this?
seadooman said:
Not sure if its related but I lost the handsfree "HI Galaxy" , Get the cannot connect to servers error. Anyone experience this?
Click to expand...
Click to collapse
If it really happened out of the blue, without installing or reconfiguring anything, your issue will probably be fixed with a power cycle. I would try a battery pull, holding down the power button for a couple seconds without the battery in place (to drain remnants of electricity), replace the battery, boot, reboot, soft/hotboot. If that doesn't fix it, you must have done something to stop it from functioning in the first place.
Yes that also happened to me.. Not sure if it was related to towel root or something I froze. I unfroze everything and uninstalled towel root still had issue..ended up reinstalling oem firmware and everything works normal now. Wondering if the samsung servers know the phone is rooted and refuse connection?
seadooman said:
Yes that also happened to me.. Not sure if it was related to towel root or something I froze. I unfroze everything and uninstalled towel root still had issue..ended up reinstalling oem firmware and everything works normal now. Wondering if the samsung servers know the phone is rooted and refuse connection?
Click to expand...
Click to collapse
Doubtful; people saying "Hi Galaxy" is free advertising for them. If it occured after freezing tasks I'm sure that was the source of the problem. Must be SELinux related. Next time, just redo your root; you probably didn't need to forfeit data.
I unfroze everything and it was hit and miss if it connected or not. Reinstalled android problem was gone. Just thought I would offer my experience on this..
On NC5 it was the fastest and easiest root ever.
One of my phone's is a Galaxy S3 using NE1 and since i couldn't unlock the bootloader but, i had successfully rooted it using towelroot.
It has been about 6 months and i never had issues.
Not everyone with a matching phone has the same issues when it comes to Rooting as well as Bootloader Unlocking.
One's bad experience doesn't always mean another will have the same. This all depends on the expertise and know-how of the user as well as the reliability of an individual who provides the information and/or files accomplishing a Root and/or Bootloader Unlocking.
Just my opinion :fingers-crossed:
Looks like every other thread... but all the methods recommended here seem to not work for unlocking my phone. I've tried:
Galaxy S Unlock from the play store. Fails, no error message
GalaxSim Unlock (old free version). Unrecognized NV. Free XDA version seems to be gone
ChainFire's Unlock Code seach tool. No code found
Backstory. My phone was happily rooted, unlocked and being used in a different country than where I purchased it, for about 1.5 years. No problems. At the time I rooted it by flashing a PDA and using GalaxSim Unlock. It was runnin 4.1.2. 3 days ago I uninstalled titanium backup and a few other apps and it seemed to lose root. The next day it was not unlocked any more so now I can't use it. I have successfully re-rooted the phone but the recommended methods of unlocking do not seem to work for me. I've listed what I tried above.
The only thing I can think to do is flash it back to gingerbread, hope an unlock works, and then hope it will persist after being updated back to 4.1.2. Is this feasible or is there something else to try?
Thanks!
I guess there isn't a way to unlock Galaxy S2 for free any more, at least mine. I've paid for the GalaxSim Unlock.
My phone is rooted stock on the very first original ROM (forgot the version). I asked Sprint for GSM unlock, they sent the request, but it didn't go through. The "UICC unlock" option does nothing. Could it be because I'm rooted and/or on an old ROM? I didn't tell Sprint rep about the root.
Idk probably the root it mess with the system try flashtooling back to ZV4 and then try it but dont ota to ZV6 or else you'll lose root. Alsi they code/ method may be bad. What carrier are you trying to go to?
1619415 said:
Idk probably the root it mess with the system try flashtooling back to ZV4 and then try it but dont ota to ZV6 or else you'll lose root. Alsi they code/ method may be bad. What carrier are you trying to go to?
Click to expand...
Click to collapse
Thanks for the advise. I just figured out the problem- I froze a lot of bloat with TB, and it affected UICC. unlock. I did it a while ago, and it didn't occur to me right away to defrost before attempting to unlock.
I'm thinking about traveling to South America and want to use a local SIM card while over there.
OK well have fun, glad it works
However I'm not sure how to check that the unlock actually worked. When Sprint network is available, the phone will use it regardless of the SIM. I tried to install a T-Mobile SIM from friend's phone, and my phone came up with red X SIM icon in the status bar- the same as with no SIM.
Spring does not support unlocking.
Sprint does not support domestic sim unlocking but will allow international unlocking.
If you want to use another carrier then try out cloudyg3 1.2 rom or cm11 rom. You can use any carrier with them. Or else you have to modify your build.prop file and replace the ro.carrier.target from SPR to spr using the rom toolbox app and then you get a unlocked gsmphone.
I recently swapped my iPhone 5c to a guy with a Samsung S4 AT&T.I am aware that these carriers are locking their bootloaders.Everytime I restart or turn on my phone normally,there is a "Samsung Custom" message on the boot screen with an unlocked padlock on it.Most of the time it shows up,and in rare random moments in goes away with the normal Samsung S4 boot screen.What does this mean? Did the guy unlocked the bootloader? or flashed another firmware? or is it because Knox was tripped off due to rooting,And I can see that the phone is actually rooted because there's the SuperSU app.I am asking on how I can indentify if my phone's bootloader is actually unlocked.Because I dont have access to my own PC,so it means I cant operate adb.Are there any direct methods? I also checked if he installed a custom recovery,and there's none,just the default one.
Most likely it's from just rooting it. The bootloader hasn't been unlockable on those since 4.2.2, build number ending in MDK (I think). Not many were kept on that update. It's possible to update the rest of the system and firmware on that older bootloader, but since it doesn't have a custom recovery already, that seems unlikely.
es0tericcha0s said:
Most likely it's from just rooting it. The bootloader hasn't been unlockable on those since 4.2.2, build number ending in MDK (I think). Not many were kept on that update. It's possible to update the rest of the system and firmware on that older bootloader, but since it doesn't have a custom recovery already, that seems unlikely.
Click to expand...
Click to collapse
Thanks for the reply! I am sending my phone to a local tech guy to unlock my bootloader.He only charged me $6 and it is pretty cheap.