From /efs/nv.log -
Sat Oct 2 10:31:40 2010: secondary NV built.
Sat Oct 2 10:31:42 2010: Plain text NCK deleted.
Samsung have wised up. Can't find the NCK code in nv_data.bin any longer.
The I897UCJI6-OCD-REV02-Low.exe one-click odin method wipes everything, including /efs I would think - Not sure though. I was SIM unlocked before upgrading and I just checked and still SIM unlocked.
Not sure if -
1) The old /efs data + unlocked nv_data.bin were kept and "upgraded"
or
2) The nv_data.bin within I897UCJI6-OCD-REV02-Low.exe is factory SIM unlocked
Either way - I'm good
Thanks for that. I'll have to get my unlock code before updating.
Good idea posting this. I read an article a few weeks ago that said they were going to do that, and someone yesterday was saying how he was unable to unlock his phone after upgrading. Like you, I'm good though--have the digits saved safely on my pc.
This info should be included somewhere. Up at the top, like, "warning, you will be unable to unlock your phone if you upgrade to 2.2, so be sure to do that first!"
not really development related... people have been told time and time again since the JPC fiasco to backup their EFS folder. if they haven't, well, that's their own fault.
Kaik541 said:
not really development related... people have been told time and time again since the JPC fiasco to backup their EFS folder. if they haven't, well, that's their own fault.
Click to expand...
Click to collapse
can you restore a efs folder from eclair and restore it to froyo?
why would any1 need to unlock this phone.
this cappy clone (galaxy S) is available in almost all the wireless carriers!
travel and the fact that the carrier restricts that
and for those getting refurbished exchanges?
I too am interested in hearing if reverting back to an earlier version will let me find the SIM unlock code.
I unlocked and saved the code for my current (random shutdown plagued) phone.
But I am expecting a new (refurbished) phone in the next few days. Any ideas if I will be able to unlock it to use my TMobile card also? Or have I once again been struck down by the fickle finger of fate?
Those files are unique for each phone. Hence they are not included in firmware. Once it is moved, it will be very difficult to get back.
However, don't expect AT&T to give you a phone with anything other than JF6. It will be a few more months before they load JH7 to them.
netnerd said:
why would any1 need to unlock this phone.
this cappy clone (galaxy S) is available in almost all the wireless carriers!
Click to expand...
Click to collapse
If you travel outside of US, you don't have to pay AT&T over $2/min (average)for each call.
FireRaider said:
I too am interested in hearing if reverting back to an earlier version will let me find the SIM unlock code.
I unlocked and saved the code for my current (random shutdown plagued) phone.
But I am expecting a new (refurbished) phone in the next few days. Any ideas if I will be able to unlock it to use my TMobile card also? Or have I once again been struck down by the fickle finger of fate?
Click to expand...
Click to collapse
Just run the un-locker script before applying the OTA update to jf7 on the new one and you should be good.
Sent from my SAMSUNG-SGH-I897 using XDA App
ardyer said:
Just run the un-locker script before applying the OTA update to jf7 on the new one and you should be good.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
really can anyone verify this
tjsooley said:
really can anyone verify this
Click to expand...
Click to collapse
once you upgrade the firmware, the file is gone...reverting back to stock and trying to find the code does not work, iv tested :/
ok good.
does backing up the efs folder on a lodversion and then restoring it in froyo work?
netnerd said:
why would any1 need to unlock this phone.
this cappy clone (galaxy S) is available in almost all the wireless carriers!
Click to expand...
Click to collapse
And this phone has the nicest design of all of them.....
USHERROB said:
once you upgrade the firmware, the file is gone...reverting back to stock and trying to find the code does not work, iv tested :/
Click to expand...
Click to collapse
reverting to stock via Odin3 one click does not restore it? I have not tried, but find that surprising.
Why unlock? My provider (Rogers) still hasn't launched the phone... and the Captivate is the sexiest design, IMHO.
When I flashed to JH7 a while ago, I was prompted for the unlock code again. I had to restore the ROM backup in order to get the code again. When I flashed back to JH7, it oddly no longer asked to be unlocked.
Sent from my Samsung Captivate using XDA App
Soooo for you guys panicking that the unlock codes have been removed... have you tried to use the backups of the nv_data.bin files to pull the unlock code? Just do a ls -l -a in the /efs directory and you should find them there. Either that or I have them because of all the froyo shuffling I've done in the past...
I am assuming that nv_data.bin is just an on disk shadow of the non-volatile (NV) RAM associated with the modem. If you successfully unlocked the phone before going to a recent build where /efs/nv_data.bin is scrubbed it shouldn't matter - The unlock is already registered in NV RAM...
That's why I wasn't prompted for the unlock code after flashing the JI6 one-click.
That's what I have deduced and it seems logical... at least to me :-D
Wow that sucks for me :/ should have read more before flashing froyo. Oh well. Ill just wait till my contract is up before I escape the clutches of att
Yay no more fc
Related
okay im having problems unlocking sgs on ugjk4 on sgs unlock app i get sorry no code found unknown error ??
that app no longer (or is having a hard time working) with FROYO firmwares. I used it to unlock mine when I was still in Eclair.
Maybe you should revert to a stock Eclair? Anyways, once you have the unlock and freeze code, make sure you write it down and save it in your PC.
Note: When I flashed to Froyo using Odin, network locked re-appeared and I needed to punch in the exact code I got when I was in Eclair. Now, It's totally unlocked. No more unlock code after that initial flash to Froyo.
Wish you luck!
okay new too this please understand i think got what u mean but how would i revert back to eclair never did this!!! so basically your saying be more easy to go back eclair then root it then SGS unlock will work then write code paper update back to froyo and unlock would work still.....is this correct ??
update
i think figured out why get error code silly me forgot put sim!!! okay now what Sim must be inserted SGS unlock app (original Sim that phone locked to) or any Sim will do sorry i am new to this was i phone user for while
mr.galaxys said:
update
i think figured out why get error code silly me forgot put sim!!! okay now what Sim must be inserted SGS unlock app (original Sim that phone locked to) or any Sim will do sorry i am new to this was i phone user for while
Click to expand...
Click to collapse
With or without sim, you should be able to get the code since the code itself is for the phone and is embedded in the phone.
Sent from my GT-I9000 using XDA App
hmmm....then 2.2 sgs app doesnt work??any other ideas i dont wann downgrade just 2 unlock???
It's not a permanent downgrade. Flash back to eclair, unlock your phone, write down the unlock code and freeze code then flash back to froyo.
Don't forget to back up your EFS folder to your SD card and laptop.
Sent from my GT-I9000 using XDA App
android.francis said:
It's not a permanent downgrade. Flash back to eclair, unlock your phone, write down the unlock code and freeze code then flash back to froyo.
Don't forget to back up your EFS folder to your SD card and laptop.
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
how would one do this(downgrade) i am new to this thanks...
[Q] SuperOneClick vs OCLF
Hey Guys, I have the i9000m through Bell Mobility, and today I rooted it using SuperOneClick. It ran and said completed successfully, and installed a SuperUser app on my phone.
What is the difference between this and the OCLF? Does SuperOneClick include some sort of "lag fix"? Is one method superior to the other?
Cheers!
OCLF does lagfix your phone, yes. However, it is outdated. I would recommend you to try z4root and z4mod.
I've heard about Z4 from a few friends, couldn't find it on the Market so I went with SuperOneClick. Thank you for the suggestion - I will probably try this one if I need to do it again.
I've also learned that most third party ROM's include LagFixes in their Kernel, eliminating the need for them in the rooting process.
Are there any real differences in the rooting apps?
What is your end-goal?
End goal, to educate myself on a few fronts of Android phones. I'd like to have enough knowledge to root, and install new ROM's (which I can confidently do). I'd also like to have a good understand of reverting to factory ROM and settings (if you could point me a to a descriptive thread on this it would be much appreciated!).
Just wondering if one rooting method is superior to the others
Hello, can anyone of you help me please? I see someone mentioned z4root. Now this is my problem:
I downloaded z4root, ran it and it seems like it started but after few seconds my phone just vibrated and then it turned me to my home screen, which means i wasnt able to root.
Could anyone be so kind and help me out with it?
My firmware version is 2.2.
Thanks in advance
Sorry - haven't tried it myself. But, you can use SuperOneClick if you like with a simple instructional video
http://forum.xda-developers.com/showthread.php?t=803682
[Q] is superoneclick safe to root?
Hi, I want to root my froyo JPO with Superoneclick in order to install lagfix,
but the main problem is my 3 combo buttons not working..
Is it safe to do so?
I would work on getting your 3 button combo working before attempting any type of modifications. On the odd chance something goes wrong you need that to enter recovery mode or download mode. I believe there are a few faqs on it around the site.
As for super one click, I've used it several times flawlessly
Kops said:
I would work on getting your 3 button combo working before attempting any type of modifications. On the odd chance something goes wrong you need that to enter recovery mode or download mode. I believe there are a few faqs on it around the site.
As for super one click, I've used it several times flawlessly
Click to expand...
Click to collapse
Agreed. There's a reason the 3-button fix is a pinned post in every i9000 forum. Fix that BEFORE doing anything.
WRT superoneclick, I've also never had any problems with it although your mileage may vary. Note that there are easier rooting solutions available although none appear to support as many firmware versions as superoneclick.
superoneclick android drivers?
Hello, i plan to use superoneclick to root my galaxy s phone. I went to superoneclick site and it said "You NEED to install make sure the Android drivers for your phone are installed". Now i have installed kies drivers, is that enough or do i need to install other drivers? Also, i have adb installed.
someone please reply...
Hi there,
I picked up my Nexus S a couple of days ago and i'm totally loving the device. My only problem is connecting to T-Mobile's 3G network, I can only connect for 4-5 mins before it switches back to Edge, which is terribly slow. I've read that this has been an issue for some people and I tried to remove the sim card, change the APN Settings but nothing seems to help.
I read something about updating to newer radio but I'm not sure how to do that, any help would be appreciated !
All the best,
Gianpy
Ploone said:
Hi there,
I picked up my Nexus S a couple of days ago and i'm totally loving the device. My only problem is connecting to T-Mobile's 3G network, I can only connect for 4-5 mins before it switches back to Edge, which is terribly slow. I've read that this has been an issue for some people and I tried to remove the sim card, change the APN Settings but nothing seems to help.
I read something about updating to newer radio but I'm not sure how to do that, any help would be appreciated !
All the best,
Gianpy
Click to expand...
Click to collapse
Go into your settings menu>About Phone and tell us your baseband version please.
I should note that I've not really heard of this happening before and to me it sounds like you're just not in a 3G area.
kenvan19 said:
Go into your settings menu>About Phone and tell us your baseband version please.
I should note that I've not really heard of this happening before and to me it sounds like you're just not in a 3G area.
Click to expand...
Click to collapse
You might not have 3g in your area. Other than that it sounds weird
Sent from my Nexus S using XDA App
I am on the Strip in Las Vegas, NV - I doubt there is no 3G here since there is even 4G here!
Baseband version- I9020XXJK8
You are right now on 2.3.2 Stock without root right?
-So, first step is rooting your phone. You can do it without oem unlock and not losing all your archives. But I did this and I just copied all files again(Yes, it's boring to wait all the time transfering archives but it's better).
- Now you have to flash Clockworkmod (It's the same topic, showing how to do it).
- Then flash through CWM (ClockWorkMod) the update. GRH78 is 2.3.1, GRH78C is 2.3.2, GRI40 is 2.3.3. Link: http://forum.xda-developers.com/showthread.php?t=967953
Any douts?
This should solve a lot of issues that you have now.
liquelt said:
You are right now on 2.3.2 Stock without root right?
-So, first step is rooting your phone. You can do it without oem unlock and not losing all your archives. But I did this and I just copied all files again(Yes, it's boring to wait all the time transfering archives but it's better).
- Now you have to flash Clockworkmod (It's the same topic, showing how to do it).
- Then flash through CWM (ClockWorkMod) the update. GRH78 is 2.3.1, GRH78C is 2.3.2, GRI40 is 2.3.3. Link: http://forum.xda-developers.com/showthread.php?t=967953
Any douts?
This should solve a lot of issues that you have now.
Click to expand...
Click to collapse
I am on 2.3.1 Stock without root, should I still follow the same steps?
Ploone said:
I am on the Strip in Las Vegas, NV - I doubt there is no 3G here since there is even 4G here!
Baseband version- I9020XXJK8
Click to expand...
Click to collapse
Well, I just pulled a coverage map of the strip and it seems that there are spots of worse coverage so it all depends on where you are. Nonetheless, I will help you update your radio or even update to 2.3.3 altogether as long as you're willing to root your phone and flash a rom (you can use download and use the update that Google pushes out but a lot of people have problems with it so I think its just easier to root, flash the rom, then just not root again once you have the new ROM). If you want me to help you do this, just say so and tell me if you have a mac or a PC.
kenvan19 said:
Well, I just pulled a coverage map of the strip and it seems that there are spots of worse coverage so it all depends on where you are. Nonetheless, I will help you update your radio or even update to 2.3.3 altogether as long as you're willing to root your phone and flash a rom (you can use download and use the update that Google pushes out but a lot of people have problems with it so I think its just easier to root, flash the rom, then just not root again once you have the new ROM). If you want me to help you do this, just say so and tell me if you have a mac or a PC.
Click to expand...
Click to collapse
Sure, I'd love some help doing that, I appreciate your help!
I am on a Mac.
You should follow the same steps but the update file is different!
Here is the link for you to root: http://forum.xda-developers.com/showthread.php?t=931865
There are a lot of Custom ROMs, you should choose one and flash it.
I put the wrong link, I didn't known that you had a Mac.
Sorry, here is the right one! http://forum.xda-developers.com/showthread.php?t=931865
Enjoy this beautiful phone!
liquelt said:
You should follow the same steps but the update file is different!
Here is the link for you to root: http://forum.xda-developers.com/showthread.php?t=931865
Click to expand...
Click to collapse
****, I'm completely lost..
Kenvan is your method the same as this or something different?
Ploone said:
****, I'm completely lost..
Kenvan is your method the same as this or something different?
Click to expand...
Click to collapse
The method he linked only works for builds prior to 2.3.3 which is a category you fall into. That guide is quite nice and works very well but it will not unlock your bootloader, which means your SDcard partition for your files and music and pictures etc won't be wiped. If you intend to stay rooted, I don't suggest using that guide but instead using the one I wrote here:
http://forum.xda-developers.com/showthread.php?t=970237
Now before you do either, tell me if you want to unlock your bootloader (if you plan to stay rooted after doing the updated) or want to leave it locked (if you plan to remove root after updating).
kenvan19 said:
The method he linked only works for builds prior to 2.3.3 which is a category you fall into. That guide is quite nice and works very well but it will not unlock your bootloader, which means your SDcard partition for your files and music and pictures etc won't be wiped. If you intend to stay rooted, I don't suggest using that guide but instead using the one I wrote here:
http://forum.xda-developers.com/showthread.php?t=970237
Now before you do either, tell me if you want to unlock your bootloader (if you plan to stay rooted after doing the updated) or want to leave it locked (if you plan to remove root after updating).
Click to expand...
Click to collapse
Whichever is easier to be honest and requires less steps, you tell me haha. I don't mind either option.
Or you could just wait for the official 2.3.3 OTA if you don't want to root. Might get it quicker if you do a checkin request. Simply dial *#*#checkin#*#*
Sent from my Nexus S using XDA App
Ploone said:
Whichever is easier to be honest and requires less steps, you tell me haha. I don't mind either option.
Click to expand...
Click to collapse
lol the difference between the two is literally two command. if you unlock the bootloader you add one command (fastboot oem unlock) and you use the command "fastboot boot" for the locked method where as you use fastboot flash for the unlocked. After that the two are exactly the same so if you want to stay rooted after updating (so you can use apps like AdFree, Titanium Backup, Root Explorer, etc or want to install custom roms) you should unlock your bootloader.
To be completely frank, if you don't mind unlocking the bootloader I've had some people have trouble with the command "fastboot boot" which is why I changed my guide to use "fastboot flash". What I'm saying is I recommend using my guide, which again you can find at the link below. Remember though, before you go through any of the steps copy the contents of your SD card to your computer. Actually that is a step I should really add lol
http://forum.xda-developers.com/showthread.php?t=970237
I'm going to go find the link to the 2.3.3 ROM so I can give you that but just take a look at my guide while I'm looking.
kenvan19 said:
lol the difference between the two is literally two command. if you unlock the bootloader you add one command (fastboot oem unlock) and you use the command "fastboot boot" for the locked method where as you use fastboot flash for the unlocked. After that the two are exactly the same so if you want to stay rooted after updating (so you can use apps like AdFree, Titanium Backup, Root Explorer, etc or want to install custom roms) you should unlock your bootloader.
To be completely frank, if you don't mind unlocking the bootloader I've had some people have trouble with the command "fastboot boot" which is why I changed my guide to use "fastboot flash". What I'm saying is I recommend using my guide, which again you can find at the link below. Remember though, before you go through any of the steps copy the contents of your SD card to your computer. Actually that is a step I should really add lol
http://forum.xda-developers.com/showthread.php?t=970237
I'm going to go find the link to the 2.3.3 ROM so I can give you that but just take a look at my guide while I'm looking.
Click to expand...
Click to collapse
Ok, I'll check out your guide. Thank you so much for all your help! I hope my problem is fixed !
Ploone said:
Ok, I'll check out your guide. Thank you so much for all your help! I hope my problem is fixed !
Click to expand...
Click to collapse
No problem man, if you have any questions at all let me know.
Also, here is the link to the full ROM for 2.3.3:
http://forum.xda-developers.com/showthread.php?t=967953
Now I'm not 100% sure if this will update your radio but it will give you the newest update. I'm currently trying to check on that so you can get everything done at once (if it doesn't do the radio there is another file you can install right after installing the ROM that will update your radio. That way you'll be 100% up to date)
EDIT: Yes, it does contain the radio, so that will put you 100% on 2.3.3 with the updated radio.
Do you have any questions?
kenvan19 said:
Do you have any questions?
Click to expand...
Click to collapse
All is well and my problem is fixed, thank you very much!
I stupidly wrote down the wrong sim unlock code given to me by ATT on my phone and I guess I entered the wrong code too many times. I called ATT tech support and they said that my phone is locked permanently ATT now.
Is there a fix around this or am I screwed?
Thx
he.spinal said:
I stupidly wrote down the wrong sim unlock code given to me by ATT on my phone and I guess I entered the wrong code too many times. I called ATT tech support and they said that my phone is locked permanently ATT now.
Is there a fix around this or am I screwed?
Thx
Click to expand...
Click to collapse
As far as I know, you are SOL and is locked permanently to ATT, unless theres a way to unlock it via the service menu after a code has been inputted wrong.
Go to Cellunlocker.net and talk to someone in support about getting a code that unlocks your sim-locked status. It's not the code to unlock your phone, it's the code that resets the perma-lock state of the phone.
I guess i am SOL i called cell unlocker and they said they dint have the software to do it
Did you try the method listed for unlocking your phone from the service menus - without an unlock code?
I have not seen it explained, but it appears to me that by disabling the SHA256 network lock, you are basically getting rid of the requirement for the unlock code that is cryptographically dependent on the IMEI.
I did it on my AT&T phone and plopped in a T-mo sim and it worked fine:
http://forum.xda-developers.com/showthread.php?t=2285431
I am not responsible for anything you may mess up though.
he.spinal said:
I guess i am SOL i called cell unlocker and they said they dint have the software to do it
Click to expand...
Click to collapse
You might have one other option that I know of that might work, might not work, or might make things worse. It is the "Free unlock" menu method in the general section. I am assuming you haven't tried it already. Normally I tell people to stay clear of it because of the slim chance it could screw your phone up, but in your case, I'd say it's already screwed up.
Follow the directions and see if restoring your "Golden backup" (NV restore) resets the cell locks on your phone. You can also try thing like turning SHA256 "On", or "Off" and see if it makes a difference. The reason the free unlock method works for some and not others all depends on what info resides in your phones NV backup. For some, it restores full phone functionality without network locks (sim unlocked), for others, it restores exactly what is already on the phone's NV memory (still network locked), and for others, it restores a backup that screws the phone up. There is a slim possibility that if you restore the NV data via the hidden menu, you might restore your phones original sim locked state and then be able to use the code with SHA256ON or maybe Off.
The risk you take if you try it is completely yours.
It might help, it might not help, or it could make it worse. Good luck.
Would flashing back to stock rom work? I am still fairly new with android devices coming from iphones so i dont want to mess with it if it has absolutely no chance of working. The phone is still working fine just can't unlock it.
Thx for the suggestions tho
he.spinal said:
Would flashing back to stock rom work? I am still fairly new with android devices coming from iphones so i dont want to mess with it if it has absolutely no chance of working. The phone is still working fine just can't unlock it.
Thx for the suggestions tho
Click to expand...
Click to collapse
Flashing back to stock is not going to cure your problem. You're kind of hosed at this point. Scott's suggestion is probably your best bet, BUT you could end up with no phone working at all. If you can still get phone service I'd leave it as is and give up ever unlocking.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
---------- Post added at 07:19 PM ---------- Previous post was at 07:01 PM ----------
TO ANYONE WHO IS FOLLOWING THIS THREAD, PLEASE DON'T DO ANY THING TO YOUR PHONE BECAUSE YOU THINK IT MAY BE COOL. Really know what your doing and why before you do try it. You can really mess up your phone. There a lot of good info in this forum, use it. And take your time, read, study, and read some more.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
about permanent unlock!!
hello buddy , did you found any solution for the permanently lock to att? im having the same problem! thanks
he.spinal said:
Would flashing back to stock rom work? I am still fairly new with android devices coming from iphones so i dont want to mess with it if it has absolutely no chance of working. The phone is still working fine just can't unlock it.
Thx for the suggestions tho
Click to expand...
Click to collapse
I wasn't able to unlock my AT&T GS4 via the service menu methods, nor with an unlock code I bought online. I was finally able to unlock it via the USB program at FastGSM. It seemed kind of shady but it worked for me...
Zoide_ said:
I wasn't able to unlock my AT&T GS4 via the service menu methods, nor with an unlock code I bought online. I was finally able to unlock it via the USB program at FastGSM. It seemed kind of shady but it worked for me...
Click to expand...
Click to collapse
Which Version worked for you? Their download page has several but none of them say Fire Phone.
I bought this phone for my mom and sent her the unlock code... but she missed it 5 times.. LOL now it is permanently locked to At&t
ZeroHart said:
Which Version worked for you? Their download page has several but none of them say Fire Phone.
I bought this phone for my mom and sent her the unlock code... but she missed it 5 times.. LOL now it is permanently locked to At&t
Click to expand...
Click to collapse
Sorry, it was so long ago I don't know. The Paypal receipt says "Samsung i337 Unlocking Software", if that helps.
Zoide_ said:
I wasn't able to unlock my AT&T GS4 via the service menu methods, nor with an unlock code I bought online. I was finally able to unlock it via the USB program at FastGSM. It seemed kind of shady but it worked for me...
Click to expand...
Click to collapse
Zoide_ said:
Sorry, it was so long ago I don't know. The Paypal receipt says "Samsung i337 Unlocking Software", if that helps.
Click to expand...
Click to collapse
No Problem, Thanks
I searched the forums, and didn't really find an answer I'm looking for. I'm hoping that someone can quickly help me without too much bashing :laugh:
Is there a way I can test to see if my BL is unlocked without bricking anything if it's actually locked? I bought a phone off of ebay, and the person stated that nothing was ever done to it. However, after rooting / VooDoo, and not doing anything else to it, it wouldn't take the .94 update... kept getting the EMMC:boot error. Had to use matt's utility to RSD to stock (even though it was already stock) and root / VooDoo again.... after which it took update.
So, since the person may have lied about it not being rooted before, maybe they unlocked the BL, and just covered it up...
I DO show Bootloader Locked: Status 0 though in AP mode. I'm just wondering if I can run Motocopylis (or whatever it's called) without fear of bricking anything if it's still locked, and what kind of message or error I'd get if it's already unlocked.
dreamersipaq said:
I searched the forums, and didn't really find an answer I'm looking for. I'm hoping that someone can quickly help me without too much bashing :laugh:
Is there a way I can test to see if my BL is unlocked without bricking anything if it's actually locked? I bought a phone off of ebay, and the person stated that nothing was ever done to it. However, after rooting / VooDoo, and not doing anything else to it, it wouldn't take the .94 update... kept getting the EMMC:boot error. Had to use matt's utility to RSD to stock (even though it was already stock) and root / VooDoo again.... after which it took update.
So, since the person may have lied about it not being rooted before, maybe they unlocked the BL, and just covered it up...
I DO show Bootloader Locked: Status 0 though in AP mode. I'm just wondering if I can run Motocopylis (or whatever it's called) without fear of bricking anything if it's still locked, and what kind of message or error I'd get if it's already unlocked.
Click to expand...
Click to collapse
If your build is prior to may 24 '13 there is the apk in my goodies. If its equal or later there is no point.
Go to the 1st link below.
dreamersipaq said:
I searched the forums, and didn't really find an answer I'm looking for. I'm hoping that someone can quickly help me without too much bashing :laugh:
Is there a way I can test to see if my BL is unlocked without bricking anything if it's actually locked? I bought a phone off of ebay, and the person stated that nothing was ever done to it. However, after rooting / VooDoo, and not doing anything else to it, it wouldn't take the .94 update... kept getting the EMMC:boot error. Had to use matt's utility to RSD to stock (even though it was already stock) and root / VooDoo again.... after which it took update.
So, since the person may have lied about it not being rooted before, maybe they unlocked the BL, and just covered it up...
I DO show Bootloader Locked: Status 0 though in AP mode. I'm just wondering if I can run Motocopylis (or whatever it's called) without fear of bricking anything if it's still locked, and what kind of message or error I'd get if it's already unlocked.
Click to expand...
Click to collapse
I'm no expert at all but I ran motoapocolyps and if didn't do anything. It will either fail and your phone will be fine or, depending on what update you last took, unlock it. My phone is past due for unlocking the bootloader unless there is a way to downgrade it.
Hi
aviwdoowks said:
If your build is prior to may 24 '13 there is the apk in my goodies. If its equal or later there is no point.
Go to the 1st link below.
Click to expand...
Click to collapse
Hi, Thanks for the reply! I don't think my question came across right. I know I can't unlock on my build. I guess I'm asking what i can do to test if it's already been unlocked and covered up by someone before...
Thanks!
Follow up question:
What would be the difference in the output on the screen that you get of
1) if you run Motocopylis and you're already unlocked
vs.
2) if you run Motocopylis and failing since you're locked and on the May build
Thanks!
dreamersipaq said:
Hi, Thanks for the reply! I don't think my question came across right. I know I can't unlock on my build. I guess I'm asking what i can do to test if it's already been unlocked and covered up by someone before...
Thanks!
Follow up question:
What would be the difference in the output on the screen that you get of
1) if you run Motocopylis and you're already unlocked
vs.
2) if you run Motocopylis and failing since you're locked and on the May build
Thanks!
Click to expand...
Click to collapse
You said it already:
""I DO show Bootloader Locked: Status 0 though in AP mode.""
With the knowledge that the build is may 24 or later means no unlock.
Build before May, 24 and running the UL apk results in an UL'ed boot.
status 0: never rooted
1: rooted previously but not now.
3 : rooted
dreamersipaq said:
Hi, Thanks for the reply! I don't think my question came across right. I know I can't unlock on my build. I guess I'm asking what i can do to test if it's already been unlocked and covered up by someone before...
Thanks!
Follow up question:
What would be the difference in the output on the screen that you get of
1) if you run Motocopylis and you're already unlocked
vs.
2) if you run Motocopylis and failing since you're locked and on the May build
Thanks!
Click to expand...
Click to collapse
You can't cover up a BL unlock. Like Avi said, it shows locked on you AP Fastboot screen, so that means you're locked.
aviwdoowks said:
You said it already:
""I DO show Bootloader Locked: Status 0 though in AP mode.""
With the knowledge that the build is may 24 or later means no unlock.
Build before May, 24 and running the UL apk results in an UL'ed boot.
status 0: never rooted
1: rooted previously but not now.
3 : rooted
Click to expand...
Click to collapse
do you mean unlocked or rooted?
I'm rooted, but I show status 0
Thanks for your reply!
RikRong said:
You can't cover up a BL unlock. Like Avi said, it shows locked on you AP Fastboot screen, so that means you're locked.
Click to expand...
Click to collapse
"You can't cover up a BL unlock." <- THANK YOU! That is what I was trying to confirm....
I was thinking that since you can do this to cover up the unlocked bl warning: http://forum.xda-developers.com/showthread.php?t=1901444
that you can also do something to cover up the AP screen as well.
Since I'm rooted, and this phone is supposed to get 4.4, I'm not too upset that I can't unlock (Though with 4.4 I'll probably lose root ).. The stock rom is pretty nice on these, and root gives me pretty much anything I want for customization.
Thanks!
dreamersipaq said:
do you mean unlocked or rooted?
I'm rooted, but I show status 0
Thanks for your reply!
Click to expand...
Click to collapse
I am the one confused! I need to learn my codes.
Hi my contact run to its end and EE has an audacity to ask me for £20 quid to unlock a phone that they locked, that now belongs to me. As I have absolutely no intention to pay for it or upgrade, nor conduct any further business I would like to remove the lock, I am on new cyanogenmod 12 and rooted with CWM recovery. It shouldn't be that difficult, anyone is willing to help?
Thanks!
intacto said:
Hi my contact run to its end and EE has an audacity to ask me for £20 quid to unlock a phone that they locked, that now belongs to me. As I have absolutely no intention to pay for it or upgrade, nor conduct any further business I would like to remove the lock, I am on new cyanogenmod 12 and rooted with CWM recovery. It shouldn't be that difficult, anyone is willing to help?
Thanks!
Click to expand...
Click to collapse
I don't think so if you had android 4.4.2 before flash the custom ROM. You will have to buy a unlock code.
How is that even legal, it wouldn't be in any other country this phone belongs to me, how the company can ask me to pay for unlocking something that belongs in 100% to me!
intacto said:
How is that even legal, it wouldn't be in any other country this phone belongs to me, how the company can ask me to pay for unlocking something that belongs in 100% to me!
Click to expand...
Click to collapse
I don't know if is legal or no. All depends of the little letter of the contract. Did you read the contract when you signed it?
intacto said:
Hi my contact run to its end and EE has an audacity to ask me for £20 quid to unlock a phone that they locked, that now belongs to me. As I have absolutely no intention to pay for it or upgrade, nor conduct any further business I would like to remove the lock, I am on new cyanogenmod 12 and rooted with CWM recovery. It shouldn't be that difficult, anyone is willing to help?
Thanks!
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2282683
You'll need to install the 4.2.2 stock ROM here in order for either method discussed to work. Once done, then you can reinstall CyanogenMod. So, before starting, take a nandroid backup through CWM.
Strephon Alkhalikoi said:
http://forum.xda-developers.com/showthread.php?t=2282683
You'll need to install the 4.2.2 stock ROM here in order for either method discussed to work. Once done, then you can reinstall CyanogenMod. So, before starting, take a nandroid backup through CWM.
Click to expand...
Click to collapse
So you think hat will work, I will definitely try it, anything to prevent this blood sucking supplier getting any more money off me! One question tho, when I do the backup of my current lollipop via cwm, do I have to wipe all the cache and after restoring it I wont have any issue with all the applications/customisation I currently have? It would kill me to set up everything again
and one more question, my lollipop version is like a week old, if I was to download the latest nightly can I upgrade my lollipop without loosing any apps/settings?
Thanks a lot for your help, I really appreciate it.
intacto said:
So you think hat will work, I will definitely try it, anything to prevent this blood sucking supplier getting any more money off me! One question tho, when I do the backup of my current lollipop via cwm, do I have to wipe all the cache and after restoring it I wont have any issue with all the applications/customisation I currently have? It would kill me to set up everything again
and one more question, my lollipop version is like a week old, if I was to download the latest nightly can I upgrade my lollipop without loosing any apps/settings?
Thanks a lot for your help, I really appreciate it.
Click to expand...
Click to collapse
I hope he explain you too the PROS and CONS about that process :highfive:
I know the pross, what are the cons?
The con with the service menu method is that it's possible to really screw up the phone. The RegionLock Away method is far better, but its cons are that there's no guarantee that the unlock will stick if the modem is upgraded, plus the app was never intended to unlock phones but simply remove region locking.
For a price of free though, neither can be beat and I didn't encounter any problems when I did it myself. The foolproof method however is to pay for the unlock. Why your carrier charges is unknown. As to whether it's legal for them to do so, unfortunately it probably is. Otherwise they would have stopped long ago.
Strephon Alkhalikoi said:
The con with the service menu method is that it's possible to really screw up the phone. The RegionLock Away method is far better, but its cons are that there's no guarantee that the unlock will stick if the modem is upgraded, plus the app was never intended to unlock phones but simply remove region locking.
For a price of free though, neither can be beat and I didn't encounter any problems when I did it myself. The foolproof method however is to pay for the unlock. Why your carrier charges is unknown. As to whether it's legal for them to do so, unfortunately it probably is. Otherwise they would have stopped long ago.
Click to expand...
Click to collapse
Well I have tried that service menu trick while on kitkat, but that didnt go pass step 2, it didnt even show me the menu, but I am fine with downgrading to 4.2.2 and giving it a try....I also tried ragionaway app 2 days ago, that was a no-go
Because the exploits that allowed both to work were patched in versions later than 4.2.2. Downgrading the modem at minimum is a requirement for either to work.
Strephon Alkhalikoi said:
http://forum.xda-developers.com/showthread.php?t=2282683
You'll need to install the 4.2.2 stock ROM here in order for either method discussed to work. Once done, then you can reinstall CyanogenMod. So, before starting, take a nandroid backup through CWM.
Click to expand...
Click to collapse
Well it didnt go well with this 4.2.2 rom i must said, i got this in Odin:
<ID:0/004> sbl3.mbn
<ID:0/004> rpm.mbn
<ID:0/004> aboot.mbn
<ID:0/004> FAIL! (Auth)
I then tried to do the stock of 4.4.2, that resorted fine but it wiped my IMEI and now phone doesnt connect to mobile network...help...:crying:
What version of Odin are you using? If it's not 3.09 or 3.10, download either of those and try again. Also, make sure you're using the original cable, are connected directly to the computer and not through a hub, have the drivers properly installed, and don't have Kies running.
EDIT: Lastly, try changing the USB port.
Strephon Alkhalikoi said:
What version of Odin are you using? If it's not 3.09 or 3.10, download either of those and try again. Also, make sure you're using the original cable, are connected directly to the computer and not through a hub, have the drivers properly installed, and don't have Kies running.
EDIT: Lastly, try changing the USB port.
Click to expand...
Click to collapse
I have managed to revert back to lollipop from hte backup and it works fine but I am still in the square one. I do use the original cable, direct to my PC drivers are there, kies isnt running. It did a proper flashing to 4.4.2 but it refuses to have that 4.2.2, is there anyway to downgrade the modem only from 4.4.2 to see if that will work for me? also my phone is i9505xxugni2, the rome u gave me the link to has a different PDA, would that prevent the flashing of my handset?
Cheers!
Absolutely. Go here and take a look around. You should be able to find a 4.2.2 modem from there. But, unless you deleted the download, you also have it in the 4.2.2 ROM download. the .tar.md5 files can be opened in WinRAR on the PC.
Strephon Alkhalikoi said:
Absolutely. Go here and take a look around. You should be able to find a 4.2.2 modem from there. But, unless you deleted the download, you also have it in the 4.2.2 ROM download. the .tar.md5 files can be opened in WinRAR on the PC.
Click to expand...
Click to collapse
So I did manage to flash this rom and that was successful, that revert me to 4.2.2, it didn't wipe my IMEI. Then I tried any method of unlocking I could find, even the regionaway, galaxy unlock app and with no luck, when i try to bring up the service menu by typing 1 after *#0011# it never brigs it up, I followed instructions to the letter I think I would have to pay for the code:crying:
intacto said:
So I did manage to flash this rom and that was successful, that revert me to 4.2.2, it didn't wipe my IMEI. Then I tried any method of unlocking I could find, even the regionaway, galaxy unlock app and with no luck, when i try to bring up the service menu by typing 1 after *#0011# it never brigs it up, I followed instructions to the letter I think I would have to pay for the code:crying:
Click to expand...
Click to collapse
:good:
RegionLock Away requires root for it to function, as it rewrites system files. I believe the app itself mentions this. The service menu exploit may have been removed by EE.
Paying for the code is your only alternative if the free options don't.
Strephon Alkhalikoi said:
RegionLock Away requires root for it to function, as it rewrites system files. I believe the app itself mentions this. The service menu exploit may have been removed by EE.
Paying for the code is your only alternative if the free options don't.
Click to expand...
Click to collapse
Yes region away always ask for root so I have to re-do it every time after the flash. But seriously EE is the worst provider and one of the most hated companies in UK. I would rather pay someone on the street with z3x box than them
in our country we can get unlock code for free, but only till one month from end of contract. later they ask money.
i hate them too for asking money, but on other hand: why they should do anything for free if phone is yours and not their.