Not really an issue but just an annoyance. Since i updated to EMUI 5 and recovering from a soft brick to fully working every time i power off my phone i get the message above re unlocked. Is this the bootloader that is unlocked and is it an easy fix to get rid. Phone is running great with the update so far
Related
Just out of interest, has anyone unlocked their bootloader and then successfully had their device repaired under warranty?
Read this forum. It appears that people have better luck with a warranty repair instead of exchanging the device when the bootloader is unlocked.
http://forum.xda-developers.com/showthread.php?t=681723
I'm waiting to see how this works out for me. I sent my bootloader-unlocked Nexus in because I had dust under the screen. Also... I'm kinda sick of the unlocked padlock appearing on the screen every time I turn my phone on. I hope they relock it as I can root it without unlocking it anyway now. I'll let you guys know how it works out for me.
I opted for the swap when my Nexus One was acting up and my bootloader was unlocked and everything. After they received my old unit, I checked the status site and it shows: "Service is complete. Please visit HTC Customer Survey if you would like to take a quick survey regarding your experience contacting HTC.". They also took the hold off my credit card as well so I think everything is all good!
I sent mine in for repair with an unlocked bootloader and no problems.
Just got mine back today with an unlocked bootloader that was rooted and running a custom recovery with FRF93. No charge whatsoever! An HTC rep told me that they run the phone through a software test that is supposed to determine whether you unlocking/rooting the phone caused the issue. If they deem that you weren't at fault EVEN IF you did unlock/root then they repair the phone free of charge. Otherwise you're at fault and they will charge you.
rickytenzer said:
Just got mine back today with an unlocked bootloader that was rooted and running a custom recovery with FRF93. No charge whatsoever! An HTC rep told me that they run the phone through a software test that is supposed to determine whether you unlocking/rooting the phone caused the issue. If they deem that you weren't at fault EVEN IF you did unlock/root then they repair the phone free of charge. Otherwise you're at fault and they will charge you.
Click to expand...
Click to collapse
Hey Ricky was your bootloader still unlocked when you got your phone back?
Nope. Came back locked.
Just got my Nexus One back from HTC. It was bootloader unlocked, but I had installed ERD79 and had everything in the condition in which I originally received it. It came back with a locked bootloader and ERE27 (The 1st official OTA update.) I have now rooted it without unlocking the bootloader and am running CM6 RC1.
Would there be anyway to replace it, then get a fresh and new device?
whats getting me is the fact you guys are missing something here.. you have unlocked the bootloader and get it back locked! so either they jus switch the mobo on the n1 and flashed the original first release rom( seems to be the simple and most likely option)
OR there is an actual way to relock the bootloader that has not been found, to think if there is the way to do this, this will actually save lots of ppl that did software damage and still want to get warranty with you getting charged or getting denied!
ilostchild said:
whats getting me is the fact you guys are missing something here.. you have unlocked the bootloader and get it back locked! so either they jus switch the mobo on the n1 and flashed the original first release rom( seems to be the simple and most likely option)
OR there is an actual way to relock the bootloader that has not been found, to think if there is the way to do this, this will actually save lots of ppl that did software damage and still want to get warranty with you getting charged or getting denied!
Click to expand...
Click to collapse
I'm thinking the 2nd one.
Hey guys I'm so bummed.
So I unlocked my phone with Sunshine some time ago. Verizon recently pushed the marshmallow update to my droid turbo original. All good no problems. Anyways I'm now returning it to Verizon but I wanted to lock the bootloader first.
So I locked the bootloader with fastboot then rebooted the phone and got the pink failed to validate system image.
I had a freak out and so I tried to flash a stock rom (after locking the bootloader). I saw some messages saying downgrading. which makes sense because I used this:
https://forum.xda-developers.com/droid-turbo/general/guide-how-to-unlock-bootloader-install-t3292684
which I assume is old.
I got a lot of fail messages as I was flashing. And since the bootloader is locked, I don't see how this could work anyways.
I have two days before my new phone arrives and I have to send this back. How screwed am I?
Any help would be ridiculously appreciated.
Through some miracle, I just unbricked my phone. I locked it and bricked it but then I flashed the stock 6.0.1 rom and i'm good!. I'm now at a status 2 because i unlocked and relocked it. I know you guys hate that because why relock it, but i'm returning it and wanted to play it safe.
Weird thing is I'm still getting the unlocked bootloader warning on power on. Any ideas why and how I can get rid of it? I thought for sure relocking would fix it.
droidfun1 said:
Through some miracle, I just unbricked my phone. I locked it and bricked it but then I flashed the stock 6.0.1 rom and i'm good!. I'm now at a status 2 because i unlocked and relocked it. I know you guys hate that because why relock it, but i'm returning it and wanted to play it safe.
Weird thing is I'm still getting the unlocked bootloader warning on power on. Any ideas why and how I can get rid of it? I thought for sure relocking would fix it.
Click to expand...
Click to collapse
This might not work with a locked bootloader, but you can give it a shot.
Download the boot logo from this thread that looks like the original one: https://forum.xda-developers.com/mo...o-maxx-droid-turbo-x-style-logos-bin-t3407046
Double click on the .exe file while your phone is in bootloader mode and plugged into your computer.
Thanks ya, I have seen that logo fix floating around for the Droid Turbo but I didn't want to try until I had at least one confirmation that it could work on a relocked bootloader. Anyone have a guess/idea/or success story?
I got my H9L 2 months back and had rooted it (and unlockedd bootloader). Im having a big battery issue battery drains too fast. I want to get it to service centre as waranty is not over.
I've read posts saying if I relock bootloader I'll get waranty back but some says I won't get back warranty even if I relock bootloader.
Can someone sort this out please
IF you've unlocked the bootloader and rooted the device you have no warranty in the eyes of the manufacturer, it states this in the terms and conditions when you get your bootloader code from them.
See when you unlock the bootloader you get a warning screen upon booting the device and relocking the bootloader will not get rid of that warning.
However have you tried to see if the battery issue is intact an software issue. I.e have you wiped caches, checked if an app such as Google assistant WhatsApp Facebook is running in the background. Do you have the same issue when booting android into safe mode????
Sent from my SHIELD Tablet K1 using Tapatalk
hacktrix2006 said:
IF you've unlocked the bootloader and rooted the device you have no warranty in the eyes of the manufacturer, it states this in the terms and conditions when you get your bootloader code from them.
See when you unlock the bootloader you get a warning screen upon booting the device and relocking the bootloader will not get rid of that warning.
However have you tried to see if the battery issue is intact an software issue. I.e have you wiped caches, checked if an app such as Google assistant WhatsApp Facebook is running in the background. Do you have the same issue when booting android into safe mode????
Sent from my SHIELD Tablet K1 using Tapatalk
Click to expand...
Click to collapse
That's strange. I've relocked it today after flashing compete stock using HuRupdater tool.
I'm not having the warning screen I had earlier when my bootloader was unlocked.
So does that mean I'll be able to claim my waranty now?
And I've tried different ROMs the issue persists.
If they ask if I've unlocked the bootloader(since I've given my product number they might know) I'll just tell that I took the unlock code just in case, as they were shutting it down and that I haven't used it. Well at least that's the plan
So will they know that I've unlocked it earlier if there is no warning screen? As I've told I have complete stock firmware including kernal and recovery like @Fredin_ told.
Please reply fast.
If your no longer showing that Warning message after going back to stock then you can try and claim warranty if you wish, however they might have other ways to finding out if the bootloader has been unlocked.
So put your claim in and see what they do, they will either honor the Warranty or not Honor the Warranty and give you a quote for the work.
Personally if i unlock my bootloader and root it i'd just put up with the issue as i fully knew that the warranty went when i unlocked the device.
But i will leave it upto you how you go about it.
I just got a new Mi A2 and, thanks to Amazon, it came on a very old version of Android.
I have done Original version -> November OTA -> March OTA (Pie) and now trying to do April. However, the phone boot loops every time it tries to install it. If I leave it for 20 minutes or so unpowered it will finally restart and report 'Couldn't Update'
I have enabled OEM unlock, but not done the actual unlock in fastboot - could this be the cause? Is there a way to manually skip April too and go straight to June?
Thanks for any help.
Did have the same problem after unlocking bootloader it finished the update , was strange as hell so I stay unlocked for any case.
anryl said:
Did have the same problem after unlocking bootloader it finished the update , was strange as hell so I stay unlocked for any case.
Click to expand...
Click to collapse
So do a full unlock before trying again? At the moment I don't have the boot loader unlocked, I've just enabled the OEM unlock so I could unlock in case needed.
I never wait so long always do the 3button restart and see what's going on but here I did the full unlock and then it worked. On my wife's pink a2 all went fine no unlock needed so it's strange.
Sigh. I thought all this nonsense wouldn't be needed on an Android One phone.
Will give it a week or so and then go down the full unlock and re-set up route.
FFS found the solution on one of the other myriad boot loop threads - take the sim cards out before restarting.
Good for u mine was without sim.
It's still flaky. Have to power it on manually two or three times after restart - it doesn't boot loop, it just doesn't boot.