Database Users

Bootlooping Nexus

My Nexus 6P is seemingly bootlooping.
I can boot into the bootloader menu but not into recovery. My bootloader is not unlocked so I cannot flash anything.
Issuing the command: "fastboot flashing unlock" does not work nor does "fastboot oem unlock". I cannot flash a custom recovery. Because my bootloader is locked.
Any help would be great.

avansledright said:
My Nexus 6P is seemingly bootlooping.
I can boot into the bootloader menu but not into recovery. My bootloader is not unlocked so I cannot flash anything.
Issuing the command: "fastboot flashing unlock" does not work nor does "fastboot oem unlock". I cannot flash a custom recovery. Because my bootloader is locked.
Any help would be great.
Click to expand...
Click to collapse
You say that your bootloader was not unlocked, so I'm assuming you didn't have developer options turned on and USB debugging checked before fastboot flashing unlock?

Fe Mike said:
You say that your bootloader was not unlocked, so I'm assuming you didn't have developer options turned on and USB debugging checked before fastboot flashing unlock?
Click to expand...
Click to collapse
I don't recall if i had them turned on or not. I know my device was enrolled in the Android beta program.

avansledright said:
I don't recall if i had them turned on or not. I know my device was enrolled in the Android beta program.
Click to expand...
Click to collapse
Do you remember if you modded anything prior to bootloop? The reason you can't unlock bootloader is because USB debugging isn't on. What version of Android were you on when it happened? I believe you can still use google factory Image to restore your phone.

Fe Mike said:
Do you remember if you modded anything prior to bootloop? The reason you can't unlock bootloader is because USB debugging isn't on. What version of Android were you on when it happened? I believe you can still use google factory Image to restore your phone.
Click to expand...
Click to collapse
The last thing i did was installed the new Google camera 4.2 but it worked fine after that.

avansledright said:
The last thing i did was installed the new Google camera 4.2 but it worked fine after that.
Click to expand...
Click to collapse
Since you don't have twrp you probably don't have a backup, which what I'm going to suggest will bring you back to stock and may lose everything. Though it's better than a bricked phone. Since I never did the flash-all.bat you may lose your stuff on internal SD. In this link, download the correct image your phone was on (under angler) and if using windows use the flash-all.bat in fastboot. If you're phone isn't 32 GB, extract all from zip and flash everything except user data. Forgive me for assuming you may be new. https://developers.google.com/android/nexus/images

Fe Mike said:
Since you don't have twrp you probably don't have a backup, which what I'm going to suggest will bring you back to stock and may lose everything. Though it's better than a bricked phone. Since I never did the flash-all.bat you may lose your stuff on internal SD. In this link, download the correct image your phone was on (under angler) and if using windows use the flash-all.bat in fastboot. If you're phone isn't 32 GB, extract all from zip and flash everything except user data. Forgive me for assuming you may be new. https://developers.google.com/android/nexus/images
Click to expand...
Click to collapse
Tried that. Continue to get the "Remote: (device is locked)" error every time it tries to flash a new image.
I'm not worried about losing any data on the phone. everything is backed up in the cloud.

,
avansledright said:
Tried that. Continue to get the "Remote: (device is locked)" error every time it tries to flash a new image.
I'm not worried about losing any data on the phone. everything is backed up in the cloud.
Click to expand...
Click to collapse
Do you get the error on all that you try to flash? Maybe just try the recovery img only to see if you can at least get that. If that works you should be able to sideload ota through recovery. With having a locked bootloader you might be at a loss. But on the flip side, having everything locked and not rooted you should be ok for warranty replacement.

avansledright said:
Tried that. Continue to get the "Remote: (device is locked)" error every time it tries to flash a new image.
I'm not worried about losing any data on the phone. everything is backed up in the cloud.
Click to expand...
Click to collapse
Fastboot is useless since your bootloader is locked. Try to ADB sideload the latest OTA image from Google and see if it will boot.
Sent from my Nexus 5X using Tapatalk

SlimSnoopOS said:
Fastboot is useless since your bootloader is locked. Try to ADB sideload the latest OTA image from Google and see if it will boot.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
How would i get into ADB mode without being able to boot into recovery? I thought of this as well but haven't been able to find a way to boot it into an ADB mode

