Database Develop

Warning ahead of unlocking bootloader

http://support.setool.net/showthread.php?3-UPDATES-AND-NEWS&p=74240#post74240
read down to Oct 27 news update.
This should kinda serve as a general warning to those who want to unlock their bootloader, though it is not fully confirmed as of yet
Please check production date of your model before any attempt

oh thats so scary. My phone is E16i and has a date of 11W34.
I was able to unlock and relock bootloader for so many times... does it mean that my phone will not get a bad luck on that?

whats resurruction cable method?
Sent from my E15i using xda premium

vientito said:
read down to Oct 27 news update.
This should kinda serve as a general warning to those who want to unlock their bootloader, though it is not fully confirmed as of yet
Please check production date of your model before any attempt
Click to expand...
Click to collapse
To spare everyone the trouble, here's the text of the post in question:
seems most of lately produced msm7227-based phones have chipset with FIXED security hole, which used to altbypass unlock.
(that is not 100% confirmed, we only have few reports, however better be warned)
such phones will DIE after successful unlock procedure.
such dead phones CAN NOT be recovered. ( perhaps, jtag can fix that, perhaps, qualcomm fixed jtag security hole too )
there is NO WAY to determine if phone has fixed chipset or chipset with security hole.
the ONLY safe way is to use unlock by resurrection cables.
if phone can be connected and booted by resurrection cables, phone is safe to unlock.
if phone can not be booted by resurrection cables, phone has fixed chipset and could not be unlocked.
you have been warned.
get and use resurrection cables.
update:
e16 phone with manufacture date 11w38 affected, i think we should care about phones which produced after 11w26
maliceomalice said:
whats resurruction cable method?
Click to expand...
Click to collapse
Seems to be a special designed interface to access the UART recovery mode on a hard bricked device (very low-level stuff, comes right after JTAG'ing). See this YouTube link.
If anyone of you ever followed the awesome Samsung unbrick posts by Adam Outler you should have an idea what UART access means and therefore should have a clue about what the "recovery cable" device is able to do.
The only thing that doesn't add up ... the recovery cable video doesn't show any interface for the W8/E16.

so does it mean newer phones cant unlock bootloader? so my w8 i bought from last week got brick during unlocking bootloader might be a victim of this new security hole? o ya...why must SE do this? to prevent us from bootloading?

....... I got my x8 12 months ago and I successfuly unlocked my bootloader. But what your basically saying is that newer phones can't be unlocked.. like the unlock tool to new phones is a deathtrap? Woooo. Watch out new buyers
sent from my x8 running gingerdx

Simply put, SE has a lot of stakes to protect.

wilbso said:
But what your basically saying is that newer phones can't be unlocked.. like the unlock tool to new phones is a deathtrap?
Click to expand...
Click to collapse
That's the point in case. If the phone is within the specified date of manufacturing you can successfully unlock the bootloader, but after you did the stunt and reboot the device it's basically hard bricked beyond "do it yourself at home" repair possibilities.
The best shot you then have left is to find a repair shop having a RIFF Box (JTAG) or the aforementioned Resurrection Cable (UART Recover) to breathe new life into the device.
However, it's at least good to know that this pithole is there (though I find it fascinating that they kept on fixing up the hardware flaws - or hardware based security holes - in the chipset). EDIT: Might also explain why some people experience weird problems with custom ROMs the majority isn't able to reproduce.

Mine's a 11W28 unlocked my bootloader and it's not bricked.......

B.Jay said:
That's the point in case. If the phone is within the specified date of manufacturing you can successfully unlock the bootloader, but after you did the stunt and reboot the device it's basically hard bricked beyond "do it yourself at home" repair possibilities.
The best shot you then have left is to find a repair shop having a RIFF Box (JTAG) or the aforementioned Resurrection Cable (UART Recover) to breathe new life into the device.
However, it's at least good to know that this pithole is there (though I find it fascinating that they kept on fixing up the hardware flaws - or hardware based security holes - in the chipset). EDIT: Might also explain why some people experience weird problems with custom ROMs the majority isn't able to reproduce.
Click to expand...
Click to collapse
Mine must have been within the specified date cuz like I said before
I unlocked it successfuly, its works perfect. But yeah, thanks for the explanation
sent from my x8 running gingerdx

wilbso said:
....... I got my x8 12 months ago and I successfuly unlocked my bootloader.
Click to expand...
Click to collapse
wilbso said:
Mine must have been within the specified date cuz like I said before I unlocked it successfuly, its works perfect.
Click to expand...
Click to collapse
If you got yours 12 MONTHS ago ... No, yours is NOT in the specified date!
11w26 (and onwards) seem to be problematic
11w38 (and onwards) seem to be sure hard brick
2011, wilbso - NOT 2010 (hint: we're still in 2011 for a few more days)

B.Jay said:
If you got yours 12 MONTHS ago ... No, yours is NOT in the specified date!
11w26 (and onwards) seem to be problematic
11w38 (and onwards) seem to be sure hard brick
2011, wilbso - NOT 2010 (hint: we're still in 2011 for a few more days)
Click to expand...
Click to collapse
Just cuz I got it 12 months ago dosnt mean the model was created then.... on he back of my x8 it says 10w47, that specific anough for ya?
sent from my x8 running gingerdx

Plus my phone is an e15 not an e16 as mentioned in earlier post that's its e16 not e15 phones that willl have the problem
sent from my x8 running gingerdx

amnher said:
oh thats so scary. My phone is E16i and has a date of 11W34.
I was able to unlock and relock bootloader for so many times... does it mean that my phone will not get a bad luck on that?
Click to expand...
Click to collapse
Mine with 11w33,, not bricked..., and always change with many custom kernel....
can explain me with it...?

@wilbso:
U mad, bro?
donny_mey said:
Mine with 11w33,, not bricked..., and always change with many custom kernel....
can explain me with it...?
Click to expand...
Click to collapse
Well, as we can only speculate on the Engrish post TheLaser made on the site from where the info comes from ...
W8/E16 phones within the range of 11W26 through 11W37 seem to be problematic. I interpret this as "there's some hardware fix though it can be worked around in software". If this now refers to flashtool or the replacement bootloader binary is up for anyone's guess.
11W38 and onwards seems to be a candidate for a sure kill after unlocking the bootloader. I interpret this as "the new bootloader binary that gets installed doesn't manage to start up because various 'security holes' have been fixed in the hardware therefore rendering the code defunct". That would at least explain why such hard bricks show no sign of life anymore at all (no LED, no screen, no nothing).
If you find a better theory or a better detailed description written in non-Engrish type ahead ...

B.Jay said:
@wilbso:
U mad, bro?
Well, as we can only speculate on the Engrish post TheLaser made on the site from where the info comes from ...
W8/E16 phones within the range of 11W26 through 11W37 seem to be problematic. I interpret this as "there's some hardware fix though it can be worked around in software". If this now refers to flashtool or the replacement bootloader binary is up for anyone's guess.
11W38 and onwards seems to be a candidate for a sure kill after unlocking the bootloader. I interpret this as "the new bootloader binary that gets installed doesn't manage to start up because various 'security holes' have been fixed in the hardware therefore rendering the code defunct". That would at least explain why such hard bricks show no sign of life anymore at all (no LED, no screen, no nothing).
If you find a better theory or a better detailed description written in non-Engrish type ahead ...
Click to expand...
Click to collapse
i realy sure about that but in 11w38 maybe killed with this act....
but i'm not sure for this,,,, or this a promotion tools from SE tool, and we must buy if we want to unlock that...
it's right...???

donny_mey said:
but i'm not sure for this,,,, or this a promotion tools from SE tool, and we must buy if we want to unlock that...
Click to expand...
Click to collapse
This is not a promotion from SE or any other company. The fact behind this is...
...that if you have a hard bricked W8 you need the "resurrection cable" thingy to _maybe_ restore the firmware on the phone (as there's no intel on how the "resurrection" is possible on the aforementioned models it's yet another guessing based on what has been written all over the place (read: "oberservation"), therefore the "maybe").
...that the safest way to attempt a bootloader unlock on said phones is to do it through the "resurrection cable" as only there you can tell IF it will work or not.
The only "promotion" in all of it is the heads-up on that piece of hardware a do-it-yourself-at-home technician (or privateer wanting to specialize in unbricking dead phones) may need - and that's all.

B.Jay said:
@wilbso:
U mad, bro? Is the 10w47 within the specified date. Because I unlocked bootloader without trouble
Well, as we can only speculate on the Engrish post TheLaser made on the site from where the info comes from ...
W8/E16 phones within the range of 11W26 through 11W37 seem to be problematic. I interpret this as "there's some hardware fix though it can be worked around in software". If this now refers to flashtool or the replacement bootloader binary is up for anyone's guess.
11W38 and onwards seems to be a candidate for a sure kill after unlocking the bootloader. I interpret this as "the new bootloader binary that gets installed doesn't manage to start up because various 'security holes' have been fixed in the hardware therefore rendering the code defunct". That would at least explain why such hard bricks show no sign of life anymore at all (no LED, no screen, no nothing).
If you find a better theory or a better detailed description written in non-Engrish type ahead ...
Click to expand...
Click to collapse
Sorry.... is 10w47 in the specific date? Cuz I managed to unlock bootloader and flash custom kernel. In about to flash another soon just need your oponion
sent from my x8 running gingerdx

wilbso said:
is 10w47 in the specific date? Cuz I managed to unlock bootloader and flash custom kernel. In about to flash another soon just need your oponion
Click to expand...
Click to collapse
10W## through 11W25 should be considered safe
(where 10W## means "from start of production all through 2010")
11W26 through 11W37 could turn out to be problematic
(though I'm not sure what Laser means by that exactly)
11W38 and newer are supposed to hard brick
("no sign of life" .. no LED, no vibrate, no screen, no flash-mode connection)
Note that this seems to apply to the W8 E16 AND X8 E15 as well ... in one of tohno's threads we have a hard bricked X8 (11W43) mentioned.
I'm still trying to make head and tails out of the random info, but I think it's safe to say that one should better have a look at the manufacturing code before trying to unlock the bootload to avoid a bad awakening.
Edit: On a second thought ... while we're still lacking in-depth details I think someone should prod one of the mods to post a sticky tagged as "[WARNING] Read BEFORE attempting bootloader unlock".

I can confirm a hard brick on my Xperia x8 (11w40) when trying to unlock my bootloader.

Problems X8.help!!

I got through msm7227_semc the boot loader unlock the phone but then no longer clear.
I'm doing?

My phone is not clear
sorry for my english

omidsys said:
I got through msm7227_semc the boot loader unlock the phone but then no longer clear.
I'm doing?
Click to expand...
Click to collapse
By "no longer clear" you mean what?
You unlocked the boot loader and now the phone does NOT show any light, vibration or things on the screen anymore?
Simply try to describe the problem in a few words so we can get the idea.

got the same issue unlocking bootloader, wait till process is dne completely!
then verify using s1 tool if unlocked!
ur fone shud boot up! hope ur on stock rom
Sent from my E15i using XDA App

B.Jay said:
You unlocked the boot loader and now the phone does NOT show any light, vibration or things on the screen anymore?
.
Click to expand...
Click to collapse
Yes! I have exactly the same
The phone does not react.
The phone does not power.

In this case I'm very sorry to break it over to you, but this is a hard brick - especially if the manufacturing date of your phone is 11W29 or newer (11W30, 11W31, 11W32, ...) - take out the battery and look at the sticker below.
There's no way left by which you can "repair" the phone yourself. You need to either take the phone to a repair shop (if such a thing even exists in Iran) or send it in for repair.
From the hard bricks we observed around here the repair measure will be that the motherboard needs to be replaced past a working one.
Simply take a look in the X8 Q&A section and have a look at the "Warning ahead of unlocking bootloader" thread.

B.Jay said:
In this case I'm very sorry to break it over to you, but this is a hard brick - especially if the manufacturing date of your phone is 11W29 or newer (11W30, 11W31, 11W32, ...) - take out the battery and look at the sticker below.
There's no way left by which you can "repair" the phone yourself. You need to either take the phone to a repair shop (if such a thing even exists in Iran) or send it in for repair.
From the hard bricks we observed around here the repair measure will be that the motherboard needs to be replaced past a working one.
Simply take a look in the X8 Q&A section and have a look at the "Warning ahead of unlocking bootloader" thread.
Click to expand...
Click to collapse
yes.Date of manufacture 11w40
Whether the box is setool?

omidsys said:
yes.Date of manufacture 11w40
Click to expand...
Click to collapse
Yap, that phone is dead.
omidsys said:
Whether the box is setool?
Click to expand...
Click to collapse
I honestly don't get what you mean, but the hard brick you now have in your hands was caused by two facts ...
1. The phone being manufactured 11W40 (way past 11W29 where the trouble starts) means that the chips used in your phone are of a newer revision which have the security hole the boot loader unlock tool uses closed. At the moment you unlock the boot loader you kill the phone.
2. You didn't do your homework in gathering info about the boot loader unlock procedure. While the guys maintaining the "How to unlock the boot loader" are ignorant to inserting the hard brick warning, a simple in-depth reading of the X8 related boards and posts would have spared you this fate.
The only way to get the phone back to work now is to, as written above, take it to a repair shop or to send it to Sony Ericsson.

Try charging the bettery ,full, then begin the whol process again
Sent from my E15i using XDA App

B.Jay said:
Yap, that phone is dead.
I honestly don't get what you mean, but the hard brick you now have in your hands was caused by two facts ...
1. The phone being manufactured 11W40 (way past 11W29 where the trouble starts) means that the chips used in your phone are of a newer revision which have the security hole the boot loader unlock tool uses closed. At the moment you unlock the boot loader you kill the phone.
2. You didn't do your homework in gathering info about the boot loader unlock procedure. While the guys maintaining the "How to unlock the boot loader" are ignorant to inserting the hard brick warning, a simple in-depth reading of the X8 related boards and posts would have spared you this fate.
The only way to get the phone back to work now is to, as written above, take it to a repair shop or to send it to Sony Ericsson.
Click to expand...
Click to collapse
I've pm'ed the op to put the bootloader warning long ago.
To this thread op.. ur phone is dead.. take it to sony center for repair..
Sent from my Android using Tapatalk

joe200 said:
I've pm'ed the op to put the bootloader warning long ago.
Click to expand...
Click to collapse
That was a good idea on your behalf (will give a thanks to you), though it seems the warning didn't stick or wasn't understood in full.
Well, seems to be a somewhat common issue that English seems to be too hard to learn.

[Q] why phone get hard brick

why r my phone get hard bricked after succesfully unlock bootloader ..the script is like these ..
process requires standard 2.x android firmware.
Press any key to continue . . .
Getting ROOT rights.
1743 KB/s (585731 bytes in 0.328s)
error: protocol fault (no status)
Waiting ...
Removing NAND MPU restrictions via SEMC backdoor. Permanent. Require ROOT rights.
192 KB/s (3087 bytes in 0.015s)
success
Waiting ...
Getting ROOT rights.
Waiting ...
Writing patched semcboot. Two step process
First, we need get access to semcboot area
504 KB/s (8064 bytes in 0.015s)
Second, we need to write semcboot
1130 KB/s (596916 bytes in 0.515s)
successfully wrote 0003ff00
Press any key to continue . . .
after that my phone won't boot nor any green light ..please help ..
it's my friends phone and his brother bought it for his mother and i was giving him a stupid idea that unlock bl will make phone more faster ..
Edit : ..i have unlock bl before using my own x8 and it went well ..no problem at all ..but my friends phone ..well ..

try removing the battery and putting it back and try again to start the phone.
i unlocked bootloader a few days ago got the same log and everything worked well
before putting your battery back..post here the 11wXX number behind the battery.

well ..its my friends phone but i'll ask em when he comes ..but ..i did tried remove the battery for couple of minutes ..the battery status is about 32% before i unlock the bl ..when use s1tool to identify, ..it can't even detect the phone anymore ..like i said ..not even a green light ..
they said if there were a green light, then i will have a little hope left ..
EDIT : ..the battery is 11w29

i think after 11w28 if you successfully unlock the bootloader,your phone is DEAD......saw it in the bootloader unlocking thread....
hope it helps

ohh my
great ..looks like i'm going to replace my friends phone ..uhh ..i don't have that much kind of money ..thanks though~

caer_ayu said:
11w29
Click to expand...
Click to collapse
That's exactly the start of the manufacturing date range where the "hard brick upon boot loader unlock starts.
In short - if it does not show any signs of life (no LED, no vibrate, no screen) you can safely assume it's dead now.

humm... read this thread
http://forum.xda-developers.com/showthread.php?t=1399381
I think you are unlucky!
Sorry for my bad english!

pesky_89 said:
try removing the battery and putting it back and try again to start the phone.
i unlocked bootloader a few days ago got the same log and everything worked well
before putting your battery back..post here the 11wXX number behind the battery.
Click to expand...
Click to collapse
what about my 11W14 and my friends 10W33 ??is it safe to unlock bootloader??

wanazrimuahaha said:
what about my 11W14 and my friends 10W33 ??is it safe to unlock bootloader??
Click to expand...
Click to collapse
11w28 bellow = safe
11w29 above = risky

can it be fix by jtag ? ..who live's in malaysia and stay around ipoh ..does ipoh have jtag ? ..i've search at google but it only came out jtag xbox360 ..wtf
EDIT : even though if i send it back to se cause the phone was bought only 1 week, will they notice that the warranty has been sealed because i root first before unlock the bl ..even though tried to unlock the bl ..will they notice ?

caer_ayu said:
can it be fix by jtag ? ..who live's in malaysia and stay around ipoh ..does ipoh have jtag ? ..i've search at google but it only came out jtag xbox360 ..wtf
EDIT : even though if i send it back to se cause the phone was bought only 1 week, will they notice that the warranty has been sealed because i root first before unlock the bl ..even though tried to unlock the bl ..will they notice ?
Click to expand...
Click to collapse
tohno, who happens to live in Malaysia as well, also hard bricked his W8 and had it repaired (motherboard got replaced).
Various other posts also suggest that SE won't recognize the cause - they will either swap out the motherboard or send you a new phone altogether.

@B.jay I don't thing so..
because my 2nd bricked I got E15i stock rom running on my W8
and on the rom I has super User and rooted..
when repaired done..I got the same firmware and with the superuser..
I thing maybe they just push bootloader ro something like that..
(just my 2cent IMO)
@caer_ayu
for me I got 4 times hard bricked
and they repaired my phone without lot of questions
I mean just show them my phone died and:-
(for1st bricked)i said IDK when I leave it for charging and when I cameback it died..
(2nd bricked)(just less than 1hour i got my phone) I ask my friend to sent it
(3rd bricked) I sent to vendor (not like b4 sent dirrect to warranty provider)
(4th bricked) Just like 2nd brick (with same person)
Hahaha...and now I confirm my phone can't go far enought...
and that why i just catch a X8 which can go far enought..11w23 and cypress digitizer...and very happy when i have to waiting for my W8 comeback...
sorry for long explaination..

nelikp ..where did you live ? ..my friend buy this phone at the shopping mall, at there, they know about rooting and unlck bootloaders to android phones. i was just affraid they might notice. will they send it to se or they do it themself ..

I live in KL..
for me I brought at shopping mall
and this is "AP" set (I mean warranty provided by 'COMSAT')
and the original set (warranty provided by 'SE')
'AP' set cheper than 'ORI' set
and if "COMSAT" can't fix the phone they will send to "SE" to handle
in my case "COMSAT" only 10 miniutes drive from my home
so I'm lucky stay here..
In your case..ask them about your "phone set (ORI or AP)
and ask them which company provide warranty for your phone
and go direct to the warranty (incase wanrannty provider isn't SE)

i think it was an ORI set ..because it has a Midland warranty seal ..i bought my x8 originally from the se center few months ago and it has Midland warranty seal also ..so it's definitely ORI set ..i hope they didn't charge for repair fees ..

nelikp said:
@B.jay I don't thing so..
because my 2nd bricked I got E15i stock rom running on my W8
and on the rom I has super User and rooted..
when repaired done..I got the same firmware and with the superuser..
I thing maybe they just push bootloader ro something like that..
(just my 2cent IMO)
Click to expand...
Click to collapse
I don't see why it should be impossible to "revive" a hard bricked phone when the repair shop, or SE themselves, have the required hardware and knowledge about how to do it ... that would explain why the phone you got back still had the ROM you had flashed prior to the hard brick.
I never ruled this possibility out, I only questioned the service centers having the means to get it done.

caer_ayu said:
i think it was an ORI set ..because it has a Midland warranty seal ..i bought my x8 originally from the se center few months ago and it has Midland warranty seal also ..so it's definitely ORI set ..i hope they didn't charge for repair fees ..
Click to expand...
Click to collapse
good luck honey..

B.Jay said:
I don't see why it should be impossible to "revive" a hard bricked phone when the repair shop, or SE themselves, have the required hardware and knowledge about how to do it ... that would explain why the phone you got back still had the ROM you had flashed prior to the hard brick.
I never ruled this possibility out, I only questioned the service centers having the means to get it done.
Click to expand...
Click to collapse
wow ..now i'm more nervous and affraid to send it back to the vendor ..i'm affraid of they charging repair fees ..cause i don't have any money ..i'm just a student at some college ..

this my advise...
just play dummy to them..
just said u really don't know what really happened
and play seriously!
IF U WON"T REPAIR MY PHONE I'LL REPORT TO KHDNDHEP
(KementerianDalamNegeriDanHalEhwalPengguna)
i wish your luck..
---------- Post added at 01:08 PM ---------- Previous post was at 01:05 PM ----------
B.Jay said:
I don't see why it should be impossible to "revive" a hard bricked phone when the repair shop, or SE themselves, have the required hardware and knowledge about how to do it ... that would explain why the phone you got back still had the ROM you had flashed prior to the hard brick.
I never ruled this possibility out, I only questioned the service centers having the means to get it done.
Click to expand...
Click to collapse
Yeah and I tot maybe they got a rifbox or Jtag cable..
and maybe they found the tutorial about how to do it on youtube..

nelikp said:
this my advise...
just play dummy to them..
just said u really don't know what really happened
and play seriously!
IF U WON"T REPAIR MY PHONE I'LL REPORT TO KHDNDHEP
(KementerianDalamNegeriDanHalEhwalPengguna)
i wish your luck..
Click to expand...
Click to collapse
HAHA ..my cousin works at LHDN ...i was just affraid after it has successfuly revive the device ..they would find the superuser app just like ur case ..

[Q] Unlock bootloader wipes all data ?

Hello.
Im abit new to the forum but here goes.
Ive read tons of posts everywhere and there aint any exact answers anywhere to find.
In the past ive never known about the TA and DRM so happy as i am i just unlocked the bootloader on all the phones and still happy. The latest phone is the Xperia Z1. It has been abit buggy to say the least but im hoping software updates will cure this.
Anyway, i rooted my phone and unlocked the bootloader on the .681 firmware and now i am on .757 firmware. Using Doomlords kernel. I thought id check if i could backup my TA partition after unlocking the bootloader. And from what ive read its suppose to be wiped when you unlock the bootloader.
Well it was no problem backing up the TA partion. All files were there and it came out with no errors. So the question, how is this possible ?
I posted this same thing in General, sorry for that but i posted it here now so if a moderator finds this post in general then please delete it.
/Jonas740

If you Unlocked your Bootloader without Backup TA (DRM keys) first, then your DRM Keys are lost forever and you can Backup TA how much you want but there is no DRM Keys at all. The application to Backup TA do not give errors because you can backup partitions with or without DRM Keys, in the case you want switch between Locked and Unlocked Bootloader.
So long story short, you don't have DRM Keys, your warranty is lost forever, you cannot Update via OTA,PC Companion or SUS.

eclyptos said:
If you Unlocked your Bootloader without Backup TA (DRM keys) first, then your DRM Keys are lost forever and you can Backup TA how much you want but there is no DRM Keys at all. The application to Backup TA do not give errors because you can backup partitions with or without DRM Keys, in the case you want switch between Locked and Unlocked Bootloader.
So long story short, you don't have DRM Keys, your warranty is lost forever, you cannot Update via OTA,PC Companion or SUS.
Click to expand...
Click to collapse
The one time I had to use my warranty there was no problem with missing TA.
So there is hope for people without it
Sent from my C6903 using XDA Premium 4 mobile app

well.
HellRoot said:
The one time I had to use my warranty there was no problem with missing TA.
So there is hope for people without it
Sent from my C6903 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
dunno if the previous author saw what i wrote in my post but when i relocked my Xperia V using flashtool i could update with the pc companion or sony update or whats it called nowdays
And funny thing is, i actually have a case at Sony about this phone since i do have some issues with it but i think thats software related since ppl have been getting all sorts of errors from the KitKat firmwares. But i said how it was that i have unlocked bootloader and all that and she replied that my warranty was still valid and i could send it in for them to test it.
And i need to say this. Since sony posts an official way on their webpage, for ANYONE to read about how to unlock the bootloader and they also supply the code for unlocking it. Then i think it shouldnt affect the phone in any way or brake the warranty. (Sure it does say something about that, but all aint reading stuff like that). So if a developer wanted to unlock the phone. Why not have them contacting sony instead.
And surley, DRM keys (i just think sony shouldnt even bother having them) can be put back in if you let Sony do it. They put it there in the first place you know. And in the lovely electronic world we live in we all know that, if Sony can put thoose there, anyone could do it with the knowhow. But since the keys dont really mean anything, not that ive noticed you could really think about what use they actually do. And Sony knows that if ppl cant have the phone it was meant to be even with a unlocked bootloader, they will probably get some other phone or just whine hard enough so that Sony makes a software where everything works the same way with locked or unlocked. Camera stopped to work if you unlocked before 4.3 right ? What can you read about that like everywhere ? Loads of whining and Sony released a software that works just as good with locked or unlocked.
God damn this became a long post. So with this said im just saying. Why even bother in the first place having DRM keys if the rules dont apply anyway ? An everyday user doesent even need them either, he or she doesent even know what rooting or unlocking is anyway. And the ones that do know about it, also know about how to whine to get sony to fix the errors wich an unlock will produce

Jonas740 said:
dunno if the previous author saw what i wrote in my post but when i relocked my Xperia V using flashtool i could update with the pc companion or sony update or whats it called nowdays
And funny thing is, i actually have a case at Sony about this phone since i do have some issues with it but i think thats software related since ppl have been getting all sorts of errors from the KitKat firmwares. But i said how it was that i have unlocked bootloader and all that and she replied that my warranty was still valid and i could send it in for them to test it.
And i need to say this. Since sony posts an official way on their webpage, for ANYONE to read about how to unlock the bootloader and they also supply the code for unlocking it. Then i think it shouldnt affect the phone in any way or brake the warranty. (Sure it does say something about that, but all aint reading stuff like that). So if a developer wanted to unlock the phone. Why not have them contacting sony instead.
And surley, DRM keys (i just think sony shouldnt even bother having them) can be put back in if you let Sony do it. They put it there in the first place you know. And in the lovely electronic world we live in we all know that, if Sony can put thoose there, anyone could do it with the knowhow. But since the keys dont really mean anything, not that ive noticed you could really think about what use they actually do. And Sony knows that if ppl cant have the phone it was meant to be even with a unlocked bootloader, they will probably get some other phone or just whine hard enough so that Sony makes a software where everything works the same way with locked or unlocked. Camera stopped to work if you unlocked before 4.3 right ? What can you read about that like everywhere ? Loads of whining and Sony released a software that works just as good with locked or unlocked.
God damn this became a long post. So with this said im just saying. Why even bother in the first place having DRM keys if the rules dont apply anyway ? An everyday user doesent even need them either, he or she doesent even know what rooting or unlocking is anyway. And the ones that do know about it, also know about how to whine to get sony to fix the errors wich an unlock will produce
Click to expand...
Click to collapse
closed for being a duplicate.
use this link for other thread.
http://forum.xda-developers.com/showthread.php?t=2730169

[Q] stuck on locked bootloader question

I have a nexus 6 with locked bootloader with 5.1 unable the check OEM unlock bla bla...
So... I was 3 days ago at a mobile repair service and i gave my nexus 6 for a repair...
They cant repair my phone.. They tried with 3 different engineers but non of them can repair it...
motorola will not replace your phone i asked them because i not updated with OTA...flash over usb errors
Not covered by the warranty...
So does anyone succeeded with this solution? On anyway ?? Anyhow?? For money or for free? I dont care .... Just please reply something ...Any working method? Please answer i really need my device... Thanks and sorry for my english. i think in this thread this is the main issue

necroside007 said:
I have a nexus 6 with locked bootloader with 5.1 unable the check OEM unlock bla bla...
So... I was 3 days ago at a mobile repair service and i gave my nexus 6 for a repair...
They cant repair my phone.. They tried with 3 different engineers but non of them can repair it...
motorola will not replace your phone i asked them because i not updated with OTA...flash over usb errors
Not covered by the warranty...
So does anyone succeeded with this solution? On anyway ?? Anyhow?? For money or for free? I dont care .... Just please reply something ...Any working method? Please answer i really need my device... Thanks and sorry for my english. i think in this thread this is the main issue
Click to expand...
Click to collapse
Ooooh... That's tough. The only place I've heard of any kind of fix is in this thread:
http://forum.xda-developers.com/nexus-6/general/relock-bootloader-time-updating-to-5-1-t3053497
But, I don't think your situation applies... You're probably SOL.

There's no fix. You can try fastboot format cache and fastboot format userdata. If that doesn't work, there's no fix.

rootSU said:
There's no fix. You can try fastboot format cache and fastboot format userdata. If that doesn't work, there's no fix.
Click to expand...
Click to collapse
So i can throw away my phone?

necroside007 said:
So i can throw away my phone?
Click to expand...
Click to collapse
I wouldn't yet. Someone may eventually find a fix. But yes, you're going to need a new phone in the meantime.

Just a random thought; so what is covered by warranty? Say an internal connection was to get detached and the phone just won't power up, I think that would probably be something they may honor and replace the phone. I would not go back to the same place you tried to have it fixed, I would contact Motorola direct.
Again just a thought without thinking through all the scenarios nor with any thought of the morality of it.

jackpollard said:
Just a random thought; so what is covered by warranty? Say an internal connection was to get detached and the phone just won't power up, I think that would probably be something they may honor and replace the phone. I would not go back to the same place you tried to have it fixed, I would contact Motorola direct.
Again just a thought without thinking through all the scenarios nor with any thought of the morality of it.
Click to expand...
Click to collapse
This is a very good idea!

jackpollard said:
Just a random thought; so what is covered by warranty? Say an internal connection was to get detached and the phone just won't power up, I think that would probably be something they may honor and replace the phone. I would not go back to the same place you tried to have it fixed, I would contact Motorola direct.
Again just a thought without thinking through all the scenarios nor with any thought of the morality of it.
Click to expand...
Click to collapse
It does say in post 1 that he asked Motorola

I'm confused. What did u do to screw up your phone
sent from your moms phone

necroside007 said:
So i can throw away my phone?
Click to expand...
Click to collapse
Send it in for repair mate, off course its fixable in a servicecenter but not by us consumers.
---------- Post added at 03:53 PM ---------- Previous post was at 03:52 PM ----------
93fuelslut said:
I'm confused. What did u do to screw up your phone
sent from your moms phone
Click to expand...
Click to collapse
He probably locked the bootloader and had oem-unlock disabled in developer options, and now he can`t flash anything and the phone has no OS.

rootSU said:
It does say in post 1 that he asked Motorola
Click to expand...
Click to collapse
"Hello Ms. Motorola, yes my mother called earlier today, she thought my N6 was in some sort of loop or something, man you know how moms can be. It just won't turn on, I have no idea why, I just know it was working great 1 minute and now, nothing. OK, where do I send it? Thanks"
The crap part would be if someone finds a fix after the phone is damaged. But, before you do anything, make the call.
I see many many threads regarding how to get free tethering, so I don't feel this is too out of place. Again, everyone has to work out for themselves whats right for them.

gee2012 said:
Send it in for repair mate, off course its fixable in a servicecenter but not by us consumers.
---------- Post added at 03:53 PM ---------- Previous post was at 03:52 PM ----------
He probably locked the bootloader and had oem-unlock disabled in developer options, and now he can`t flash anything and the phone has no OS.
Click to expand...
Click to collapse
I'm thinking abt getting a n6. Can u elaborate a little more? Wouldn't "unlocked disabled" mean locked, so that phrase would mean the same as a locked bootloader which he did?
sent from your moms phone

93fuelslut said:
I'm thinking abt getting a n6. Can u elaborate a little more? Wouldn't "unlocked disabled" mean locked, so that phrase would mean the same as a locked bootloader which he did?
sent from your moms phone
Click to expand...
Click to collapse
Since 5.1, you need "enable OEM unlock" set in settings to unlock the bootloader. If it is not set, you cannot unlock the bootloader. It only stays set until you boot up.
So some people update then immediately lock the bootloader. Then their phone won't boot so they cannot set "enable OEM unlock" so they're screwed.

rootSU said:
Since 5.1, you need "enable OEM unlock" set in settings to unlock the bootloader. If it is not set, you cannot unlock the bootloader. It only stays set until you boot up.
So some people update then immediately lock the bootloader. Then their phone won't boot so they cannot set "enable OEM unlock" so they're screwed.
Click to expand...
Click to collapse
So when I get my n6, I just need a laptop to root, and not to unlock boot loader? Since I can just go into settings and check "enable unlock bootloader?
sent from your moms phone

93fuelslut said:
So when I get my n6, I just need a laptop to root, and not to unlock boot loader? Since I can just go into settings and check "enable unlock bootloader?
sent from your moms phone
Click to expand...
Click to collapse
You have to enable oem-unlock after every boot, it will not stick after a reboot.

93fuelslut said:
So when I get my n6, I just need a laptop to root, and not to unlock boot loader? Since I can just go into settings and check "enable unlock bootloader?
sent from your moms phone
Click to expand...
Click to collapse
No. The "enable OEM unlock" setting allows you to boot to the bootloader, connect to a pc and use the "fastboot oem unlock" command to unlock the bootloader.

gee2012 said:
You have to enable oem-unlock after every boot, it will not stick after a reboot.
Click to expand...
Click to collapse
Is this the same with aosp ROMs?
What happens if I forget to check it after a reboot? Like if my ROM does a random reboot and I don't know about it
sent from your moms phone

93fuelslut said:
Is this the same with aosp ROMs?
What happens if I forget to check it after a reboot? Like if my ROM does a random reboot and I don't know about it
sent from your moms phone
Click to expand...
Click to collapse
I think we're confusing the issue. It doesn't need to stay ticked. All it stops you doing is unlocking the bootloader. Once the bootloader is unlocked, its unlocked.
The only reason you'll need to tick it is if you relocked the bootloader and then wanted to unlock it again. But this is dangerous because if your ROM breaks and you're locked, you cannot then unlock.

jackpollard said:
Just a random thought; so what is covered by warranty? Say an internal connection was to get detached and the phone just won't power up, I think that would probably be something they may honor and replace the phone. I would not go back to the same place you tried to have it fixed, I would contact Motorola direct.
Again just a thought without thinking through all the scenarios nor with any thought of the morality of it.
Click to expand...
Click to collapse
With OTA should be fine.. If something goes wrong during ota thats covered by warranty, but i was impatient to wait for it, so i did for my self over USB thats not covered by warranty like when u **** up something with root permissions.. This method is not the original updating method. but its a bit confusing because this was an official google suggested method (https://developers.google.com/android/nexus/images) Terms of use, i accepted hurray!

"Send it in for repair mate, off course its fixable in a servicecenter but not by us consumers."
I did it and they cant repair it.. No way to access to that software part