Related
Just a quick question.....
Does unlocking the Bootloader in te HTC One X remove any data from the home? I.e. does it wipe the device?
Thanks.
PS. I am planning in purchasing a One X because my iPhone is driving me mad.
Yup, the Phone Storage will be wiped!
Oh noes! I guess I'll just unlock it right out of the box then..
Appl_Usr said:
Oh noes! I guess I'll just unlock it right out of the box then..
Click to expand...
Click to collapse
You should just play around and test the phone before unlocking it. It will make warranty claims significantly easier if you've not unlocked or altered it at all. There have been quite a lot of reports about flaws in hardware and software in certain One Xs.
Most details should be synced to your Google account or whatever anyway so getting it going again after the unlock wipes data is easy.
I have bought through clove.co.uk my HTC ONE X.
I have successfully unlocked it through htcdev.com
Now I have a yellowish spot on the lower left corner - a hardware fault, clearly.
I have sent it back to clove.co.uk
They told me that HTC has some doubts about free of charge repairing.
I will keep you posted.
ninja.rogue said:
I have bought through clove.co.uk my HTC ONE X.
I have successfully unlocked it through htcdev.com
Now I have a yellowish spot on the lower left corner - a hardware fault, clearly.
I have sent it back to clove.co.uk
They told me that HTC has some doubts about free of charge repairing.
I will keep you posted.
Click to expand...
Click to collapse
please do..as your story seems quite interesting now. hopefully they will replace it for you but kinda makes you think twice before unlocking it now kinda makes me sad hearing that..i really do hope there is an S-OFF exploit cause if there is not i maybe just maybe might end up selling this and going back to either s2 or buy the s3 when that comes out and hopefully that bootloader will be unlocked...i am really loving my phone but things on this side seem so complicated compare to the s2 one
The htcdev unlock shouldn't affect your hardware warranty but it is worded so that in theory anything could be blamed on you altering the firmware. It would be daft if they do end up refusing to fix your phone for free as it is obviously nothing to do with the unlock.
NoobTerminator said:
please do..as your story seems quite interesting now. hopefully they will replace it for you but kinda makes you think twice before unlocking it now kinda makes me sad hearing that..i really do hope there is an S-OFF exploit cause if there is not i maybe just maybe might end up selling this and going back to either s2 or buy the s3 when that comes out and hopefully that bootloader will be unlocked...i am really loving my phone but things on this side seem so complicated compare to the s2 one
Click to expand...
Click to collapse
Yea if you want an easy to root/mod phone Samsung ones are generally better.
Sent from my HTC One X using XDA
I also have informed Clove that I have posted here.
Let's wait and see whether all the hype about HTC opening the bootloader is just marketing or has some sense. After all, I didn't alter anything hardware so if - say - some button or screen ceases to function or doesn't do it properly, why shouldn't warranty be valid??
The thing with the yellow point is well known. At least in Germany. Had a One X that had the same yellow spot on the left bottom of the display too.
Brought it back to the shop (Saturn) and get a complete new one.
Hopefully you get a new one, too!
Forget to mention that I've didn't unlock it.
ninja.rogue said:
After all, I didn't alter anything hardware so if - say - some button or screen ceases to function or doesn't do it properly, why shouldn't warranty be valid??
Click to expand...
Click to collapse
The way HTC word it on htcdev is that because you're not using official validated firmware then you might have had faulty firmware which damaged hardware e.g. it was overheating but the firmware somehow managed to ignore it and continue.
It depends on what is faulty I guess. If the micro USB socket breaks then it is obviously nothing that could be caused by firmware.
The yellowish spot is probably the glue they used to stick the LCD to the touchscreen. There are quite a few mentions of similar spots on this forum. Was it there when you first got the phone?
Yes it was there but it went unnoticed due to excess of enthusiasm in going through each and every menu and too much work to take care of small details. but then, with time, I got aware of the yellow spot.
Clove also noticed it and sent the phone to HTC.
I avoided unlocking at HTCDev as I'd like to keep my warranty, so I will be waiting for Revolutionary
Sent from my HTC One X using xda premium
same story here, i'm about to send it to htc, i'll await your results, too.
So no rooting without potential warranty issues?
patp said:
So no rooting without potential warranty issues?
Click to expand...
Click to collapse
HTC is entitled to some form of protection. If you overclock and fry your CPU they shouldn't have to eat the cost. Friends who unlocked international phones have gotten h/w (display, build issues, etc.) related warranty service from HTC with no hassle.
Here's their policy:
It is our responsibility to caution you that not all claims resulting or caused by or from the unlocking of the bootloader may be covered under warranty.
Unlocking the bootloader means that you now have the ability to customize software on your device. Please note that changing your bootloader can cause significant issues with your device and once you have unlocked your device, you have agreed to the disclaimer that states a change in warranty status such that in the event you render your device unusable, you are responsible for the recovery of your device, whether by repair or by other means.
It seems fairly reasonable. Asus has Prime owners completely waive their warranty rights, even for non-related issues, when they unlock their bootloaders. So it could be worse.
You know the old saying - "you play, you pay."
BarryH_GEG said:
HTC is entitled to some form of protection. If you overclock and fry your CPU they shouldn't have to eat the cost. Friends who unlocked international phones have gotten h/w (display, build issues, etc.) related warranty service from HTC with no hassle.
Here's their policy:
It is our responsibility to caution you that not all claims resulting or caused by or from the unlocking of the bootloader may be covered under warranty.
Unlocking the bootloader means that you now have the ability to customize software on your device. Please note that changing your bootloader can cause significant issues with your device and once you have unlocked your device, you have agreed to the disclaimer that states a change in warranty status such that in the event you render your device unusable, you are responsible for the recovery of your device, whether by repair or by other means.
It seems fairly reasonable. Asus has Prime owners completely waive their warranty rights, even for non-related issues, when they unlock their bootloaders. So it could be worse.
You know the old saying - "you play, you pay."
Click to expand...
Click to collapse
One one side - an entirely software based brick: user should pay. On the other side, failed hardware: manufacturer should pay. In between there may be differences of opinion!
patp said:
So no rooting without potential warranty issues?
Click to expand...
Click to collapse
I have also sent my phone in for a yellow spot. Phone was rooted on HTC dev. Right now the status is "In Repair". So we will see what they say. I did flash back to stock before sending it in.
i rooted my HOX also. after 2 weeks i noticed the wifi fault AND a yellow spot. relocked it and send it in for repair. returned the phone a few weeks later. Still had a wifi issue, but now i don't get warranty for their faulty repair the first time because they saw is was *relocked*
after a few angry phone calls i decided to fix it my self
Lazy-eye said:
i rooted my HOX also. after 2 weeks i noticed the wifi fault AND a yellow spot. relocked it and send it in for repair. returned the phone a few weeks later. Still had a wifi issue, but now i don't get warranty for their faulty repair the first time because they saw is was *relocked*
after a few angry phone calls i decided to fix it my self
Click to expand...
Click to collapse
My status just changed to "REPAIR COMPLETE". So i think i am in the clear.
I think due to a bad install of a rom on my part the phone would not charge.I had used Htcdev to unlock but reset to facory settings before sending it back to HTC for repair.I have been told its been repaired and on its way back to me.
Flyinace2000 said:
My status just changed to "REPAIR COMPLETE". So i think i am in the clear.
Click to expand...
Click to collapse
Strange now i am back to "In Repair"
Flyinace2000 said:
Strange now i am back to "In Repair"
Click to expand...
Click to collapse
And now it is back to awaiting device....very strange.
Flyinace2000 said:
And now it is back to awaiting device....very strange.
Click to expand...
Click to collapse
And now it shows the phone is being returned. So looks like they didn't care/check that my phone was "relocked".
UPS is set to drop it off tonight, but i am away on business so won't be able to report back on the quality until this weekend.
-Will
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
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
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.