avansledright said:
How would i get into ADB mode without being able to boot into recovery? I thought of this as well but haven't been able to find a way to boot it into an ADB mode
Click to expand...
Click to collapse
Ahh, missed that in your first post. I'm not sure how you can get recovery going if it's bootlooping when you access it.
Sent from my Nexus 5X using Tapatalk

avansledright said:
How would i get into ADB mode without being able to boot into recovery? I thought of this as well but haven't been able to find a way to boot it into an ADB mode
Click to expand...
Click to collapse
Check out this thread at post number 268 they mention using adb through mtp mode when not able to use recovery.
http://forum.xda-developers.com/nexus-6p/help/figure-brick-t3450921/page6

Fe Mike said:
Check out this thread at post number 268 they mention using adb through mtp mode when not able to use recovery.
http://forum.xda-developers.com/nexus-6p/help/figure-brick-t3450921/page6
Click to expand...
Click to collapse
Tried running through those steps. I can't even get a temporary boot of TWRP or stock recovery continues to bootloop even though WugFresh claims it was successful. Tried doing it manually via Fastboot and continue to get the error in flashing.
I just received my replacement phone. So I might just call it a day on this one. :crying:

avansledright said:
Tried running through those steps. I can't even get a temporary boot of TWRP or stock recovery continues to bootloop even though WugFresh claims it was successful. Tried doing it manually via Fastboot and continue to get the error in flashing.
I just received my replacement phone. So I might just call it a day on this one. :crying:
Click to expand...
Click to collapse
Good to hear about replacement! There are a few people in these forums that have a brick and can't get out of it. I thought you couldn't Hard brick these phones unless that was your goal. And most of these users who have bricks don't even know what causes it. Just a random reboot then loops. Kinda scary.

How to fix boot loop without OEM unlocking allowed or allow it using fastboot?

I have recently purchased Nexus 6P which has boot loop problem and I know that I could potentially fix this issue by side loading OTA image via adb or flashing full factory image via fastboot. Side loading has completed successfully, but it hasn't fixed boot loop issue. Also I cannot flash full factory image because OEM unlocking wasn't allowed.
Maybe someone knows how to allow OEM unlocking using fastboot? I will appreciate any help. Thanks in advance!

anokmik said:
I have recently purchased Nexus 6P which has boot loop problem and I know that I could potentially fix this issue by side loading OTA image via adb or flashing full factory image via fastboot. Side loading has completed successfully, but it hasn't fixed boot loop issue. Also I cannot flash full factory image because OEM unlocking wasn't allowed.
Maybe someone knows how to allow OEM unlocking using fastboot? I will appreciate any help. Thanks in advance!
Click to expand...
Click to collapse
Not possible. If the bootloader is locked and you can't boot into Android OS to allow OEM unlocking, you won't be using fastboot. Any luck using stock recovery to factory reset after a sideload? FYI all data on the phone will be lost.

RoyJ said:
Not possible. If the bootloader is locked and you can't boot into Android OS to allow OEM unlocking, you won't be using fastboot. Any luck using stock recovery to factory reset after a sideload? FYI all data on the phone will be lost.
Click to expand...
Click to collapse
You mean by factory reset formatting cache and data from recovery options?
Also I'm currently on MTC20F/6.0.1 build. Maybe it is reasonable to sideload more recent version?

anokmik said:
You mean by factory reset formatting cache and data from recovery options?
Also I'm currently on MTC20F/6.0.1 build. Maybe it is reasonable to sideload more recent version?
Click to expand...
Click to collapse
Yeah that's what I meant. Factory reset and cache wipe from stock recovery options. I guess it couldn't hurt to try sideloading 7.1.1.
It sort of sounds like the issue people had with the bugged versions of TWRP when restoring a backup, but the phone has stock recovery, right? I'll post a link to the thread where a bunch of people were collaborating to try to figure it out. You can search the thread to see if any suggestions help you out. I don't personally follow the thread, since I never had the issue and generally don't restore nandroid backups unless I absolutely have to. Usually if I need to restore I just plug into a PC and restore manually.
Edit: http://forum.xda-developers.com/nexus-6p/help/figure-brick-t3450921/page44
Not sure if a solution is there for you, but can't hurt to check out.

