Related
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.
I am trying to unlock my bootloader so that I can root my phone but when I type "fastboot oem get_unlock_data" nothing is coming except this
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem get_unlock_data
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
(bootloader) Unlock data:
(bootloader) Unlock data unavailable
(bootloader) Failed
OKAY [ 0.109s]
finished. total time: 0.109s
Anyone please help what to do....
Have you enabled 'OEM unlock' under Settings > Developer Options? If you don't have Developer Options, head to Settings > About Phone, then scroll to your build number and tap it 7 times, then head to Settings. Developer Options should be there.
If you can, could we see the results of 'fastboot getvar all', if you're still in the bootloader please? You may wish to remove your IMEI and serial number from the output.
echo92 said:
Have you enabled 'OEM unlock' under Settings > Developer Options? If you don't have Developer Options, head to Settings > About Phone, then scroll to your build number and tap it 7 times, then head to Settings. Developer Options should be there.
If you can, could we see the results of 'fastboot getvar all', if you're still in the bootloader please? You may wish to remove your IMEI and serial number from the output.
Click to expand...
Click to collapse
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8952-B1.03
(bootloader) product: athene_16mp
(bootloader) board: athene_16mp
(bootloader) secure: yes
(bootloader) hwrev: P2A
(bootloader) radio: 4
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SAMSUNG RX1BMB RV=08 PV=07 FV=0000000000000007
(bootloader) ram: 3GB SAMSUNG LP3 DIE=6Gb M5=01 M6=05 M7=00 M8=7B
(bootloader) cpu: MSM8952
(bootloader) serialno: ZY2238QXGJ
(bootloader) cid: 0x0000
(bootloader) channelid: 0x00
(bootloader) uid: 0B7E180000000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: ****************
(bootloader) meid:
(bootloader) date: 06-03-2016
(bootloader) sku: XT1643
(bootloader) battid: SNN5970A
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Sat May 21 8:23:27 UTC 2016"
(bootloader) ro.build.fingerprint[0]: motorola/athene_f/athene_f:7.0/NPJ
(bootloader) ro.build.fingerprint[1]: 25.93-14/16:user/release-keys
(bootloader) ro.build.version.full[0]: Blur_Version.25.11.16.athene.reta
(bootloader) ro.build.version.full[1]: il.en.US
(bootloader) ro.build.version.qcom: LA.BR.1.3.6-01710-8976.0
(bootloader) version-baseband[0]: M8952_70030.25.03.62R ATHENE_INDIA_DSD
(bootloader) version-baseband[1]: S_CUST
(bootloader) kernel.version[0]: Linux version 3.10.84-g478d03a (hudsoncm
(bootloader) kernel.version[1]: @ilclbld26) (gcc version 4.8 (GCC) ) #1
(bootloader) kernel.version[2]: SMP PREEMPT Fri Jan 6 05:12:56 CST 2017
(bootloader) sbl1.git: git=MBM-NG-VB1.03-0-ge433b40
(bootloader) rpm.git: git=a970ead
(bootloader) tz.git: git=119e5b2-dirty
(bootloader) hyp.git: git=119e5b2-dirty
(bootloader) keymaster.git: git=119e5b2-dirty
(bootloader) cmnlib.git: git=119e5b2-dirty
(bootloader) aboot.git: git=MBM-NG-VB1.03-0-gb44c0ee
(bootloader) qe: qe 0/0
(bootloader) frp-state: no protection (142)
(bootloader) ro.carrier: unknown
all: listed above
finished. total time: 0.172s
Thanks for the reply - you may wish to have a look at this official Motorola/Lenovo page for help: https://forums.lenovo.com/t5/forums/v3_1/forumtopicpage/board-id/230/thread-id/2654/page/1 Looks like if you submit the above info along with the failed 'fastboot oem get_unlock_data', they'll attempt to generate a key for you in 48 business hours (though bear in mind that the Easter holidays may have caused a backlog). On page 235, I saw an athene device in a similar position to yours (CID is 0, though I'm confused as to why your bootloader can't see a carrier! Was this a service centre repair?)
same as
same problem is here. Are you get your unlock code from moto?
Dibesh16 said:
I am trying to unlock my bootloader so that I can root my phone but when I type "fastboot oem get_unlock_data" nothing is coming except this
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem get_unlock_data
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
(bootloader) Unlock data:
(bootloader) Unlock data unavailable
(bootloader) Failed
OKAY [ 0.109s]
finished. total time: 0.109s
Anyone please help what to do....
Click to expand...
Click to collapse
You may just simply have a locked device (example carrier locked). What is your model number? (Ex. XT16XX)
Kali Muthu.M.G. said:
same problem is here. Are you get your unlock code from moto?
Click to expand...
Click to collapse
nope....waiting if someone can help!!!!
Btrusa said:
You may just simply have a locked device (example carrier locked). What is your model number? (Ex. XT16XX)
Click to expand...
Click to collapse
XT1643
Dibesh16 said:
nope....waiting if someone can help!!!!
Click to expand...
Click to collapse
Did you post your getvar data and the OEM unlock output to that Lenovo thread I posted? All I saw from a user with the same username as yourself was a post from today asking for a solution, whereas if you'd posted the information as requested in that thread, like the other posters in the Lenovo official thread, you might have gotten an unlock code by now, or be in the queue to get one.
If you don't know how to unlock it, you probably shouldn't root your phone. I tried, and I messed everything up. Not worth it. #BrickedPhone #IKnowWhatIAmDoingTonight
echo92 said:
Did you post your getvar data and the OEM unlock output to that Lenovo thread I posted? All I saw from a user with the same username as yourself was a post from today asking for a solution, whereas if you'd posted the information as requested in that thread, like the other posters in the Lenovo official thread, you might have gotten an unlock code by now, or be in the queue to get one.
Click to expand...
Click to collapse
Ya I did posted there....now waiting
FIUSHerson said:
If you don't know how to unlock it, you probably shouldn't root your phone. I tried, and I messed everything up. Not worth it. #BrickedPhone #IKnowWhatIAmDoingTonight
Click to expand...
Click to collapse
I know how to do it ....I think there is something wrong with phone
Dibesh16 said:
Ya I did posted there....now waiting
Click to expand...
Click to collapse
I had a quick look to see if your request in that thread might have been submitted, and unless I've got the wrong user, a user with the same user name as yourself has posted 'Same problem here...got any solution?' in that Motorola forum... https://forums.lenovo.com/t5/forums/v3_1/forumtopicpage/board-id/230/thread-id/2654/page/241
Which isn't very useful and will probably mean they will be waiting a long time unless they post the correct info. Like the information requested in the opening post of that Motorola thread and the information posted by users of that thread. Seems that those who posted their data have had it, from what I see, been forwarded by alpha dog (the moderator) for generating their unlock code...
In other words, that user, if they really want an unlock code, might like to post their getvar all data (without imei) and the OEM unlock code data to that thread for help, eh?
EDIT - I see you've posted the getvar and oem unlock output, hopefully they'll get back to you in the stated time. Motorola may ask you for the IMEI number but that'll be in their response when they get round to your report. Good luck!
Found the solution! I had to find the deep parts of the Motorola website, and downloaded the stock ROM. (Their servers are super slow though) Everything is back to normal except for the fact that I can't upgrade to Android 7.0.
FIUSHerson said:
Found the solution! I had to find the deep parts of the Motorola website, and downloaded the stock ROM. (Their servers are super slow though) Everything is back to normal except for the fact that I can't upgrade to Android 7.0.
Click to expand...
Click to collapse
Nice one, i'm guessing you got the XT1625 image from https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images# ? (hopefully your device is a XT 1625!)
What does your device say when it's searching for an update? Also, just to confirm, you can still make calls and your IMEI is still present?
Oh, if you desire Nougat, you may wish to look into this fastboot stock ROM (https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369) though understandable if you don't wish to flash anything right now, now you've got your device operational again
echo92 said:
I had a quick look to see if your request in that thread might have been submitted, and unless I've got the wrong user, a user with the same user name as yourself has posted 'Same problem here...got any solution?' in that Motorola forum... https://forums.lenovo.com/t5/forums/v3_1/forumtopicpage/board-id/230/thread-id/2654/page/241
Which isn't very useful and will probably mean they will be waiting a long time unless they post the correct info. Like the information requested in the opening post of that Motorola thread and the information posted by users of that thread. Seems that those who posted their data have had it, from what I see, been forwarded by alpha dog (the moderator) for generating their unlock code...
In other words, that user, if they really want an unlock code, might like to post their getvar all data (without imei) and the OEM unlock code data to that thread for help, eh?
EDIT - I see you've posted the getvar and oem unlock output, hopefully they'll get back to you in the stated time. Motorola may ask you for the IMEI number but that'll be in their response when they get round to your report. Good luck!
Click to expand...
Click to collapse
I got the reply and they said my device needs servicing and asked for some info about me and which I mailed them back but its been 3 days i didn't got any response from there side.... How much time they take to reply?
Dibesh16 said:
I got the reply and they said my device needs servicing and asked for some info about me and which I mailed them back but its been 3 days i didn't got any response from there side.... How much time they take to reply?
Click to expand...
Click to collapse
Well, at least's progress... As for how much time they need, I don't know (though don't forget Saturday and Sunday are not usually business days), so you may get a response early next week, but if they don't reply in a week or so, I'd suggest replying to them via the contact email/message they sent you. I'm hoping they're consulting with engineers/service centres as to what needs to be done with your device.
echo92 said:
Well, at least's progress... As for how much time they need, I don't know (though don't forget Saturday and Sunday are not usually business days), so you may get a response early next week, but if they don't reply in a week or so, I'd suggest replying to them via the contact email/message they sent you. I'm hoping they're consulting with engineers/service centres as to what needs to be done with your device.
Click to expand...
Click to collapse
I have a question what if I relock my device bootloader will I be able to unlock it again
suryaprakash123 said:
I have a question what if I relock my device bootloader will I be able to unlock it again
Click to expand...
Click to collapse
I've not tried this, but I recall you should be able to by using the unlock key provided to you by Motorola. I do not know if this will wipe your device again should you choose to unlock again, so ensure your data is backed up somewhere. Also, if you choose to relock (especially now we've got the latest stock ROM: https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138) don't have anything non-stock on your system, else a brick may occur (by non stock, I mean no custom recovery, no custom kernel and no system modifications, like root).
echo92 said:
I've not tried this, but I recall you should be able to by using the unlock key provided to you by Motorola. I do not know if this will wipe your device again should you choose to unlock again, so ensure your data is backed up somewhere. Also, if you choose to relock (especially now we've got the latest stock ROM: https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138) don't have anything non-stock on your system, else a brick may occur (by non stock, I mean no custom recovery, no custom kernel and no system modifications, like root).
Click to expand...
Click to collapse
My security patch update is not on March 1 i.e latest.does it make any sense
I need to relock the bootloader, but the fastboot oem lock command doesn't work saying
C:\G5>fastboot oem lock
...
(bootloader) Check 'Allow OEM Unlock' in Android Settings > Developer
(bootloader) Options
OKAY [ 0.002s]
finished. total time: 0.003s
But that option is greyed out. I'm on POTTER_NPN25.137-92 Stock ROM with unlocked bootloader (XT1686).
Please help!
SD008 said:
I need to relock the bootloader, but the fastboot oem lock command doesn't work saying
C:\G5>fastboot oem lock
...
(bootloader) Check 'Allow OEM Unlock' in Android Settings > Developer
(bootloader) Options
OKAY [ 0.002s]
finished. total time: 0.003s
But that option is greyed out. I'm on POTTER_NPN25.137-92 Stock ROM with unlocked bootloader (XT1686).
Please help!
Click to expand...
Click to collapse
Because that isn't how you lock the bootloader on Moto devices... you can't just lock your bootloader on the fly, it can only be down with a full factory image flash. In your case, it is something like this:
'fastboot oem lock ' <get prompted to make sure you want to this and enter command again>
'fastboot oem lock'
Then fastboot flash the full factory image of NPN25.137-92 or newer ROM for your device, including all wipes, and end it with
`fastboot oem lock` - but this will only work if you used oem lock at the beginning and in conjunction with a complete image flash.
There are tutorials on here how to do it, a little research in the forums here will yield a couple different tutorials.
BTW, it is well known that relocking the bootloader on the Moto G5 series is problematic... Sometimes it doesn't work, and sometimes it bricks.
Remember that regardless of if you relock or not, the bootloader unlock warning screen will always be there, and the bootloader will never go back to Status 0 - Locked, it will become Status 2 - Relocked so it is still a clear indication the phone was modified at one point.
After a lot of Googling I was able to find the solution. Had to search high and low for it, finally found the relevant information in the Oneplus 5 subforums. What I needed to do was flash Magisk and then the OEM unlock option becomes usable again. For anyone facing a similar issue, flash either stock or a stock-based rom along woth Magisk and enable OEM unlock in the dev options and the you should be able to re-lock.
acejavelin said:
Because that isn't how you lock the bootloader on Moto devices... you can't just lock your bootloader on the fly, it can only be down with a full factory image flash. In your case, it is something like this:
'fastboot oem lock ' <get prompted to make sure you want to this and enter command again>
'fastboot oem lock'
Then fastboot flash the full factory image of NPN25.137-92 or newer ROM for your device, including all wipes, and end it with
`fastboot oem lock` - but this will only work if you used oem lock at the beginning and in conjunction with a complete image flash.
There are tutorials on here how to do it, a little research in the forums here will yield a couple different tutorials.
BTW, it is well known that relocking the bootloader on the Moto G5 series is problematic... Sometimes it doesn't work, and sometimes it bricks.
Remember that regardless of if you relock or not, the bootloader unlock warning screen will always be there, and the bootloader will never go back to Status 0 - Locked, it will become Status 2 - Relocked so it is still a clear indication the phone was modified at one point.
Click to expand...
Click to collapse
It's funny how you automatically assumed that I didn't see any of the 3 or 4 guides posted in here and just straight-up made a thread to beg for help. Obviously I flashed a stock firmware before beginning the locking process (and after it too), but as I clearly mentioned in the OP, the problem was that due to the Allow OEM switch being disabled and greyed out, the 'fastboot oem lock' command was not doing its thing. Had it worked properly, it'd tell me to proceed with flashing the system chunks, but it didn't. So yeah, what you said wasn't really helpful. Thanks anyway for taking the time to reply. Just please don't assume w/o any evidence that someone is so ignorant as to not read a guide and beg for answers. There are many people like me who only lurk and do everything by following tutorials and only ever post if all else fails.
SD008 said:
After a lot of Googling I was able to find the solution. Had to search high and low for it, finally found the relevant information in the Oneplus 5 subforums. What I needed to do was flash Magisk and then the OEM unlock option becomes usable again. For anyone facing a similar issue, flash either stock or a stock-based rom along woth Magisk and enable OEM unlock in the dev options and the you should be able to re-lock.
It's funny how you automatically assumed that I didn't see any of the 3 or 4 guides posted in here and just straight-up made a thread to beg for help. Obviously I flashed a stock firmware before beginning the locking process (and after it too), but as I clearly mentioned in the OP, the problem was that due to the Allow OEM switch being disabled and greyed out, the 'fastboot oem lock' command was not doing its thing. Had it worked properly, it'd tell me to proceed with flashing the system chunks, but it didn't. So yeah, what you said wasn't really helpful. Thanks anyway for taking the time to reply. Just please don't assume w/o any evidence that someone is so ignorant as to not read a guide and beg for answers. There are many people like me who only lurk and do everything by following tutorials and only ever post if all else fails.
Click to expand...
Click to collapse
Hi I want to ask a question I restored my nandroid stock backup VoLTE , LTE everything is working fine. I have Moto stock recovery but on device bootup it shows bootloader unlocked sign.
Can I install updates when update come without any issue or will it brick my device I have stock moto recovery
sinchan_nohara said:
Hi I want to ask a question I restored my nandroid stock backup VoLTE , LTE everything is working fine. I have Moto stock recovery but on device bootup it shows bootloader unlocked sign.
Can I install updates when update come without any issue or will it brick my device I have stock moto recovery
Click to expand...
Click to collapse
If you haven't changed anything in /system or /vendor and your device is stock unrooted there's no problem with OTA updates. If you flashed the stock logo.bin everything is ok even when it shows BL is unlocked.
Sent from my Moto G5 Plus using XDA Labs
SD008 said:
After a lot of Googling I was able to find the solution. Had to search high and low for it, finally found the relevant information in the Oneplus 5 subforums. What I needed to do was flash Magisk and then the OEM unlock option becomes usable again. For anyone facing a similar issue, flash either stock or a stock-based rom along woth Magisk and enable OEM unlock in the dev options and the you should be able to re-lock.
It's funny how you automatically assumed that I didn't see any of the 3 or 4 guides posted in here and just straight-up made a thread to beg for help. Obviously I flashed a stock firmware before beginning the locking process (and after it too), but as I clearly mentioned in the OP, the problem was that due to the Allow OEM switch being disabled and greyed out, the 'fastboot oem lock' command was not doing its thing. Had it worked properly, it'd tell me to proceed with flashing the system chunks, but it didn't. So yeah, what you said wasn't really helpful. Thanks anyway for taking the time to reply. Just please don't assume w/o any evidence that someone is so ignorant as to not read a guide and beg for answers. There are many people like me who only lurk and do everything by following tutorials and only ever post if all else fails.
Click to expand...
Click to collapse
I've been here a long time, didn't mean to offend... All I had to go by was your limited information of the first post, I assumed nothing that wasn't included in your post. You didn't state anything that you had tried, so of course I assumed you didn't look because you didn't state anything.
Sorry. I will just bow out and wish you luck.
SD008 said:
After a lot of Googling I was able to find the solution. Had to search high and low for it, finally found the relevant information in the Oneplus 5 subforums. What I needed to do was flash Magisk and then the OEM unlock option becomes usable again. For anyone facing a similar issue, flash either stock or a stock-based rom along woth Magisk and enable OEM unlock in the dev options and the you should be able to re-lock.
Click to expand...
Click to collapse
Man, I was having the same issue on my Moto G6 (Ali) and was like you, looking here and there with no solution, and your solution was the only one that worked!! Thank you so much!
Stock rooted PIE a month ago.
Looking through my command history, I see
Code:
$ fastboot flashing unlock
but I do not see the subsequent
Code:
$ fastboot flashing unlock_critical
I am 99% sure I did run this command also, but there's that 1%...
Is there anything I can check on the phone itself to confirm that indeed, I've unlocked critical as well?
When in fastboot mode, the phones' display shows SECURE BOOT - yes and DEVICE STATE - unlocked.
Also
Code:
$ fastboot getvar unlocked
unlocked: yes
finished. total time: 0.001s
$
I wonder if there's a var for critical.. or how to get a list a vars..
IDK if there is, but I am interested in finding out if there's a variable to check, and more importantly if that command does anything of value. I've not unlocked "critical" (100% certain), but I couldn't see it having a real point.
To be clear, I've never had any issue in flashing or rooting the PH-1, or with many of the issues that others report.
Code:
fastboot oem device-info
ultrasuper said:
Stock rooted PIE a month ago.
Looking through my command history, I see
Code:
$ fastboot flashing unlock
but I do not see the subsequent
Code:
$ fastboot flashing unlock_critical
I am 99% sure I did run this command also, but there's that 1%...
Is there anything I can check on the phone itself to confirm that indeed, I've unlocked critical as well?
When in fastboot mode, the phones' display shows SECURE BOOT - yes and DEVICE STATE - unlocked.
Also
Code:
$ fastboot getvar unlocked
unlocked: yes
finished. total time: 0.001s
$
I wonder if there's a var for critical.. or how to get a list a vars..
Click to expand...
Click to collapse
I also forgot and was unsure so I just ran the critical unlock again and got the message already unlocked
jionny said:
I also forgot and was unsure so I just ran the critical unlock again and got the message already unlocked
Click to expand...
Click to collapse
I am afraid to simply re-issue the cmd because *I think* it wipes the phone completely.
munchy_cool said:
Code:
fastboot oem device-info
Click to expand...
Click to collapse
Code:
...
(bootloader) Verity mode: true
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: true
(bootloader) Device modem EFS unlocked: false
(bootloader) Charger screen enabled: true
OKAY [ 0.001s]
finished. total time: 0.001s
Thanks for the tip.
Any idea what the last two represent?
ultrasuper said:
Any idea what the last two represent?
Click to expand...
Click to collapse
nopes
ultrasuper said:
I am afraid to simply re-issue the cmd because *I think* it wipes the phone completely.
Click to expand...
Click to collapse
you should be prompted in the bootloader to confirm
ultrasuper said:
I am afraid to simply re-issue the cmd because *I think* it wipes the phone completely.
Click to expand...
Click to collapse
how can it rewipe the phone if its already unlocked? impossible besides the cmd shows you that its unlocked so you are good
jionny said:
how can it rewipe the phone if its already unlocked? impossible besides the cmd shows you that its unlocked so you are good
Click to expand...
Click to collapse
both unlock and unlock_critical initiate wipes
ziddey said:
both flashing unlock and flashing unlock_critical initiate a wipe
Click to expand...
Click to collapse
not if its already unlocked. I did so already and simply got back already unlocked
---------- Post added at 06:15 PM ---------- Previous post was at 06:05 PM ----------
ziddey said:
both unlock and unlock_critical initiate wipes
Click to expand...
Click to collapse
lmao ok you got it
jionny said:
not if its already unlocked. I did so already and simply got back already unlocked
---------- Post added at 06:15 PM ---------- Previous post was at 06:05 PM ----------
lmao ok you got it
Click to expand...
Click to collapse
both initiate wipes, and warn accordingly. but yes, if op is already unlocked, it won't do anything
ziddey said:
both initiate wipes, and warn accordingly. but yes, if op is already unlocked, it won't do anything
Click to expand...
Click to collapse
That has been my point all along if it is already unlocked it will do nothing but tell you its already unlocked. Thank you
kboya said:
IDK if there is, but I am interested in finding out if there's a variable to check, and more importantly if that command does anything of value. I've not unlocked "critical" (100% certain), but I couldn't see it having a real point.
To be clear, I've never had any issue in flashing or rooting the PH-1, or with many of the issues that others report.
Click to expand...
Click to collapse
Yes the command is of value, it's to Unlock Critical Partitions
https://mata.readthedocs.io/en/latest/
Thanks but that's not as self-evident as you seem to think. I've read that and much more besides about other devices. Yet I still don't see its value to me and my use case where I've never needed these critical partitions. The last Android partitioning I needed to do was on the Nexus one and HTC Desire to ensure that small ROMs had a suitably small system partition and thus more storage abatement for apps.
Also, without unlock_critical I've had no issues with flashing and rooting, unlike so many others that have unlocked it.
kboya said:
IDK if there is, but I am interested in finding out if there's a variable to check, and more importantly if that command does anything of value. I've not unlocked "critical" (100% certain), but I couldn't see it having a real point.
To be clear, I've never had any issue in flashing or rooting the PH-1, or with many of the issues that others report.
Click to expand...
Click to collapse
kboya said:
Thanks but that's not as self-evident as you seem to think. I've read that and much more besides about other devices. Yet I still don't see its value to me and my use case where I've never needed these critical partitions. The last Android partitioning I needed to do was on the Nexus one and HTC Desire to ensure that small ROMs had a suitably small system partition and thus more storage abatement for apps.
Also, without unlock_critical I've had no issues with flashing and rooting, unlike so many others that have unlocked it.
Click to expand...
Click to collapse
This is suppose to be the basic understanding, they/the partitions are Locked and in order to flash properly to them, we need to Unlock them...
I highly suggest until someone says otherwise to make sure you unlock them...
I understand the difference between locked and unlocked; you've missed the point entirely.
I'll leave it.
kboya said:
I understand the difference between locked and unlocked; you've missed the point entirely.
I'll leave it.
Click to expand...
Click to collapse
You asked before if there was any value and you didn't see the point.
So if it's locked, it can't be flashed to, so you don't see the value or point in that?
From reading around, there seems to be some people getting away with keeping them locked, and others having problems.
But the correct way for now is to unlock them to avoid any problems.
I thought that was clear.
Yeah, read around:
"For Pixel 2 XL only with loader version prior to TMZ20a: the critical partitions may also need to be unlocked before flashing. The unlock can be performed with this command, and should NOT be done on other devices:
fastboot flashing unlock_critical" (source: google factory images)
kboya said:
Yeah, read around:
"For Pixel 2 XL only with loader version prior to TMZ20a: the critical partitions may also need to be unlocked before flashing. The unlock can be performed with this command, and should NOT be done on other devices:
fastboot flashing unlock_critical" (source: google factory images)
Click to expand...
Click to collapse
I have already read around...
I unlock it because I am hacking on Stock.
Hey there!
Complete newbie here, so only used my Redmi Note 7 with stock firmware and did all updates through the phone (never flashed any ROM or even unlocked the bootloader), but woke up with the "System has been destroyed" message.
Tried to fastboot the newest Lavender ROM, but (duh) it failed because the phone is locked. Can someone help me or EDL with test points is my only option?
\Minimal ADB and Fastboot>fastboot oem device-info
(bootloader) Verity mode: true
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: false
OKAY [ 0.016s]
Do you have the option to factory reset from the boot menu? It may have updated overnight.
I always keep OTA updates disabled on my Samsung's... destroyer of worlds.
blackhawk said:
Do you have the option to factory reset from the boot menu? It may have updated overnight.
I always keep OTA updates disabled on my Samsung's... destroyer of worlds.
Click to expand...
Click to collapse
Boot menu (power+up) keeps showing the same "System has been destroyed", only screen I can access is the fastboot one (power+down) :'(
great_thunder said:
Boot menu (power+up) keeps showing the same "System has been destroyed", only screen I can access is the fastboot one (power+down) :'(
Click to expand...
Click to collapse
Can you try to boot recovery image from fastboot? Not sure it will work on locked bootloader though, but it worth the shot.
If it doesn't work, I'm afraid edl or official service center might your only option. You might find unofficial way to unlock bootloader through exploit, but it's not worth the risk or money.
This is one of reason why I'd rather keep my phone unlocked, in case Xiaomi officially mess up, I have my chance to fix it myself, especially if it's already out of warranty.
x3r0.13urn said:
Can you try to boot recovery image from fastboot? Not sure it will work on locked bootloader though, but it worth the shot.
If it doesn't work, I'm afraid edl or official service center might your only option. You might find unofficial way to unlock bootloader through exploit, but it's not worth the risk or money.
This is one of reason why I'd rather keep my phone unlocked, in case Xiaomi officially mess up, I have my chance to fix it myself, especially if it's already out of warranty.
Click to expand...
Click to collapse
Tried a recovery image, but still got the "FAILED (device is locked)" message.
Funny thing is that I always had an itch for ROMs and modding, but never went through with it because I was scared of bricking my phone. Now I'm stuck because of OTA updates and if I had unlocked the bootloader my life would be so much easier now
great_thunder said:
Tried a recovery image, but still got the "FAILED (device is locked)" message.
Funny thing is that I always had an itch for ROMs and modding, but never went through with it because I was scared of bricking my phone. Now I'm stuck because of OTA updates and if I had unlocked the bootloader my life would be so much easier now
Click to expand...
Click to collapse
You still can receive OTA and apply it even it's unlocked. The only downsides are your device won't pass safetynet and cts, and widevine will go lower to L3. Other device might losing other features as well (camera breaks when unlocked in samsung, fingerprint won't work in realme, cmiiw), Xiaomi is quite genereous only introduce those downsides when unlocked.
I have seen few times Xiaomi messed up with official OTA, roll back updates is nothing unusual with Xiaomi (or other manufacturers as well).