Ok we have gain unlock bootloader now and that is wonderful for future playing , but how can we go back to locked bootloader (or trick), so we take again the official update from SEUS (I know about the Bi4ary's flash tool, but here in XDA we want all the options available ). After the unlocking when you try to update your phone you take an error massage: "The software on this phone has been altered or modified" and after that it doesn't let you (SEUS) to update your phone!!
Let's try to find a way!!!!
try fastboot.exe oem lock and post result.
lollylost100 said:
try fastboot.exe oem lock and post result.
Click to expand...
Click to collapse
Code:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Program Files (x86)\android-sdk-windows\platform-tools>fastboot.exe oem lock
...
FAILED (remote: oem unlock 0xFFFFFFFFFFFFFFFF)
finished. total time: 0.001s
C:\Program Files (x86)\android-sdk-windows\platform-tools>fastboot.exe -i 0x0fce
oem lock 0xMYKEY
...
FAILED (remote: oem unlock 0xFFFFFFFFFFFFFFFF)
finished. total time: 0.001s
C:\Program Files (x86)\android-sdk-windows\platform-tools>
I try the commands:
fastboot.exe oem lock
and
fastboot.exe -i 0x0fce oem lock 0xMY_UNLOCK_KEY
Then it's a one way procedure like on Nexus One .
lollylost100 said:
Then it's a one way procedure like on Nexus One .
Click to expand...
Click to collapse
That's mean no way to get back official update?
SEUS has the ability to check for unlocked/locked bootloader. OTA Update won't work either because DRM keys have been wiped in the unlocking process. You can still get updates but these will have to be done through FlashTool.
You'd have though that SE would have mentioned this in the blurb!!.. swines. I'd like to relock the BL to get the SEUS updates when they come out.. although I can live with using flashtool I guess.
Completely going off topic here but I just watched the vid on ur signature iceman and it slayed me.
I'm going to start a new thread in the wrong section just to express my opinion about it!!
Back on topic. I think SE should have defiantly let us know that there was no way back! Honestly though, once the custom ROM's start appearing, are you going to be that bothered?
im_iceman said:
You'd have though that SE would have mentioned this in the blurb!!.. swines. I'd like to relock the BL to get the SEUS updates when they come out.. although I can live with using flashtool I guess.
Click to expand...
Click to collapse
Hmmmm thats interesting.
Does anyone have a Flash Tool UK Image, so i can use it as a backup?
EDIT: Found them.
Ill upload shortly.
I asked SE about this and they said...
Yeah Alan, that's right, as long as you use the Sony Ericsson stock software, it is only if you use custom software from third party that you won't be offered any updates - Johnny.
Click to expand...
Click to collapse
Check this out. Might be useful, might not. I just see lock the bootloader.
Sent from my LT15i using XDA Premium App
going to find an alternative to locked the bootloader again. Reflashing the stock firmware doesn't help
SE reckon you don't need to re-lock it - as long as you have stock FW and stock bootloader then you should get the updates via SEUS.
I take it that once im unlocked there is no way back if the phone has a problem and needs to be sent off for repair
Sent from my LT15i using Tapatalk
Related
When I try to acces recoveryPLAY or try to unlock the bootloader I get the "failed, phone must bee rooted" I just flashed everything to 2.3.3 before I was rooted and haad a unlocked bootloader, but relocked it to update OTA, now none of the fastboot stuff is working. Anyone have any ideas? I would really really appreciate any help.
You have to unlock the bootloader again. I had the same problem.
Sent from my R800x using XDA App
IfI could unlock the bootloader I would. The unlock code is not working. Its the same code I used over a month ago to unlock my bootloader before I relocked it to update.
Whether I am trying to unlock the bootloader or fastboot recoveryPLAY both come back with "failed, phone must be rooted".
Probably a silly question, but, do you have the unlock command line correct, and have you verified if fastboot is working properly? Try 'fastboot -i 0x0fce getvar version'. It should return a version number if fastboot is working properly.
Sent from my R800x using XDA App
Yes, I have checked everything 4 times and the fastboot getvar is showing the phone is connected. Even using flashtool to flash back to 2.3.2 then trying to use the fastboot commands gives the same results.
Is there a 2.3.2 .FTF files that has root embedded that I can try and flash and see if that works?
What does it say when you try to unlock the bootloader?
Sent from my R800x using XDA App
I have already listed what it says. "Failed, phone must be rooted".
This repsonse is for both commands to either unlock the bootloader or boot into recoveryPLAY.img
And yes my bootloader unlock code is correct when i type it in, and when I used it before the OTA to unlock my bootloader. So the code is the correct code.
That's very strange. If all your command lines are correct, and you are inputting the correct code, it should be working. I only got that message when trying to boot a recovery image without unlocking. Sorry, I don't know what to tell you now.
Sent from my R800x using XDA App
thats okay. I just really hate having no root access and a locked bootloader. I would at least like to have root so I can use TB. I appreciate your attempts to assist me. Thank you
Anyone have any ideas for a solution to this or why this is happening? Everyone else seems to be able to reroot and unlock the way they have always done, except for me nothing is working.....
Bootloader unlock request spits out this:
<bootloader> Unlock phone requested
FAILED <remote: oem unlock failed!>
finished. total tim: 0.003s
Is there a FTF file that has root embedded into it I can use with flashtool? Fastboot is not accepting my code lines for either recoveryPLAY or my attempts to unlock the bootloader.
bump.......
Just realized about 10 minutes ago the unlock code IWas using was for my old xperia play. I found the code that pertained to my current phone and it still gives me the same results.....damn
Can you try wontanserver to go back to 2.3.2?
never heard of it, is it free? Looks like its a website or something
wow.... I am so unintelligent sometimes. I have been fighting with getting this phones bootlaoder to unlock and then it came to me, I am not typing it in caps. So I did and BAM!!!!!! bootloader unlocked. Guess since the 2 months I last unlocked it my brain got soggy like a bowl of runny oatmeal
Ya its free and imho the easiest way to flash any stock firmware from every region. The wontanserver program has it all.
K, I will save that for later. Thank you.
IS your phone R8OOX? ask alejandrox -whatever his name is for you to unlock it
edit: glad you fixxed it
I finally got my bootloader unlocked last night. I was misinterpreting a "0" (zero) as a "O" as in Oh. Got my phone updated i 2.3.3 with root and bootloader unlocked. I would like to thank everyone for their help. Guess I should get me eyes checked.
This process has been done with the HTC International version available in Australia.
Im sure everyone would appreciate follow up from others to confirm which versions of the phone this process works with.
The process below assumes a small amount of familiarity with HTC unlock process AND WILL WIPE THE DATA FROM YOUR PHONE!
The process is basically the same as ever with a few variations
Install adb
Go to http://www.htcdev.com/bootloader and sign up, click unlock bootloader
In the device selection drop-down select "any other supported device"
Boot into "Download Mode" - Which is the equivalent of fastboot. (shutdown your phone, hold power+volume down until you boot into this mode). This is the mode with the black background and red text
Connect phone to PC, and issue "fastboot oem get_identifier_token"
Copy the code into the returned by adb into space on HTCs website
Get the email, download the attachment and issue "fastboot flash unlocktoken Unlock_code.bin"
I'll wait for a S-OFF method
You won't need htcdev, your phone won't be registered over there.
Always good to know we can root the new flagship
Super-Veloce said:
I'll wait for a S-OFF method
You won't need htcdev, your phone won't be registered over there.
Click to expand...
Click to collapse
On Lollipop there's no such shortcut.. your device must be rooted before proceeding to S-OFF..
jauhien said:
On Lollipop there's no such shortcut.. your device must be rooted before proceeding to S-OFF..
Click to expand...
Click to collapse
Really?? Damn..
I keep getting:
Code:
C:\WINDOWS\system32>fastboot oem get_identifier_token
...
FAILED (remote: unknown command)
finished. total time: 0.007s
Tried it on 2 different systems :S
What mode was your phone in? Were you in download mode? Or in the bootloader?
daveh86 said:
What mode was your phone in? Were you in download mode? Or in the bootloader?
Click to expand...
Click to collapse
Ahhh...... I thought i was in download, but was in bootloader (still accept fastboot commands)
HTC Download mode says... "hTC download mode" up the top and is a black screen if any one else comes across this...
EndoSurf said:
Ahhh...... I thought i was in download, but was in bootloader (still accept fastboot commands)
HTC Download mode says... "hTC download mode" up the top and is a black screen if any one else comes across this...
Click to expand...
Click to collapse
Thanks, I've added a note in my comment that mentions that download mode is the one with black background and red text.
And how i will make it S-Off?
Richi207 said:
And how i will make it S-Off?
Click to expand...
Click to collapse
By being patient... the device is not even available in most regions yet, give developers a little time would you.
For Verizon test M9's, can't even pull identifier token. Fastboot command yields "FAILED (remote: unknown command)," which is interesting because I used fastboot to successfully flash TWRP then root.
jauhien said:
On Lollipop there's no such shortcut.. your device must be rooted before proceeding to S-OFF..
Click to expand...
Click to collapse
Is there a way to s-off? Ive seen some have already done it, but how?
Test devices come S-OFF.
hgoldner said:
Test devices come S-OFF.
Click to expand...
Click to collapse
Or you can give the Phone to a shop / repair centre to s-off it
In Germany you can do it at:
http://www.gsm-europe.de/epages/635...3/Products/htc_soff/SubProducts/htc_soff-0001
Its a shop in Berlin they do s-off and supercid
And they can do it on the Onde M9
Only bad thing they cant Unlock bootloader it without HTC Dev.
So You get your phone back with S-Off and with Super Cid but Boodloader is Locked and you must Unlock it via HTC dev
because for Unlock via Fastboot you need root on Android 5
I remember when I first unlocked the bootloader on the M7, I lost a couple stock apps. If anyone's tried the official HTC-DEV unlock method yet, are all apps intact?
Prasad said:
I remember when I first unlocked the bootloader on the M7, I lost a couple stock apps. If anyone's tried the official HTC-DEV unlock method yet, are all apps intact?
Click to expand...
Click to collapse
Didn't notice any loss after unlocking M9 ..
jauhien said:
Didn't notice any loss after unlocking M9 ..
Click to expand...
Click to collapse
Thank you! Now I can confidently proceed when the device arrives in a couple hours.
Richi207 said:
And how i will make it S-Off?
Click to expand...
Click to collapse
you're gonna have to wait a while for that
Been a long time since I unlocked a bootloader. But I don't lose any OTA functionality do I?
Sent from my HTC One M9 using XDA Free mobile app
Hey there.
So I tried to use the Nexus Root Toolkit to sideload the OTA, but now when I try to boot my phone it just shows the white google screen and doesn't do anything. I can use ADB and fastboot and get into the bootloader but I can't flash the factory image because I never checked the "Allow OEM Unlock" tick since I didn't plan on unlocking the bootloader. Can anyone help me out here?
Durvid said:
Hey there.
So I tried to use the Nexus Root Toolkit to sideload the OTA, but now when I try to boot my phone it just shows the white google screen and doesn't do anything. I can use ADB and fastboot and get into the bootloader but I can't flash the factory image because I never checked the "Allow OEM Unlock" tick since I didn't plan on unlocking the bootloader. Can anyone help me out here?
Click to expand...
Click to collapse
This is exactly why you should never mess with updates or flashing anything with a locked bootloader. If a factory reset doesn't fix it you're likely out of luck.
if your bootloader is locked still I can't see how flashing an OTA would effect this.
Have you tried to flash just the original bootloader from the android version on your device ( not the version you wish to update to )
Fastboot flash bootloader bootloader.img
DON'T USE A TOOL KIT ! UNLESS YOU KNOW WHAT YOU ARE DOING ! There where clear instructions on how to flash OTA's on this site and likely in the toolkit.
Unfortunately this is a case of NOT reading before doing things, I have yet to see anyone recover from this.
Best of luck tho, but it might be a lesson learned the hardway a.k.a RMA
hutzdani said:
if your bootloader is locked still I can't see how flashing an OTA would effect this.
Have you tried to flash just the original bootloader from the android version on your device ( not the version you wish to update to )
Fastboot flash bootloader bootloader.img
DON'T USE A TOOL KIT ! UNLESS YOU KNOW WHAT YOU ARE DOING ! There where clear instructions on how to flash OTA's on this site and likely in the toolkit.
Unfortunately this is a case of NOT reading before doing things, I have yet to see anyone recover from this.
Best of luck tho, but it might be a lesson learned the hardway a.k.a RMA
Click to expand...
Click to collapse
I'll attempt this. Weirdly enough when I look at device info in adb it shows it as being on the newest version. But Yeah I'll attempt to flash what I was on before.
Yeah, I mean I've done this before with no issues on my Nexus 6 and there were no issues but that was unlocked when I got it. I just thought you didn't have to unlock the bootloader to sideload OTA's? I may be wrong.
hutzdani said:
if your bootloader is locked still I can't see how flashing an OTA would effect this.
Have you tried to flash just the original bootloader from the android version on your device ( not the version you wish to update to )
Fastboot flash bootloader bootloader.img
Click to expand...
Click to collapse
Yeah like I thought, "Device is locked. Cannot Flash Images"
I wish I had known they added that "Allow OEM Unlock" Switch in Lollipop. Would have solved my problem if I had that toggled.
Durvid said:
Yeah like I thought, "Device is locked. Cannot Flash Images"
I wish I had known they added that "Allow OEM Unlock" Switch in Lollipop. Would have solved my problem if I had that toggled.
Click to expand...
Click to collapse
You just said you had a nexus 6 unlocked, how did you not know the switch existed?
hutzdani said:
if your bootloader is locked still I can't see how flashing an OTA would effect this.
Have you tried to flash just the original bootloader from the android version on your device ( not the version you wish to update to )
Fastboot flash bootloader bootloader.img
DON'T USE A TOOL KIT ! UNLESS YOU KNOW WHAT YOU ARE DOING ! There where clear instructions on how to flash OTA's on this site and likely in the toolkit.
Unfortunately this is a case of NOT reading before doing things, I have yet to see anyone recover from this.
Best of luck tho, but it might be a lesson learned the hardway a.k.a RMA
Click to expand...
Click to collapse
akellar said:
You just said you had a nexus 6 unlocked, how did you not know the switch existed?
Click to expand...
Click to collapse
I bought it used on /r/hardwareswap and whoever I got it from had already unlocked it.
I know someone advised you to try to flash a bootloader, but it isn't going to work of your bootloader is locked. What build were you on and which OTA zip did you try to flash?
Heisenberg said:
I know someone advised you to try to flash a bootloader, but it isn't going to work of your bootloader is locked. What build were you on and which OTA zip did you try to flash?
Click to expand...
Click to collapse
I started on 6.0 MDB08L and was trying to flash 6.1 MMB29M
Durvid said:
I started on 6.0 MDB08L and was trying to flash 6.1 MMB29M
Click to expand...
Click to collapse
OK, but I need the name of the zip please.
Heisenberg said:
OK, but I need the name of the zip please.
Click to expand...
Click to collapse
Sorry, it's
533df5ddfa4297997634a8553f0122be5cca4c09.signed-angler-MMB29M-from-MDB08L.zip.
Grabbed it from here: https://www.reddit.com/r/Nexus6P/comments/3w6qzd/easy_how_to_sideload_ota_601/
Durvid said:
Sorry, it's
533df5ddfa4297997634a8553f0122be5cca4c09.signed-angler-MMB29M-from-MDB08L.zip.
Grabbed it from here: https://www.reddit.com/r/Nexus6P/comments/3w6qzd/easy_how_to_sideload_ota_601/
Click to expand...
Click to collapse
OK, just needed to make sure you had the right one. What have you done to troubleshoot so far?
Heisenberg said:
OK, just needed to make sure you had the right one. What have you done to troubleshoot so far?
Click to expand...
Click to collapse
I've tied to flash stock, but can't do that due to the bootloader being locked, tried to just hard reset but it just does the same thing where it gets stuck on the Google logo. I checked the manufacture info in the toolkit and everything is clean. Tried to flash the old bootloader but like you said I can't flash since I'm locked. Not really sure what else to do :/
Durvid said:
I've tied to flash stock, but can't do that due to the bootloader being locked, tried to just hard reset but it just does the same thing where it gets stuck on the Google logo. I checked the manufacture info in the toolkit and everything is clean. Tried to flash the old bootloader but like you said I can't flash since I'm locked. Not really sure what else to do :/
Click to expand...
Click to collapse
Honestly, I think you're pretty much screwed unfortunately. You could talk to Google support and see if they'll RMA the phone.
Heisenberg said:
Honestly, I think you're pretty much screwed unfortunately. You could talk to Google support and see if they'll RMA the phone.
Click to expand...
Click to collapse
Yeah I think they would do it since I technically didn't void any warrantys or anything. I appreciate the help. What do I need to make sure to do if I do this again in the future? Definitely "Allow OEM Unlock", and do I have to unlock the bootloader? I was under the impression that you didn't have to to flash an OTA.
Durvid said:
Yeah I think they would do it since I technically didn't void any warrantys or anything. I appreciate the help. What do I need to make sure to do if I do this again in the future? Definitely "Allow OEM Unlock", and do I have to unlock the bootloader? I was under the impression that you didn't have to to flash an OTA.
Click to expand...
Click to collapse
Definitely unlock the bootloader, it isn't needed to flash an update via the stock recovery, but it is needed to get out of sticky situations like this. If your bootloader was unlocked now you'd be up and running in ten minutes.
Durvid said:
Sorry, it's
533df5ddfa4297997634a8553f0122be5cca4c09.signed-angler-MMB29M-from-MDB08L.zip.
Grabbed it from here: https://www.reddit.com/r/Nexus6P/comments/3w6qzd/easy_how_to_sideload_ota_601/
Click to expand...
Click to collapse
Hilarious that the top comment is mine telling you why doing this is a bad idea
Heisenberg said:
Definitely unlock the bootloader, it isn't needed to flash an update via the stock recovery, but it is needed to get out of sticky situations like this. If your bootloader was unlocked now you'd be up and running in ten minutes.
Click to expand...
Click to collapse
Yeah, I'll probably wait for the update over the air for a while and maybe if I feel reallly eager I'll just make sure I unlock and such. Annoying that you can't unlock via fastboot anymore without that toggle. I get that Google is trying to make Android super secure but It's not too useful for folks like us. Sure it's bricked a lot of devices.
akellar said:
Hilarious that the top comment is mine telling you why doing this is a bad idea
Click to expand...
Click to collapse
I've done it before with other devices. I wouldn't say it's inherently bad. It's just that there was one toggle that I wasn't aware of that caused the issue. You live and you learn.
THIS IS NOT MY IDEA !
I found this in a N9 thread and it worked according to the user with the issue, apply this with the correct t factory image ( do it with the version you have on your device not the one you tried to update to ! )
This might not work but its worth a try ! Before doing this read about ADB and Fastboot !!!!!!!!!!!!!!!! Try and understand the basics and know what the commands are doing to help backtrack e.C.t
If it does work - go to settings and allow OEM Unlock and USB debug !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! Then go read from reputable sources how to flash images manually via adb !!!!!!!!!!!!!!!!!!!!!!!
I'd follow vomers guides.
Had this problem with another device cool thing to remeber is that on locked devices the only thing that is different is that there is a signature before the MAGIC header so the solution is to pull the android stock images from https://developers.google.com/android/nexus/images. Once done extract the images in both the zip and the tar that is inside the zip. You will see recovery.img inside the tar. One thing about the boot process of TWRP is that it enables adb in preboot meaning while in the boot loop you should have access to adb. With access to adb all you need to do is dd the images over the corresponding partitions: i.e.
PLEASE NOTE NOT FOR THE FEINT OF HEART. I AM NOT RESPONSIBLE FOR YOU BRICKING YOUR DEVICE.
Quote:
adb push recovery.img recovery.img
adb shell dd if=recovery.img of=/dev/block/<recoverymmcblock>
I dont know if the default recovery has adb push update so id probably recommend doing this on every partition thats inside the tar, i.e. system, boot.
I have a moto x pure pre release phone. It was a model that was issued before the initial release of moto x pure. I have tried to get the unlock code with no success. I get a failed error message. I have tried this on windows 10 and Linux. I can successfully recognize the device on fastboot and adb. However, no unlock code. I am now thinking somehow the phone is locked and unable to get this code. I'm thinking about selling this phone and getting a new one. I would like any feedback if you think I will have the same issue or if the pre release may be locked.
Sent from my Nexus 6 using XDA Free mobile app
I had no issue unlocking a phone bought directly from Motorola on November.
jcasares said:
I had no issue unlocking a phone bought directly from Motorola on November.
Click to expand...
Click to collapse
Was it a pre-release version? My guess is no.
Did you go into settings and flip the unlock switch? Hard to help when you don't list the steps you took to unlock.
lafester said:
Did you go into settings and flip the unlock switch? Hard to help when you don't list the steps you took to unlock.
Click to expand...
Click to collapse
I installed Android sdk and Motorola driver. Then enabled USB debugging and checked OEM unlock. Then booted into bootloader. Then typed fastboot OEM get_unlock_data. Then it fails to get information.
brholt6 said:
Was it a pre-release version? My guess is no.
Click to expand...
Click to collapse
It is special phone specifically designed to show off the phone before launch.
droc83 said:
I installed Android sdk and Motorola driver. Then enabled USB debugging and checked OEM unlock. Then booted into bootloader. Then typed fastboot OEM get_unlock_data. Then it fails to get information.
Click to expand...
Click to collapse
Eng boot loader by chance ? Did you try fast oem unlock?
Sent from my SM-T810 using Tapatalk
I was simply answering his doubt about purchasing a new one and facing the issue of unlocking the bootloader again.
He won't have this issue anymore with a unit purchased from Motorola.
dottat said:
Eng boot loader by chance ? Did you try fast oem unlock?
Sent from my SM-T810 using Tapatalk
Click to expand...
Click to collapse
What does fast oem unlock do? Do you mean fastboot oem unlock? I didn't try either one.
droc83 said:
What does fast oem unlock do? Do you mean fastboot oem unlock? I didn't try either one.
Click to expand...
Click to collapse
Yes dang keyboard.
Sent from my XT1575 using Tapatalk
droc83 said:
It is special phone specifically designed to show off the phone before launch.
Click to expand...
Click to collapse
Ya, I wasn't asking what a pre-release version was. I think you misread.
dottat said:
Yes dang keyboard.
Sent from my XT1575 using Tapatalk
Click to expand...
Click to collapse
I tried fastboot oem unlock. It is asking for a code which I can't get.
Did you go to moto and request unlock?
The code you need you can get it on the Motorola support site (I believe this).
jcasares said:
The code you need you can get it on the Motorola support site (I believe this).
Click to expand...
Click to collapse
I need the code from my phone to do this. That is where my trouble is. Everytime I enter fastboot oem get_unlock_data it gives me this.
C:\SDK\platform-tools>fastboot oem get_unlock_data
...
(bootloader) Failed to get unlock data, please try again!
FAILED (remote failure)
finished. total time: 0.016s
lafester said:
Did you go to moto and request unlock?
Click to expand...
Click to collapse
They won't help with unlocking my bootloader. They just refer to a website on how to do it. I have told them I believe something is wrong with the phone but they don't want to help with this. I think I am going to just give up and sell the phone and cut my losses.
So why dont you actually follow the process for Bootloader unlock on Moto's Site?
droc83 said:
I need the code from my phone to do this. That is where my trouble is. Everytime I enter fastboot oem get_unlock_data it gives me this.
C:\SDK\platform-tools>fastboot oem get_unlock_data
...
(bootloader) Failed to get unlock data, please try again!
FAILED (remote failure)
finished. total time: 0.016s
Click to expand...
Click to collapse
Did you try flashing the stock factory images in fastboot, then rebooting and trying the process once more? You could have an odd boot loader version or something.
Sent from my XT1575 using Tapatalk
dottat said:
Did you try flashing the stock factory images in fastboot, then rebooting and trying the process once more? You could have an odd boot loader version or something.
Sent from my XT1575 using Tapatalk
Click to expand...
Click to collapse
Do you have a link on how to do this?
fkofilee said:
So why dont you actually follow the process for Bootloader unlock on Moto's Site?
Click to expand...
Click to collapse
I did follow these steps. However, I have to send them a code from my phone which I cannot get.
Guys please help I can't unlock the boot loader(ze550kl) for the following model I wanted to install cm. Thank you
ASUSSKU WW
BOARD msm8916
BOOTLOADER unknown
BRAND asus
CHARACTERISTICS phone
COUNTRYCODE WW
CPU_ABI arm64-v8a
DEVICE ASUS_Z00L_63
DISPLAY LRX22G.WW_user_1.17.40.1234_20160304
FINGERPRINT asus/WW_Z00L/ASUS_Z00L_63:5.0.2/LRX22G/WW_user_1.17.40.1234_20160304:user/release-keys
HARDWARE qcom
HOST builder5-pc
ID LRX22G
MANUFACTURER asus
MODEL ASUS_Z00LD
PRODUCT WW_Z00L
TAGS release-keys
TYPE user
USER builder5
CODENAME REL
INCREMENTAL WW_Z00L-WW_user_1.17.40.1234_20160304-user-20160304
RELEASE 5.0.2
SDK_INT 21
RADIO 202c10_11.1.0_160304
Root Access:no access
SU:not found
How to unlock bootloader?
Use the boot loader unlock app found in the General subforum.
HampTheToker said:
Use the boot loader unlock app found in the General subforum.
Click to expand...
Click to collapse
I tried it just restarts and there is no white logo screen
The white logo screen is only for the ZenFone 2 base models. For ZenFone 2 Laser variants, the logo screen will and should remain black. To verify whether your device hadha been truly unlocked, head over to fastboot mode on your device, and type the command: "fastboot oem device-info" (without the quotes) into the command prompt/terminal.
If it says device unlocked: true, that means your device had been successfully unlocked.
Another method is to try flashing TWRP onto your device, then attempting to boot into recovery. If it boot successfully, your device had been unlocked. If the ASUS logo just flashes and goes instantly, and then rebooting back to the system, it is still locked.
Rizzed said:
The white logo screen is only for the ZenFone 2 base models. For ZenFone 2 Laser variants, the logo screen will and should remain black. To verify whether your device hadha been truly unlocked, head over to fastboot mode on your device, and type the command: "fastboot oem device-info" (without the quotes) into the command prompt/terminal.
If it says device unlocked: true, that means your device had been successfully unlocked.
Another method is to try flashing TWRP onto your device, then attempting to boot into recovery. If it boot successfully, your device had been unlocked. If the ASUS logo just flashes and goes instantly, and then rebooting back to the system, it is still locked.
Click to expand...
Click to collapse
Thanks Rizzed I'll check via fastboot
Any results?
Same device and same problem
I have tried with a few "different" unlock apps and still get the following result after running
Code:
fastboot oem device-info
HTML:
...
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.004s]
finished. total time: 0.004s
Also I noticed that Asus' support page from the country where the device was bought does not have "utilities" section where the unlock apk would be located. (can't post a direct link since I'm new here, so here's part of the link: asus.com/br/Phone/ZenFone-2-Laser-ZE550KL/HelpDesk_Download/)
for this version of firmware(WW_user_1.17.40.1234_20160304) it does not work.. I have tried many times ... I am downgrading to 1.16.... will check.. For 1.16, bootloader unlock works with the unlocker app for ze600kl
hemantjangid39 said:
for this version of firmware(WW_user_1.17.40.1234_20160304) it does not work.. I have tried many times ... I am downgrading to 1.16.... will check.. For 1.16, bootloader unlock works with the unlocker app for ze600kl
Click to expand...
Click to collapse
Does it really work after downgrading? I'm currently sitting right here pulling my hair out over this. Would be great if it really works.
Did you manage to downgrade?
I tried downgrading but failed with fota_return_code 409 ("can't install this package [date] over newer build [date]").
igorrafael said:
Did you manage to downgrade?
I tried downgrading but failed with fota_return_code 409 ("can't install this package [date] over newer build [date]").
Click to expand...
Click to collapse
Before attempting to downgrade, go to FASTBOOT mode, and type this commands (in order),
fastboot erase system
fastboot oem reboot-recovery
It should be able to flash successfully now.
Rizzed said:
Before attempting to downgrade, go to FASTBOOT mode, and type this commands (in order),
fastboot erase system
fastboot oem reboot-recovery
It should be able to flash successfully now.
Click to expand...
Click to collapse
Thanks for the tip. Erasing system didn't work but your gave me the idea of changing the recovery partition. I managed to flash the stock version from this post. Only after the second line of the recovery screen showed "1.16" I managed to flash the file UL-Z00L-WW-1.16.40.763-user.zip
Unfortunately still didn't manage to unlock after a factory reset with the new firmware. Using unlock apk from this post:
igorrafael said:
Thanks for the tip. Erasing system didn't work but your gave me the idea of changing the recovery partition. I managed to flash the stock version from this post. Only after the second line of the recovery screen showed "1.16" I managed to flash the file UL-Z00L-WW-1.16.40.763-user.zip
Unfortunately still didn't manage to unlock after a factory reset with the new firmware. Using unlock apk from this post:
Click to expand...
Click to collapse
Really sorry about that..
I'm currently trying out all the other previous software, starting from the latest to the oldest. I will inform you immediately if it works out.
nrv.patel said:
I tried it just restarts and there is no white logo screen
Click to expand...
Click to collapse
I have been trying to unlock using the official unlock app since seven days. @Rajko said the app works sometimes. Also I have noticed that devices that were updated to 1.17 build are facing the same problem. Others who unlocked their device before the update were able to unlock BL. I even tried downgrading to 1.15 and 1.16 but no success till now. Maybe Asus has patched the bootloader with the 1.17 update and as you know bootloaders cannot be downgraded normally and can be fatal for any device. We may be able to unlock when Asus releases unlock app for Z00L.
sziraqui said:
I have been trying to unlock using the official unlock app since seven days. @Rajko said the app works sometimes. Also I have noticed that devices that were updated to 1.17 build are facing the same problem. Others who unlocked their device before the update were able to unlock BL. I even tried downgrading to 1.15 and 1.16 but no success till now. Maybe Asus has patched the bootloader with the 1.17 update and as you know bootloaders cannot be downgraded normally and can be fatal for any device. We may be able to unlock when Asus releases unlock app for Z00L.
Click to expand...
Click to collapse
Can confirm this. I downgraded to the oldest but to no avail.
Is there any way to downgrade the bootloader though? I really am thinking of selling this device for those high-end phones (Samsung S7/HTC 10) if there really is no solution.
Sent from my ASUS_Z00LD using XDA-Developers mobile app
Rizzed said:
Can confirm this. I downgraded to the oldest but to no avail.
Is there any way to downgrade the bootloader though? I really am thinking of selling this device for those high-end phones (Samsung S7/HTC 10) if there really is no solution.
Sent from my ASUS_Z00LD using XDA-Developers mobile app
Click to expand...
Click to collapse
if we don't figure it out within a month I'll also look into a replacement. For now I'll try to live with the stock rom...
btw, any reason you'd go for Samsung/HTC instead of Motorola/OnePlus?
igorrafael said:
if we don't figure it out within a month I'll also look into a replacement. For now I'll try to live with the stock rom...
btw, any reason you'd go for Samsung/HTC instead of Motorola/OnePlus?
Click to expand...
Click to collapse
The HTC looks to be an excellent choice. Their last few devices weren't up to par, and it's cost them dearly. They've stepped their game up with the 10, and I think it'll be the device to put them back in the game.
The Galaxy S7 family speaks for itself.
As for Motorola, I'd avoid them like the plague. They're horrible with updates and are getting sued right now for failing to properly honor their customers warranty claims.
Oneplus is a toss up, IMO. The Oneplus 3 could be a hit or a miss. I'm not sure when it's supposed to drop, but I'd keep my eye on it.
HampTheToker said:
The HTC looks to be an excellent choice. Their last few devices weren't up to par, and it's cost them dearly. They've stepped their game up with the 10, and I think it'll be the device to put them back in the game.
The Galaxy S7 family speaks for itself.
As for Motorola, I'd avoid them like the plague. They're horrible with updates and are getting sued right now for failing to properly honor their customers warranty claims.
Oneplus is a toss up, IMO. The Oneplus 3 could be a hit or a miss. I'm not sure when it's supposed to drop, but I'd keep my eye on it.
Click to expand...
Click to collapse
Interesting, I personally had very good experience with Motorola and have seen a lot of people having trouble with samsung phones.
My view on Samsung is biased though, as I barely consider them android phones. Prejudice aside , I see them as designed for people who want the status of iPhones but want something "like an android".
I hope the OnePlus 3 turns out to be good
igorrafael said:
Interesting, I personally had very good experience with Motorola and have seen a lot of people having trouble with samsung phones.
My view on Samsung is biased though, as I barely consider them android phones. Prejudice aside , I see them as designed for people who want the status of iPhones but want something "like an android".
I hope the OnePlus 3 turns out to be good
Click to expand...
Click to collapse
Well, sorry for saying this, but I personally do not trust any companies from (you know which country). Their phones may pack in very high specifications at very low and attractive prices, but really, there must be a catch, right? (personal opinion)
I live in Singapore and unfortunately, I don't see any Motorola smartphones being sold at any of our major electronics store or even online.
Sent from my ASUS_Z00LD using XDA-Developers mobile app
igorrafael said:
Interesting, I personally had very good experience with Motorola and have seen a lot of people having trouble with samsung phones.
My view on Samsung is biased though, as I barely consider them android phones. Prejudice aside , I see them as designed for people who want the status of iPhones but want something "like an android".
I hope the OnePlus 3 turns out to be good
Click to expand...
Click to collapse
I didn't say Moto makes a bad phone. On the contrary, their phones are usually pretty solid. It's their business practices and weak update support that turns me off, but they undeniably make good phones. Just don't expect to run the latest and greatest Android has to offer a year after release.
My opinion of Samsung is biased as well. My previous device was a Galaxy S4, and I LOVED it. It was a damn good phone that could take whatever I threw at it. And, the dev support...that phone had every ROM and mod you could ever want. The only reasons I didn't stick with Sammy were the price, and I the fact that my Samsung experience had gotten a little stale after three years with a Galaxy S4. Plus, these Zenfone variants dropped when I was ready to upgrade, and they were pretty attractive. I don't regret it for a second. Like I said previously, if Asus would drop ZenUI, I'm certain that the root community would want what they have to offer.
Oneplus is due to release a good device. I have a good feeling that they'll drop that crappy invite system this time around. If they do that and give us another flagship killer, the Oneplus 3 would be more than likely sell like hotcakes.