anokmik said:
I have recently purchased Nexus 6P which has boot loop problem and I know that I could potentially fix this issue by side loading OTA image via adb or flashing full factory image via fastboot. Side loading has completed successfully, but it hasn't fixed boot loop issue. Also I cannot flash full factory image because OEM unlocking wasn't allowed.
Maybe someone knows how to allow OEM unlocking using fastboot? I will appreciate any help. Thanks in advance!
Click to expand...
Click to collapse
When did you purchase the phone?
Was it used before purchasing?
What version of Android was running on the phone when it bootlooped?
Does your phone boot upto Android colorful dots animation or boots upto Google logo only?
Please answer these questions to give us insight about your problem.

RoyJ said:
Yeah that's what I meant. Factory reset and cache wipe from stock recovery options. I guess it couldn't hurt to try sideloading 7.1.1.
It sort of sounds like the issue people had with the bugged versions of TWRP when restoring a backup, but the phone has stock recovery, right? I'll post a link to the thread where a bunch of people were collaborating to try to figure it out. You can search the thread to see if any suggestions help you out. I don't personally follow the thread, since I never had the issue and generally don't restore nandroid backups unless I absolutely have to. Usually if I need to restore I just plug into a PC and restore manually.
Edit: http://forum.xda-developers.com/nexus-6p/help/figure-brick-t3450921/page44
Not sure if a solution is there for you, but can't hurt to check out.
Click to expand...
Click to collapse
Yep, this device has stock recovery and I will try to sideload 7.1.1 with factory reset and will reply here with the result. Also thanks for thread link! I will read it and maybe follow up in this thread with some questions.
fapste said:
When did you purchase the phone?
Was it used before purchasing?
What version of Android was running on the phone when it bootlooped?
Does your phone boot upto Android colorful dots animation or boots upto Google logo only?
Please answer these questions to give us insight about your problem.
Click to expand...
Click to collapse
1. Yes, it was used previously by someone.
2. 6.0.1. I guess. This is the build version that is specified in the stock recovery.
3. Unfortunately only Google boot logo appear on device's screen.
Will be very happy if this could help.

anokmik said:
Yep, this device has stock recovery and I will try to sideload 7.1.1 with factory reset and will reply here with the result. Also thanks for thread link! I will read it and maybe follow up in this thread with some questions.
1. Yes, it was used previously by someone.
2. 6.0.1. I guess. This is the build version that is specified in the stock recovery.
3. Unfortunately only Google boot logo appear on device's screen.
Will be very happy if this could help.
Click to expand...
Click to collapse
Can you manually get the device into the bootloader? If so you should be able to flash the full factory image following the instructions on Google's image download page. The flash.bat.all command works even with a locked bootloader and even if USB debugging is not enabled. It saved me a few times when I was soft bricked and nothing else helped.

jhs39 said:
Can you manually get the device into the bootloader? If so you should be able to flash the full factory image following the instructions on Google's image download page. The flash.bat.all command works even with a locked bootloader and even if USB debugging is not enabled. It saved me a few times when I was soft bricked and nothing else helped.
Click to expand...
Click to collapse
are you sure you can flash the factory img with a locked bootloader? I'm counting on this because I can flash rescue OTAs in recovery successfully but nothing changes after OTA sideload. I was hoping I can flash factory img but unfortunately my bootloader is locked.

Alsen Lea said:
are you sure you can flash the factory img with a locked bootloader? I'm counting on this because I can flash rescue OTAs in recovery successfully but nothing changes after OTA sideload. I was hoping I can flash factory img but unfortunately my bootloader is locked.
Click to expand...
Click to collapse
Try fastboot flashing unlock or fastboot oem unlock to unlock your bootloader.
---------- Post added at 09:04 AM ---------- Previous post was at 08:59 AM ----------
jhs39 said:
Try fastboot flashing unlock or fastboot oem unlock to unlock your bootloader.
Click to expand...
Click to collapse
I thought I read that flash-all.bat worked even with a locked bootloader but that may have been wrong. But if you can get into fastboot you should be able to unlock the bootloader.

