I have finally locked my bootloader. After many failed attempts, I've realized doing the next:
Flash a Stock Firmware (most probably an old version)
Boot it and apply all system updates.
Reboot into Bootloader
Run fastboot oem lock
Boot noramlly
and in fastboot mode you have oem_locked or flashing_locked?
gorbatschoff said:
and in fastboot mode you have oem_locked or flashing_locked?
Click to expand...
Click to collapse
I got flashing locked after I did...
And before that, I was able to unlock and lock the bootloader without a problem. Yesterday something strange happened. I entered fastboot mode, you unlocked the bootloader because I can't flash the stock on locked, I installed the latest version from the August patch and strange things started to happen. After starting the phone and entering the updates, I have information about the patch from August, but it also says that the integrity of the software has been compromised and I will not get updates. It is written that I would like to contact the service center to re-program the device. So I went into fastboot again and threw the June patch version. But now I have a situation that. I can not lock the bootloader because when I do it with the fastboot OEM lock command, the phone does not start and gets a message that the device is damaged. Only after unlocking the bootloader can I start the phone.
Wysłane z mojego moto g(8) plus przy użyciu Tapatalka
gorbatschoff said:
And before that, I was able to unlock and lock the bootloader without a problem. Yesterday something strange happened. I entered fastboot mode, you unlocked the bootloader because I can't flash the stock on locked, I installed the latest version from the August patch and strange things started to happen. After starting the phone and entering the updates, I have information about the patch from August, but it also says that the integrity of the software has been compromised and I will not get updates. It is written that I would like to contact the service center to re-program the device. So I went into fastboot again and threw the June patch version. But now I have a situation that. I can not lock the bootloader because when I do it with the fastboot OEM lock command, the phone does not start and gets a message that the device is damaged. Only after unlocking the bootloader can I start the phone.
Wysłane z mojego moto g(8) plus przy użyciu Tapatalka
Click to expand...
Click to collapse
Its nothing. You first need to flash stock ROM from fastboot and then when your ROM normally.
You now need to have Lenovo rescue tool installed on your sytem. After skipping initial setup in stock ROM,
attach your phone to computer and open Lenovo rescue tool. It will ask for permissions. From there you need to go to rescue option. Once there, the tool itself going to guide you. It will now download the latest stock ROM. Have some patience. Once downloaded just let it flash the stock ROM.
After it finishes flashing and your phones boot to stock ROM. Just go to fastboot again and relock bootloader again. This should work now.
gorbatschoff said:
and in fastboot mode you have oem_locked or flashing_locked?
Click to expand...
Click to collapse
I have flashing_locked
Anybody knows if there is a youtube video for this process? Or any most exhausted step by step list.
X4vier said:
Anybody knows if there is a youtube video for this process? Or any most exhausted step by step list.
Click to expand...
Click to collapse
I saw you in several posts, what do you really want?
help me please
Relock Bootloader on Moto deen one
Krzysztof323 said:
help me please
Relock Bootloader on Moto deen one
Click to expand...
Click to collapse
here's a topic about the G8 Plus doha, Krzysiulku
gorbatschoff said:
here's a topic about the G8 Plus doha, Krzysiulku
Click to expand...
Click to collapse
im have moto one and G8+ help relock bootloader
Krzysztof323 said:
im have moto one and G8+ help relock bootloader
Click to expand...
Click to collapse
fastboot oem lock
fastboot flashing lock
gorbatschoff said:
fastboot oem lock
fastboot flashing lock
Click to expand...
Click to collapse
fastboot oem lock and dont start sytem
then reinstall the system and then it might turn on
gorbatschoff said:
then reinstall the system and then it might turn on
Click to expand...
Click to collapse
gorbatschoff said:
then reinstall the system and then it might turn on
Click to expand...
Click to collapse
fastboot oem lock =Your device is corrupt.It cant't be trusted and will not boot
Related
Hi everyone! y have a very hard trouble, and wait you can help me. (im not english native speaker, i am using a google translater, sorry for that)
I have a Moto G 3er generation (XT1542) and it cant booting it, the phone not run from away boot logo. if i go to bootloader the recovery not run. I have the phone with bootloader locked and i cant unlocked because when i try it the cmd send me a error: Allow oem unlock, but I CANT because i need go to the developer options in the SO.
Also i tried install a custom recovery, but i need the bootloader unlocked.
I really will be very graced if you can help me.
Did you tried to do a factory reset?
fastboot -w
just flash the stock firmware..
HelpMeruth said:
just flash the stock firmware..
Click to expand...
Click to collapse
Thanks! Im not need unlock the bootloader?
GP190292 said:
Thanks! Im not need unlock the bootloader?
Click to expand...
Click to collapse
nope
https://forum.xda-developers.com/xperia-z5/help/bootloader-unlock-allowed-able-to-boot-t3715524
So, in the end, I decided to flash the customized E6653 NOBA ROM for my Z5
Later, I was thinking... if I can go to the Flashmode & Fastboot mode, can I continue to unlock the bootloader, even though it says No?
Because to my knowledge, with Bootloader Unlock Allowed No, means that I can't access both Flashmode & Fastboot mode
Thanks lads, again
Aircatcher said:
https://forum.xda-developers.com/xperia-z5/help/bootloader-unlock-allowed-able-to-boot-t3715524
So, in the end, I decided to flash the customized E6653 NOBA ROM for my Z5
Later, I was thinking... if I can go to the Flashmode & Fastboot mode, can I continue to unlock the bootloader, even though it says No?
Because to my knowledge, with Bootloader Unlock Allowed No, means that I can't access both Flashmode & Fastboot mode
Thanks lads, again
Click to expand...
Click to collapse
As i said earlier - no you cant, no possible way.
EugenStanis said:
As i said earlier - no you cant, no possible way.
Click to expand...
Click to collapse
What a bummer... I may likely to RMA or sell this phone and go for XZ, the global version ofc
I did root my phone with fastboot commands when my bootloader was still locked.
That means I could still go to fastboot stuff.
Try the fastboot commands. It might works.
Hi, I'm trying to root my Honor 8 device and install TWRP. However when I try to flash the TWRP file in ADB, I get this error message:
FAILED(remote not allowed). I have tried different versions of TWRP, the latest one and the one thats for Honor 8 on their site. I have unlocked bootloader. I don't understand what's happening. Can someone please explain this?
It's my first time rooting a device manually, so i dont know much. If you are able to, please refer to things in an easy manner.
Thanks in advance.
ver1x said:
Hi, I'm trying to root my Honor 8 device and install TWRP. However when I try to flash the TWRP file in ADB, I get this error message:
FAILED(remote not allowed). I have tried different versions of TWRP, the latest one and the one thats for Honor 8 on their site. I have unlocked bootloader. I don't understand what's happening. Can someone please explain this?
It's my first time rooting a device manually, so i dont know much. If you are able to, please refer to things in an easy manner.
Thanks in advance.
Click to expand...
Click to collapse
Is Your Bootloader Unlocked???
And Also This TWRP:
https://forum.xda-developers.com/honor-8/development/twrp-t3566563/page1
Can Only Work For The Honor 8 Android 7
On TWRP Website, The TWRP There Only Works For The Honor In Android 6.
Also When Flashing a recovery Do "fastboot flash recovery [Filename]"
RealFireBlaze20 said:
Is Your Bootloader Unlocked???
And Also This TWRP:
https://forum.xda-developers.com/honor-8/development/twrp-t3566563/page1
Can Only Work For The Honor 8 Android 7
On TWRP Website, The TWRP There Only Works For The Honor In Android 6.
Also When Flashing a recovery Do "fastboot flash recovery [Filename]"
Click to expand...
Click to collapse
Yes i have unlocked the bootloader. I'm pretty sure i've already tried that version of TWRP, but i will try again tomorrow.
I always flash recovery using "fastboot flash recovery (file name)" so that's not the problem.
ver1x said:
Yes i have unlocked the bootloader. I'm pretty sure i've already tried that version of TWRP, but i will try again tomorrow.
I always flash recovery using "fastboot flash recovery (file name)" so that's not the problem.
Click to expand...
Click to collapse
Hmmmm... Okay
RealFireBlaze20 said:
Hmmmm... Okay
Click to expand...
Click to collapse
I think i might have found the problem.
When i go into bootloader it says FRP lock, i've looked around a bit, and i cant seem to figure out what it is and how i can unlock it.
If you know, how?
ver1x said:
I think i might have found the problem.
When i go into bootloader it says FRP lock, i've looked around a bit, and i cant seem to figure out what it is and how i can unlock it.
If you know, how?
Click to expand...
Click to collapse
I had same problem. I successfully unlocked bootloader but after that I accidentally restored default settings in developer settings and oem unlock was ticked off and greyd out. Then I noticed the same FRP lock.
I had to relock and unlock the bootloader. Only after that I was able to flash twrp on my phone.
To relock you type "fastboot oem relock (unlock code)"
After that you can turn on "oem unlock" and "usb debugging"
And yes, It will wipe your data when relocking and again after unlocking so it takes some time. Hope this helps :fingers-crossed:
Juhkimo said:
I had same problem. I successfully unlocked bootloader but after that I accidentally restored default settings in developer settings and oem unlock was ticked off and greyd out. Then I noticed the same FRP lock.
I had to relock and unlock the bootloader. Only after that I was able to flash twrp on my phone.
To relock you type "fastboot oem relock (unlock code)"
After that you can turn on "oem unlock" and "usb debugging"
And yes, It will wipe your data when relocking and again after unlocking so it takes some time. Hope this helps :fingers-crossed:
Click to expand...
Click to collapse
Thanks, i will definetely try this!
Edit: it worked! Thank you so much.
ver1x said:
Thanks, i will definetely try this!
Edit: it worked! Thank you so much.
Click to expand...
Click to collapse
Good to hear that
I can't do it
How am I supposed to get the bootloader code now that Huawei disabled it on their site?
VFR99 said:
How am I supposed to get the bootloader code now that Huawei disabled it on their site?
Click to expand...
Click to collapse
Dc unlocker Progam for pc
Hello guys, I dont know whats happening with my Nexus 5 right now. Its stuck on Google logo which appears during restarting of the phone.
I have tried everything. I try to go into recovery it dosent work. I tried changing it to CWM from TWRP still it stays TWRP i get errors while flashing .bat files like (error: failure to write). Please help been stuck on this since past 72hours. Any help to resolve this issue is appreciated. Thanks :crying::crying::crying:
If the bootloader is unlocked, relock the bootloader and reboot into fastboot mode. If the bootloader unlocks itself, the internal memory is probably damaged. If the bootloader remains locked, unlock it and flash 4.4 using fastboot commands.
audit13 said:
If the bootloader is unlocked, relock the bootloader and reboot into fastboot mode. If the bootloader unlocks itself, the internal memory is probably damaged. If the bootloader remains locked, unlock it and flash 4.4 using fastboot commands.
Click to expand...
Click to collapse
OEM can be locked and unlocked. But the only problem now is i cannot override the previous partitions as there is an error "failed to write" i dont understand why is this happening this is also the reason i cannot get into my recovery as when i enter recovery it gets stuck for some reason.
audit13 said:
If the bootloader is unlocked, relock the bootloader and reboot into fastboot mode. If the bootloader unlocks itself, the internal memory is probably damaged. If the bootloader remains locked, unlock it and flash 4.4 using fastboot commands.
Click to expand...
Click to collapse
Also what does flash 4.4 mean? Sorry new to this!
audit13 said:
If the bootloader is unlocked, relock the bootloader and reboot into fastboot mode. If the bootloader unlocks itself, the internal memory is probably damaged. If the bootloader remains locked, unlock it and flash 4.4 using fastboot commands.
Click to expand...
Click to collapse
Also i tried to erase partitions manually but i always got an error as (remote: failed to erase partition)
Let's start with the bootloader.
Boot into fastboot mode, lock the bootloader, reboot into fastboot mode. Does the bootloader stay "locked" or does it go back to say "unlocked"?
audit13 said:
Let's start with the bootloader.
Boot into fastboot mode, lock the bootloader, reboot into fastboot mode. Does the bootloader stay "locked" or does it go back to say "unlocked"?
Click to expand...
Click to collapse
It goes back to unlocked
audit13 said:
Let's start with the bootloader.
Boot into fastboot mode, lock the bootloader, reboot into fastboot mode. Does the bootloader stay "locked" or does it go back to say "unlocked"?
Click to expand...
Click to collapse
Do you have discord or teamspeak or any other apps to chat directly?
NeXussssssssss said:
It goes back to unlocked
Click to expand...
Click to collapse
The internal memory may be damaged.
You might want to try this: https://forum.xda-developers.com/google-nexus-5/general/how-fixed-bricked-nexus-5-corrupted-t2903593
audit13 said:
The internal memory may be damaged.
You might want to try this: https://forum.xda-developers.com/google-nexus-5/general/how-fixed-bricked-nexus-5-corrupted-t2903593
Click to expand...
Click to collapse
I tried the 1st step by overwriting twrp with cwm dint work. Also ADB isnt connected. I tried to but just fastboot works.
I recommend flashing stock 4.4 using fastboot commands.
Stock ROMs are here: https://developers.google.com/android/images
audit13 said:
I recommend flashing stock 4.4 using fastboot commands.
Stock ROMs are here: https://developers.google.com/android/images
Click to expand...
Click to collapse
I tried flashing new roms it says failure to write to cache,boot,recovery everything fails!
There is no way to erase partitions as it fails!
I would say the internal memory is damaged and will require a motherboard change.
I kept my phone on charge for a few mins and when I came back to unplug, it was stuck on google screen. tried turning off the device or restarting it but nothing works. The phone was extremely hot. My phone is completely factory stock. the bootloader is locked too. how to recover it now ? please help.
i tried entering recovery mode but as soon as i select recovery it gets back to google logo screen again.
right now i have kept the phone in freezer now.
my bootloader is locked .. can i still unlock it and flash factory image ?
help ?
not a single reply ? bump...
Are you able to communicate with the device using fastboot?
Try flashing the stock images via fastboot
You won't need an unlocked bootloader for this
post-mortem said:
Are you able to communicate with the device using fastboot?
Click to expand...
Click to collapse
yes im able to communicate with the device through fastboot. but my bootloader is locked.
wahur1 said:
yes im able to communicate with the device through fastboot. but my bootloader is locked.
Click to expand...
Click to collapse
Try the instructions at the top of the page here https://developers.google.com/android/images
It may work without unlocking the bootloader.
post-mortem said:
Try the instructions at the top of the page here https://developers.google.com/android/images
It may work without unlocking the bootloader.
Click to expand...
Click to collapse
whatever command i use it says OEM unlock is not allowed.
Just throwing out ideas that you may have already tried. If I understand right you cannot get into recovery which eliminates trying to sideload the stock image. Your bootloader is locked and it will not let you unlock so booting into TWRP is out of the question. Are you just wanting your phone operational again? Have you tried wiping/factory resetting with fastboot commands? i.e. fastboot erase userdata or fastboot format userdata.
wahur1 said:
whatever command i use it says OEM unlock is not allowed.
Click to expand...
Click to collapse
Have you tried flashing without unlocking the bootloader?
post-mortem said:
Have you tried flashing without unlocking the bootloader?
Click to expand...
Click to collapse
yes i have tried flashing by giving the fastboot command "flash-all.bat" it starts flashing and it stops in the initial stage by giving error " restarting bootloader" then I get 2nd error " bootloader locked" and process repeats again
toasterboy1 said:
Just throwing out ideas that you may have already tried. If I understand right you cannot get into recovery which eliminates trying to sideload the stock image. Your bootloader is locked and it will not let you unlock so booting into TWRP is out of the question. Are you just wanting your phone operational again? Have you tried wiping/factory resetting with fastboot commands? i.e. fastboot erase userdata or fastboot format userdata.
Click to expand...
Click to collapse
both command not working .. same bootloader locked message.
error message " Please unlock the device to activate this command"
anyone else can help ?
I would contact Google customer support. Even though my phone was out of warranty and I was not the original buyer (bought in eBay), they were willing to make a one-time exception for an RMA. I didn't use it because my phone is rooted and I was afraid of being charged for any repairs. As long as your phone is stock and unrooted, you have a chance. Just say that you think you have a hardware failure and while you understand that they are in no obligation to help, you would appreciate anything they can do.
Sent from my Pixel XL using Tapatalk