Related
My carrier (C Spire) has found a problem with the device on their network that makes the device lose it's signal all the time. They claim it is a device problem anyway. I have unlocked the bootloader on the phone, but have not flashed any roms or made any other changes to the phone. Just the unlocked bootloader. They have said that since they know it is a problem with the device, they will let owners come in and exchange the phone for a Galaxy SIII free and clear. The only stipulation is it has to be in like new condition. My phone is perfect except for the unlocked bootloader. They'd probably never notice if it wasn't for that notification screen when the phone reboots that would tell them. I need to relock the bootloader to make that screen go away.
So, my question is, how do I do that? I've tried doing 'fastboot oem lock' but that doesn't work.
This is what I get when I try:
Code:
C:\Users\adear\AppData\Local\Android\android-sdk\platform-tools>fastboot oem lock
...
(bootloader) FAIL: Please run fastboot oem lock begin first!
OKAY [ 0.014s]
finished. total time: 0.016s
If I run the command as it suggests I get:
Code:
C:\Users\adear\AppData\Local\Android\android-sdk\platform-tools>fastboot oem lock begin
...
(bootloader) Ready to flash signed images
OKAY [ 0.246s]
finished. total time: 0.248s
I'm not sure what to do to get it to lock again.
Can anyone please help?
The problem is, you've unlocked it 'officially' from Moto... so it's registered in the database as unlocked.
You can try to change the boot logo, I haven't tried yet... Supposedly you can to get rid of that annoying screen.
Maybe you will just have to take it in and hope they don't reboot it. Kinda sucks that we have official unlocks now, because they can now easily track who has unlocked their phones and who hasn't :/
According to Moto, you can relock the bootloader, although the warranty remains voided. I know Moto knows about it, but I doubt very much that the carrier is going to go so far as to check it.
I just need to know why the 'fastboot oem lock' command didn't work. And what I can do to relock it.
adear11 said:
According to Moto, you can relock the bootloader, although the warranty remains voided. I know Moto knows about it, but I doubt very much that the carrier is going to go so far as to check it.
I just need to know why the 'fastboot oem lock' command didn't work. And what I can do to relock it.
Click to expand...
Click to collapse
Did you try using the same key to unlock to relock?
I've never bothered relocking...
arrrghhh said:
Did you try using the same key to unlock to relock?
I've never bothered relocking...
Click to expand...
Click to collapse
Is the key required to relock? I had not tried using it.
adear11 said:
Is the key required to relock? I had not tried using it.
Click to expand...
Click to collapse
I said I've never tried to relock.
It makes sense tho. Same process to relock as it was to unlock. Give it a shot, what do you have to lose.
arrrghhh said:
I said I've never tried to relock.
It makes sense tho. Same process to relock as it was to unlock. Give it a shot, what do you have to lose.
Click to expand...
Click to collapse
Just gave it a try, got the same result. "Fail: Please run fastboot oem lock begin first!"
adear11 said:
Just gave it a try, got the same result. "Fail: Please run fastboot oem lock begin first!"
Click to expand...
Click to collapse
You entered fastboot oem lock begin <key>?
arrrghhh said:
You entered fastboot oem lock begin <key>?
Click to expand...
Click to collapse
When I do 'fastboot oem lock begin [key]' I get "(bootloader) Ready to flash signed images".
From here, if I do 'fastboot oem lock' again, I get "Re-Lock Failure. See display." On the phone's display, I get:
Code:
No valid PIV block in SP for system
piv validation failed (system)
Re-lock failure
Hrm. I was poking around Moto's FAQ's and community site, and they talk about relocking - but not in detail unfortunately. They cryptically state that they will not release any stock recoveries at this time - so perhaps if you don't have the stock recovery, you can't relock...?
I would post up on Moto's forums or call their support... Not sure how much help they will be, but their website leaves much to be desired about the relocking process...
oh dear some anonymous person had pasted motorola's flashing script, perhaps you can use it to figure out how to fix your device
http://pastebin.com/Ca8wcGAv windows
http://pastebin.com/SnxrbdaW linux/mac
im just really glad i happened to be browsing around pastebin and found that in it.
shabbypenguin said:
oh dear some anonymous person had pasted motorola's flashing script, perhaps you can use it to figure out how to fix your device
http://pastebin.com/Ca8wcGAv windows
http://pastebin.com/SnxrbdaW linux/mac
im just really glad i happened to be browsing around pastebin and found that in it.
Click to expand...
Click to collapse
so, if one were interested in using this anonymous persons script, how would one proceed?
adear11 said:
so, if one were interested in using this anonymous persons script, how would one proceed?
Click to expand...
Click to collapse
i would imagine gathering all the files and putting them in the proper spots/folders would assemble a replica of this script. i was just mentioning you should look thru to see if there is anything taht helps you tho
In short, in order to relock the bootloader, you have to flash signed software in the process.
Ugh why did I try this lol.. Still having problems. I restarted my computer and that fixed the problem "waiting for device" now in cmd it will at least recognize the phone BUT, I get this trying to figure out some information
getvar:cid FAILED (command write failed (unknown error))
After entering to Moto G's fastboot and typing "fastboot getvar all" a lot of interesting informations about device are showed. There are two, that interest me:
Code:
(bootloader) unlocked: no
(bootloader) iswarrantyvoid: no
I know, that bootloader can be easily unlocked with quick "fastboot oem unlock". What's more, "fastboot oem lock" relocks bootloader like in Nexus devices. However, in Nexus world relocking and stock reflashing is equal with warranty restore - I've tested this on myself, when my Nexus 7's screen has cracked (it was little raised on one side) and speaker was buzzing - I've relocked, restored stock, wiped, sent it back and they have repaired it.
So my question is: does relocking bootloader and full stock reflash (like one from there) restore iswarrantyvoid variable back to no? Or at least does Motorola still pay attention to it after Moto X's liberal warranty declarations?
Konpon96 said:
After entering to Moto G's fastboot and typing "fastboot getvar all" a lot of interesting informations about device are showed. There are two, that interest me:
Code:
(bootloader) unlocked: no
(bootloader) iswarrantyvoid: no
I know, that bootloader can be easily unlocked with quick "fastboot oem unlock". What's more, "fastboot oem lock" relocks bootloader like in Nexus devices. However, in Nexus world relocking and stock reflashing is equal with warranty restore - I've tested this on myself, when my Nexus 7's screen has cracked (it was little raised on one side) and speaker was buzzing - I've relocked, restored stock, wiped, sent it back and they have repaired it.
So my question is: does relocking bootloader and full stock reflash (like one from there) restore iswarrantyvoid variable back to no? Or at least does Motorola still pay attention to it after Moto X's liberal warranty declarations?
Click to expand...
Click to collapse
Nope. Unlocking the devices triggers a hardware fuse that lets Motorola know that the device has been unlocked. Plus the UUID or whatever it is that is used to give you the bootloader unlock code is probably marked down as unlocked on Moto's side, as well, which voids your warranty.
We need a better 'crack' to go back iswarrantyvoid: no to yes without cross motorola side..
If you have a hardware fault then you are still covered under EU law so Motorola cannot use this bootloader unlock thing to get out of repairs.
Yesterday, I unlocked bootloader and rooted my Moto G. Today, after relocked boatloader and unroot (reinstalled the stock rom and reset factory), my phone come back to status
(bootloader) unlocked: no
(bootloader) iswarrantyvoid: no
Does that mean I will have my guarantee back again
flibblesan said:
If you have a hardware fault then you are still covered under EU law so Motorola cannot use this bootloader unlock thing to get out of repairs.
Click to expand...
Click to collapse
gunnroseclose said:
Yesterday, I unlocked bootloader and rooted my Moto G. Today, after relocked boatloader and unroot (reinstalled the stock rom and reset factory), my phone come back to status
(bootloader) unlocked: no
(bootloader) iswarrantyvoid: no
Does that mean I will have my guarantee back again
Click to expand...
Click to collapse
That sounds good! I'll wait for stable CWM/TWRP and CM 11 nightlies though (I assume official one are on way).
Thanks for sharing info!
gunnroseclose said:
Yesterday, I unlocked bootloader and rooted my Moto G. Today, after relocked boatloader and unroot (reinstalled the stock rom and reset factory), my phone come back to status
(bootloader) unlocked: no
(bootloader) iswarrantyvoid: no
Does that mean I will have my guarantee back again
Click to expand...
Click to collapse
Amazing :good:
Except when you get the unlock code from Motorola, they would remember your device
jonovw said:
Except when you get the unlock code from Motorola, they would remember your device
Click to expand...
Click to collapse
Here we talk about unlock bootloader brother. We no need a code to unlock bootloader and root device. Unlock code is to let device using many different networks, not lock to only 1 network.
Just in reply to the OP....
re the N7 "cracked screen" and "buzzing speaker"...
Just how did or could the unlocked boatloader cause these apparent manufacturing faults?
In what way would the unlocked bootloader allow Motorola a get out from any Warranty, even outside of the EU??
Manufacturers and retailers hide behind this myth of "your warranty is now void"....in circumstances where it is wholly BS.
Sent from my Moto G using TapaTalk
gunnroseclose said:
Here we talk about unlock bootloader brother. We no need a code to unlock bootloader and root device. Unlock code is to let device using many different networks, not lock to only 1 network.
Click to expand...
Click to collapse
Incorrect. Currently the only way to unlock the bootloader on the MotoG is to get an unlock code directly from Motorola's website.
Sent from my XT1034 using Tapatalk
jmoore4294 said:
Incorrect. Currently the only way to unlock the bootloader on the MotoG is to get an unlock code directly from Motorola's website.
Sent from my XT1034 using Tapatalk
Click to expand...
Click to collapse
we need a crack or something to lock the bootloader
but in Europe i think there is no problem for warranty at least u have some software issues
if is hardware i don t tink they say something or they don t repair ur device
gunnroseclose said:
Here we talk about unlock bootloader brother. We no need a code to unlock bootloader and root device. Unlock code is to let device using many different networks, not lock to only 1 network.
Click to expand...
Click to collapse
Wrong. We DO need an unlock code from Moto to unlock the bootloader. The Moto G comes without simlock by default (exception with PrePay phones) so that sort of unlocking is mostly rather pointless.
gunnroseclose said:
Yesterday, I unlocked bootloader and rooted my Moto G. Today, after relocked boatloader and unroot (reinstalled the stock rom and reset factory), my phone come back to status
(bootloader) unlocked: no
(bootloader) iswarrantyvoid: no
Does that mean I will have my guarantee back again
Click to expand...
Click to collapse
To unlock you used an unlock code from motorola or simply you used a oem unlock command ?
nupi said:
Wrong. We DO need an unlock code from Moto to unlock the bootloader. The Moto G comes without simlock by default (exception with PrePay phones) so that sort of unlocking is mostly rather pointless.
Click to expand...
Click to collapse
I have to pay 2 GBP to unlock my moto G which was locked to Tesco Network after pay the full price of phone without a contract. So how could it be pointless here.
danger2u said:
we need a crack or something to lock the bootloader
but in Europe i think there is no problem for warranty at least u have some software issues
if is hardware i don t tink they say something or they don t repair ur device
Click to expand...
Click to collapse
For lock there is not need a crack
yes but in fastboot says that the warranty is avoid after u unlock with motorola code.i ve flashed a original firmwarw,unroot,lock the bootloader and in fastboot says that i am out of warranty
Inviato dal mio XT1032 utilizzando Tapatalk
denzel09 said:
To unlock you used an unlock code from motorola or simply you used a oem unlock command ?
Click to expand...
Click to collapse
I followed the guide in modaco site to root the phone which was here. As follow that guide, I don't think that i got an unlock code from motorola to unlock bootloader
gunnroseclose said:
I followed the guide in modaco site to root the phone which was here. As follow that guide, I don't think that i got an unlock code from motorola to unlock bootloader
Click to expand...
Click to collapse
Yup, but you, pratically, what have done for unlock bootloader?
Write here all that you have done. Only for unlock bootloader, not root and rest. Thank you..
gunnroseclose said:
I followed the guide in modaco site to root the phone which was here. As follow that guide, I don't think that i got an unlock code from motorola to unlock bootloader
Click to expand...
Click to collapse
with that metode u don t receive the OTA updates
Wouldn't it be nice to have a keygen to unlock the bootloader without obtaining the key from motorola?
I have been investgating the relationship between the bootloader return code and unlock key and have discovered the following:
Note: For security I have replaced my IMEI and serial number, all other numbers are real. I'm not sure if anyone else has had a go at this but found nothing on XDA.
Code:
fastboot oem get_unlock_data
1A23457698214365#54413839303042
42443700585431303332000000#140A
858731D55F3B5DF78F0F6BB9EAE32A2
B8945#3D372B020F000000000000000
0000000
If I use the # character as a separator I get:
Code:
1A23457698214365
5441383930304242443700585431303332000000
140A858731D55F3B5DF78F0F6BB9EAE32A2B8945
3D372B020F0000000000000000000000
Line 1: With the exception of the 2nd character 'A' inserted, these characters are my IMEI number re-arranged a little.
The last 5 pairs of digits are swapped so an IMEI of 123456789123456 converts to 1A23457698214365
Line 2: Converting this line from hex to ascii gives me TA8900BBD7�XT1032���
This is serial and model number with a 00 byte as a spacer and 3 filler at the end.
Line 4: This is my bootloader UID (obtained from 'fastboot getvar uid' command)
Lines 1&2&4 I suspect have no relationship whatsoever with the unlock key.
Probably used to validate and log you on the motorola server when you request the unlock key, ultimately serving the purpose of voiding the warranty.
Line 3: Coincidence? Could this 20 byte string be relative to the 20 byte unlock key via some simple algorithm assuming lazy programming and/or limited space for code in the bootloader hardware? I couldnt tie this number to anything on my phone so I am guessing this code is derived from the unlock code during the 'fastboot oem get_unlock_data' command.
I tried online with varied IMEI and serials in the code and also using original values but with varied numbers in line 3 but could not get another unlock code. I don't think I can progress without more examples.
This was my unlock code: W4ZUEO2TZALOGJJWPRMO
Converted to hex: 57345A55454F32545A414C4F474A4A5750524D4F
Code:
So somehow 140A858731D55F3B5DF78F0F6BB9EAE32A2B8945
becomes 57345A55454F32545A414C4F474A4A5750524D4F
Could possibly involve the UID in the equation but I wouldn't bother if I were writing the bootloader and if so, then why have line 3 anyway?
I tried, a few sums but now I have a headache so I return to my life assisted by alcohol. Surely the solution has to be simple. Just thought I would post and see if anyone else could pick up from where I left off.
Have fun.......
I love the idea. I didn't unlock my phone because of the warranty but if we can find a way to unlock without allow Motorola to know it, it would be great...
Envoyé de mon Moto G en utilisant Tapatalk
Great thread. Hope in something of new
I can confirm that the first is the IMEI somehow swapped and an A added; the second one is the serial number with the model.
Certainly would help us Verizon Moto G users who currently are stuck with locked bootloaders :/
Takenover83 said:
Certainly would help us Verizon Moto G users who currently are stuck with locked bootloaders :/
Click to expand...
Click to collapse
I agree
Sent from my XT1028 using Tapatalk
Please, someone figure this out!
Help required!
What is needed is more examples. If people post the line 3 and unlock code in hex, then the problem can be solved. Unless you are the kid from mercury rising or rain man, the best that can be acheived with only one example is a headache. Trust me!
Those of you that have unlocked, please provide the required info. Maybe we need a new thread title to draw the atttention of those already unlocked.
"Request: Unlocked? Share your info here" etc..
Really nice that someone is trying to hack the bootloader protection. I intend to root my phone one day, but I am reluctant to use the official way because of warranty issues.
trifonius said:
Really nice that someone is trying to hack the bootloader protection. I intend to root my phone one day, but I am reluctant to use the official way because of warranty issues.
Click to expand...
Click to collapse
Same here. I was actually surprised to learn about this when I got this phone. I unlocked my Nexus 7 and assumed (my mistake) that I wouldn't have to get the manufacturer involved to unlock the bootloader.
Hope in some help from devs really
hey, i'm looking forward to this, actually i come from a device that had a locked bootloader but i could root it just with an exploit made with ics. maybe if someone finds an exploit in jellybean we will be able to root our phones but, that will be difficult
Hi.
Code:
My line 3: 5D0E47A39BBB9DA7B9632E8C19BD2873B018B7BA
My unlock code in hex: 4B415947324C4A424B454E414654573256544A45
I think of the possibility that all data used.
I am not an expert on algorithms, but the lines 1 2 3 and 4 are 64 bytes (whitout the #), groups of 8 or 16 bytes required for any algorithm.
The SHA1 with 64 bytes return 20 bytes hex the result.
Although I can be wrong, sorry for my bad english, i using g translator.
vientodearena said:
Although I can be wrong, sorry for my bad english, i using g translator.
Click to expand...
Click to collapse
Your English writing skills are better than many individuals from English speaking countries.
Thanks for your input. Hopefully, the people with the right skills can solved the problem.
My Unlock Code
I really couldn't stand to be without root, so here's my information:
Code:
fastboot oem get_unlock_data
3A55000805631104#54413931393030
364F4A00585431303334000000#FF1E
8DC44A01DC00C5CA53DB553418873A7
50D1C#5FABFE010F000000000000000
0000000
Code:
Unlock code:
BEXHELCKBBJZKZ5GYUWE
I hope this information can be of some use.
Aldo6 said:
I really couldn't stand to be without root, so here's my information:
Code:
fastboot oem get_unlock_data
3A55000805631104#54413931393030
364F4A00585431303334000000#FF1E
8DC44A01DC00C5CA53DB553418873A7
50D1C#5FABFE010F000000000000000
0000000
Code:
Unlock code:
BEXHELCKBBJZKZ5GYUWE
I hope this information can be of some use.
Click to expand...
Click to collapse
Converted to the following.
Line 3: 42455848454c434b42424a5a4b5a354759555745
Unlock Code: FF1E8DC44A01DC00C5CA53DB553418873A750D1C
Hope I did that right. Just trying to help.
Even if a keygen of sorts is created, won't the unlock still be flagged in the bootloader?
theoneofgod said:
Even if a keygen of sorts is created, won't the unlock still be flagged in the bootloader?
Click to expand...
Click to collapse
it would but you might be able to remove this flag and as long as motorola dont know that you have unlocked the bootloader all would be fine
Maybe it's need some help also from devs i think..
24/043/2014 14:43:35 - INFO - Device connected in fastboot mode
24/043/2014 14:43:39 - INFO - Unlocking phone using key 9DD79123E2A287C0
24/043/2014 14:43:39 - INFO - ...
24/043/2014 14:43:39 - INFO - FAILED (remote: Command did not succeed)
24/043/2014 14:43:39 - INFO - finished. total time: 0.021s
24/043/2014 14:43:42 - INFO - Unlocking phone using key 9DD79123E2A287C0
24/043/2014 14:43:42 - INFO - ...
24/043/2014 14:43:42 - INFO - FAILED (remote: Device is already rooted)
24/043/2014 14:43:42 - INFO - finished. total time: 0.004s
Did you unlock and relock? I remember for HTC if you did that you had to get a new token.
abhinav.tella said:
Did you unlock and relock? I remember for HTC if you did that you had to get a new token.
Click to expand...
Click to collapse
my one is Sony Z3 yes i have unlock and relock back...so have to take new Token back??
how to do it...???
David6632 said:
my one is Sony Z3 yes i have unlock and relock back...so have to take new Token back??
how to do it...???
Click to expand...
Click to collapse
I mentioned HTC because that happened to me with my One X and Butterfly, similar fastboot error, so I assumed so Sony is the same.
I believe you have to go to the Sony website and get another token:
http://developer.sonymobile.com/unlockbootloader/unlock-yourboot-loader/
New token will be the same. Give the forums a search you have to put the key in a text file in a folder in flash tool to re-unlock. There is a tutorial somewhere on this forum. Use search see if you can find it. If not I will post the link for you when I'm on my pc later.
nobby00900 said:
New token will be the same. Give the forums a search you have to put the key in a text file in a folder in flash tool to re-unlock. There is a tutorial somewhere on this forum. Use search see if you can find it. If not I will post the link for you when I'm on my pc later.
Click to expand...
Click to collapse
can you help us bro? i cannot unlock my bootloader on my xperia z2. i dont know why. and already get my key from sony but it wont work. same problem appear on above. please guide me to fix this problem sir. we really really need it. thanks
xerwudjohn said:
can you help us bro? i cannot unlock my bootloader on my xperia z2. i dont know why. and already get my key from sony but it wont work. same problem appear on above. please guide me to fix this problem sir. we really really need it. thanks
Click to expand...
Click to collapse
Look at the end of the first post.
http://forum.xda-developers.com/xperia-z/development/tutorial-relock-xperia-z-bootloader-t2191907
nobby00900 said:
Look at the end of the first post.
http://forum.xda-developers.com/xperia-z/development/tutorial-relock-xperia-z-bootloader-t2191907
Click to expand...
Click to collapse
I already did that bro. but same error. i am pretty sure that i installed correctly my drivers too. because my device will appear if i try to command in cmd "fastboot devices"
What error are you getting and you have unlocked the bootloader before and relocked it and now your trying to re-unlock it?
nobby00900 said:
What error are you getting and you have unlocked the bootloader before and relocked it and now your trying to re-unlock it?
Click to expand...
Click to collapse
I have the exact same problem surely someone must have a idea?
The OP has already unlocked his bootloader, relocked it and is attempting to unlock it again via flashtool.
There is no need to get a new code from Sony the old one will do.
Here are the instruction on how to correct Flashtools folder structure so that it will work
http://forum.xda-developers.com/showpost.php?p=51604352&postcount=22
For the rest of you, first of all ensure that you are unable to unlock the bootloader first by dialling
*#*#7378423#*#*
then going to service info and configuration. The last line will tell you if the bootloader is able to be unlocked or not, and if it is already unlocked.
Hi bro please help me
I m having d6653 Xperia z3 whn i bought i did rooting by mistake i updatd 5.0.2 then i relocked bootloader now it shows bootloader unkown please help me to unlock again i want to root .i m not able to flash the stock firmware phone just hangs up whn starting and restarts again with noice...
Peace be upon everybody, and good morning/evening
Last night I remained using my PC for a whopping 9 hours of work to figure out how to unlock my E6633 bootloader - and I finally figured it out.
The whole process was bumpy and the Sony Mobile Developers tutorial didn't wholly work out, but it had some vital info for the process. I had to unlock the boot loader using the Flashtool (thankfully), and I had some lack of luck at the beginning, which involved a journey to find the lost driver for my Z5, and to install it in the Device Manager (took some time). And then I took a "detour", since facing another roadblock, by creating a folder in C:\Users\<User>\.flashTool\registeredDevices named by my devices code (that appears when you enter adb devices in cmd), then inside of that folder I've created a .txt named ulcode.txt which contains the serial code provided by Sony Mobile to unlock your boot loader. And I've gotta tell you, it was all a pain in the bass.
More frustratingly, this whole procedure has resulted in zero luck with rooting the goddamn device (thanks Sony), and now I'm stuck with an unrooted bootloader-unlocked device . I'm sure this requires taking another detour. I've failed in every way I know to flash the modified stock kernel for some reason. I've tried cmd to flash the kernel and it comes back with FAILED <Remote: command not allowed>. I've also tried Flashtool to root it directly, and it turned out to be non-working as well.
Now, I'm not going to complain about this whole situation, even though I'm recalling how easy rooting my good old Galaxy S3 was. I'm now looking for a solution for that last tiny bit of the puzzle, and I'm sure there are other fellow members who are facing the same hitch.
Cheers .
Is oem unlocking ticked? It sounds like your bootloader is still locked.
All I did to unlock mine was type the command Sony provided with the unlock code and unlocked it with fastboot, took maybe 10 seconds?
Sent from my E6653 using Tapatalk
After unlocking the bootloader does the phone reset to factory settings? Just to make sure that you succeed unlocking.
Go to developer options and check if oem unlock is ticked
This difference in rooting experience that the OP had with the GS3 and now with the Z5 raises a question in my mind. Is the modding community more focused on popular devices? This is often a deal breaker for some people. If the 6P or the GS6 gets more ROMs and mods and faster root exploits than the Z5, then I myself would prefer those devices over the Z5.
bishshoy said:
This difference in rooting experience that the OP had with the GS3 and now with the Z5 raises a question in my mind. Is the modding community more focused on popular devices? This is often a deal breaker for some people. If the 6P or the GS6 gets more ROMs and mods and faster root exploits than the Z5, then I myself would prefer those devices over the Z5.
Click to expand...
Click to collapse
Then buy a Samsung...
Sent from my E6653 using XDA Free mobile app
Everything is explained here
celderic said:
Is oem unlocking ticked? It sounds like your bootloader is still locked.
All I did to unlock mine was type the command Sony provided with the unlock code and unlocked it with fastboot, took maybe 10 seconds?
Sent from my E6653 using Tapatalk
Click to expand...
Click to collapse
It is indeed ticked and I'm positive that the bootloader is unlocked.
Yes I tried the easy way of doing it with cmd but it just didn't work out. Kept returning with FAILED <Remote: command did not succeed> and that's why I resorted to the other way of creating those files in the flashtool folders (as explained in the OP).
gm007 said:
After unlocking the bootloader does the phone reset to factory settings? Just to make sure that you succeed unlocking.
Click to expand...
Click to collapse
It didn't reset to factory settings. Does that mean it wan't unlocked?
dylanel98 said:
Go to developer options and check if oem unlock is ticked
Click to expand...
Click to collapse
It is ticked along with debugging just in case.
bishshoy said:
This difference in rooting experience that the OP had with the GS3 and now with the Z5 raises a question in my mind. Is the modding community more focused on popular devices? This is often a deal breaker for some people. If the 6P or the GS6 gets more ROMs and mods and faster root exploits than the Z5, then I myself would prefer those devices over the Z5.
Click to expand...
Click to collapse
I think maybe the developers at Sony are narrowing down the possibility of modifying their devices.
Funkmasterchilla said:
Everything is explained here
Click to expand...
Click to collapse
Checking it out...
Funkmasterchilla said:
Everything is explained here
Click to expand...
Click to collapse
I went through the steps in that thread and without any problems until the part with
Code:
fastboot –i 0x0fce oem unlock 0xXXXXXXXXXXXXXXXX
I have checked the recognition of my device by entering fastboot devices and it recognized my device successfully.
The X's above being the code provided by Sony, the cmd window (of minimal adb and fastboot) returned with
Code:
FAILED (remote: Command did not succeed)
Although, the step prior to this one which is to unlock the bootloader using Flashtool has succeeded.
It's really mind-boggling...
As far as i know that unlocking bootloader will reset ur phone to factory settings.
And not sure but i think you need to remove a number from the code sony sent to you.
Take a look here: http://forum.xda-developers.com/xperia-z5/general/guide-sony-xperia-z5-unlock-root-tweaks-t3298224
Bootloader unlock is under # STEP 1 - GENERAL GUIDE
I hope this will help
Also check if you're bootloader is allowed to be unlocked.
Type in dialer *#*#7378423#*#* (*#*#SERVICE#*#*)
Service info > configuration > rooting status.
If it says bootloader unlock allowed :YES you can unlock it, if it says NO u can't unlock it.
If it says rooted or unlocked, you've successfully unlocked it already.
UM, I have E6633 and everything works fine... I used flashtool to unlock bootloader.
langeveld024 said:
Type in dialer *#*#7378423#*#* (*#*#SERVICE#*#*)
Service info > configuration > rooting status.
If it says bootloader unlock allowed :YES you can unlock it, if it says NO u can't unlock it.
If it says rooted or unlocked, you've successfully unlocked it already.
Click to expand...
Click to collapse
Mine says no to unlock, does that mean it can never be unlocked? If so, why would that be?
Sent from my E6653 using Tapatalk
mrbubba999 said:
Mine says no to unlock, does that mean it can never be unlocked? If so, why would that be?
Sent from my E6653 using Tapatalk
Click to expand...
Click to collapse
Yes you cannot unlock bootloader.
I think you have branded phone,locked by carrier.
mrbubba999 said:
Mine says no to unlock, does that mean it can never be unlocked? If so, why would that be?
Sent from my E6653 using Tapatalk
Click to expand...
Click to collapse
Carrier lock, unfortunately as far as I know since the very first Z series impossible to unlock unless u contact the carrier and they unlock it for u.
Keep in mind that they might charge u for that.
langeveld024 said:
Carrier lock, unfortunately as far as I know since the very first Z series impossible to unlock unless u contact the carrier and they unlock it for u.
Keep in mind that they might charge u for that.
Click to expand...
Click to collapse
That sucks, means my foray into Sony phone ownership might be short lived! Perhaps I should have stuck with a nexus and got the upgrade and a 6P
Sent from my E6653 using Tapatalk
mrbubba999 said:
That sucks, means my foray into Sony phone ownership might be short lived! Perhaps I should have stuck with a nexus and got the upgrade and a 6P
Sent from my E6653 using Tapatalk
Click to expand...
Click to collapse
Yeah or next time only buy carrier free Sony
Thank you all, guys! I tried everything you told me but guess what! Nothing worked unfortunately...