Hi guys,
I wanted to completly reset my nexus 5, but I forgot to flash a the stock recovery, before locking the bootloader (fastboot oem lock). The problem is, fastboot devices are not shown with CWM (my current custom recovery) in bootloader mode, so my PC can't recognize my phone in fastboot mode. How can I unlock the bootloader again, so I can flash the stock recovery?
Please Help me fast
Fastboot won't work in a custom recovery. Boot to the bootloader and fastboot will work. Then unlock your device.
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
Fastboot won't work in a custom recovery. Boot to the bootloader and fastboot will work. Then unlock your device.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Thank you, it did work
emspiele said:
Thank you, it did work
Click to expand...
Click to collapse
Glad you got. Adb works in recovery, fastboot works in the bootloader.
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
Glad you got. Adb works in recovery, fastboot works in the bootloader.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
This might be a stupid question. Is it safe to "relock" the bootloader if I have a custom recovery and root on my device? I assume "fastboot oem lock" is all I need to do. People indicate that I shouldn't leave my device's bootloader unlocked. Will this affect things like custom recovery and my root status?
Appreciate the help.
dcxgod said:
This might be a stupid question. Is it safe to "relock" the bootloader if I have a custom recovery and root on my device? I assume "fastboot oem lock" is all I need to do. People indicate that I shouldn't leave my device's bootloader unlocked. Will this affect things like custom recovery and my root status?
Appreciate the help.
Click to expand...
Click to collapse
Bootloader state has absolutely no relation to anything else. The only difference between having it locked and unlocked is certain fastboot commands, like flashing images.
Locking the bootloader is completely pointless if you have a custom recovery that doesn't use a password and/or no lock in Android.
Also, if you are rooted, install bootunlocker. The apk will let you lock/unlock from within Android without data loss. Will also let you reset tamper flags.
wangdaning said:
Also, if you are rooted, install bootunlocker. The apk will let you lock/unlock from within Android without data loss. Will also let you reset tamper flags.
Click to expand...
Click to collapse
Thanks. I keep my device locked. I don't lock TWRP (I guess I should).
Appreciate the answer!
Related
Hi, when the bootloader is **LOCKED**, will fastboot erase system/recovery work?
I need to ask here instead of actually trying it as I don't want to brick a device if it erases successfully.
nexus 9 with android 5
Thanks
From my experience (not on nexus, but i think it should be similar), "fastboot flash system/recovery " worked for me when bootloader is not unlocked. So, i don't see reasons why "fastboot erase" shouldn't work.
I think that the main thing with locked bootloader is that custom roms and recovery cannot load, but it shouldn't prevent you to change the system/recovery, even if it brick the device.
SK009 said:
Hi, when the bootloader is **LOCKED**, will fastboot erase system/recovery work?
I need to ask here instead of actually trying it as I don't want to brick a device if it erases successfully.
nexus 9 with android 5
Thanks
Click to expand...
Click to collapse
i would use fastboot format instead of erase, but yes commands will work with a locked bl.
My google pixel is now bricked or atleast i think it is. This is what i did.
I already had PA 7.1.2 installed on my phone along with GAPPS. Everything was just fine untill i thought to get rid of the "unlocked bootloader warning screen". Stupid me!
I wanted a rooted phone with custom recovery but without the annoying warning message when i restart my phone everytime. Something like "google cant check the corruption of my phone".
I got into the bootloader mode and locked my bootloader with "fastboot flashing lock". The huge mistake i did was that i never turned on the OEM unlock option in my developer settings nor the USB debugging mode. Now my phone would not start into system and recovery. It bootloops for ever if i did those.
I am in India and not sure how i will get it replaced by google. Can this be solved. The solution i can think of is unlocking OEM from fastboot mode. Now if i try "fastboot flashing unlock", it tells me "Failed (remote: oem unlock is not allowed).
Someone please help meeeee. I have no other phone. Pleaseeeeeeeeeee.....
Prem's Pixel said:
My google pixel is now bricked or atleast i think it is. This is what i did.
I already had PA 7.1.2 installed on my phone along with GAPPS. Everything was just fine untill i thought to get rid of the "unlocked bootloader warning screen". Stupid me!
I wanted a rooted phone with custom recovery but without the annoying warning message when i restart my phone everytime. Something like "google cant check the corruption of my phone".
I got into the bootloader mode and locked my bootloader with "fastboot flashing lock". The huge mistake i did was that i never turned on the OEM unlock option in my developer settings nor the USB debugging mode. Now my phone would not start into system and recovery. It bootloops for ever if i did those.
I am in India and not sure how i will get it replaced by google. Can this be solved. The solution i can think of is unlocking OEM from fastboot mode. Now if i try "fastboot flashing unlock", it tells me "Failed (remote: oem unlock is not allowed).
Someone please help meeeee. I have no other phone. Pleaseeeeeeeeeee.....
Click to expand...
Click to collapse
You can get into fastboot mode. Have you tried reinstalling your firmware? Can you fastboot boot into TWRP?
Try this utility to see if it can help.
https://forum.xda-developers.com/pixel/development/tool-skipsoft-android-toolkit-google-t3482761
Tulsadiver said:
You can get into fastboot mode. Have you tried reinstalling your firmware? Can you fastboot boot into TWRP?
Click to expand...
Click to collapse
Yes i tried reinstalling. When the installation begins it tells me that it cant continue cuz the OEM is not unlocked. When i boot into recovery, it bootloops non-stop.
Not sure what to do.
I am in the process of installing the skipsoft tool. Lets see. Thanks for your response. Much appretiated. I hope this works.
I tried skipsoft. No luck. It is asking to unlock the OEM from developer settings in order to unlock the bootloader, which is technically impossible.
Because my phone cant boot into its OS. Any other idea. Please. I spent a lot of money for this phone and now this. There should be some way to unlock OEM without enabling it in developer option.
God help me !!!!
Prem's Pixel said:
I tried skipsoft. No luck. It is asking to unlock the OEM from developer settings in order to unlock the bootloader, which is technically impossible.
Because my phone cant boot into its OS. Any other idea. Please. I spent a lot of money for this phone and now this. There should be some way to unlock OEM without enabling it in developer option.
God help me !!!!
Click to expand...
Click to collapse
Have you tried fastboot boot twrp, install twrp, wipe everything and reinstall PA?
Sent from my Google Pixel using XDA Labs
It is not allowing me to fastboot boot twrp because it tells me that i have to unlock the bootloader first. So when i try to unlock bootloader..it is asking me to unlock OEM from developer settings. Its kind of a paradox now...
I am stuck in between. My only stupidness is the main reason i got into this trouble.. why god why...!
I appretiate your help man... just help me plss.
Prem's Pixel said:
It is not allowing me to fastboot boot twrp because it tells me that i have to unlock the bootloader first. So when i try to unlock bootloader..it is asking me to unlock OEM from developer settings. Its kind of a paradox now...
I am stuck in between. My only stupidness is the main reason i got into this trouble.. why god why...!
I appretiate your help man... just help me plss.
Click to expand...
Click to collapse
Also not booting to stock recovery from bootloader?
You got yourself into a hell of a situation m8.
Sent from my Google Pixel using XDA Labs
Prem's Pixel said:
It is not allowing me to fastboot boot twrp because it tells me that i have to unlock the bootloader first. So when i try to unlock bootloader..it is asking me to unlock OEM from developer settings. Its kind of a paradox now...
I am stuck in between. My only stupidness is the main reason i got into this trouble.. why god why...!
I appretiate your help man... just help me plss.
Click to expand...
Click to collapse
Try this:
Boot into bootloader
Run fastboot command:
Fastboot continue
Sgace said:
Also not booting to stock recovery from bootloader?
You got yourself into a hell of a situation m8.
Sent from my Google Pixel using XDA Labs
Click to expand...
Click to collapse
I know
Tulsadiver said:
Try this:
Boot into bootloader
Run fastboot command:
Fastboot continue
Click to expand...
Click to collapse
When i run "fastboot continue" it still bootloops...
Prem's Pixel said:
I know
Click to expand...
Click to collapse
From fastboot:
fastboot erase system
fastboot erase data
fastboot erase cache
Everything should now be wiped clean so you need to flash factory image
Sent from my Google Pixel using XDA Labs
Sgace said:
From fastboot:
fastboot erase system
fastboot erase data
fastboot erase cache
Everything should now be wiped clean so you need to flash factory image
Sent from my Google Pixel using XDA Labs
Click to expand...
Click to collapse
This is what i get when i do those.
Fastboot erase system - please unlock device to enable this command. (Remote failure)
Fastboot erase data - same as above
Fastboot erase cache - same as above.
Thanks though. Still waiting for a miracle to happen.
Prem's Pixel said:
This is what i get when i do those.
Fastboot erase system - please unlock device to enable this command. (Remote failure)
Fastboot erase data - same as above
Fastboot erase cache - same as above.
Thanks though. Still waiting for a miracle to happen.
Click to expand...
Click to collapse
Damn bro, thats crap. Sorry I'm out of ideas for now.
If I come up with something will let you know.
Good luck m8.
Sent from my Google Pixel using XDA Labs
Prem's Pixel said:
This is what i get when i do those.
Fastboot erase system - please unlock device to enable this command. (Remote failure)
Fastboot erase data - same as above
Fastboot erase cache - same as above.
Thanks though. Still waiting for a miracle to happen.
Click to expand...
Click to collapse
Try this to get to stock recovery
https://www.google.com/amp/s/www.androidexplained.com/pixel-recovery-mode/amp/
Do you have a nandroid backup?
Sent from my Google Pixel using XDA Labs
Tulsadiver said:
Try this to get to stock recovery
https://www.google.com/amp/s/www.androidexplained.com/pixel-recovery-mode/amp/
Click to expand...
Click to collapse
I tried the steps mentioned in the link you provided, when i select recovery mode. It starts bootlooping. It bootloops everywhere except the fastboot screen. And, the fastboot screen shows that bootloader is locked loke i mentioned before. Back to where i started.
Sgace said:
Do you have a nandroid backup?
Sent from my Google Pixel using XDA Labs
Click to expand...
Click to collapse
Nope, i dont have a nandroid backup.
Sgace said:
Damn bro, thats crap. Sorry I'm out of ideas for now.
If I come up with something will let you know.
Good luck m8.
Sent from my Google Pixel using XDA Labs
Click to expand...
Click to collapse
Thank you very much for your patience.
Try to push the full OTA thru recovery..
Found here: https://developers.google.com/android/ota?hl=vi
Although I'm a nood, but maybe there's a solution found here
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 unlock the bootloader to install twrp and magisk, it's possible to lock the bootloader again without problems or the phone don't boot?
Toni Moon said:
I unlock the bootloader to install twrp and magisk, it's possible to lock the bootloader again without problems or the phone don't boot?
Click to expand...
Click to collapse
Locking you bootloader while TWRP and Magisk are installed will give you a guaranteed brick. Use a Fastboot Rom to return to stock, then you can lock it
If you want to keep TWRP and root, do not lock the bootloader. As the user mentioned above, you'll brick your device.
if i flash stock rom, than is that ok to lock the bootloader ? and how to lock it ?
majidshahab091 said:
if i flash stock rom, than is that ok to lock the bootloader ? and how to lock it ?
Click to expand...
Click to collapse
If you flash a full stock rom then yes. All you do is use the fastboot rom we talked about earlier, let the phone boot up (don't bother completing the setup process, just let the phone boot up), restart to bootloader, and use the following command from the command prompt on your pc:
Fastboot oem lock
It will give you a menu on your pone asking if you want to lock the bootloader. Tell it yes. It will then lock the bootloader, factory reset the phone, and then boot up normally with the bootloader locked. It's that easy.
ok thanks.one question. is that important to flash the stock rom using fastboot only ? or can i flash it using twrp ?
majidshahab091 said:
ok thanks.one question. is that important to flash the stock rom using fastboot only ? or can i flash it using twrp ?
Click to expand...
Click to collapse
I did it through twrp, worked just fine. Make sure to wipe beforehand though, don't want to risk bricking your phone
majidshahab091 said:
ok thanks.one question. is that important to flash the stock rom using fastboot only ? or can i flash it using twrp ?
Click to expand...
Click to collapse
Doing it with a Fastboot Rom will guarantee that things needing wiped will get wiped. When returning to full stock I will always recommend the Fastboot Rom just because of how it completely handles everything it does flawlessly. I imagine flashing a full rom in TWRP will work but I have never tried to return to stock this way
i did try stock using twrp and it was perfect
I have unlocked bootloader but in the end NOT installed TWRP or root (just wanted to test if i can live without it and still be able to install without wiping everything)
Now I just want to lock bootloader again for selling device.
Can I do so with simple fastboot command "fastboot oem lock" without bricking phone?
TaranQ said:
I have unlocked bootloader but in the end NOT installed TWRP or root (just wanted to test if i can live without it and still be able to install without wiping everything)
Now I just want to lock bootloader again for selling device.
Can I do so with simple fastboot command "fastboot oem lock" without bricking phone?
Click to expand...
Click to collapse
Use msm download tool to be sure. It will however wipe all.
TaranQ said:
I have unlocked bootloader but in the end NOT installed TWRP or root (just wanted to test if i can live without it and still be able to install without wiping everything)
Now I just want to lock bootloader again for selling device.
Can I do so with simple fastboot command "fastboot oem lock" without bricking phone?
Click to expand...
Click to collapse
You can, but if you are selling the phone I would still use a fastboot rom just to be sure everything is wiped and no data sensitive to you is being sold along with the phone.
Thanks a lot for the shared info here. This is just what I need and had been asking myself for quite some time now.??
So never lock bootloader with twrp and magisk installed.
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