My phone is stuck in a bootloop (water damage). However, I can access recovery mode successfully. The bootloader is locked.
I'm hoping to recover my pictures. Is there any way to access the internal memory from recovery with a locked bootloader? (I cannot flash TWRP because my bootloader is locked.)
I have a second functional Pixel (my wife's), if that can be of any help.
Thanks for any feedback!
Don't you have them on Google Photos?
Flipz77 said:
Don't you have them on Google Photos?
Click to expand...
Click to collapse
Sadly, no.
Related
I bought oneplus one then tried to push MIUI 5 into the phone, unlocked the bootloader with no problem and flashed TWRP, into recovery and wipe all data. but can't get the MIUI insatlled .
Can't boot the phone neither becase there is no OS, can't boot to recovery mode only fastboot mode.
I used the oneplus one toolkit to install the CM11S, would not let me do it . and accidentally I lock it again with toolbox. the problem comes that I can't unlock the bootloader anyway for somehow.
Pls help. my phone just stuck on the fastboot or 1+ booting. can't flash the img because it's locked!!!
How can I flash recovery under locked bootloader with fastboot?
jasonnew said:
How can I flash recovery under locked bootloader with fastboot?
Click to expand...
Click to collapse
You can't. The bootloader has to be unlocked to change recoveries.
This is why you don't use toolkits, you do things without thinking and then are unable to get yourself out of sticky situations.
NEVER relock bootloader without custom recovery installed AND rooted OS running!
if you do, you're unable to change tamper bit to unlock bootloader again.
that's why i never relock my bootloader! just to be safe.
Gesendet von meinem 1+ One
zephiK said:
You can't. The bootloader has to be unlocked to change recoveries.
This is why you don't use toolkits, you do things without thinking and then are unable to get yourself out of sticky situations.
Click to expand...
Click to collapse
+1 to this.
Transmitted via Bacon
Hi,
I have a Nexus 5 (d820) stucked in fastboot mode.
After doing some research, I got the TWRP working as recovery.
When I try to wipe, or flash any rom, even the original ones, I got some errors regarding read-only partitions.
I can LOCK and UNLOCK the boot at will... I can access fastboot/adb, etc...
How can I be sure my memory is defective? (I know it is probably the problem)
Anyone tried to replace the memory? (No warranty anymore)
Thanks for any help!
When you unlock the bootloader, does it stay unlocked?
I can unlock my bootloader but, after rebooting to fastboot, it says the bootloader is locked.
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
Hello, I have a vanilla Pixel 2 which corrupted itself and will not boot. It boots to recovery mode, but Bootloader is locked. I have not done a factory reset, and am attempting to recover the files. Fastboot mode works but will not allow temporary boot or unlocking of bootloader. I can access adb but only in sideload mode. OTA images successfully sideload but it still will not boot... After hours of scouring google I'm stumped. Any thoughts or suggestions welcome.
Hint: Add Pixel 2 to this thread's title thus mainly owners of such a phone get addressed.
jm001 said:
Hello, I have a vanilla Pixel 2 which corrupted itself and will not boot. It boots to recovery mode, but Bootloader is locked. I have not done a factory reset, and am attempting to recover the files. Fastboot mode works but will not allow temporary boot or unlocking of bootloader. I can access adb but only in sideload mode. OTA images successfully sideload but it still will not boot... After hours of scouring google I'm stumped. Any thoughts or suggestions welcome.
Click to expand...
Click to collapse
I see that u want to keep your files but sorry to say this but your gonna have to do a factory reset because their is no other way to fix this
To do this boot into recovery mode and perform a factory reset
If u can't boot into recovery mode u probably have to unlock bootloader than install twrp
But that's probably only gonna work if u enabled oem unlock and enabled usb debugger before your device got bricked
Because if u try to unlock the bootloader with oem unlock and usb debugger disenable your gonna receive error when trying to unlock bootloader
Try to start in recovery mode. Otherwise only restore is the option.
You can start mobile in fastboot mode. You can back up mobile.
adb backup -all
jm001 said:
Hello, I have a vanilla Pixel 2 which corrupted itself and will not boot. It boots to recovery mode, but Bootloader is locked. I have not done a factory reset, and am attempting to recover the files. Fastboot mode works but will not allow temporary boot or unlocking of bootloader. I can access adb but only in sideload mode. OTA images successfully sideload but it still will not boot... After hours of scouring google I'm stumped. Any thoughts or suggestions welcome.
Click to expand...
Click to collapse
On Android-side bootloader initializes ADB and mounts partitions. Hence check whether phone is accessible via ADB:
Code:
adb reboot
adb devices
If it is, and partitions got mounted, then you can fetch the user-data you are interested in by means of adb pull method.