Recover Pixel XL - Google Pixel ROMs, Kernels, Recoveries, & Other De

Hey folks! I have an OG Pixel XL - Stock ROM and locked bootloader.
Yesterday my phone just rebooted - no warning, and is now stuck on the Google logo screen. I can get the bootloader up by holding PWR + Volume Down, but when I go into recovery mode, I just get the Google Logo again - not what is expected with the broken Android icon, and the "No command" message.
I'd love to be able to flash the ROM back onto it - either stock or third-party since the phone is still in good condition from a hardware perspective.
Any other ways to flash a phone that seems to be soft-bricked?
Thanks!
UPDATE: When I try to use fastboot flashing unlock or similar commands, I get an error "FAILED (remote: 'oem unlock is not allowed')"

Kevingwpg said:
Hey folks! I have an OG Pixel XL - Stock ROM and locked bootloader.
Yesterday my phone just rebooted - no warning, and is now stuck on the Google logo screen. I can get the bootloader up by holding PWR + Volume Down, but when I go into recovery mode, I just get the Google Logo again - not what is expected with the broken Android icon, and the "No command" message.
I'd love to be able to flash the ROM back onto it - either stock or third-party since the phone is still in good condition from a hardware perspective.
Any other ways to flash a phone that seems to be soft-bricked?
Thanks!
UPDATE: When I try to use fastboot flashing unlock or similar commands, I get an error "FAILED (remote: 'oem unlock is not allowed')"
Click to expand...
Click to collapse
https://forum.xda-developers.com/t/...ck-twrp-factory-image-stock-recovery.3730229/

spiral777 said:
https://forum.xda-developers.com/t/...ck-twrp-factory-image-stock-recovery.3730229/
Click to expand...
Click to collapse
Doesn't seem to work. I get the same error that OEM Unlock is not allowed - I cannot flash TWRP

Related

Htc one mini 2 stuck in startscreen - fastboot mode available.

About two months back, I rooted my htc one mini 2.
Unlocked the bootloader, installed a new recovery (This one) and finally rooted the device. I wanted to install different fonts for it, and in the process relocked the bootloader again.
Now, after several weeks of not doing anything regarding the root, my phone has errors after errors.
First, Google Play stopped working, and along with it, Youtube and the Play Store of course.
About two weeks later, even the "internet" app stopped working.
Today i wanted to start my phone only to find it stuck in the starting screen. (Looks like this)
What I want to do now is get my phone factory resetted, not rooted anymore and WORKING.
What I tried to do is get the phone into fastbood mode (this worked) and connecting it with the "Minimal ADB and Fastboot" console. (This did NOT work)
Rebooting the device from the fastboot menu did not work, it either gets stuck in the loading screen again or directly enters fastboot.
What can I do to make my phone work again?
I hope you can help me :/
Montor
Montor said:
About two months back, I rooted my htc one mini 2.
Unlocked the bootloader, installed a new recovery (This one) and finally rooted the device. I wanted to install different fonts for it, and in the process relocked the bootloader again.
Now, after several weeks of not doing anything regarding the root, my phone has errors after errors.
First, Google Play stopped working, and along with it, Youtube and the Play Store of course.
About two weeks later, even the "internet" app stopped working.
Today i wanted to start my phone only to find it stuck in the starting screen. (Looks like this)
What I want to do now is get my phone factory resetted, not rooted anymore and WORKING.
What I tried to do is get the phone into fastbood mode (this worked) and connecting it with the "Minimal ADB and Fastboot" console. (This did NOT work)
Rebooting the device from the fastboot menu did not work, it either gets stuck in the loading screen again or directly enters fastboot.
What can I do to make my phone work again?
I hope you can help me :/
Montor
Click to expand...
Click to collapse
Try unlocking the bootloader again.Flash the custom recovery and then flash the stock rom available in the development section. It looks like your system partition got corrupted
csoulr666 said:
Try unlocking the bootloader again.Flash the custom recovery and then flash the stock rom available in the development section. It looks like your system partition got corrupted
Click to expand...
Click to collapse
How can i unlock the bootloader again?
The only way i know is via the console and "fastboot oem unlock" - i cant get my phone to connect though.
The available devices the console gives me are an emulator and three times my phone, which is/are offline.
Edit:
Stupid me. "Fastboot oem devices" and it shows my phone in fastboot mode.
Next problem: "fastboot oem unlock" does not work, and flashing the recovery with "fastboot flash myrecovery.img" doesn't work either :/
Edit 2: Managed to unlock the bootloader again (mistook the android folder with de adb folder, no unlocktoken there of course)
Directly after unlocking the bootloader again, the device went into recovery mode, showed the recovery starting logo, and went black.
After turning it back on, it got stuck in the starting screen again - will have to wait for it to run out of battery.
Edit 3: Flashed the recovery, but i can't seem to find a stock rom (only one i did find is this here - and the files are down...)
Solved it!
Just did a factory reset in bootloader menu.
(I hope i didn't forget anything, since I don't know s*** about android development)