RoyJ said:
Yeah that's what I meant. Factory reset and cache wipe from stock recovery options. I guess it couldn't hurt to try sideloading 7.1.1.
It sort of sounds like the issue people had with the bugged versions of TWRP when restoring a backup, but the phone has stock recovery, right? I'll post a link to the thread where a bunch of people were collaborating to try to figure it out. You can search the thread to see if any suggestions help you out. I don't personally follow the thread, since I never had the issue and generally don't restore nandroid backups unless I absolutely have to. Usually if I need to restore I just plug into a PC and restore manually.
Edit: http://forum.xda-developers.com/nexus-6p/help/figure-brick-t3450921/page44
Not sure if a solution is there for you, but can't hurt to check out.
Click to expand...
Click to collapse
Steps that I have done from stock recovery:
1. Wipe cache
2. Wipe data/ factory reset
3. Sideload 7.0 (angler-ota-nbd91k-32c2eac8) and the result is successful "script succeded: result was [1.000000]"
4. Wipe cache
5. Wipe data/ factory reset
6. Power off
7. Power on
Unfortunately boot loop persists and if I go back to recovery there is the same build version MTC20F (6.0.1).
jhs39 said:
Can you manually get the device into the bootloader? If so you should be able to flash the full factory image following the instructions on Google's image download page. The flash.bat.all command works even with a locked bootloader and even if USB debugging is not enabled. It saved me a few times when I was soft bricked and nothing else helped.
Click to expand...
Click to collapse
jhs39 said:
Try fastboot flashing unlock or fastboot oem unlock to unlock your bootloader.
I thought I read that flash-all.bat worked even with a locked bootloader but that may have been wrong. But if you can get into fastboot you should be able to unlock the bootloader.
Click to expand...
Click to collapse
For "fastboot oem unlock" command prompt returns "failed: remote: unknown command". I think this is because Google has changed such command to "fastboot flashing unlock", which gives me "failed: remote: oem unlock is not allowed". This because OEM unlocking hasn't been allowed from Developer Options by previous owner and now I cannot get there because of boot loop. Also have tried "flash-all.bat" from 7.0 latest factory image and on each step it returns error "failed: remote: device is locked. cannot flash images" and this is because of locked bootloader.
Possible solution?
In Stock recovery I have "Mount /system" option. Maybe someone can clarify what does it mean and could it potentially fix boot loop in some way? I have tried google for it, but unfortunately have no luck in finding information about this option.
Thanks in advance for any information!

anokmik said:
Yep, this device has stock recovery and I will try to sideload 7.1.1 with factory reset and will reply here with the result. Also thanks for thread link! I will read it and maybe follow up in this thread with some questions.
1. Yes, it was used previously by someone.
2. 6.0.1. I guess. This is the build version that is specified in the stock recovery.
3. Unfortunately only Google boot logo appear on device's screen.
Will be very happy if this could help.
Click to expand...
Click to collapse
Seems like the previous owner had upgraded to NOUGAT and then downgraded to 6.0.1 when he put the device up for sale. This issue occurs because of nougat. Star this issue on Google's website to bring to Google's attention to it
https://code.google.com/p/android/issues/detail?id=230848&thanks=230848&ts=1482412796

You might want to take a look at this:
https://drive.google.com/file/d/0Bz6x7k-VkpUJRjl6WjRhVmdXU0E/view
They are instructions for applying a rescue OTA, which supposedly works even if your bootloader is locked.
---------- Post added at 11:39 AM ---------- Previous post was at 11:29 AM ----------
There is also a toolkit you might want to take a look at:
http://www.wugfresh.com/nrt/

fapste said:
Seems like the previous owner had upgraded to NOUGAT and then downgraded to 6.0.1 when he put the device up for sale. This issue occurs because of nougat. Star this issue on Google's website to bring to Google's attention to it
https://code.google.com/p/android/issues/detail?id=230848&thanks=230848&ts=1482412796
Click to expand...
Click to collapse
Issue has star from me now. Thanks for the link!
jhs39 said:
You might want to take a look at this:
https://drive.google.com/file/d/0Bz6x7k-VkpUJRjl6WjRhVmdXU0E/view
They are instructions for applying a rescue OTA, which supposedly works even if your bootloader is locked.
There is also a toolkit you might want to take a look at:
http://www.wugfresh.com/nrt/
Click to expand...
Click to collapse
I have tried applying rescue OTA and that tool, but they doesn't help me.
The reason for my issue is that OEM unlocking hasn't been allowed by previous owner. So I'm looking for some options how to enable it from fastboot.

anokmik said:
Issue has star from me now. Thanks for the link!
I have tried applying rescue OTA and that tool, but they doesn't help me.
The reason for my issue is that OEM unlocking hasn't been allowed by previous owner. So I'm looking for some options how to enable it from fastboot.
Click to expand...
Click to collapse
Are you running the latest versions of ADB and Fastboot?

