Hello:
I sent my NEXUS in to SAMSUNG for a touch screen non-responsive on the left side issue. The tech stated there were no problems with my NEXUS S!
Upon turning it on, there is a padlock on the botton of the Google splash screen.
I called Samsung and the "level 3" tech said that my phone was now locked to T-mobile. I though that was BS.
Anyway what is it and, can I get it back to normal? My wife has the same phone and here does not have any problems so far.
I've attached a pic of the screen that shows the padlock. Thanks for the help.
Chiefdroid
that means your phone is unlocked as far as I know. I did my first unlocking and rooting of my nexus last night. When I went through the unlocking process, the "unlocked padlock" started to appear on my startup. If you hold "volume up" and the power button and turn the phone on. it should say unlocked on the fastboot screen...
You have unlocked the bootloader my young Jedi.
Sent from my Nexus S using XDA App
yup, unlocked bootloader.
thats not a bad thing, its a wonderful thing!
lol you rooted your phone and unlocked the bootloader. that is what that lock symbol means. did you forget, or not do this on purpose?
Thanks to all that replied!! I kinda figured that is what it was.. Like I said I didn't do it, the Samsung repair facility in Texas unlocked it. I called the Nexus S support line and the Level 3 tech said " When we reflashed your software, it locks your phone into the T-mobile network" and that was after she went down the hall and consulted with the "developers", Samsung tech support is a Joke. One day I'm gunna root this thing!
Thanks Again Guys.
And to the XDA moderator, sorry I posted in wrong section initially, rookie mistake..
Anybody know how to remove this lock symbol? How to re-lock the bootloader again?
soulja786 said:
Anybody know how to remove this lock symbol? How to re-lock the bootloader again?
Click to expand...
Click to collapse
fastboot oem lock
about op, what sensitive issue did you notice in your screen?
thiagodark said:
fastboot oem lock
about op, what sensitive issue did you notice in your screen?
Click to expand...
Click to collapse
Ive tried that but it doesnt work, I can reboot the bootloader via cmd but the above command has no effect? Any ideas why?
Thanks
soulja786 said:
Ive tried that but it doesnt work, I can reboot the bootloader via cmd but the above command has no effect? Any ideas why?
Thanks
Click to expand...
Click to collapse
several ideas, what error did it show? what is shown in device manager when you plug your phone in the pc in bootloader?
edit: how did you unlock it?!
Try this, these guys do a great job if breaking things down.
http://theunlockr.com/2011/01/20/how-to-unroot-the-nexus-s/
Sent from my Nexus S 4G using XDA Premium App
thiagodark said:
several ideas, what error did it show? what is shown in device manager when you plug your phone in the pc in bootloader?
edit: how did you unlock it?!
Click to expand...
Click to collapse
When I go type in 'fastboot devices' or 'Adb devices' it says
"list of devices attached:" and nothing underneath it .....
I have tried updating drivers via PDAnet .... still nothing.
the drivers I have are 'ADB interface'.
Am I missing drivers specific for bootloader or something??
Basically, the phone wouldnt restore or factory reset, so I decided to root it? so I found a new '1 click root and recovery'.
Once I run the script, it unlocked bootloader and also reset my phone which worked great. Only thing I want to do now is remove the open padlock icon on the google screen (which I think is by re-locking bootloader) but when I put in the typical 'fastboot oem lock' nothing happens .....
Much appreciate the help, thanks.
You got to remove everything "custom" (cwm recovery, user roms etc) from the device before you can lock the bootloader again.
When you are trying to lock your bootloader it doesn't do anything because your device isn't correctly recognized by windows, this is prolly due to missing/wrong drivers (try uninstalling old ones and then follow the unlockr guide to rooting your phone/installing adb, http://theunlockr.com/2009/10/06/how-to-set-up-adb-usb-drivers-for-android-devices/).
rentaric said:
You got to remove everything "custom" (cwm recovery, user roms etc) from the device before you can lock the bootloader again.
When you are trying to lock your bootloader it doesn't do anything because your device isn't correctly recognized by windows, this is prolly due to missing/wrong drivers (try uninstalling old ones and then follow the unlockr guide to rooting your phone/installing adb, http://theunlockr.com/2009/10/06/how-to-set-up-adb-usb-drivers-for-android-devices/).
Click to expand...
Click to collapse
are you positive sure that i can't lock my bootloader with customs kernels, roms or recoveries? i don't think that's entirely true!
soulja786 said:
When I go type in 'fastboot devices' or 'Adb devices' it says
"list of devices attached:" and nothing underneath it .....
I have tried updating drivers via PDAnet .... still nothing.
the drivers I have are 'ADB interface'.
Am I missing drivers specific for bootloader or something??
Basically, the phone wouldnt restore or factory reset, so I decided to root it? so I found a new '1 click root and recovery'.
Once I run the script, it unlocked bootloader and also reset my phone which worked great. Only thing I want to do now is remove the open padlock icon on the google screen (which I think is by re-locking bootloader) but when I put in the typical 'fastboot oem lock' nothing happens .....
Much appreciate the help, thanks.
Click to expand...
Click to collapse
what is your phone 4g or gsm?!
i have nexus s.its dead.i mean its not going forward from gogle logo.and boots into bootloader.it says lock status: locked.
i'm unlocking bootloader using fastboot.but when i click unlock bootloader on nexus s.it wont go further on tht.and stucked on it.i evn discconected it and tried again.but in fastboot and cell to nothing go beyond that.on nexus that unlcking bootloader screen with yes and no options and in ommand prompt
fastboot oem unlock
...
stucked on above situation.help guys!!!
thnku.
how much time it take approxmtly to unlock bootloader?means ho much time i have to wait to knw it might not working.??
If it doesn't work within a minute something is going on. Good luck sorting it out.
There are other rooting methods though, you can give them a try.
yep.its taking more than 15mins.i have clockworkmod installed.but due to locked bootloader i cant use it for flashing.i need stock recovery for nexus s.i9020t.
i have sock rom too.but while flashing it say android-text.txt and android-prduct.txt not found.any help please!!!
Hey there. I'm new here, and to be honest, I'm new to the world of smart phones. The 4xHD is my first smartphone and I've had it for about a year now. I've noticed that it performs really badly on the 4.1.2 JB so I've decided to root it, unlock the bootloader, flash cwm and get a Cyanogenmod 10.1.3 up and running on it.
Long story short, I've rooted my phone and followed this http://forum.xda-developers.com/showthread.php?t=2245836 thread to unlock the bootloader but it didn't really go as planned. I did the things in the cmd app on the phone, and did the first line of cmd on my lap top (adb reboot bootloader) and when I wanted to do the second line (fastboot oem unlock) the cmd said it was waiting for the device. I waited for 5 minutes and nothing was happening on the device. It was stuck on the LG screen (not the one with flashing lights, just the logo screen). I pulled out the USB and pressed volume down and the power button just in case. Then I pulled out the battery, turned on my phone and went to the 3845#*880# secret menu to check the bootloader status. When I tapped on the bootloader unlock check thing, it said "Unlock".
So, did I just unlock the bootloader? Operation successful? Is there a possibility that I didn't unlock the bootloader in a correct way so it will brick my device when I try to flash cwm and Cyanogen?
I'm really sorry if this thread is in a wrong section or something. I searched on the xda but couldn't find the answer to my question.
Thanks in advance
EDIT: I'd also like to mention that in no part have I encountered the screen which said "you're about to unlock your bootloader, warranty voiding, blah blah blah, are you sure you want to proceed"
hi - i have in my nexus 5 only the google logo and the unlocked key is on the screen;
when i get to fast boot it does see the device.
when ienter " fastboot oem device-info
igot device tampered true
device unlock true
off mode charge - true
when i try to write twrp recovery it says sending recovery okay and writing recovery okay.
but ucant enter to the recovery of twrp.
when i try to flash an image it says:
writing bootloader
failed (remoteflash write failure)
rebooting into bootloader okay
writing radio - failed remoteflash write failure
target reported max size of 1073741824bytes
is there any way to save my phone?
i can enter adb its says on the phone "now send the package you want to apply to the device with "adb sideload filename"..
how do i can send an image?
thank u
re
i try to flash with the lg flash rool - i did everything ok and it stuck in 6% and says"user data erase fail" what can i do?
You're using the batch commands included with the stock ROM to re-flash?
Hi my Nexus 5 also suddenly die too. And I have the same exact problem that you have when trying to flash it. I looked for hours on the internet tried formatting, erasing and many other alternatives and nothing. There are some people experiencing this same problem like us. For no reason the memory is getting corrupt or died. I get mant errors on the cache when I boot to regular recovery. The only recovery that I have manage to boot to (except for the original one) is Clockworkmod using fastboot boot "therecoveryname.img". With clockworkmod I have adb working but still can get the phone to boot or accept factory images. I can't lock the bootloader either.
I think this error was cause by the software. There was a very similar problem that never got fixed for the nexus 7 when lollipop came out.
Do you need to lock the bootloader? Once locked, you cannot flash anything via fastboot commands, not even a stock ROM.
No I don't need to. I tried just to see if the phone will relock itself. I read somewhere in the internet that if you can't relock/unlock the device the nand if fried.
If you look for these errors there are people with LG G2 and LG G3 that are having something similar happen. I think LG hardware is partly behind the problem. I call Google and told them about it and the put me through LG which want me to send the phone for repairs but not free. My guess is that it will be way to expensive to repair and that is not worthy.
Hopefully someone with real repair skill can give us light if this is something fixable by software.
audit13 said:
Do you need to lock the bootloader? Once locked, you cannot flash anything via fastboot commands, not even a stock ROM.
Click to expand...
Click to collapse
I had two different Nexus 5 phones that were stuck in a bootloop with the spinning coloured KK animation.
Every time I unlocked the bootloader, the bootloader would always re-lock itself when rebooting. Even when I managed to unlock the bootloader, I could not re-flash a stock ROM because the bootloader kept relocking itself.
Whenever I unlocked the bootloader, the phone would only take 2 ot 3 seconds to wipe the phone which is too fast.
In the end, I purchased a nexus 5 with a smashed screen to use its motherboard in my defective N5.
I have never come across a post where someone was able to solve the problem unless they had LG replace the motherboard with a new imei.
i try to go back to stock to use google pay, and I did a search on relocking the bootloader, i see alot of people mentioning that to do it in download mode, but my computer only recognizes the phone while in bootloader? all the fastboot command work, but it cant even detect device in download? am i missing something or?
thanks in advance
Bootloader is white screen multicolour writing.
Download is black screen red writing.
Recovery is obvious..
Im not sure if you can just straight forward lock the bootloader and it show as "locked" rather than "relocked" and I couldn't tell you which one safetynet requires or if there is a preference at all.
Either way make sure you do it at the correct part of the process.