New update bricked my phone

I was hoping I could get some help with this, I don't have an unlocked bootloader and everything is unfortunately stock, so here's hoping.
I was upgrading with verizon's upgrade tool while plugged into my computer and it got about halfway through updating before just stopping. Now the phone just automatically boots into fastboot flash mode. When I try to select any option aside from power off, restart bootloader, or barcodes it just flashes the motorola logo and goes back to the menu and the log says it failed to validate the system image. I looked at the unbrick thread and got nowhere and when I try to use the fastboot upgrade option with what I believe is the right image it gives me an not found error.
Is there anything I can do or is this just a paperweight now?
EnormousAxe said:
I was hoping I could get some help with this, I don't have an unlocked bootloader and everything is unfortunately stock, so here's hoping.
I was upgrading with verizon's upgrade tool while plugged into my computer and it got about halfway through updating before just stopping. Now the phone just automatically boots into fastboot flash mode. When I try to select any option aside from power off, restart bootloader, or barcodes it just flashes the motorola logo and goes back to the menu and the log says it failed to validate the system image. I looked at the unbrick thread and got nowhere and when I try to use the fastboot upgrade option with what I believe is the right image it gives me an not found error.
Is there anything I can do or is this just a paperweight now?
Click to expand...
Click to collapse
Was anything non-stock on your phone when you tried the update?

LOCK Oneplus 5 Bootloader (GUIDE)

