Hi everybody,
i have a really strange issue. I unlocked my device using Asus unlocker. After some day i did a "Factory Reset". Now I'm stuck at the Bootlogo. I see there "The devices is unlocked". When i boot into fastboot and use "fastboot getvar all" i see as value for unlocked false.
I can not flash anything using fastboot in this case right? Is there a way to fix this?
thePatzen said:
Hi everybody,
i have a really strange issue. I unlocked my device using Asus unlocker. After some day i did a "Factory Reset". Now I'm stuck at the Bootlogo. I see there "The devices is unlocked". When i boot into fastboot and use "fastboot getvar all" i see as value for unlocked false.
I can not flash anything using fastboot in this case right? Is there a way to fix this?
Click to expand...
Click to collapse
I and a few other people I have checked with, with unlocked devices also have there getvar command display the same, "unlocked: no".
This is not an issue as far as I know, not sure why the getvar command displays unlocked as no, - but your device is unlocked.:good:
pjc21 said:
I and a few other people I have checked with, with unlocked devices also have there getvar command display the same, "unlocked: no".
This is not an issue as far as I know, not sure why the getvar command displays unlocked as no, - but your device is unlocked.:good:
Click to expand...
Click to collapse
Thanks for your answer. Then i have an other question. When i switch into the Fastboot menu should there be an USB icon? I only have 3 Icons
-> RCK, Android, Wipe Data. If i want to flash a stock rom using Fastboot should there be this USB icon?
thePatzen said:
Thanks for your answer. Then i have an other question. When i switch into the Fastboot menu should there be an USB icon? I only have 3 Icons
-> RCK, Android, Wipe Data. If i want to flash a stock rom using Fastboot should there be this USB icon?
Click to expand...
Click to collapse
No there is no usb icon in the new 4.2.1 bootloader.
Fastboot will automatically be running if you boot in bootloader while connected to pc.
http://forum.xda-developers.com/showthread.php?t=2195883
pjc21 said:
No there is no usb icon in the new 4.2.1 bootloader.
Fastboot will automatically be running if you boot in bootloader while connected to pc.
http://forum.xda-developers.com/showthread.php?t=2195883
Click to expand...
Click to collapse
Thanks! Tried this but it seems i can not flash anything like people describe in this thread:
http://forum.xda-developers.com/showthread.php?t=2179874
Seems we do not have luck
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.
Hi, I've got the 6045Y model which I've been trying to install twrp on, but I can't unlock the bootloader; it says oem unlock is not allowed.
I've tried on os x and linux with sudo but it's the same on both sides. As my phone isn't carrier locked, I don't understand why it's not allowing me to unlock the bootloader. There's also no oem unlock option in the developer options.
Any help?
You must do something wrong?
Can you trY with Windows
You need Alcatel Drivers+Minimal Adb and Fastboot
connect device you must enable debugging and then
-type "adb reboot-bootloader" to reboot into bootloader. The device should reboot to the screen showing "alcatel onetouch...powered by android". This is bootloader mode.
-Then type "fastboot -i 0x1bbb devices" should show some numbers and "fastboot" after the numbers
-Type "fastboot -i 0x1bbb oem device-info" shows device info including bootloader status (e.g. locked).
-Type "fastboot -i 0x1bbb oem unlock" to unlock the bootloader; after this you should get, for device info,
-Type "fastboot -i 0x1bbb oem device-info" and you should see "Device unlocked: true"
-To reboot normally: "fastboot -i 0x1bbb reboot"
Alek Dev said:
You must do something wrong?
Can you trY with Windows
You need Alcatel Drivers+Minimal Adb and Fastboot
connect device you must enable debugging and then
-type "adb reboot-bootloader" to reboot into bootloader. The device should reboot to the screen showing "alcatel onetouch...powered by android". This is bootloader mode.
-Then type "fastboot -i 0x1bbb devices" should show some numbers and "fastboot" after the numbers
-Type "fastboot -i 0x1bbb oem device-info" shows device info including bootloader status (e.g. locked).
-Type "fastboot -i 0x1bbb oem unlock" to unlock the bootloader; after this you should get, for device info,
-Type "fastboot -i 0x1bbb oem device-info" and you should see "Device unlocked: true"
-To reboot normally: "fastboot -i 0x1bbb reboot"
Click to expand...
Click to collapse
I tried on windows just now and the same thing happened: "FAILED (remote: oem unlock is not allowed)". I should mention though, I flashed twrp before unlocking the bootloader. I wonder if this is what's causing the problem.
I dont remember if this option was there, but you can try. Go into Settings/About Phone, scroll down and click on “build number” continuously until you see a toast notification telling you that you've enabled Developer Options. Go back to your Settings menu and enter Developer Options, scroll down and click on the “Enable OEM Unlock” checkbox, also make sure you enable USB Debugging while you're in the Developer Options menu.
DallasCZ said:
I dont remember if this option was there, but you can try. Go into Settings/About Phone, scroll down and click on “build number” continuously until you see a toast notification telling you that you've enabled Developer Options. Go back to your Settings menu and enter Developer Options, scroll down and click on the “Enable OEM Unlock” checkbox, also make sure you enable USB Debugging while you're in the Developer Options menu.
Click to expand...
Click to collapse
I have the same problem an update was pushed to the UK version last week 6045Y 5.0.2 -010 02 now unable to unlock bootloader i tried everything, so the bootloader must of changed BTW the update was about 458mb.
aradalien said:
I have the same problem an update was pushed to the UK version last week 6045Y 5.0.2 -010 02 now unable to unlock bootloader i tried everything, so the bootloader must of changed BTW the update was about 458mb.
Click to expand...
Click to collapse
same here in the uk have same version and cannot unlock bootloader anyone been sucssesful
aradalien said:
I have the same problem an update was pushed to the UK version last week 6045Y 5.0.2 -010 02 now unable to unlock bootloader i tried everything, so the bootloader must of changed BTW the update was about 458mb.
Click to expand...
Click to collapse
Same problem with same UK model and installed that patch too. I managed to flash TWRP and install PAC ROM still bootloader claims to be locked.
fastboot -i 0x1bbb oem unlock
FAILED (remote: oem unlock is not allowed)
fastboot -i 0x1bbb oem device-info
(bootloader) Device tempered:false
(bootloader) Device Unlock:false
easiest way is to download stock firmware with flsh tool for panasonic eluga switch (rebranded idol3),. Flash it with using the included flash tool. then unlock bootloader. Then use mobile upgrade Q 5.0.6 to go back to stock. And you are on stock uk firmware with unlocked bootloader.
I flashed someone's stock 6045Y(Europe) Firmware: 5.0.2-010 03 but couldn't unlock it either. After that I flashed 6045-i806-DCZ. I was really surpriced it let me do that while claiming to be locked and untempered. After that I did factory reset and flashed PAC-ROM. I'm not sure why should I bother to unlock bootloader if I already have TWRP and PAC-ROM flashed. I've no idea how can I even flash rom's with locked bootloader? Maybe oem device-info is bugged.
Anyways I download panasonic eluga switch firmwire, gonna test it after taking backups.
Reippi said:
I flashed someone's stock 6045Y(Europe) Firmware: 5.0.2-010 03 but couldn't unlock it either. After that I flashed 6045-i806-DCZ. I was really surpriced it let me do that while claiming to be locked and untempered. After that I did factory reset and flashed PAC-ROM. I'm not sure why should I bother to unlock bootloader if I already have TWRP and PAC-ROM flashed. I've no idea how can I even flash rom's with locked bootloader? Maybe oem device-info is bugged.
Anyways I download panasonic eluga switch firmwire, gonna test it after taking backups.
Click to expand...
Click to collapse
the Panasonic firmware flash also the aboot partition which has bootloader unlock enabled. without unlocked bootloader you could end with bricked device and the only solution is mobile upgrade q.
I did as you said and finally got bootloader unlocked, yey! Hopefully I don't have to go thought that process anytime soon. Thanks and thumps up!
Reippi said:
I did as you said and finally got bootloader unlocked, yey! Hopefully I don't have to go thought that process anytime soon. Thanks and thumps up!
Click to expand...
Click to collapse
no, its permanent.
I try to unlock my bootloader but two problems : oem unlock is not allowed and eluga sotware stuck at 2 %!!! I want install MM and I have stock rom can install the same the MM upgrade without unlock the bootloader? Regards
camelotto said:
I try to unlock my bootloader but two problems : oem unlock is not allowed and eluga sotware stuck at 2 %!!! I want install MM and I have stock rom can install the same the MM upgrade without unlock the bootloader? Regards
Click to expand...
Click to collapse
1-You didnt wrote phch model do you have.
2-newer heard of this issue . Install the drivers from the eluga firmware app, reboot, turn off your device, connect device to computer, run the download form the eluga firmware app.
jlocohustler said:
I tried on windows just now and the same thing happened: "FAILED (remote: oem unlock is not allowed)". I should mention though, I flashed twrp before unlocking the bootloader. I wonder if this is what's causing the problem.
Click to expand...
Click to collapse
And do you have sucess in flash? It worked? Do you have TWRP????
---------- Post added at 10:34 AM ---------- Previous post was at 10:30 AM ----------
Reippi said:
I flashed someone's stock 6045Y(Europe) Firmware: 5.0.2-010 03 but couldn't unlock it either. After that I flashed 6045-i806-DCZ. I was really surpriced it let me do that while claiming to be locked and untempered. After that I did factory reset and flashed PAC-ROM. I'm not sure why should I bother to unlock bootloader if I already have TWRP and PAC-ROM flashed. I've no idea how can I even flash rom's with locked bootloader? Maybe oem device-info is bugged.
Anyways I download panasonic eluga switch firmwire, gonna test it after taking backups.
Click to expand...
Click to collapse
That is the point from my previouse question! If you flash TWRP, your bootloader is unlocked by default!
persona78 said:
And do you have sucess in flash? It worked? Do you have TWRP????
---------- Post added at 10:34 AM ---------- Previous post was at 10:30 AM ----------
That is the point from my previouse question! If you flash TWRP, your bootloader is unlocked by default!
Click to expand...
Click to collapse
After flashing panasonic rom, you have unlockable bootloader.
Look here
http://forum.xda-developers.com/idol-3/general/guide-repair-idol-3-t3372076
I have 6045Y and panasonic rom work!
fastboot is detecting device but oem unlock/flashing unlock command not working.
I think that command has been changed since this june month security patch.
yash_rathore25 said:
fastboot is detecting device but oem unlock/flashing unlock command not working.
I think that command has been changed since this june month security patch.
Click to expand...
Click to collapse
It looks like MM update dont include aboot with commands for unlocking bootloader. You have to use mobile upgrade Q PC aPP, or Panasonic eluga firmware flash tool (for 6045Y) to go back to 5.0.2. Then unlock bootloader, and flash update to MM (or when on panasonic firmware youhave to use mobile upgrade Q to go back to stock). When on stock, wat for OTA MM or flash MM from XDA thread.
DallasCZ said:
It looks like MM update dont include aboot with commands for unlocking bootloader. You have to use mobile upgrade Q PC aPP, or Panasonic eluga firmware flash tool (for 6045Y) to go back to 5.0.2. Then unlock bootloader, and flash update to MM (or when on panasonic firmware youhave to use mobile upgrade Q to go back to stock). When on stock, wat for OTA MM or flash MM from XDA thread.
Click to expand...
Click to collapse
but fastboot flash command is working and also sending data to phone but unable to write on phone as bootloader is locked
yash_rathore25 said:
but fastboot flash command is working and also sending data to phone but unable to write on phone as bootloader is locked
Click to expand...
Click to collapse
because they have erased this command/s from aboot partition (bootloader)
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 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