This sounds like an issue that would have been covered under warranty --for the original owner. Did you buy the phone knowing about the boot loop problem?

jhs39 said:
Are you running the latest versions of ADB and Fastboot?
Click to expand...
Click to collapse
These are the outputs from command prompt:
adb:
Android Debug Bridge version 1.0.36
Revision 0e9850346394-android
fastboot:
fastboot version 0e9850346394-android
I think that they are the latest, because I'm an Android dev and I'm updating SDK with tools as soon as new version come in.
jhs39 said:
This sounds like an issue that would have been covered under warranty --for the original owner. Did you buy the phone knowing about the boot loop problem?
Click to expand...
Click to collapse
Yep, I have known that device has boot loop issue and it was selling as-is for repair. Also I have known that this issue could be fixed, so it was hit or miss. Now I think that this was a miss.

It's starting to look that way. You would think there would be a way to reformat the drive and start from scratch like a computer. Maybe someone with programming knowledge will find a fix for you. It's odd the owner didn't RMA the phone rather than sell it as is/not working. Huawei was even fixing phones with similar issues for free a couple months out of warranty.

jhs39 said:
It's starting to look that way. You would think there would be a way to reformat the drive and start from scratch like a computer. Maybe someone with programming knowledge will find a fix for you. It's odd the owner didn't RMA the phone rather than sell it as is/not working. Huawei was even fixing phones with similar issues for free a couple months out of warranty.
Click to expand...
Click to collapse
Maybe there are some options for me to contact Huawei and ask for replacement? What are the requirements?

anokmik said:
Maybe there are some options for me to contact Huawei and ask for replacement? What are the requirements?
Click to expand...
Click to collapse
I don't think the warranty is transferable but it won't cost you anything to contact Huawei and see if they will help you out.
http://consumer.huawei.com/in/support/warranty-query/index.htm
You can go to this site to check if the device is still under warranty. I have read about them allowing RMA on 6Ps that were out of warranty so it's worth a try at least.

http://consumer.huawei.com/us/support/warranty-query/index.htm
Sorry this is the site to check if phone is in warranty within the US. Other site was for India.

Help!! plzz

Hi. I have got a problem. I currently have a lg nexus 4 . i accidently installed twrp in boot. so every time i open my phone twrp comes. and half of my touch screen does not work. so i can't fully swipe to install roms and cant type certain lettrs in keyboard in terminal and the bootloader is locked. so how do i get out of this . any help will be greatly appreciated . Thank you

How is your bootloader locked while having TWRP installed? Boot to bootloader and unlock it again. Then proceed with flashing the stock image.

n0b0dy666 said:
How is your bootloader locked while having TWRP installed? Boot to bootloader and unlock it again. Then proceed with flashing the stock image.
Click to expand...
Click to collapse
I used flashify to install twrp

098765 said:
Hi. I have got a problem. (...)
Click to expand...
Click to collapse
So read slowly and accurately:
[HOW-TO] How to flash a factory image / return to stock / unlock / root #

Or try this simple way of flashing factory image on your mako...
Nitin

nitin.chobhe said:
Or try this simple way of flashing factory image on your mako...
Nitin
Click to expand...
Click to collapse
it requres an unlocked bootlodaer

098765 said:
it requres an unlocked bootlodaer
Click to expand...
Click to collapse
Can you boot in to fastboot mode?
You can flash full OTA image even if the bootloader is locked. Flashing instructions here.
Nitin

nitin.chobhe said:
Can you boot in to fastboot mode?
You can flash full OTA image even if the bootloader is locked. Flashing instructions here.
Nitin
Click to expand...
Click to collapse
it seems there isn't one for nexus 4

nitin.chobhe said:
Can you boot in to fastboot mode?
You can flash full OTA image even if the bootloader is locked. Flashing instructions here.
Nitin
Click to expand...
Click to collapse
I don,t see one for my nexus 4

nitin.chobhe said:
Can you boot in to fastboot mode?
You can flash full OTA image even if the bootloader is locked. Flashing instructions here.
Nitin
Click to expand...
Click to collapse
Umm to apply update from adb a swipe is required which I can't

