Okay, I guess it's been a while since I played with flashing ROMs etc, but I didn't know this was possible. I just flashed Colt OS on my Pixel 2 XL, everything was going fine. I've been having issues with a few apps not allowing me to proceed because the bootloader is unlocked/phone is rooted. So I figured I would lock the bootloader to see if I could get around it. Rebooted to fastboot, did "fastboot flashing lock" and followed the onscreen prompt.
Phone rebooted: Cannot find a valid OS. Device will not start.
Ah crap. Booted back into fastboot, assuming I'd just unlock it and if needed wipe the phone. However, when I type "fastboot flashing unlock" I get the heart-stopping message:
Code:
FAILED (remote: Flashing Unlock is not allowed
)
Finished. Total time: 0.006s
Trying to boot into twrp using "fastboot boot twrp.img" results in
Code:
Downloading 'boot.img'
OKAY [ 1.659s]
booting
FAILED (remote: Can not boot in Lock State)
Finished. Total time: 1.751s
I've unlocked it before with no issues. Why is it suddenly doing this? I can't get into recovery, I can't boot the device, it's effectively bricked until I can figure out how to solve this. Other fastboot commands work fine, as far as I can tell. I have this huge lump in my stomach right now because I *thought* I was experienced enough to not brick my phone. I don't know how I could have forseen this, though.
Any and all help is appreciated. The "fastboot getvar all" returns this, which I've put in a pastebin: https://pastebin.com/NzwfE67T
I'm on the verge of really panicking here. There must be a way to unlock it, I can't imagine why this would even happen. I am literally sick to my stomach right now, reading that other people had to RMA. I bought this phone used about a year ago, no way it's under warranty and I doubt Google will replace it. I cannot go without a phone, I'm seriously freaking the **** out.
Sorry to say but you've screwed yourself.
You only ever lock the bootloader if you're completely stock.
This happens too often because people don't do a quick search to find out if locking the bootloader after unlocking is a good idea.
Sigh...
Sent from my Pixel 2 XL using XDA Labs
ilal2ielli said:
Sorry to say but you've screwed yourself.
You only ever lock the bootloader if you're completely stock.
This happens too often because people don't do a quick search to find out if locking the bootloader after unlocking is a good idea.
Click to expand...
Click to collapse
Yeah well, I've unlocked and relocked bootloaders a million times before on other phones. I just forgot and now I have a ****ing $800 paperweight.
AirCombat said:
Yeah well, I've unlocked and relocked bootloaders a million times before on other phones. I just forgot and now I have a ****ing $800 paperweight.
Click to expand...
Click to collapse
Sorry to hear about your issue.
The only way to safely lock the bootloader on the 2 XL is to be completely stock (as far as I'm aware)... Not sure if you've looked into Deuce's Tool Kit (search it) to see if there is a "brick" option...
Like others have said, I'm afraid you might have an irreversible situation there.
Any chance this device was purchased via Google and still under warranty? If so, might be able to RMA it through them. I thought I bricked my 2 XL while it was under warranty and called Google, told them it was unlocked with a cust Rom, but wouldn't boot and they issued me an RMA for refurb, but I figured it out and ended up keeping the new device over getting a refurb.
Best of luck with this!
AirCombat said:
Yeah well, I've unlocked and relocked bootloaders a million times before on other phones. I just forgot and now I have a ****ing $800 paperweight.
Click to expand...
Click to collapse
Can you get Google to RMA it?
Az Biker said:
Sorry to hear about your issue.
The only way to safely lock the bootloader on the 2 XL is to be completely stock (as far as I'm aware)... Not sure if you've looked into Deuce's Tool Kit (search it) to see if there is a "brick" option...
Like others have said, I'm afraid you might have an irreversible situation there.
Any chance this device was purchased via Google and still under warranty? If so, might be able to RMA it through them. I thought I bricked my 2 XL while it was under warranty and called Google, told them it was unlocked with a cust Rom, but wouldn't boot and they issued me an RMA for refurb, but I figured it out and ended up keeping the new device over getting a refurb.
Best of luck with this!
Click to expand...
Click to collapse
I didn't know Google even had a phone number to call... I thought they were famous for being unreachable and having no customer support. Can you share the number or where you got it? I'm in Canada, not sure if that matters.
I have no idea if it was bought from Google, but I suspect it was because it was factory unlocked. If it did have a warranty I'm sure it's expired, but maybe I can sweet talk someone.
My backup option is to buy a smashed/broken Pixel 2 XL and swap the mainboard out. Cheaper than buying a new one, and I do have an electronics lab at home, so I'm quite confident I can do the swap (have done many many screen replacements, board swaps before). Someone offered to buy it for parts, but I have a feeling that's not the best route to go unless I can't fix/replace it.
Thanks for the info. It does seem bricked. I'm pretty pissed that it's even possible to get in this state. The bootloader should check before locking if there is a valid OS! You'd think it'd be pretty simple to add that check in.
AirCombat said:
I didn't know Google even had a phone number to call... I thought they were famous for being unreachable and having no customer support. Can you share the number or where you got it? I'm in Canada, not sure if that matters.
I have no idea if it was bought from Google, but I suspect it was because it was factory unlocked. If it did have a warranty I'm sure it's expired, but maybe I can sweet talk someone.
My backup option is to buy a smashed/broken Pixel 2 XL and swap the mainboard out. Cheaper than buying a new one, and I do have an electronics lab at home, so I'm quite confident I can do the swap (have done many many screen replacements, board swaps before). Someone offered to buy it for parts, but I have a feeling that's not the best route to go unless I can't fix/replace it.
Thanks for the info. It does seem bricked. I'm pretty pissed that it's even possible to get in this state. The bootloader should check before locking if there is a valid OS! You'd think it'd be pretty simple to add that check in.
Click to expand...
Click to collapse
If your phone was bought from Google it will still be under warranty. I'm not sure if that warranty transfers when it is bought from a third party though. There website does state that the warranty applies to the US and Canada. Here is the link. https://support.google.com/store/answer/6160400?hl=en&ref_topic=3244667
Related
Hello,
Recently my Nexus 7 (2013) battery ran out because I forgot to charge it. Since then, it won't boot back into Android when it's turned on - all I get is the black screen with "Google" written on it. I have searched all over the internet for the past few days, but I'm unable to find a solution. I'm hoping that someone here can help me, because the tablet's warranty has expired and I'm completely out of ideas. Here are the things I've tried or noticed:
I can't boot into Android. The tablet gets stuck on the black screen with "Google" written on it.
I can access the bootloader and interact with the tablet via fastboot.
The bootloader is locked. Trying to unlock it via fastboot oem unlock displays the "Unlock bootloader?" screen on the tablet. After I select "Yes", the command line output on the computer shows the following output, but doesn't get any further:
Code:
...
(bootloader) Unlocking bootloader...
(bootloader) erasing userdata...
Trying to boot into recovery mode from the bootloader results in the tablet being stuck on that black screen with "Google" written on it.
I have removed the back cover from the tablet and reconnected every exposed connector. I couldn't take the battery out because I don't have the appropriate screwdriver. Doing this changed nothing.
Any help would be sincerely appreciated. At this point I'm worried that it is a hardware issue, but I'd like to exhaust all options before declaring it as such, as it would essentially mean the tablet is going in the garbage bin.
How long did you let it sit at "erasing userdata"?
I don't recall specifically on my N7 but I know when I unlocked the bootloader on my 2013 Moto X it seemed like an eternity, which was mostly because there is no progress indicator, it just said "erasing userdata" and sat there for a while. Probably like 5-10 minutes.
fury683 said:
How long did you let it sit at "erasing userdata"?
Click to expand...
Click to collapse
It'll be around 2 hours now.
Wengard said:
It'll be around 2 hours now.
Click to expand...
Click to collapse
Well that is surely too long. Not sure what else to suggest. Someone else with more experience might able to help.. It sounds like your partitions may have been messed up somehow, which I have seen others post about recently with the updates. I'm not sure what causes this or if there are any fixes, but I know there are threads about people being stuck on the Google screen and having issues after the update to 5.0/.1/.2.
fury683 said:
Well that is surely too long. Not sure what else to suggest. Someone else with more experience might able to help.. It sounds like your partitions may have been messed up somehow, which I have seen others post about recently with the updates. I'm not sure what causes this or if there are any fixes, but I know there are threads about people being stuck on the Google screen and having issues after the update to 5.0/.1/.2.
Click to expand...
Click to collapse
Hi,
i had exactly the same problem. I tried everything to fix it and no luck. I had to resort in sending it to Asus for repair. Unfortunately my warranty has expired. I just got a quote from them saying the motherboard has gone and it will cost me £250 to repair!!!!! I almost fell off my chair. A brand new 32gb tablet will cost be around £180. This is surely a joke? I will be giving them a call tomorrow to complain!
I hope yours is still under warranty because it is most likely your motherboard that has gone. I've read a few others having the same issue and its been the motherboard.
Mo
mo123456789 said:
Hi,
i had exactly the same problem. I tried everything to fix it and no luck. I had to resort in sending it to Asus for repair. Unfortunately my warranty has expired. I just got a quote from them saying the motherboard has gone and it will cost me £250 to repair!!!!! I almost fell off my chair. A brand new 32gb tablet will cost be around £180. This is surely a joke? I will be giving them a call tomorrow to complain!
I hope yours is still under warranty because it is most likely your motherboard that has gone. I've read a few others having the same issue and its been the motherboard.
Mo
Click to expand...
Click to collapse
Thank you for your response.
I'm sorry to hear about what happened to you. I've been reading around and guessed it's probably a hardware problem based on other people's similar experiences. Unfortunately my tablet is out of warranty as well, and I'm definitely not going to spend more on the repairs than I would on a brand new tablet. I regret purchasing the tablet in the first place, I really expected it to last longer than a year.
If you can, please let me know what ASUS says about this, if you intend to call them. They don't have a subsidiary in my country, but if you get lucky, I might press my chances as well and perhaps I can get this repaired for a reasonable price.
Mine has lasted 5 years more but my Nexus 7 has ended its days the same way as yours. Stuck at google when switched on, and stuck at bootloader when triying to flash it.
Time to go, it seems.
I finally was forced to update to android 5.0.1. I updated at work but it failed halfway through and is now in a boot loop. I've tried every solution the internet can provide me. What do I do now? The device IMEI has a limited warranty until 2017. I purchased through swappa. I have original box but no documentation besides the barcode sticker on the side. Will AT&T replace this? It was their update that caused this anyway. Any experiences with this sort of thing please? I dropped a large chunk of change on this paperweight. Thanks
Wildstar34 said:
I finally was forced to update to android 5.0.1. I updated at work but it failed halfway through and is now in a boot loop. I've tried every solution the internet can provide me. What do I do now? The device IMEI has a limited warranty until 2017. I purchased through swappa. I have original box but no documentation besides the barcode sticker on the side. Will AT&T replace this? It was their update that caused this anyway. Any experiences with this sort of thing please? I dropped a large chunk of change on this paperweight. Thanks
Click to expand...
Click to collapse
The first thing to do is find a local Best Buy with a Samsung Experience shop. They can reflash the firmware or send the phone in for repairs. This would be the best and easiest option. Most likely, you'll be able to get everything fixed in around an hour max.
BTW, it doesn't matter if the device was purchased from somewhere other than Best Buy!
I'm not sure if ATT will replace the phone if you didn't buy it from ATT. You can contact them to see though. Call them and tell them that you bought the device from Swappa. Though, most likely, they'll turn you away unless they have some sort of business alliance with Swappa.
Do this as a Plan B.
The third option is to get in contact with Swappa. I don't know anything about that service though. Usually in order to claim warranty, you need the device and proof of purchase. If Swappa has an online receipt, or even just an online purchase history, that should work. They most likely would just need some sort of proof that you actually bought the device from or through them. Like I said, I don't know anything about Swappa, so you'll have to contact them to get specifics of what you'd need.
When all else fails, go directly to Samsung. Again, tell them that you got the device from Swappa. Though, this would basically be like the first option, except that it would take longer.
All options except the first one may result in you getting a refurbished replacement. Just an FYI. The only way that Best Buy will give you a refurbished replacement is if they were to send the phone back to Samsung and it was replaced.
PM me if needed!
Sent from my SM-P600 using Tapatalk
spexwood said:
The first thing to do is find a local Best Buy with a Samsung Experience shop. They can reflash the firmware or send the phone in for repairs. This would be the best and easiest option. Most likely, you'll be able to get everything fixed in around an hour max.
BTW, it doesn't matter if the device was purchased from somewhere other than Best Buy!
I'm not sure if ATT will replace the phone if you didn't buy it from ATT. You can contact them to see though. Call them and tell them that you bought the device from Swappa. Though, most likely, they'll turn you away unless they have some sort of business alliance with Swappa.
Do this as a Plan B.
The third option is to get in contact with Swappa. I don't know anything about that service though. Usually in order to claim warranty, you need the device and proof of purchase. If Swappa has an online receipt, or even just an online purchase history, that should work. They most likely would just need some sort of proof that you actually bought the device from or through them. Like I said, I don't know anything about Swappa, so you'll have to contact them to get specifics of what you'd need.
When all else fails, go directly to Samsung. Again, tell them that you got the device from Swappa. Though, this would basically be like the first option, except that it would take longer.
All options except the first one may result in you getting a refurbished replacement. Just an FYI. The only way that Best Buy will give you a refurbished replacement is if they were to send the phone back to Samsung and it was replaced.
PM me if needed!
Sent from my SM-P600 using Tapatalk
Click to expand...
Click to collapse
Hey, thanks a lot. This may be the single most helpful forum post I've ever read. I will drive up to BestBuy tomorrow and give it a shot. I wasn't able to flash a AT&T stock rom through Odin, but I guess it's worth a shot. I believe the flash failure was due to the AT&T bootloader being locked?
Wildstar34 said:
Hey, thanks a lot. This may be the single most helpful forum post I've ever read. I will drive up to BestBuy tomorrow and give it a shot. I wasn't able to flash a AT&T stock rom through Odin, but I guess it's worth a shot. I believe the flash failure was due to the AT&T bootloader being locked?
Click to expand...
Click to collapse
Welcome!
Most likely something just went wrong during the installation. The bootloader is not a factor in this matter since all ATT Note 4s have it locked and the firmware is meant for this phone.
Now, if you had the phone rooted (permanently), installed a custom kernel and recovery, etc, then the update failure would be 100% explainable. But since you can't do any of that with this phone, then the most likely cause is just "sh1t happened" or the installation was interrupted (like battery died).
Sent from my SAMSUNG-SM-N910A using Tapatalk
Have you tried kies to reflash your phone?
floatingtrees said:
Have you tried kies to reflash your phone?
Click to expand...
Click to collapse
I used Kies, Kies3 and Swap Sync or whatever to do an emergency restore. All of them failed. Kies 3 recognized the phone and was 98% done downloading the firmware and then failed.
Also i am not rooted and never attempted a root (on this phone anyway).
Good news. Just got off the phone with AT&T and they have a replacement on the way. Thanks for your help everybody. We have achieved the best case senario for me as i was having problems with the volume buttons anyway
I would consider this case solved.
Wildstar34 said:
Good news. Just got off the phone with AT&T and they have a replacement on the way. Thanks for your help everybody. We have achieved the best case senario for me as i was having problems with the volume buttons anyway
I would consider this case solved.
Click to expand...
Click to collapse
Awesome! Win-win for you (I guess?)
If the volume keys were messed up, then I wonder if there was some other problems with the phone too. Ones you couldn't see... ones that prevented proper firmware installation.
Sent from my SM-P600 using Tapatalk
So the issue can be referred to :http://forum.xda-developers.com/pixel-c/help/corrupted-hard-drive-dead-pixel-c-t3290331
https://productforums.google.com/forum/#!topic/nexus/xoaMSAa8yC8
I bought the Pixel C few days ago. I'm in China , I haven't got it yet. It's till in transit. I have read some people have this issue. It really worries me because I don't get to RAM it since I'm in China. If anything like this happens then I will have a bricked device.
My question is if I unlock the bootloader as soon as I get it. If this issue occurs, am I able to sideload the factory image to unbrick it?
Also , I would like to know if the latest batch(the ones you can get with the developer discount) have the wifi issue or are they of the same batch as the previous ones?
randy6644 said:
So the issue can be referred to :http://forum.xda-developers.com/pixel-c/help/corrupted-hard-drive-dead-pixel-c-t3290331
https://productforums.google.com/forum/#!topic/nexus/xoaMSAa8yC8
I bought the Pixel C few days ago. I'm in China , I haven't got it yet. It's till in transit. I have read some people have this issue. It really worries me because I don't get to RAM it since I'm in China. If anything like this happens then I will have a bricked device.
My question is if I unlock the bootloader as soon as I get it. If this issue occurs, am I able to sideload the factory image to unbrick it?
Also , I would like to know if the latest batch(the ones you can get with the developer discount) have the wifi issue or are they of the same batch as the previous ones?
Click to expand...
Click to collapse
For every Nexus device I purchase, it's standard practice to unlock it before completely setting everything up. So right after opening it, I'll do a quick setup and use a couple apps to check for things like dead pixels or lightbleed. Then, if everything checks out, I'll unlock the bootloader and flash the latest factory image to make sure I'm getting a fresh start from scratch. I've never seen a reason NOT to unlock the bootloader first. It helps get you out of trouble if something were to go awry on the software side. I've never encountered an issue that flashing a factory image couldn't fix.
While I can't attest to anything regarding the original batches, I can tell you the device I received with the dev discount has been perfect. No issues so far after using it for 2 weeks. I believe it was manufactured in January 2016 if the serial number naming scheme is the same as other Nexus devices.
If you have a dead HDD, nothing can fix it other than replacing it. I'm not sure if that's a software or hardware error, if it's software, reformatting the drive may help, if it's hardware, you're obviously screwed.
charesa39 said:
For every Nexus device I purchase, it's standard practice to unlock it before completely setting everything up. So right after opening it, I'll do a quick setup and use a couple apps to check for things like dead pixels or lightbleed. Then, if everything checks out, I'll unlock the bootloader and flash the latest factory image to make sure I'm getting a fresh start from scratch. I've never seen a reason NOT to unlock the bootloader first. It helps get you out of trouble if something were to go awry on the software side. I've never encountered an issue that flashing a factory image couldn't fix.
While I can't attest to anything regarding the original batches, I can tell you the device I received with the dev discount has been perfect. No issues so far after using it for 2 weeks. I believe it was manufactured in January 2016 if the serial number naming scheme is the same as other Nexus devices.
Click to expand...
Click to collapse
I've bought lots of nexii devices ,say, Gnex, nexus 7 , nexus 6 and 6P. I used to do a lot of flashing just like you do, the first thing I did was unlocked the BL and flashed a new ROM, kernel and maybe did some tweaking. But I haven't messed with my 6P cause I don't wanna unlock the BL for security reason. With an unlocked bootloader, just think about it, if you lose your phone, anyone can do whatever they want. with it That's not cool at all. So I'd rather keep it the way it is.
Glad to know that you don't have any issue with your device. I hope it's the same in my case. Thanks for the information.
brando56894 said:
If you have a dead HDD, nothing can fix it other than replacing it. I'm not sure if that's a software or hardware error, if it's software, reformatting the drive may help, if it's hardware, you're obviously screwed.
Click to expand...
Click to collapse
I think the problem mentioned should be a software issue. As in those two threads , they are not able to boot up the device simply by factory resetting it. And they failed to flash the factory image to the bricked device since it's locked.
randy6644 said:
I've bought lots of nexii devices ,say, Gnex, nexus 7 , nexus 6 and 6P. I used to do a lot of flashing just like you do, the first thing I did was unlocked the BL and flashed a new ROM, kernel and maybe did some tweaking. But I haven't messed with my 6P cause I don't wanna unlock the BL for security reason. With an unlocked bootloader, just think about it, if you lose your phone, anyone can do whatever they want. with it That's not cool at all. So I'd rather keep it the way it is.
Glad to know that you don't have any issue with your device. I hope it's the same in my case. Thanks for the information.
Click to expand...
Click to collapse
While this is definitely true, your average cellphone thief is about as tech savvy as a wet piece of leather hahaha I've had this concern myself but then realized that maybe 2% of Android owners know how to get to the recovery, hell most reps at cell phone stores don't even know how to do it, even the ones that are "techs"!. When I had my S4 rooted and stupidly let it slip that the phone was rooted, next time I came in the rep looked over the phone and called out a tech who looked at the phone for 30 seconds then said "do you know how to get to the recovery on this???". A simple pin/password/pattern lock will thwart about 90% of phone thieves out there from getting access to your data, they're most likely just going to wipe it anyway. They couldn't care less about your data, they can't sell or use that as easily as they can the device itself.
Sent from my Pixel C using Tapatalk
brando56894 said:
While this is definitely true, your average cellphone thief is about as tech savvy as a wet piece of leather hahaha I've had this concern myself but then realized that maybe 2% of Android owners know how to get to the recovery, hell most reps at cell phone stores don't even know how to do it, even the ones that are "techs"!. When I had my S4 rooted and stupidly let it slip that the phone was rooted, next time I came in the rep looked over the phone and called out a tech who looked at the phone for 30 seconds then said "do you know how to get to the recovery on this???". A simple pin/password/pattern lock will thwart about 90% of phone thieves out there from getting access to your data, they're most likely just going to wipe it anyway. They couldn't care less about your data, they can't sell or use that as easily as they can the device itself.
Sent from my Pixel C using Tapatalk
Click to expand...
Click to collapse
Well, usually thieves might just wipe everything. But still, there are risks. There are certain ways to go around the locked screen if you got a unlcoked BL and rooted phone. I've got all my photos( No nude pics ) stored on Google, and also all my contacts, whom wouldn't be happy to share their information with a thief, and some notes, payment apps as well as some important emails. There's too much going on and I don't wanna take risks. Also, if my phone got stolen, I'll have make sure the SOB got a brick ,nothing more. Sure they can tear it apart and sell some parts of it, but they don't get a phone.
I still flash roms and stuff on my oneplux which i got few days ago since my nexus 6 went dead, I do that because it's not my main phone and I don't have a lot of personal information stored there unlike on my 6P. For a tablet, maybe I would do that since I'll put it home usually .
randy6644 said:
Well, usually thieves might just wipe everything. But still, there are risks. There are certain ways to go around the locked screen if you got a unlcoked BL and rooted phone. I've got all my photos( No nude pics ) stored on Google, and also all my contacts, whom wouldn't be happy to share their information with a thief, and some notes, payment apps as well as some important emails. There's too much going on and I don't wanna take risks. Also, if my phone got stolen, I'll have make sure the SOB got a brick ,nothing more. Sure they can tear it apart and sell some parts of it, but they don't get a phone.
I still flash roms and stuff on my oneplux which i got few days ago since my nexus 6 went dead, I do that because it's not my main phone and I don't have a lot of personal information stored there unlike on my 6P. For a tablet, maybe I would do that since I'll put it home usually .
Click to expand...
Click to collapse
In that case, Android Device Manager comes into play and allows you to beef up your security.
Sent from my Pixel C using Tapatalk
I can't relock my bootloader no matter what I do, I always get this message:
command: fastboot oem lock begin
(bootloader) Check 'Allow OEM Unlock' in Android Settings > Developer
(bootloader) Options
OKAY [ 0.004s]
Finished. Total time: 0.006s
Why is this happening? I'm not trying to unlock it, it's already unlocked. I was able to relock it once before today but now I can't. I've tried wiping everything on twrp and installing different firmware but still get the same message. Before this I used to get a message saying "Please fully flash the signed build before locking phone" when I tried locking.
Why are you trying to relock it? Unlocking a bootloader does not cause performance issues or anything wrong and there is simply no point in relocking it. If your wanting to relock it before sending it in to Motorola don't even bother. They will know if it's been unlocked and relocking it doesn't magical get your warranty back. If selling it simply tell the person that the performance of the phone is not affected at all.
ninjakira said:
Why are you trying to relock it? Unlocking a bootloader does not cause performance issues or anything wrong and there is simply no point in relocking it. If your wanting to relock it before sending it in to Motorola don't even bother. They will know if it's been unlocked and relocking it doesn't magical get your warranty back. If selling it simply tell the person that the performance of the phone is not affected at all.
Click to expand...
Click to collapse
I really don't understand why this comes up so much. The answer is almost always the same too, warranty, sale, or return. None of which are good reasons to lock it.
This is a bit off topic but I'm going to share it anyways because I think it's hilarious. I once rooted and installed twrp on my neighbors phone to debloat it. Now, he's not tech savvy in the least bit. A few days later, he accidentally boots into twrp while turning his phone on. I wasn't home so he couldn't ask me what to do. In his anger and frustration, he dunked it right in the toilet. It still worked after that so he went to Best Buy to return it. The geek squad in all their wisdom... thought that twrp was special software designed to break into government servers. They call the police. The police show up and don't know what it is, or what to do with it. After 2.5hrs of head scratching and a nice chat with the FBI, he finally got his phone replaced. (The FBI knew exactly what it was.) If anyone had bothered to read what twrp's menus say, they would've understood what it was for in like 1-2min.
Tales from the tech department...
Right like I guess I understand the logic behind the thought process though so I don't mind it to much lol. and that was the best story about geek squad I've ever heard ??? leave up to them to think it's for hacking stuff lmfao this would go great ona Reddit geek squad encounters post
go to "developer options" and check again "oem unlock" and try again
ninjakira said:
Why are you trying to relock it? Unlocking a bootloader does not cause performance issues or anything wrong and there is simply no point in relocking it. If your wanting to relock it before sending it in to Motorola don't even bother. They will know if it's been unlocked and relocking it doesn't magical get your warranty back. If selling it simply tell the person that the performance of the phone is not affected at all.
Click to expand...
Click to collapse
Takes longer to boot and reboot. Stays stuck on bad key for a little while before it actually boots.
jrebmontana said:
go to "developer options" and check again "oem unlock" and try again
Click to expand...
Click to collapse
I can't, it's grayed out.
Spaceminer said:
I really don't understand why this comes up so much. The answer is almost always the same too, warranty, sale, or return. None of which are good reasons to lock it.
This is a bit off topic but I'm going to share it anyways because I think it's hilarious. I once rooted and installed twrp on my neighbors phone to debloat it. Now, he's not tech savvy in the least bit. A few days later, he accidentally boots into twrp while turning his phone on. I wasn't home so he couldn't ask me what to do. In his anger and frustration, he dunked it right in the toilet. It still worked after that so he went to Best Buy to return it. The geek squad in all their wisdom... thought that twrp was special software designed to break into government servers. They call the police. The police show up and don't know what it is, or what to do with it. After 2.5hrs of head scratching and a nice chat with the FBI, he finally got his phone replaced. (The FBI knew exactly what it was.) If anyone had bothered to read what twrp's menus say, they would've understood what it was for in like 1-2min.
Tales from the tech department...
Click to expand...
Click to collapse
Takes longer to boot.
needhelp4 said:
Takes longer to boot.
Click to expand...
Click to collapse
That's not true. An unlocked device actually boots up slightly faster. The reason why is; when you unlock the bootloader it skips verifying the boot.img signature. Meaning there's actually less work for the cpu to do before startup. The difference is extremely minimal though and probably not noticable without timing it in milliseconds.
Spaceminer said:
That's not true. An unlocked device actually boots up slightly faster. The reason why is; when you unlock the bootloader it skips verifying the boot.img signature. Meaning there's actually less work for the cpu to do before startup. The difference is extremely minimal though and probably not noticable without timing it in milliseconds.
Click to expand...
Click to collapse
You can see why in my reply to ninjakira. The screen displays 'bad key' on boot and only after a while restarts and actually boots.
needhelp4 said:
You can see why in my reply to ninjakira. The screen displays 'bad key' on boot and only after a while restarts and actually boots.
Click to expand...
Click to collapse
It's actually not restarting. That's the bootloader handing off control to the boot.img. The bad key screen, is actually the boot logo screen. The bootloader is just designed to show that instead of the logo if you're unlocked. The boot animation has it's own splash screen that perfectly matches the one in the boot logo. So when you're still locked and the hand-off occurs, it looks seamless. When you're unlocked it goes from black to the Moto logo, so you end up seeing the transition. The current brightness setting also kicks in at the boot animation, which makes it look even worse when unlocked. You can fix that by flashing one of my boot logos from here.
I just recently bought the Pixel 4xl just recently decided to sell it back to good but have to wipe & lock bootloader again what's the best way to do this?
WoZzYDoesitbest said:
I just recently bought the Pixel 4xl just recently decided to sell it back to good but have to wipe & lock bootloader again what's the best way to do this?
Click to expand...
Click to collapse
Factor reset, fastboot the latest factory image, lock the bootloader. Be sure to leave OEM unlocking and USB debugging turned on until you are completely done :good:
Honestly....so many instances of bricked devices doing this....I would honestly just do a device data reset swipe and just leave it unlocked bootloader and OEM unlocking retaining its "tick" (enabled)...i don't believe or think it makes any difference selling it and stating that it is still unlocked (bootloader) and what not....I mean, Google still accepts devices for servicing or replacement even if the device is in said state.
In the end, I think the risk of the device bricking outweighs the potential buyers passing on it; if anything, it might be a good selling point…!
Whichever you do, I hope & wish you have good luck!
simplepinoi177 said:
Honestly....so many instances of bricked devices doing this....I would honestly just do a device data reset swipe and just leave it unlocked bootloader and OEM unlocking retaining its "tick" (enabled)...i don't believe or think it makes any difference selling it and stating that it is still unlocked (bootloader) and what not....I mean, Google still accepts devices for servicing or replacement even if the device is in said state.
In the end, I think the risk of the device bricking outweighs the potential buyers passing on it; if anything, it might be a good selling point…!
Whichever you do, I hope & wish you have good luck!
Click to expand...
Click to collapse
Agreed, it seems to be insanely dangerous. Not sure why they made it this way considering the error at the start definitely makes it confusing when selling it and makes the device seem shady.