Related
Recently got an R800at from ebay that was unlocked (first ever smartphone, woo). I was able to use my dad's sim card no problem, and dialing the number for the settings window showed no column stating whether the bootloader was allowed to be unlocked or not - according to some threads I've read, users who had unlocked Plays also had the same experience, leading me to believe my bootloader was indeed unlocked.
After following the Gin2Jellybean guide, I managed to brick my phone today (stuck on sony ericsson text), but restored via downloading a stock rom off the internet and installing via flashboot (the SUS and pc companion were having issues - they said no software was available or I had the most up to date software).
Now it seems I goofed up a second time; I was following the Gin2Jellybean guide again when I realized I was following the version for locked bootloaders! I was already on step 4 to install CWM when I realized this, but I decided to just try to install doomlord kernel v14 as per normal and hope that the doomlord root toolbox from the locked bootloder tutorial that I had used wouldn't conflict with anything.
Upon reading the directions for doomlord kernal v14, I decided to double check that my bootloader was still the same as yesterday (before I had bricked my phone). As it turns out, I now have a column for bootloader, and it says unlocking is not allowed. So what's the deal, was my phone's bootloader actually unlocked in the first place, and if so, why is it not unlocked now? According to this thread (http://forum.xda-developers.com/showthread.php?t=1720201), bootloader unlocking is permanent.
Here's the link to the guide I'm following: http://forum.xda-developers.com/showthread.php?t=1631144
Gonna go take the dog for a walk now and listen to some calm relaxing music... Hopefully I didn't screw myself over here.
So when you typed in that code, you got told that your bootloader can't be unlocked? If this is the case, you would have to pay to have it unlocked by someone such as Alejandrissimo. It may be that your bootloader was never able to be unlocked as i can't think of why that would change
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
SIM unlock and bootloader unlock are two very different things, as you've probably found out by now; the r800at models can't be bootloader-unlocked with the free Sony method; you're going to have to pay someone, and it'll cost you at least $20. If you got one of the phones from the guy selling them for $105 on eBay, I'm pretty sure those are SIM-unlocked only.
If you don't want to pay extra, there's nothing wrong with keeping it locked; there're a few ROMs you won't be able to use, and you can't change your kernel, but for the most part you should have a good experience.
FEGuy said:
SIM unlock and bootloader unlock are two very different things, as you've probably found out by now; the r800at models can't be bootloader-unlocked with the free Sony method; you're going to have to pay someone, and it'll cost you at least $20. If you got one of the phones from the guy selling them for $105 on eBay, I'm pretty sure those are SIM-unlocked only.
If you don't want to pay extra, there's nothing wrong with keeping it locked; there're a few ROMs you won't be able to use, and you can't change your kernel, but for the most part you should have a good experience.
Click to expand...
Click to collapse
Everything you said seems to be spot on. The only thing that doesn't add up is why there wasn't anything saying one way or the other whether my bootloader was unlocked yesterday, but now today there is.
And ya, I probably won't end up paying the $20; basically I just wanted to remove bloatware and have a nice looking interface. Besides the question about why there was nothing on my bootloader yesterday, can you say offhand whether my sim should still be unlocked? I don't have one nearby to test.
Go to the dialer and enter *#*#7378423#*#* and go to Service Info -> SIM lock. The bottom line should say SIM 0 if it's unlocked. As for why it wasn't showing the bootloader status, I don't know. I was having the same problem yesterday, on multiple ROMs, so perhaps it was added in some specific update.
I unlocked my bootloader several months ago, but now my SIM card readers (both of them) have gone out. I have no idea how, no water damage or anything like that has happened. They just stopped working. So I went complete stock firmware, locked bootloader, everything but I am still unable to take OTA updates like a new phone would be able to. I think this is because they banned my device from OTAs which I believe they do if you have messed with the device. I need to RMA my device so my question is would it be better to say that I didn't tamper with the device and run the risk of them finding out I did, which is pretty likely seeing as how my device has been banned from OTA updates, or tell them that I did unlock it and all of that but that I have relocked it and I am back to stock? If any of you have had a similar issue how did ASUS handle that? Thanks!
E3AANG11E3 said:
I unlocked my bootloader several months ago, but now my SIM card readers (both of them) have gone out. I have no idea how, no water damage or anything like that has happened. They just stopped working. So I went complete stock firmware, locked bootloader, and all of that but that I have relocked it.
Click to expand...
Click to collapse
How to you relock bootloader?
mr_gourav2000 said:
How to you relock bootloader?
Click to expand...
Click to collapse
Since I am a new user I cannot post links. But Google "Zenfone 2 bootloader unlock" and I followed the instructions of Grekky's Blog.
there is no such thing as relocking the bootloader. only thing you can do it flash the stock image to make it look stock (since an unlocked bootloader has a white splash screen) but im sure asus knows of this and will still check and see that the bootloader is indeed unlocked and not warranty it.
This is just something we all accepted as a consequence of unlocking our bootloaders. hell i have a screen thats getting worse and worse with a yellow/brownish line coming from the top of the phone, but alas i have an unlocked phone too.
You can replace the white splash screen by flashing a black splash screen image to try and cover up unlocking your bootloader. http://forum.xda-developers.com/zenfone2/themes-apps/551-black-white-splashscreen-twrp-flash-t3141945 . If the reseller has no clue about custom recoveries and trying to flash a rom you'll be safe.
They fixed it, no questions asked. And yes, I was able to relock the bootloader.
I bought a Moto Z Play off of Swappa and it's arriving on Tuesday. I wanted to double check that the bootloader's locked to make sure that it wasn't loaded with any kind of keylogging software. The seller had photos of it still in the original packaging, but I'm paranoid, so I just wanted to make sure. If I do the volume down + power button method to go into fastboot, how will I know if the bootloader's unlocked? I've seen a few photos of the fastboot screen, and none of them seemed like they had that info.
If the bootloader ist unlocked you should see a warning screen for 5 seconds immediatly after starting the phone.
Edit: i found this in the OnePlus Forum:
"You can also type this command : fastboot oem device-info
if you see the word : true instead o false near the result, that means you're phone is or have been unlocked"
the easyest way is to see if you getting 5 second warning on boot
Anyone else know where the info would be on the fastboot screen?
Xecu said:
If the bootloader ist unlocked you should see a warning screen for 5 seconds immediatly after starting the phone.
Edit: i found this in the OnePlus Forum:
"You can also type this command : fastboot oem device-info
if you see the word : true instead o false near the result, that means you're phone is or have been unlocked"
Click to expand...
Click to collapse
Where do I use that command? On the fastboot screen? I know there's a dial code I can use to check the bootloader, but I was hoping to see it before I logged into the phone.
defilip69 said:
the easyest way is to see if you getting 5 second warning on boot
Click to expand...
Click to collapse
Any idea what that warning looks like? Is it just the little unlocked lock icon?
You cant miss it. It shows up as the first screen your device displays immediatly after starting it. It will say something like "The bootloader has been unlocked. This device can not be trusted" for 5 seconds and then proceed the normal startup procedure. If you miss it then your bootloader is locked.
Xecu said:
You cant miss it. It shows up as the first screen your device displays immediatly after starting it. It will say something like "The bootloader has been unlocked. This device can not be trusted" for 5 seconds and then proceed the normal startup procedure. If you miss it then your bootloader is locked.
Click to expand...
Click to collapse
So, if the bootloader's locked, then phone should be safe for use, right? Or is there anything else the seller might've done to tamper with it?
Even if the bootloader is unlocked it could be safe.
Jimi Mack said:
Even if the bootloader is unlocked it could be safe.
Click to expand...
Click to collapse
But if the bootloader is locked, does that mean it's definitely safe? Anything else I could do to protect myself?
Bantersaurus said:
Anyone else know where the info would be on the fastboot screen?
Where do I use that command? On the fastboot screen? I know there's a dial code I can use to check the bootloader, but I was hoping to see it before I logged into the phone.
Any idea what that warning looks like? Is it just the little unlocked lock icon?
Click to expand...
Click to collapse
before boot animation u have boot logo which have moto logo. if you have message like ... warning ... bla bla bla ... your phone is unlocked ... bla bla bla ... ( yellow triangle thing ) bla bla bla then is unlocked
Bantersaurus said:
But if the bootloader is locked, does that mean it's definitely safe? Anything else I could do to protect myself?
Click to expand...
Click to collapse
Basically what separates a locked bootloader and an unlocked bootloader is the ability to alter the partitions of the phone. A phone with an unlocked bootloader could probably be reflashed in a way to skip the Google sign in lock after a "reset" and be sold off if it were stolen. If you have a locked bootloader and a password on the device, all that could be done is a wipe through stock recovery and be prompt by Google to sign in with the previous account. In terms of OS security patches, your basically helpless until the device manufacturer feels like maintaining the device. Apparently Android O is supposed to fix that with project treble where Google adds an extra API layer on the kernel level.
DroneDoom said:
Basically what separates a locked bootloader and an unlocked bootloader is the ability to alter the partitions of the phone. A phone with an unlocked bootloader could probably be reflashed in a way to skip the Google sign in lock after a "reset" and be sold off if it were stolen. If you have a locked bootloader and a password on the device, all that could be done is a wipe through stock recovery and be prompt by Google to sign in with the previous account. In terms of OS security patches, your basically helpless until the device manufacturer feels like maintaining the device. Apparently Android O is supposed to fix that with project treble where Google adds an extra API layer on the kernel level.
Click to expand...
Click to collapse
Did you miss my opening post? I said I'm buying a new phone from an independent seller. I wanted to know if there's any way to check if they installed malware of any kind that might keylog me.
Bantersaurus said:
Did you miss my opening post? I said I'm buying a new phone from an independent seller. I wanted to know if there's any way to check if they installed malware of any kind that might keylog me.
Click to expand...
Click to collapse
I'd check the indication of an unlocked bootloader as others previously mentioned, look at what's prompted upon booting up the phone. If it was unlocked, the message is as clear as day that tells you it's unlocked. If they tried to cover that up you'd still see part of the message like "N/A" or "bad key" within the logo. That indication right there alone is suspicious. Should you contact the seller or reflash the stock firmware yourself, you should be wary about what's already installed on the device.
If you don't see any indication of an unlocked bootloader, then I'd still wipe it through stock recovery and run an app that checks signature verifications and heuristics of malicious apps (Malwarebytes or some other antivirus app).
I forgot to mention the logos that are SUPPOSED to show on the device depending on what Android version it's on.
For marshmallow, you should see the white logo I've posted in attachments along with the indication I marked where you'll see text from the bootloader telling you that's unlocked if the seller tried to cover it up.
For nougat, the one with the aqua colored background and the indication I marked where the cover up text should be.
If there's nothing and the logo is "natural" looking and you don't see a message before the logo then your bootloader is probably locked.
Edit: sorry the indication for the nougat is slightly lower than where it needs to be. Should be on the same level as the marshmallow one.
DroneDoom said:
Should you contact the seller or reflash the stock firmware yourself, you should be wary about what's already installed on the device..
Click to expand...
Click to collapse
I don't think there'll be anything installed (besides the possibility of malware). It's supposed to be a brand new, unopened phone that's still in the original packaging. It'd be too suspicious if there are apps already installed (besides bloatware that's on most phones).
a) There is no logical reason to bootloader lock a phone. You will gain nothing.
b) If you lock it there is a high probability you won't ever be able to bootloader unlock it again - no more mods - ever.
EDIT: Perhaps if you flash the "correct stock" meaning one like/identical to the one that you originally had on your phone when you unlocked it the first time, it will work...
Think about this, please, before you flash things!!!
Do you refer to lock and unlock the bootloader? I locked and unlocked it much times and I've never had problems (obviously considering the bootloader version).
gercdgcat said:
Do you refer to lock and unlock the bootloader? I locked and unlocked it much times and I've never had problems (obviously considering the bootloader version).
Click to expand...
Click to collapse
Thanks for replying - could you perhaps write a guide as to exactly how you unlock your bl after using fastboot lock?
I have seen a few folks who appear stuck at that point and I and they would be happy campers if they could get around that!!!
Thanks!
EDIT: I added a comment about "correct stock" to the first post... This may be key to the folks that are having trouble...
You might look at thread
https://forum.xda-developers.com/moto-z-play/help/please-help-urgently-t3814260
But I guess I would have to call anyone who successfully locks and unlocks again their bootloader as darn lucky. Some, (many?) can't.
In the end I still have to ask "why the heck are you locking your phone" - what could you possibly gain? It's totally unnecessary. it can be a very expensive little line of code.
I lock my phone all the time, multiple times per day even! It's really easy to unlock: I simply put my finger on the sensor and voila!
Maybe you mean the bootloader? That would be a helpful little detail to add to the title of your post.
pkadavid said:
I lock my phone all the time, multiple times per day even! It's really easy to unlock: I simply put my finger on the sensor and voila!
Maybe you mean the bootloader? That would be a helpful little detail to add to the title of your post.
Click to expand...
Click to collapse
LOL - right! Thanks!!!
bump
I've locked mine as I upgraded to a Pixel 2 XL and gave my Z Play to my father, so I don't really care if I can't unlock it again, but I'm sure that wouldn't be an issue anyway.
IncendiaryPyro said:
I've locked mine as I upgraded to a Pixel 2 XL and gave my Z Play to my father, so I don't really care if I can't unlock it again, but I'm sure that wouldn't be an issue anyway.
Click to expand...
Click to collapse
How's the 2xl?
hithere
KrisM22 said:
a) There is no logical reason to bootloader lock a phone. You will gain nothing.
b) If you lock it there is a high probability you won't ever be able to bootloader unlock it again - no more mods - ever.
EDIT: Perhaps if you flash the "correct stock" meaning one like/identical to the one that you originally had on your phone when you unlocked it the first time, it will work...
Think about this, please, before you flash things!!!
Click to expand...
Click to collapse
I prefer stock without modifications but sometimes when i have time to try news modifications or roms i used to unlocked the phone and after this relock again, the process that i use is very simple, i just unlock with the same code that Motorola gaves to unlock bootloader, i don't have sure but if you request unlock codes to many times can be a problem but i use the same code and works good.
Basically: relock as are specifcified in another topic in this device forum( using the last stock version that you used)
And after this unlock with code again
Obs.: Is not recommended to unlock/relock to many times.
Obs2.: I only did this three times and i don't know if has a limit
bumpsi
It is my opinion also that relocking is a bad idea. But if someone likes to do it, eg to get Google Pay working without Magisk, why do you want to warn him?
Relock only is possible in combination with flashing a complete correctly firmware. If something is wrong with the firmware you flash, relocking won't succeed. Your device won't be locked if it does not fully succeed or the firmware is not correctly signed. The unlock code is supposed to stay valid, you should be able to unlock your device as many times as you want using the same code.
a) is fine, but does not consider Android SafetyNet
b) is just wrong, and this already was written in a comment.
Please do not bump wrong warnings.
I've had my eye on this phone for a bit now, and if all is good, I'm going to get one next weekend.
Some disturbing news though, it appears that unlocking the bootloader will completely kill the cameras. And the only way to get them functional again, is to lock the bootloader again.
SO, I guess this means that recovery, root, or anything else that requires modifiying the system in any way, will kill the use of the cameras?
Is it possible to unlock, root and do whatever, then relock the bootloader and get cameras back while still having root?
The 90% people on this community first what learn ro do is to unlock bootloader. You think that they all dont need camera or..
How is that even possible?
Once when you unblock bootloader you can do what you want, flash custom rom, custom recovery, custom Kernel. Magisk. Magisk modules..
But when you lock it ,and something got wrong ,you get hard brick phone. Bootloader must ne unlock until you use root and etc..
Camera have nothing to do with unlocking and working perfectly. I dont know who say to you ...or make a joke
Btw what phone you want to unlock?
Sometimes it is better to keep quite, specially when you are not aware about current affairs.
@ OP yes, still same.
dr.ketan said:
Sometimes it is better to keep quite, specially when you are not aware about current affairs.
@ OP yes, still same.
Click to expand...
Click to collapse
Well, dang. That kind of kills the idea of fully functional phone with root. I mostly use root for ad blocking anymore. I don't really do the custom ROM thing all that much. Custom Android development these days isn't what it used to be.
I'm looking at either the carrier unlocked version, or the Verizon version (as I have Verizon as my carrier)
I believe rooting for ad blocking means you are paying more (now a days). In my opinion, Private DNS could be a good choice for ad block on unrooted.
I use AdAway. Works perfectly. But for best use, requires root. But yeah, other than that, I don't really use root. Would be nice to have a functional TWRP, but that may or may not happen. But that camera kill is a problem. I guess if I can get DNS to work, I won't have to worry about the bootloader at all. There would be no point.
I use AdGuard on my non-rooted phone and I don't see ads. None.
I see no reason why you need to root to just block ads. There are some great ad blocking apps out there. I love AdGuard because it works not only on my phone, but my PC as well.
There is a reason you cannot get this on the PlayStore. Google kicked it off because it works so well.
NextDNS
tze_vitamin said:
The 90% people on this community first what learn ro do is to unlock bootloader. You think that they all dont need camera or..
How is that even possible?
Once when you unblock bootloader you can do what you want, flash custom rom, custom recovery, custom Kernel. Magisk. Magisk modules..
But when you lock it ,and something got wrong ,you get hard brick phone. Bootloader must ne unlock until you use root and etc..
Camera have nothing to do with unlocking and working perfectly. I dont know who say to you ...or make a joke
Click to expand...
Click to collapse
Actually that is where you are wrong. Another user on this forum unlocked their bootloader on fold3 and then their cameras where disabled. There is even a warning message on unlocking bootloader screen that states clearly that cameras will be disabled after unlocking the bootloader. Even Sony smartphones had this but then Sony removed it so cameras won't be disabled after bootloader unlock.
You can read more about it here: https://forum.xda-developers.com/t/unlocking-bootloader-will-disable-the-camera.4321957/
So if bootloader locked/unlocked doesn't much matter (at least at this point), since I have Verizon, is there any reason to spring for the Unlocked version over the Verizon version? Does the Verizon version have any more apps preinstalled on it that the Unlocked version doesn't? Does either perform any differently?
Unlocked carrier is not the same as unlocked bootloader.
chevycam94 said:
So if bootloader locked/unlocked doesn't much matter (at least at this point), since I have Verizon, is there any reason to spring for the Unlocked version over the Verizon version? Does the Verizon version have any more apps preinstalled on it that the Unlocked version doesn't? Does either perform any differently?
Click to expand...
Click to collapse
ronaldheld said:
Unlocked carrier is not the same as unlocked bootloader.
Click to expand...
Click to collapse
What he said.
Carrier Unlock is the same as SIM Unlock which lets you use other carrier SIM Cards, has NOTHING to do with the Bootloader.
The Bootloader just unlocks the ability to flash custom Recoveries and ROM's. This does NOT SIM Unlock your phone.
Guys, I'm well aware of the difference between the two. I've been at this for 14+ years. I'm just wondering if there is a performance difference, or bloatware content difference between the Carrier Unlocked version and the Verizon Locked version.
chevycam94 said:
Guys, I'm well aware of the difference between the two. I've been at this for 14+ years. I'm just wondering if there is a performance difference, or bloatware content difference between the Carrier Unlocked version and the Verizon Locked version.
Click to expand...
Click to collapse
Today, the hardware in the US variant "Unlocked" and "Verizon" versions are exactly the same. The difference is only in the software set. And you have choices there. With Odin 3B you can cross-flash between the models to get the software set you want. Hell, you can even put the TMO software on the VZW "locked" device (I use quotes there because it is only locked for 90 days, at which point it becomes fully SIM unlocked automatically). You can load the U1-XAA, the U1-VZW, the U-VZW, whatever you can get your hands on. I am currently using a Verizon device with U1-XAA software, happily on One UI 4.0 beta. The Note 10 was the last device to have different hardware profiles between carriers that prevented full cross-flash support, and that was just because of the differing 5G networks as 5G was still in its infancy.
Notice how my phone setting in the photo show my phone as being a U1 (because it reads the phones software), and my phone info page within Samsung Members shows it to be a VZW device (because it uses the serial number to look up info from its database).
If you have any specific questions about it, feel free to message me. I have been doing this stuff since the WinMo days before Android existed. I don't post a lot because very few people read AND understand.
Oh, and for clarification to all the trolls out there, my device is still bootloader locked, Knox is fully intact, and my device is still covered under warranty (This was tested with my Note20 when i had to have the NFC chip replaced, and it too was a U-VZW running U1-XAA software.).
tze_vitamin said:
The 90% people on this community first what learn ro do is to unlock bootloader. You think that they all dont need camera or..
How is that even possible?
Once when you unblock bootloader you can do what you want, flash custom rom, custom recovery, custom Kernel. Magisk. Magisk modules..
But when you lock it ,and something got wrong ,you get hard brick phone. Bootloader must ne unlock until you use root and etc..
Camera have nothing to do with unlocking and working perfectly. I dont know who say to you ...or make a joke
Click to expand...
Click to collapse
Hoping for some progress on camera issue and all we get is this dips### lol
I didnt know that unlocking bootloader can kill camera. I unlocking phones , Samsung mostly. After then Xiaomi comes with lower prices and I now unlocking Xiaomi.
Can understand why vendors doing it..
But ... Some Hacker will always find some way
I have a U1 phone on Verizon. Everything works. 5g, wifi calling etc. Not sure if Verizon video calling works but who uses that? Duo is in the dialer I think. I've used opera browser for years which has ad blocking as well. YT vanced also and fblc
tze_vitamin said:
I didnt know that unlocking bootloader can kill camera. I unlocking phones , Samsung mostly. After then Xiaomi comes with lower prices and I now unlocking Xiaomi.
Can understand why vendors doing it..
But ... Some Hacker will always find some way
Click to expand...
Click to collapse
It's with this batch of Sammy phones. Doesn't always kill the camera.
BUT they have tried and haven't found a work around. Maybe 12 will let us, but for now we cannot unlock withou the camera "breaking".
Please see my thread - i believe with a12 this is thankfully now moot!!!!