Hi guys, if you are like me trying to lock the bootloader to get Android Pay, or Netflix back up and running without much fuss, I found a way to lock the bootloader.
WARNING: This will do a factory reset to your device, so do backups...
Requires:
- Official OOS flashed (Download here the full zip file for the latest OOS, you can flash through TWRP or stock Recovery)
- Latest Fastboot drivers and SDK file
- Basic knowledge of Fastboot commands
Guide:
- Boot the device into Bootloader mode (power the device with Volume up + Power Button)
- Connect to the PC
- Run the command "fastboot flashing lock"
- On the device, using the volume keys select "Yes" to lock the bootoader
And that's it, the 1st boot will take longer, but just wait.
Hope this helps =)
@hugoprh
It should be
Code:
fastboot oem lock
instead of
Code:
fastboot flashing lock
as OnePlus still uses the older LK. Only Nexus 6P & Pixel/Pixel XL have updated LK that includes these changes.
You should also mention that this procedures factory resets the device i.e. the internal memory is wiped.
Titokhan said:
@hugoprh
It should be
Code:
fastboot oem lock
instead of
Code:
fastboot flashing lock
as OnePlus still uses the older LK. Only Nexus 6P & Pixel/Pixel XL have updated LK that includes these changes.
You should also mention that this procedures factory resets the device i.e. the internal memory is wiped.
Click to expand...
Click to collapse
Hi, thanks for your feedback, but I did try "fastboot oem lock", as other XDA Oneplus 5 users have tried as well, without success, so I tried the Nexus 6p way "fastboot flashing lock" and it worked and this is the reason I decided to make this guide and I did write a "WARNING" about this procedure doing a factory reset, it's written in bold and underlined, please read carefully.
hugoprh said:
Hi, thanks for your feedback, but I did try "fastboot oem lock", as other XDA Oneplus 5 users have tried as well, without success, so I tried the Nexus 6p way "fastboot flashing lock" and it worked and this is the reason I decided to make this guide and I did write a "WARNING" about this procedure doing a factory reset, it's written in bold and underlined, please read carefully.
Click to expand...
Click to collapse
Let me explore the firmware - it would a curious case of hybridization then.
Regarding the warning: Yah, my bad... missed it somehow.
Trying to relock my bootloader, everytime I get to the fastboot screen I scroll through to "START" and select it using the power button the phone shuts off and reboots. Having a hard time getting into fastboot. any suggestions?
rgreene1971 said:
Trying to relock my bootloader, everytime I get to the fastboot screen I scroll through to "START" and select it using the power button the phone shuts off and reboots. Having a hard time getting into fastboot. any suggestions?
Click to expand...
Click to collapse
I was able to figure out my fastboot issues and able to flash twrp and revert back to a stock image, however when I try to lock the boot loader i get the error "FAILED (remote: flashing lock is not allowed).
Any ideas on the direction I need to go?
rgreene1971 said:
I was able to figure out my fastboot issues and able to flash twrp and revert back to a stock image, however when I try to lock the boot loader i get the error "FAILED (remote: flashing lock is not allowed).
Any ideas on the direction I need to go?
Click to expand...
Click to collapse
+1
rgreene1971 said:
I was able to figure out my fastboot issues and able to flash twrp and revert back to a stock image, however when I try to lock the boot loader i get the error "FAILED (remote: flashing lock is not allowed).
Any ideas on the direction I need to go?
Click to expand...
Click to collapse
You need to turn on OEM Unlocking in Developer Settings. If for any reason OEM Unlocking is freezed, flash Magisk and then turn on OEM Unlocking. Flash the stock recovery and the lock bootloader command. It should work flawless!
Don't forget the backup!
Why lock? Why not just use Magisk? That works fine with Android Pay.
You don't need to lock your bootloader to use Netflix
nagorimayank said:
You need to turn on OEM Unlocking in Developer Settings. If for any reason OEM Unlocking is freezed, flash Magisk and then turn on OEM Unlocking. Flash the stock recovery and the lock bootloader command. It should work flawless!
Don't forget the backup!
Click to expand...
Click to collapse
I am getting the same error saying that Flashing Lock is not allowed.I did what you said to do but the i can't turn on the OEM Unlocking in Developer Settings since it is greyed out.
What should i do?
mullafabz said:
I am getting the same error saying that Flashing Lock is not allowed.I did what you said to do but the i can't turn on the OEM Unlocking in Developer Settings since it is greyed out.
What should i do?
Click to expand...
Click to collapse
What I did was install custom ROM, the option isn't greyed out. Then try again. But make sure you install stock ROM and recovery before bootloader lock.
beache said:
What I did was install custom ROM, the option isn't greyed out. Then try again. But make sure you install stock ROM and recovery before bootloader lock.
Click to expand...
Click to collapse
I managed to lock back the bootloader but now am stuck in an bootloop.
mullafabz said:
I managed to lock back the bootloader but now am stuck in an bootloop.
Click to expand...
Click to collapse
You have to format data in recovery

Bricked leeco le2

Hi guys,
I've a leeco le2, it's in some sort of bootloop. I now have a phone which I hope is not actually bricked.
To cut to the chase:
The phone boot loops - it shows the "Leeco" on the black background for less than a second, then reboots, after 2 seconds, it comes back up with the "Leeco" and reboots, and so on.
I can get into fastboot mode. Interestingly, the status shows "Device is LOCKED"
I cant get to recovery mode. It just goes into the boot loop again.
Using the adb tools, I cant issue the "fastboot flashing unlock" or "fastboot oem unlock" commands because it returns: "FAILED (remote: 'oem unlock is not allowed')"
I am unable to get into the phone OS to change the settings because the phone is boot looping
. I am flashed several time in flashone,qfil and Miracle thunder but problem is same.
Given the fact I am unable to get to recovery, I am unable to sideload an OTA zip. And given the fact that I cant boot into the OS, I cant enable oem unlocking.
Do I have any hope at resurrecting this phone in any way? please help me
Check this : https://forum.xda-developers.com/t/...-le-2-s3-noob-friendly.3515555/#post-69996355

Stuck on MIUI logo

I seem to be stuck in a boot loop. I can hit power button and volume up options to reboot, safe mode etc - tried all of them and unable to get past the MIUI logo - It just sits on the logo until the battery runs out. I can get into fastboot but unable to do anything once there - the bootloader is locked, and it seems the only way to unlock it is to allow it by going into developer mode on the phone - which I can't do because I'm stuck at the MIUI logo!
I have tried to use MIPCSuite, ADB/Fastboot tools - but like I say all commands fail as unable to unlock bootloader.
I don't mind losing any data - but is there any way to unbrick this? Thanks in advance!

Categories

Resources