098765 said:
Hi. I have got a problem. I currently have a lg nexus 4 . i accidently installed twrp in boot. so every time i open my phone twrp comes. and half of my touch screen does not work. so i can't fully swipe to install roms and cant type certain lettrs in keyboard in terminal and the bootloader is locked. so how do i get out of this . any help will be greatly appreciated . Thank you
Click to expand...
Click to collapse
use fastboot, first unlock the bootloader with code fastboot oem unlock, then move the kernel of your android version to the fastboot folder and flash it on the boot partition, with the code fastboot flash boot boot.img, that's all.

098765 said:
I don,t see one for my nexus 4
Click to expand...
Click to collapse
And what is this: http://android.clients.google.com/p....signed-occam-LMY47V-from-LMY47O.050356b6.zip ??
Nitin

Bootloop and locked bootloader

Hello guys, I have a problem. I updated my Mi A1 and now I am in bootloop. I can't use MiFlash because I have locked bootloader.
I have tried fastboot oem edl, adb sideload in recovery but it didnt help. Any solution?

bad luck !! Test point method is the only way ? i faced the same situation ... please don't go to the service centre , they will tell you that the motherboard of your device needs a change .. and ask for a big amount of money if your phone is out of warranty ..!! search for the test point method here .. follow the video , and then follow the steps to go back to stock oreo from pie .. that's the only way ??

Same problem happened with me
My internal storage gets full and mobile automatically got switched off and bootloop
I tried to flash my self with adb command fastboot oem unlock
And successfully unlocked the bootloader & flashing process started but it keep flashing for long time whole night
So i decided to go near shop and gave him he tried with EDL test point and then phone goes in black screen He gave up :crying:
Now I'm thinking to go mi service centre but i get to know their ans is to change motherboard

PepeDaFrog said:
Hello guys, I have a problem. I updated my Mi A1 and now I am in bootloop. I can't use MiFlash because I have locked bootloader.
I have tried fastboot oem edl, adb sideload in recovery but it didnt help. Any solution?
Click to expand...
Click to collapse
What did u update? Stock rom? When did you buy the device? Can you get into fastboot? Can you get into recovery?

i just flashed the device for my wife with stock fastboot and locked the bootloader and of course it ends in bootloop.
i removed sim and micro sd and it boots up.

cheffy11 said:
What did u update? Stock rom? When did you buy the device? Can you get into fastboot? Can you get into recovery?
Click to expand...
Click to collapse
I have downgraded from pie to 8.1 oreo. Yes, i can get into fastboot and recovery but cant unlock the bootloader.

PepeDaFrog said:
I have downgraded from pie to 8.1 oreo. Yes, i can get into fastboot and recovery but cant unlock the bootloader.
Click to expand...
Click to collapse
did you try fastboot oem unlock?

Gamestrav said:
did you try fastboot oem unlock?
Click to expand...
Click to collapse
Yes, I have. I didnt work because I have OEM Unlock disabled and cant get into system.

PepeDaFrog said:
Yes, I have. I didnt work because I have OEM Unlock disabled and cant get into system.
Click to expand...
Click to collapse
What recovery do u have?

PepeDaFrog said:
I have downgraded from pie to 8.1 oreo. Yes, i can get into fastboot and recovery but cant unlock the bootloader.
Click to expand...
Click to collapse
You messed up because from stock Pie onwards, Xiaomi has implemented ARB which will bootloop your phone if you downgrade your rom.

barrack1 said:
You messed up because from stock Pie onwards, Xiaomi has implemented ARB which will bootloop your phone if you downgrade your rom.
Click to expand...
Click to collapse
Hi! Does testpoint method works here?

I'll try with a home made EDL cable, if this does not work I'll have to drive to the office for tools and try the test point. I'll update, but if anyone knows if this or that works and see this post on time, let me know!

UPDATE:
- EDL cable didn't work.
- Test point method worked fine, I thought that opening this phone would be harder, search for dissasembly tutorials on youtube and for test point method, the brick got back to life and it's fully working!

Locked Bootloader, No OS installed No Recovery Installed.

I got my 6P bootloader locked (ofcourse by accident) and now it has become a paperweight. is there any solution for this issue? I can boot into bootloader, but cannot flash anything. No recovery is installed and No OS is installed too...

