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.
Related
I tried using insecure firmware (KF1 and KF3) and both superoneclick and s2root don't recognize my device even with debugging mode on.
Anyone manage to make it work?
I have tried to start rooting, but supposedly you need kies to work.
My kies constantly tells me "devicemanager.exe has stopped working" when I try to connect it. So until its fixed I can't root it (and no one will help me )
That said, I'veheard rooting is successful, but getting an unlock key has been not so successful.
i used cf-root and now have villianrom 2.1 installed and working. yeah i don't think unlock works yet
rooted and unlocked here...
the conventional rooting methods do not work on the s2, as the poster before me mentioned you have to use CFroot to flash the custom kernel, that will automatically root it, once you have done that you can search for the galaxy s unlock by helroz on the market, and it works... thats how i did mine.
Hi guys.
My sister has a s3 (4.0.4). She wanted me to update it. (OTA not available). The phone is on 3 (UK). So i plugged it in kies and started to update it. After it had finished i turned the phone on and to my surprise it was asking for an unlock code! I was confused because it was working before the update. What made it even worse was that it hadnt updated to jellybean rather it was still 4.0.4. I was baffled.
So i decided to root it then do an unlock. This worked fine however i don't want the root for my sister as she is not into all this stuff. So i checked online if i could unroot. The only option i found was to a factory reset!. I can't do that as my sister will kill me. So now I'm stuck. Kies won't recognise my phone because its rooted. So what do i do??? I cant update it till its unrooted so I'm stuck.
Can you please tell me if there is any way round this. And how can i get jelly bean?.
Thanks.
keep it rooted and hide the root apps from the app drawer, that way your sister won't use them / mess the phone up.
Only other way is a factory reset + stock reflash i guess. :/
Well if you reeeally want to unroot, then install triangleaway first and do the "traditional steps of removing the binary count".. and then just flash a firmware from sammobile.com
Cheers!
Sent from my GT-I9300 using xda premium
mzr07 said:
Hi guys.
My sister has a s3 (4.0.4). She wanted me to update it. (OTA not available). The phone is on 3 (UK). So i plugged it in kies and started to update it. After it had finished i turned the phone on and to my surprise it was asking for an unlock code! I was confused because it was working before the update. What made it even worse was that it hadnt updated to jellybean rather it was still 4.0.4. I was baffled.
So i decided to root it then do an unlock. This worked fine however i don't want the root for my sister as she is not into all this stuff. So i checked online if i could unroot. The only option i found was to a factory reset!. I can't do that as my sister will kill me. So now I'm stuck. Kies won't recognise my phone because its rooted. So what do i do??? I cant update it till its unrooted so I'm stuck.
Can you please tell me if there is any way round this. And how can i get jelly bean?.
Thanks.
Click to expand...
Click to collapse
Rooting doesnt stop KIES from recognising your phone. It doesnt stop you from updating via KIES. After updating you will lose the root. You are doing something wrong. Also ...your phone is carrier locked so after the update you will have to unlock it again. There are different ways /software for unlocking ....choose a permanent way.....then flashing will not affect your unlock status
Cheers
If you don't want to be rooted, buy an unlock code from your network.
The software methods all require root.
Sent from my GT-I9300 using xda app-developers app
There is no reason to suddenly need an unlock code after a firmware update...
I would check the right version if the Rom you installed.
Unroot is not very complicated, it's mainly erasing the su binary in /system/bin I think and uninstalling super user app.
Hi I just installed JB 4.1.2 XXLS6 with philz kernel to root it. I can't seem to unlock my phone when I use chainfire sim unlock it asks if i'm rooted and have superuser. I have both of those already. I also tried helroz unlocker I pressed step 2 and rebooted but i'm still not unlocked. Any ideas?
RoRo1990 said:
Hi I just installed JB 4.1.2 XXLS6 with philz kernel to root it. I can't seem to unlock my phone when I use chainfire sim unlock it asks if i'm rooted and have superuser. I have both of those already. I also tried helroz unlocker I pressed step 2 and rebooted but i'm still not unlocked. Any ideas?
Click to expand...
Click to collapse
same problem with my friend's phone , any one has any idea ?
RoRo1990 said:
Hi I just installed JB 4.1.2 XXLS6 with philz kernel to root it. I can't seem to unlock my phone when I use chainfire sim unlock it asks if i'm rooted and have superuser. I have both of those already. I also tried helroz unlocker I pressed step 2 and rebooted but i'm still not unlocked. Any ideas?
Click to expand...
Click to collapse
Another OBVIOUS instance where user has clearly not bothered to use search. This has been discussed and topics create on multiple occasions. You have absolutely no need whatsoever to create another topic.
Thread closed
As stated, search, this has been answered many, many times.
So I have two Z2s. One with an unlocked BL and one with a locked BL. When I rooted the 2nd one, I noticed that the Remote Play app would error out. Once I unrooted, it would work fine. That was several months ago and I've been running stock since.
Just wondering if that is still the case now? I'm running Lollipop and was pondering rooting the phone again (I miss some of my root apps).
Thx,
Praz
as far as i know, yes having a rooted phone will produce error code 88001003 when attempting to launch remote play. my phone does it running the latest lollipop rooted posted by niaboc, and has always done it when rooted.
unroot and it works fine.
there is a modded apk that removes some of the different checks the remote play app does but its for a really old version. i was gonna try and decompile the app and see what i can do when i get free time.
i hope there devs will solve this one . i have the same problem.....have you tried on a unlocked BL?
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.