hi, im new here. I have a question regarding my galaxy s4 i9505 which is already stated in the title. Im currently using Optimized Cm13 by JDC team which runs in my very old bootloader I9505ZHU and modem. Though i dont have any problems with it, i would still like to update to later version of bootloader like i9505XX that is where the custom rom is based. So is it possible?
Yes.
There is a guide and links to modem files in the S4 General Section.
The guide is by the user Bon_Bon. It's pretty detailed. Though I'm not sure if the modems and bootloaders listed there are the most recent, but they certainly aren't that old either.
Also, you may find that going to the last pages of that thread, users have posted the latest modem/bootloader combo. If not, there's another - older - modem thread that may have them.
Another way to get the latest bootloader and modem on the phone is pretty simple: use TWRP to backup your exiting ROM, flash the latest stock ROM from sammobile.com with Odin, flash TWRP with Odin, and restore backup from TWRP.
Related
Hey there everyone. I am trying to help my sister out with her (new to her) S4.
She bought an s4 and it is very cool (I'm having a blast playing with it.).
It is carrier unlocked at the moment (I believe, though I don't have a SIM to test it out with)
I believe that it is rooted.
It is advertised as having the MDB bootloader with a MF3 baseband. How do I check this?
When I go to setting I see that the baseband version is i337ucuamf3. I am assuming that since it ends in MF3 that is correct.
The rom installed is GoldenEye 38.1 XXUGNG8.
I am assuming that XXUGNG8 is the base firmware from Samsung\At&T, is that correct?
It currently has a version of TWRP installed and the person it was bought from says it doesn't need SafeStrap. Is that correct? I see a lot of posts saying that safestrap needs to be installed.
Lastly, I'm trying to figure out if she wants CM11, Stock TouchWiz or something like Goldeneye. I am assuming that the "S" apps will only work on a TouchWiz ROM, is that right?
Lastly, how would i get the phone back to a stock? HTC has RUU's, is there an equivalent for Samsung devices? Or is there a download somewhere of the plain stock ROM? I didn't see anything in the development section.
Thanks in advance for all the help, I know that I am asking a lot of questions but I am coming from the HTC side of android (which seems to be a lot less confusing) so I am doing the best I can here.
waterboy100 said:
Hey there everyone. I am trying to help my sister out with her (new to her) S4.
She bought an s4 and it is very cool (I'm having a blast playing with it.).
It is carrier unlocked at the moment (I believe, though I don't have a SIM to test it out with)
I believe that it is rooted.
It is advertised as having the MDB bootloader with a MF3 baseband. How do I check this?
When I go to setting I see that the baseband version is i337ucuamf3. I am assuming that since it ends in MF3 that is correct.
The rom installed is GoldenEye 38.1 XXUGNG8.
I am assuming that XXUGNG8 is the base firmware from Samsung\At&T, is that correct?
It currently has a version of TWRP installed and the person it was bought from says it doesn't need SafeStrap. Is that correct? I see a lot of posts saying that safestrap needs to be installed.
Lastly, I'm trying to figure out if she wants CM11, Stock TouchWiz or something like Goldeneye. I am assuming that the "S" apps will only work on a TouchWiz ROM, is that right?
Lastly, how would i get the phone back to a stock? HTC has RUU's, is there an equivalent for Samsung devices? Or is there a download somewhere of the plain stock ROM? I didn't see anything in the development section.
Thanks in advance for all the help, I know that I am asking a lot of questions but I am coming from the HTC side of android (which seems to be a lot less confusing) so I am doing the best I can here.
Click to expand...
Click to collapse
Since the phone has TWRP installed, you either have MDB or MDL bootloader since newer firmwares (bootloader) do not allow for the stock recovery to be replaced.
http://forum.xda-developers.com/showpost.php?p=52415064&postcount=1625 gives you the way to find your bootloader (the most restrictive component of the firmware).
When samsung releases firmware/update, it sets the version of all components to the same. So, on the stock firmware, all components have the same version. Baseband is actually the version of the modem.
Since you have TWRP installed, you should be able to install a lot of ROMs. All you have to ensure is that the bootloader is not updated. When you use ODIN to flash stock firmware, your bootloader will get updated. Since MF3, we are not able to replace the stock kernel and recovery. This brings in a lot of restrictions.
http://forum.xda-developers.com/showthread.php?t=2616221 has a list of ROMs that can be installed.
jmjoyas said:
Since the phone has TWRP installed, you either have MDB or MDL bootloader since newer firmwares (bootloader) do not allow for the stock recovery to be replaced.
http://forum.xda-developers.com/showpost.php?p=52415064&postcount=1625 gives you the way to find your bootloader (the most restrictive component of the firmware).
When samsung releases firmware/update, it sets the version of all components to the same. So, on the stock firmware, all components have the same version. Baseband is actually the version of the modem.
Since you have TWRP installed, you should be able to install a lot of ROMs. All you have to ensure is that the bootloader is not updated. When you use ODIN to flash stock firmware, your bootloader will get updated. Since MF3, we are not able to replace the stock kernel and recovery. This brings in a lot of restrictions.
http://forum.xda-developers.com/showthread.php?t=2616221 has a list of ROMs that can be installed.
Click to expand...
Click to collapse
Thanks.
So my bootloader is reported as i337ucuamdb (So MDB Bootleader)
My baseband is 1337ucuamf3 (MF3?)
Does this just mean that i have an older bootloader that was rooted and had newer radios installed?
That that a problem for anything? Should they be the same?
waterboy100 said:
Thanks.
So my bootloader is reported as i337ucuamdb (So MDB Bootleader)
My baseband is 1337ucuamf3 (MF3?)
Does this just mean that i have an older bootloader that was rooted and had newer radios installed?
That that a problem for anything? Should they be the same?
Click to expand...
Click to collapse
You're on the mdb bootloader which is a good thing, don't update the firmware you can still use twrp or cwm. The baseband is the modem and does not need to be the same version as the bootloader
Sent from my Nexus 5 using XDA Free mobile app
Purchased my S4 at launch, only rooted it and never really got around to tweaking it much. It has slowed down a bit so now is the time.
I'm on MDL, stock 4.2.2, and rooted with TWRP 2.5.0.2 On to the questions/clarifications, hopefully these aren't egregious. I know the info is out there but for actually finding specific information, the xda forums are a bit overwhelming and sometimes conflicting...
1) Recovery - Latest/preferred recovery for the s4 (on MDL) with auto-loki baked in? Are any of the latest versions of TWRP/CWM dangerous/incompatible or can I just install the latest/greatest with ROM Installers and go from there?
2) Modem - Flashing an updated modem, regardless of ROM/OS # should not break anything and/or lock down the bootloader any more so than it already is at MDL, correct? Updating the baseband will have no effect on the build # and thus loki is still and option (versus safestrap)? Preferred modem at this time? (ATT, SF Bay Area)
3) ROMS - Any ROM, followed by loki patch or flashed via an auto-loki capable recovery should be fine, correct? Is a ROM specifically built for safestrap applications and thus would not work with MDL, or are ROMs noted as being safestrap ready just able to be used via safestrap, but loki as well?
4) Hard to keep track of all the ROMs and the builds and branches etc - Can anyone point me in the right direction of either a) the latest stock touch-wiz 4.4.4 ROM that can be flashed over MDL without essentially updating past MDL? b) the best/most recent pure google (Play Store S4 Edition) ROM, same story with not breaking MDL?
Again, I apologize I am sure the info is all buried in here somewhere, it just gets to a point where pointed questions rather than multiple 500+ post threads are hopefully less likely to brick my phone. Ideally I just want to get on the latest software (and enable screen casting, for one). Assuming it comes quick enough, once I get this process down I will probably make the jump to 5.0 when it is ready, anticipate a couple months? Who knows.
Thanks, much appreciated.
Norcalz71 said:
Purchased my S4 at launch, only rooted it and never really got around to tweaking it much. It has slowed down a bit so now is the time.
I'm on MDL, stock 4.2.2, and rooted with TWRP 2.5.0.2 On to the questions/clarifications, hopefully these aren't egregious. I know the info is out there but for actually finding specific information, the xda forums are a bit overwhelming and sometimes conflicting...
1) Recovery - Latest/preferred recovery for the s4 (on MDL) with auto-loki baked in? Are any of the latest versions of TWRP/CWM dangerous/incompatible or can I just install the latest/greatest with ROM Installers and go from there?
2) Modem - Flashing an updated modem, regardless of ROM/OS # should not break anything and/or lock down the bootloader any more so than it already is at MDL, correct? Updating the baseband will have no effect on the build # and thus loki is still and option (versus safestrap)? Preferred modem at this time? (ATT, SF Bay Area)
3) ROMS - Any ROM, followed by loki patch or flashed via an auto-loki capable recovery should be fine, correct? Is a ROM specifically built for safestrap applications and thus would not work with MDL, or are ROMs noted as being safestrap ready just able to be used via safestrap, but loki as well?
4) Hard to keep track of all the ROMs and the builds and branches etc - Can anyone point me in the right direction of either a) the latest stock touch-wiz 4.4.4 ROM that can be flashed over MDL without essentially updating past MDL? b) the best/most recent pure google (Play Store S4 Edition) ROM, same story with not breaking MDL?
Again, I apologize I am sure the info is all buried in here somewhere, it just gets to a point where pointed questions rather than multiple 500+ post threads are hopefully less likely to brick my phone. Ideally I just want to get on the latest software (and enable screen casting, for one). Assuming it comes quick enough, once I get this process down I will probably make the jump to 5.0 when it is ready, anticipate a couple months? Who knows.
Thanks, much appreciated.
Click to expand...
Click to collapse
I will try to help with a few of these questions, but others I am not familiar with very much. On that note DO NOT update your bootloader!!! It will be locked down further and Loki will NOT WORK. And you could NOT flash any kernels with safestrap. So with safestrap ONLY the stock kernel can be used. Now on to your questions...
1) I am using TWRP 8.1 if I remember correctly. You can find it in the Original Android Development section. It does NOT Auto Loki, so keep the loki-doki flashable zip on your sdcard OR use Roms that already have/use the boot.Loki kernels like ShoStock-i 8.1
2) Modem flashing will NOT lock anything up further as far as the bootloader. You can flash ANY or ALL of them from my modem thread. See which works BEST FOR YOU in YOUR AREA. I am in So Cal and the best for me has been either MDL. But I have and do test ALL of them. You can always flash back to whichever one works best for you.
3.) Like I said I use ShoStock-i 8.1 because it has and does EVERYTHING I need my phone to do and does it without any issues. I have NOT tried to use a Safestrap modified ROM so I have very little experience with that. Normally most devs will have two separate versions, one for safestrap compatible and one for us without safestrap. ShoStock-i is already built with Loki in the kernel so you do not NEED to flash Loki-Doki patch.
4) there are NO Touchwiz 4.4.4 Stock Roms for ATT yet. But I did try out one of the Touchwiz 4.4.4 T-Mobile based Roms and it worked perfectly. You can either get it from the ATT forums and I believe it is already lokified, or get it from the T-Mobile forum and make sure to flash Loki-Doki patch before booting up phone after flashing the ROM. Again the will NOT update your bootloader past your MDL bootloader, so you are good as you are with no worries. By the way on ShoStock-i 8.1 the screen casting to Chromecast works PERFECTLY without having to flash any other .apk's or mess with ANYTHING
This is the exact same boat I'm in. Trying to track down the answers as well. Will keep an eye here as well to watch for answers.
awesome reply thanks RockRatt, that just about covers it. I will maybe give the ShoStock ROM a go and see how I like it. As long as all the normal features are working fine, I should be good.
One last thing I forgot - Odin. I have the stock odin firmware files from when my phone was new (The MDL package). As long as I dont update the bootloader, I should be able to Odin back to the brand new in box state should something go awry or not dig the other ROMs, correct?
Thanks again,
Norcalz71 said:
awesome reply thanks RockRatt, that just about covers it. I will maybe give the ShoStock ROM a go and see how I like it. As long as all the normal features are working fine, I should be good.
One last thing I forgot - Odin. I have the stock odin firmware files from when my phone was new (The MDL package). As long as I dont update the bootloader, I should be able to Odin back to the brand new in box state should something go awry or not dig the other ROMs, correct?
Thanks again,
Click to expand...
Click to collapse
Yep. Just don't update the bootloader...So no flashing newer firmware that contains the bootloader files. Most if not all custom Roms do not have the bootloader files in them. So no problem flashing back to MDL stock if the need never arises. I still in fact have the original MDB bootloader installed that came with the phone before the MDL firmware update.
I'm going looking into flashing a custom ROM on my sister's i337m (on Rogers) . Currently it is on Lollipop OTA update, and she says that ever since the update it has been super slow and laggy. I told her i can flash a custom ROM and it should be much better performance (in my experience good custom roms can provide much better performance than stock firmware in most cases).
I'm not familiar with the S4 specifically but have been using custom ROMs myself on various other phones so i generally familiar with the procedures involved. Just want to ask for advice on a couple points.
1) From what i've read so far i am trying to decide between Goldeneye and Kangapop. both seem to be pretty solid options. I noticed in the install instructions for both it mention that the i337m useres need to have 4.4.2 baseband and bootloader. Is there any specific one that works better than others i see a few different stock versions of 4.4.2 for i337m Rogers on sammobile (MG1, NC1, NE1, NI2) I am currently downloading the most recent NI2. Just not sure if specific versions have any bugs, flaws or advantages/disadvantages to worry about..
2) I figured while i'm going to have to downgrade the firmware to install the custom ROM i might as well try the Root/Unlock procedure from this thread . Is this still working? I think i would need to flash the stock NI2 firmware then follow the procedure in that thread to root and unlock the phone then from there i could install Goldeneye or Kangapop? Has anyone done this or can confirm if it should work this way.
Thanks
Hello. I am attempting to flash new BL and Modems using Odin 3.10.6 on a Windows 7 partition on a Macbook Pro mid-2012 OS 10.10. My phone is a T-Mobile Samsung Galaxy S4, Baseband number M919UVUAMDL. My current build number on my phone is Omega v7.0 - XXUBMF8. I'm trying to upgrade to Omega v42 - XXUHOF2.
My problem:
Odin recognizes my phone fine but fails the flash very quickly. The fail message Odin gives is "FAIL! (auth)" right after "NAND Write Start!!" and my phone displays the message "Secure Check Fail: aboot". This happens no matter what USB cable I use.
The files I'm trying to flash are:
BL_I9505XXUHOF2_user_low_ship_MULTI_CERT.tar
GSM_Modem_I9505XXUHOF2_and_LTE_Modem_I9505XXUHOF2.tar
Any help?
You can't flash an I9505 bootloader or modem on a T-Mobile S4. You can only use a T-Mobile bootloader and modem. So search the T-Mobile S4 forums for the most current bootloader and modem, and flash them through Odin.
Thank you for the help. I am now quite confused and need more help, if it can be spared.
I understand now that I can only use SGH-M919 bootloaders and modems but I can use Omega ROMs, too. I tried my best to find current, and any, bootloaders and modems on the SGH-M919 forum without success. I'm not an idiot but I'm also not experienced with navigating this forum. Can anyone offer more specific direction to SGH-M919 bootloaders and modems?
Some other questions I now have:
- Do I need Lollipop BL/modem in order to flash a Lollipop-based custom ROM or can I use any generation BL/modem?
- Will all Lollipop-based custom ROMs require me to flash new BL/modems? Can I just find a ROM that doesn't require new ones?
If it seems like I'm confused or ignorant of more issues than I've addressed, it probably because I am. Any and all help and education is greatly appreciated. Thanks.
There is a link to the T-Mobile S4 forums in my previous post. Make a thread in their Q&A section and ask where the bootloaders and modems are. If I recall however, the T-Mobile S4 never went past 4.4.4, though I hope I'm wrong. Regardless, while these ROMs all recommend the latest Android 5.x bootloaders and modems, they should still work with whatever you do have available. Performance may however be affected.
Hi there,
I've been struggling with an Note 3 that for some unknown reason doesn't detected the SIM card unless it's flashed with the stock ROM. The stock ROM doesn't include the bootloader/modem and contains only the OS. I've been asking around on the baseband thread[0] about this but I think this is a broader issue as I can get the phone to work (including SIM detection) with custom bootloader/modem.
Below the steps I've taken so far:
Step 01: Recently I acquired a Note 3 and installed LineageOS 14.1 on it.
Step 02: I noticed that the SIM was not detected by LineageOS and read up on this topic via the usual channels (e.g. reddit, xda forums, LineageOS JIRA). Based on the information I gathered I tested various bootloader/modem settings, especially those other reported as working, but couldn't get LineageOS to detect the SIM with any of these. This is where I signed up to this forum and created my first post describing the situation thus far. [1]
Step 03: After the feedback on this thread I confirmed that the bootloader/modem were flashed correctly. To eliminate any other causes of the firmware being broken by redoing most of the tests with Odin (I've mainly used Heimdall up till that point). Still LineageOS didn't detect my SIM even with combinations that worked for others. [2]
Step 04: To exclude it was an issue specific to LineageOS I installed ~10 other custom ROMS from different groups and using different versions of Android. In all of these the SIM was still not detected. [3]
Step 05: After installing the stock ROM (without the matching bootloader/modem) the Note 3 was suddenly detecting the SIM and I was able to make phone calls. [4]
Step 06: I expressed my confusion about the earlier not working bootloader/modem not working with the other ROMs but that those did work with the stock ROM. [5]
This is where we are now. I don't fully grasp why the stock ROM (which doesn't include bootloader/modem) does detect my SIM whilst all the other custom ROMs don't although they're having the same bootloader/modem binaries that should make it work.
Anyone has experienced this before as well or know what might be the issue?
Thanks!
.san
[0] https://forum.xda-developers.com/galaxy-note-3/general/bootloader-baseband-bl-cp-samsung-t3582504
[1] https://forum.xda-developers.com/showpost.php?p=77273094&postcount=378
[2] https://forum.xda-developers.com/showpost.php?p=77281260&postcount=383
[3] https://forum.xda-developers.com/showpost.php?p=77288153&postcount=385
[4] https://forum.xda-developers.com/showpost.php?p=77307322&postcount=388
[5] https://forum.xda-developers.com/showpost.php?p=77344832&postcount=390
Where are your getting the stock ROM? As far as I know, roms on sammobile.com, updato.com, and samsung-firmware.org all contain a bootloader and modem with the exception of some 4.1.1 or 4.1.2 ROMs.
audit13 said:
Where are your getting the stock ROM? As far as I know, roms on sammobile.com, updato.com, and samsung-firmware.org all contain a bootloader and modem with the exception of some 4.1.1 or 4.1.2 ROMs.
Click to expand...
Click to collapse
I've grabbed them via a page on the ROMs section of this subforum (second link): https://forum.xda-developers.com/showpost.php?p=72540914&postcount=4340
Direct ROM download link: https://mega.nz/#!VU13SY5J!GrYB2Wqbo7DNs_Bbg8trkUcftaeES8jfgWMqXepv2cw
[EDIT] Perhaps I'm wrong and this ROM does include the modem and bootloader. In that can I can perhaps (don't know how) extract the modem/bootloader from that and combine it with a custom ROM. But if it doesn't contain these binaries than I'm clueless on what makes the stock ROM detect the SIM where other ROMs don't.
That mega link says
S5.
Not Note 3.
As does the thread say.
N9005][4.4.2] Galaxy S5 Stock ROM
Thats a 2014 post .
Why not flash stock rom from 2017/18 sources ??
JJEgan said:
That mega link says
S5.
Not Note 3.
As does the thread say.
S5.
You have a Note 3 ??
Click to expand...
Click to collapse
NO SIR.
the highlited link which he gave is from a stock rom ported for Note 3 N9005.
S5 stock rom for Note 3....
JJEgan said:
That mega link says
S5.
Not Note 3.
As does the thread say.
S5.
You have a Note 3 ??
Click to expand...
Click to collapse
Och that is sloppy... not sure why I found that in the Note 3 ROMs section but I should have double checked. Its still weird that that specific ROM does work with the pre-flashed modem/bootloader whist other ROMs don't, right?
I think I have a complete firmware package (that requires Odin/Heimdall) from sammobile somewhere. I'll double check that one.
.san said:
Och that is sloppy... not sure why I found that in the Note 3 ROMs section but I should have double checked. Its still weird that that specific ROM does work with the pre-flashed modem/bootloader whist other ROMs don't, right?
I think I have a complete firmware package (that requires Odin/Heimdall) from sammobile somewhere. I'll double check that one.
Click to expand...
Click to collapse
you can use BL and CP files form here. and flash them separately via odin and check if it works.
https://forum.xda-developers.com/galaxy-note-3/general/bootloader-baseband-bl-cp-samsung-t3582504
dark_phoenix said:
you can use BL and CP files form here. and flash them separately via odin and check if it works.
https://forum.xda-developers.com/galaxy-note-3/general/bootloader-baseband-bl-cp-samsung-t3582504
Click to expand...
Click to collapse
That is what I tried to explain in the OP. These bootloader/modem combinations ONLY work with the stock ROM I linked to.
As I said its not a Note 3 stock rom.
Its a custom /ported rom.
Stock sammobile. Updato.com etc
.san said:
I've grabbed them via a page on the ROMs section of this subforum (second link): https://forum.xda-developers.com/showpost.php?p=72540914&postcount=4340
Direct ROM download link: https://mega.nz/#!VU13SY5J!GrYB2Wqbo7DNs_Bbg8trkUcftaeES8jfgWMqXepv2cw
[EDIT] Perhaps I'm wrong and this ROM does include the modem and bootloader. In that can I can perhaps (don't know how) extract the modem/bootloader from that and combine it with a custom ROM. But if it doesn't contain these binaries than I'm clueless on what makes the stock ROM detect the SIM where other ROMs don't.
Click to expand...
Click to collapse
That is not a stock ROM, it is custom ROM that doesn't contain a bootloader or modem. You need to flash the latest stock ROM from sammobile.com or updato.com.
I did a quick test with a full stock firmware package from sammobile. Also with this package I get the SIM card detected. The moment I flash, using TWRP, another ROM (just tested a recent LineageOS 14.1 nighty) the SIM card is no longer detected. As far as I'm concerned this excludes the stock firmware from the pile of options and re-affirms my suspicion that it is something related to the ROMs themselves. The Samsung ROMs (either official or ported) do something different than any of the other ROMs... at least on this device.
Its your phone then thats the problem.
Which stock ROM are you flashing?
audit13 said:
Which stock ROM are you flashing?
Click to expand...
Click to collapse
N9005XXSGBPL4_N9005PHNGBOJ1_PHN which I got from this sammobile page.
That did look like the latest ROM.
Just to confirm but flashing stock ROM, flashing twrp, and flashing a custom ROM gives you the sim problem?
audit13 said:
That did look like the latest ROM.
Just to confirm but flashing stock ROM, flashing twrp, and flashing a custom ROM gives you the sim problem?
Click to expand...
Click to collapse
Yup, that is the issue! Weird isn't it?
.san said:
Yup, that is the issue! Weird isn't it?
Click to expand...
Click to collapse
Yes, it is strange.
Unfortunately, I'm out of ideas.
.san said:
Yup, that is the issue! Weird isn't it?
Click to expand...
Click to collapse
yes. this is weird.
but on the other hand just to know.
did you try different sim's ? may be the issue is related to that particular sim card.
i too have note 3 N-9005. but i never faced this type of situation ever.
my current Bootloader (BL) is N9005XXUGBPH2
Baseband (CP) is N9005DXUGBOK3
Current Rom is AryaMod Note 7 Port 2.1
i have used Ressurection remix, C9 pro upto version 4, magma Nx, Los 14, Arya mod v.9 on this same BL and CP. and NO issues so far.
may be you can try once more with these same settings/files as mine.
1st Flash Stock Rom
2nd Check from Phone Info your current settings in the Firmware tab (backup it's apk now, so that you can install it later without logging in G-services.) screenshot attached. Download the SAME BL & CP and flash it via ODIN.
3rd if it's the same, then go ahead and use TWRP 2.8.7.0 (this version is what i use).
4th now flash any of these roms written above. start with RR as the Rom is lesser in size.
5th (optional) if you want to flash a different kernel too, but flash after rom if the kernel included does not work.
now tell us the results, if the issue is resolved or not.
ONE MORE THING.
this model N9005 does not have LTE Band 40 support so if your network only provide LTE on band 40 like mine does. LTE wont work. Only 2g or 3g will work. and stock rom's 1st option of network is 2g or 3g i think.
HI,
think I'm having the same problem here. Except for me the official 14.1 version is detecting my sim card. All other "unofficial versions" 15.1 &16 are not detecting my SIM card. Any workarounds ?
Ive had the issue to with even the touch wiz variants of arya mod and others I'm in the united states though and I have to do tmo variants of aosp. Im using a emmc brick bug unlocked note 3. I'm on vzw btw. Im worried to do a full flash because ive seen mixed things on doing a full Odin update on the emmc brick bug phones saying it reverses the unlock