Shabbirkt said:
I got my 6P bootloader locked (ofcourse by accident) and now it has become a paperweight. is there any solution for this issue? I can boot into bootloader, but cannot flash anything. No recovery is installed and No OS is installed too...
Click to expand...
Click to collapse
If the device can be seen by a computer, reflash the factory image. If not, no idea.

Dear friend if you have no OS installed and the Bootloader blocked the only thing you can try is using an OTG cable and a flash memory to download the latest version of the factory image but OTA and copy it to the flash memory and try to flash it from the stock recovery

felixpaz1992 said:
Dear friend if you have no OS installed and the Bootloader blocked the only thing you can try is using an OTG cable and a flash memory to download the latest version of the factory image but OTA and copy it to the flash memory and try to flash it from the stock recovery
Click to expand...
Click to collapse
i cannot do that. how can i access OTG ? booting into recovery reboots phone in endless loop of booting into Google written screen and Screen turns off...

Can you boot to bootloader? (With the device powered off, hold Volume Down + Power)
Then run
Code:
fastboot devices
If you see your mobile then you should be able to flash the factory ROM.
See section 10 in https://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928

ghost shell said:
Can you boot to bootloader? (With the device powered off, hold Volume Down + Power)
Then run
If you see your mobile then you should be able to flash the factory ROM.
See section 10 in https://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Click to expand...
Click to collapse
yup... fastboot devices detects the phone...
but when i try to flash factory image it says cannot flash as bootloader is locked.

Shabbirkt said:
yup... fastboot devices detects the phone...
but when i try to flash factory image it says cannot flash as bootloader is locked.
Click to expand...
Click to collapse
Code:
fastboot flashing unlock
Note that it will delete all your data.
Please let me know if after that you're able to flash the factory image.

ghost shell said:
Note that it will delete all your data.
Please let me know if after that you're able to flash the factory image.
Click to expand...
Click to collapse
i tried that brother... it says 'oem unlock is not allowed'.

Shabbirkt said:
yup... fastboot devices detects the phone...
but when i try to flash factory image it says cannot flash as bootloader is locked.
Click to expand...
Click to collapse
Shabbirkt said:
i tried that brother... it says 'oem unlock is not allowed'.
Click to expand...
Click to collapse
I don't know if this will help you but
Code:
fastboot boot twrp.img
Maybe you're able to unlock it or flash from there?

ghost shell said:
I don't know if this will help you but
Maybe you're able to unlock it or flash from there?
Click to expand...
Click to collapse
i appreciate your effort brother...
but i already tried that and no luck...

Shabbirkt said:
yup... fastboot devices detects the phone...
but when i try to flash factory image it says cannot flash as bootloader is locked.
Click to expand...
Click to collapse
Shabbirkt said:
i appreciate your effort brother...
but i already tried that and no luck...
Click to expand...
Click to collapse
No worries. Normally I wouldn't dig into it... but who knows, next time could be me in the same spot.
If you can boot using twrp then you can get adb shell with root, right?
Code:
adb shell getprop | grep -i unlock
I'm getting
[ro.oem_unlock_supported]: [1]
[sys.oem_unlock_allowed]: [1]
Click to expand...
Click to collapse
I'm wondering if you set those props to 1 maybe you'll be able to flash images again.
Code:
adb -d shell setprop ro.oem_unlock_supported 1
adb -d shell setprop sys.oem_unlock_allowed 1
...
Spending way more time than I should lol...
If the above doesn't work check these
https://old.reddit.com/r/AndroidQue...astboot_oem_unlock_without_enable_oem_unlock/
https://gist.github.com/zhuowei/79b6fbcd9ba9f1726163
https://forum.xda-developers.com/nexus-6p/general/to-unlock-phone-twrp-flashed-t3334083
https://forum.xda-developers.com/android/software/frp-destroyer-flashable-zip-t3920067

Wait Brother...
My phone just mysteriously booted up... I dun know how this happend or what made it do so... And Thanks a lot for your assistance...
Another thing is my phone has booted into FRP lock, and i kinda dun know the Email associated with it. Is there any way to bypass it?

Shabbirkt said:
Wait Brother...
My phone just mysteriously booted up... I dun know how this happend or what made it do so... And Thanks a lot for your assistance...
Another thing is my phone has booted into FRP lock, and i kinda dun know the Email associated with it. Is there any way to bypass it?
Click to expand...
Click to collapse
How don't you know the email associated with it ?