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.
Related
I've got my device 2 weeks ago from T-mobile in Hungary.
So far it's been good, but I hated the Sense UI, unlocked my bootloader and installed CM10.
I've just noticed if I press the right edge of the screen I get this screen issue. I don't really know how to describe it, but it's just as if I pressed my desktop's LCD screen. The screen slightly recoulours and waves appear. I've found others with the same issue (and there seems to be another guy from T-Mobile HU): http://crave.cnet.co.uk/mobiles/htc-one-x-screen-flex-flaw-we-would-never-let-that-ship-50007596/
However I don't even have to press it hard, - normally is enough - and it's not only on the right corner, but on the edge too. Sometimes I can hear a crack. (it must be the case of the device)
So I'd like to get it fixed or replaced, but sadly as I've mentioned I've already unlocked my bootloader. Is this a problem for replacing/fixing it? Where should I take it? T-mobile or to HTC?
Thank you very much for your help and time.
P.S. Why always me? :crying: 泣く
same here.
Well, you should always look after faults with your phone before unlocking the bootloader.
Sent from my HOX running CMX by Tbalden.
Relock bootloader and return it back
Tingelholm said:
Well, you should always look after faults with your phone before unlocking the bootloader.
Sent from my HOX running CMX by Tbalden.
Click to expand...
Click to collapse
Alright, why would I start pushing around the edges of a new phone? Thanks for your constructive response.
By the way the I checked the htcdev site again, it sais
Unlocking your device allows you to install custom Operating Systems (“OS”) onto your device. Custom OS’s are not tested as thoroughly as your original OS, and unlocking your device may void all or parts of your warranty.
Click to expand...
Click to collapse
>may void.
English grammar: may means something is possible, but it is not certain. So this could be interpreted as you're only responsible for the software, and this is a build issue.
So T-mobile (carrier) or HTC?
this is going to be my last htc device, the original SGS was leaps and bounds better, even with its cheap plastic back, but sadly I've lost it. You didn't even have to unlock the bootloader.
P.S. Sorry for my English
EDIT
DoeBoi said:
Relock bootloader and return it back
Click to expand...
Click to collapse
No point, if one relocks the bootloader the fact that someone has opened it before can be seen.
Wait if I take it to the carrier they'd send to it htc to repair it right?
Im at T-Mobile Hungary, too, and if you send it back to them, they send it to HTC, and after that it doesnt matter if its repaired or not, you'll even have to pay for returning your damaged phone...my hungarian is better than my english
Well, obviously if you would just have waited a couple of weeks before unlocking your bootloader you would obviously have noticed the screen? Thank you for your constructive response.
Sent from my HOX running CMX by Tbalden.
Silgrond said:
No point, if one relocks the bootloader the fact that someone has opened it before can be seen.
Click to expand...
Click to collapse
True, but the only way to RUU it back to stock is with a ***LOCKED*** or ***RELOCKED*** HBOOT.
TripleD_HOX said:
Im at T-Mobile Hungary, too, and if you send it back to them, they send it to HTC, and after that it doesnt matter if its repaired or not, you'll even have to pay for returning your damaged phone...my hungarian is better than my english
Click to expand...
Click to collapse
Thanks for your response. But obviously its not my fault. They shouldn't charge me for anything. I still have my T-Mobile warranty.
Rusty! said:
True, but the only way to RUU it back to stock is with a ***LOCKED*** or ***RELOCKED*** HBOOT.
Click to expand...
Click to collapse
Can you please explain it? RUU is to revert to stock right? Can HTC see if I had unlocked my phone earlier if I do this? Care to post a guide or something?
No guide necessary, you just run a .exe and away it goes.
However it will fail if you try and use it with an unlocked bootloader, so as you have one, you have to relock it. Sadly though, it won't hide that you've done it, but at least it wont have CM10 on it anymore.
Rusty! said:
No guide necessary, you just run a .exe and away it goes.
However it will fail if you try and use it with an unlocked bootloader, so as you have one, you have to relock it. Sadly though, it won't hide that you've done it, but at least it wont have CM10 on it anymore.
Click to expand...
Click to collapse
Restored it with RUU, wish me luck tomorrow at T-mobile
EDIT: Aight, they sent it to HTC. They'll get back to me in 2 weeks.
This is ****ing retarded.
They've replaced the screen and the battery, but it has the same build issue but on the left side. ARE YOU ****ING KIDDING ME?!
I'm going to ask for a replacement tomorrow. What the flying **** HTC. Feels like I'm being trolled
I had this "problem" from the beginning.
Not sure why this is a big deal, since i never squeeze my phone on the sides.
I thought this was a normal thing...
Are you sure they actually replaced the screen? And why the battery? You have every right to be pissed off
JoeyDez said:
I thought this was a normal thing...
Click to expand...
Click to collapse
It's not
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.
After unlocking the bootloader, you're stuck with a message, everytime you reboot your phone, which gives you a warning that the bootloader is unlocked. Quite annoying if you ask me, especially because it takes 5 seconds before the phone continues to reboot.
Is there somebody who can remove that warning? It's already done for the motorola G4, so I guess it shouldn't be to difficult for the OP3, as long as somebody with a little bit of know how takes a look into this issue.
Somebody here who can make this happen?
wait for this mod
so annoying
Yeah will wait for this one
Shouldnt be too hard for a dev to do. i know they did it for the nexus devices. oneplus has one fugly looking fastboot and unlocked warning. also they cant spell.
fix-this! said:
Shouldnt be too hard for a dev to do. i know they did it for the nexus devices. oneplus has one fugly looking fastboot and unlocked warning. also they cant spell.
Click to expand...
Click to collapse
hahah，they can't spell
+1 for this
Gesendet von meinem OnePlus 3
Bart1981 said:
After unlocking the bootloader, you're stuck with a message, everytime you reboot your phone, which gives you a warning that the bootloader is unlocked. Quite annoying if you ask me, especially because it takes 5 seconds before the phone continues to reboot.
Is there somebody who can remove that warning? It's already done for the motorola G4, so I guess it shouldn't be to difficult for the OP3, as long as somebody with a little bit of know how takes a look into this issue.
Somebody here who can make this happen?
Click to expand...
Click to collapse
unlocking the bootloader does avoid your warranty or not?
Arrowblue said:
unlocking the bootloader does avoid your warranty or not?
Click to expand...
Click to collapse
If I remeber correctly, when you are unlocking the bootloader you get a warning that it MIGHT void warranty. But I don't think that will be the case with OnePlus.
Bart1981 said:
If I remeber correctly, when you are unlocking the bootloader you get a warning that it MIGHT void warranty. But I don't think that will be the case with OnePlus.
Click to expand...
Click to collapse
yeah other Oems like, sony samsung does avoid your warranty when you are bootloader unlocked but One plus 3 i always thought they are good to go even when your bootloader is unlocked.
It is required by Android/Alphabet as a verified device, but honestly 1+ how hard would it have been to spellcheck this screen.
I welcome a removal of this screen
Me too. The incorrect spelling drives my OCD to despair.
Sent from my ONE A3003 using XDA-Developers mobile app
+3
on the 6p. it's somewhere in the ramdisk which was risky to tinker with so nobody bothered to risk and remove it. on the other hand it's really simple with the 5x. not sure on the op3.
Arrowblue said:
unlocking the bootloader does avoid your warranty or not?
Click to expand...
Click to collapse
No
I'm waiting for this as well. Tried messing with it myself, but have very little to any experience in this particular area. I found where the LOGO file was, but when I copy and changed the format to IMG or BIN, it was unreadable with the two different programs I have to read those file types, so instead of messing things up - I gave up.
At least they fixed the spelling and the placeholder url in the latest update. I can put up with it now.
Unlocked and flashed cyanogen yesterday and didn't know the OP3 had this screen either....it's much worse that the N6P one but not as alarming lol it's still really annoying and I went back to a locked stock because of it.
Still at least it's not as annoying as the one they put on the Pixel C.....
+1 for this. Its really annoying. I hope it can be patched up quickly.
rustyshakelford2 said:
At least they fixed the spelling and the placeholder url in the latest update. I can put up with it now.
Click to expand...
Click to collapse
the gramma is still with mistake...
If no key pressed (if no key is pressed)
lol
How often do you guys reboot your phones for this to be an issue? I'll admit the unlocked padlock from the Nexus was a bit more classy but I can't see how this is a dealbreaker when you hardly ever reboot your phone outside flashing stuff.
Hi! So, a couple of months ago I bought the HTC 10, and it's safe to say that I love the phone, the only thing I wasn't a big fan of was Sense OS, so I decided to fire up Lineage OS into the phone and lo and behold, the perfect phone was born. It was beautiful, and the customization I could do was on another level, not to mention performance. Until I decided to tinker a bit with the phone's look and then the problems started.
I was prompted to update my OS which I gladly do every week, but I hadn't customized the software that much before, so when I flashed the update, I was stuck in bootloop. I flashed the zips that supposedly uninstalled everything I did to the phone and was still stuck in bootloop, did a wipe, still bootloop, it wasn't until I did a complete factory reset when I got my phone back. But then, I saw something.
After booting up, I saw a tiny bright spot under the lower left of the screen, I barely noticed it, but it was there. I decided to go back to stock, and it was still there. Looked into the problem and apparently it's a hardware issue. Called HTC and they told me that they could come for the phone on Tuesday, but the thing is, my phone's status is "modified" I try to lock the phone again and it changed from "unlocked" to "relocked", I'm afraid that these guys might have something to say about that and they'll give me back my phone with no repair at all...
So, what do you guys think? Do HTC care if the phone was unlocked and rooted once before, or that the software status is modified? How can I change those things? Is it really worth it to send my phone for repair? (the spot is really small and not that noticeable, but I'm scared it might get bigger over time)
Sorry for the lengthy post, hopefully you understand. Thanks in advance!
Since this is apparently a defective hardware issue, they shouldn't care. My first HTC 10 was broken (vibration didn't work), and it took me 6 weeks of going back and forth with them to get it replaced and it was completely unmodified. I would say you shouldn't have any issues getting a replacement, because only the software was modified, and you returned that to complete stock, then the issue with the screen spot occurred.
I agree, just returning it to stock should be enough. From what I remember they don't specifically say that unlocking the bootloader completely voids the warranty even for hardwaee issues.
I say send it in and let them replace the screen.
taker714 said:
Hi! So, a couple of months ago I bought the HTC 10, and it's safe to say that I love the phone, the only thing I wasn't a big fan of was Sense OS, so I decided to fire up Lineage OS into the phone and lo and behold, the perfect phone was born. It was beautiful, and the customization I could do was on another level, not to mention performance. Until I decided to tinker a bit with the phone's look and then the problems started.
I was prompted to update my OS which I gladly do every week, but I hadn't customized the software that much before, so when I flashed the update, I was stuck in bootloop. I flashed the zips that supposedly uninstalled everything I did to the phone and was still stuck in bootloop, did a wipe, still bootloop, it wasn't until I did a complete factory reset when I got my phone back. But then, I saw something.
After booting up, I saw a tiny bright spot under the lower left of the screen, I barely noticed it, but it was there. I decided to go back to stock, and it was still there. Looked into the problem and apparently it's a hardware issue. Called HTC and they told me that they could come for the phone on Tuesday, but the thing is, my phone's status is "modified" I try to lock the phone again and it changed from "unlocked" to "relocked", I'm afraid that these guys might have something to say about that and they'll give me back my phone with no repair at all...
So, what do you guys think? Do HTC care if the phone was unlocked and rooted once before, or that the software status is modified? How can I change those things? Is it really worth it to send my phone for repair? (the spot is really small and not that noticeable, but I'm scared it might get bigger over time)
Sorry for the lengthy post, hopefully you understand. Thanks in advance!
Click to expand...
Click to collapse
If your that worried about it, doing a ruu to get completely back to stock should fix the modified message
First of all, I want to thank everyone who answered this post, really appreciate your opinions.
So, quick update, after I sent my phone, literally got a call the next day telling me that the software was modified and it breached HTC's guarantee. So unfortunately it's a thing... I'm probably going to ignore the issue with the screen since for now it's not that big of a deal, but I have a feeling that I'll have to buy a screen replacement and try and replace it myself down the line. Kinda bummed, always been a Nexus guy but loved and admired HTC's phone designs and quality, so when my Nexus 5 died earlier this year (After three years of abuse, Android bless his soul), I thought that it was time to get "HTC's comeback phone", since the Pixel was so expensive and hard to get. Not saying I regret buying the 10, still is a joy to hold and use, and in my opinion, a lot more better looking and manageable than the HTC U11, but still, had my expectations just a tiny bit higher... I guess that's what you get when you try out new ROMs haha.
Thanks again to everyone who responded this post, hopefully this helped someone.
So even you return your htc 10 back to stock and relock bootloader phone is not under warranty?Wtf?
johnnyman25 said:
So even you return your htc 10 back to stock and relock bootloader phone is not under warranty?Wtf?
Click to expand...
Click to collapse
Ikr? The thing is that even if you flash with RUU and lock the phone, the system doesn't change to a "locked" status again, but it changes to a "relocked" status... And while it's that way, the system will appear modified in the bootloader. And any modification to software goes against HTC's guarantee because they basically blame your hardware issue on you tinkering with the software. Pretty funny if you ask me, but oh well xd
taker714 said:
Ikr? The thing is that even if you flash with RUU and lock the phone, the system doesn't change to a "locked" status again, but it changes to a "relocked" status... And while it's that way, the system will appear modified in the bootloader. And any modification to software goes against HTC's guarantee because they basically blame your hardware issue on you tinkering with the software. Pretty funny if you ask me, but oh well xd
Click to expand...
Click to collapse
But I read the htc accepts phones with stock software and relocked bootloader. It's a lie?
HTC 10 Matte Black Power
I mean, it probably depends who takes the phone and how they check for faults... Maybe I was flat out unlucky
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