Develop Bugs

Phone bricked? Urgent help needed.

I'm having a problem with my nexus 5x. Yesterday, I decided I would factory restore my nexus from it being custom ROMd. I booted it into fastboot mode and relocked the bootloader, which wiped all the data. Then, when I went to flash the nought factory image, CMD and fastboot kept telling me my device is locked and I cannot flash to it. Because I locked the bootloader when the custom rom was still on it, it wont start up. I've downloaded older marshmallow builds from google too but they all give the same messages when flashing any of the files, including running the flash all command, saying that my device is locked and I cannot flash to it. Can anyone please help?

Jeez man! Locking the bootloader is the very last thing you do - if you do it at all because there's no good reason for it!
Cross my fingers: Do you have stock recovery installed?
If yes, you can adb sideload a OTA image.
If no, you're toast
https://developers.google.com/android/nexus/ota

berndblb said:
Jeez man! Locking the bootloader is the very last thing you do - if you do it at all because there's no good reason for it!
Cross my fingers: Do you have stock recovery installed?
If yes, you can adb sideload a OTA image.
If no, you're toast
https://developers.google.com/android/nexus/ota
Click to expand...
Click to collapse
Not toast. @arx160le would only have to flash the TOT to get it working again. He could do that regardless if he didn't feel like sideloading.

PiousInquisitor said:
Not toast. @arx160le would only have to flash the TOT to get it working again. He could do that regardless if he didn't feel like sideloading.
Click to expand...
Click to collapse
I cant seem to find a tot for 16 gb nexus 5x. Things arent look too good rn lmao.

arx160le said:
I cant seem to find a tot for 16 gb nexus 5x. Things arent look too good rn lmao.
Click to expand...
Click to collapse
Flash the 32. Boot to stock recovery and sideload the OTA. Problem solved.
Sent from my XT1650 using Tapatalk

PiousInquisitor said:
Flash the 32. Boot to stock recovery and sideload the OTA. Problem solved.
Sent from my XT1650 using Tapatalk
Click to expand...
Click to collapse
I just saw post 123 and thats what I did aha. It's working. Thank you so much.

Please help. I can not get to recovery. I can get to fastboot, but it is unrecognizable when i plug it in to a windows machine. It will recognize it when i plug it into MacOS. However the bootloader is locked, it will not allow me to unlock the bootloader from fastboot.

Caligula36 said:
Please help. I can not get to recovery. I can get to fastboot, but it is unrecognizable when i plug it in to a windows machine. It will recognize it when i plug it into MacOS. However the bootloader is locked, it will not allow me to unlock the bootloader from fastboot.
Click to expand...
Click to collapse
Follow the same guide that was just posted above. It's the only fix. Make sure you install all the drivers and boot the phone into download mode.

Windows tends to be a bugger sometimes when it comes to driver installs. My business laptop has 7 professional, my personal laptop has Windows 10. I never know which one will load the drivers I need.
You might just want to try a different computer if one is available. Or you could just delete any LG drivers you already have loaded and start fresh.
Sent from my Nexus 5X using Tapatalk

Flash factory image VZ wireless

Has anyone who has unlocked their bootloader successfully flashed a different factory image other than the image on their phone. I've tried numerous ways and have had no success after unlocking my bootloader. Thanks to anyone who may chime in
Sent from my Pixel XL using XDA-Developers mobile app

treIII said:
Has anyone who has unlocked their bootloader successfully flashed a different factory image other than the image on their phone. I've tried numerous ways and have had no success after unlocking my bootloader. Thanks to anyone who may chime in
Sent from my Pixel XL using XDA-Developers mobile app
Click to expand...
Click to collapse
Could you be more specific about how you flashed (flash_all or each individual image file), and what happened? Error or what?

cam30era said:
Could you be more specific about how you flashed (flash_all or each individual image file), and what happened? Error or what?
Click to expand...
Click to collapse
I've tried flashing the entire P factory image and it fails. I've tried with adb and fast boot on my PC. I also tried with skipsoft toolkit to see if that would work. It also fails. I have posted screen shots in that thread if you'd like to see the error. Thanks

treIII said:
I've tried flashing the entire P factory image and it fails. I've tried with adb and fast boot on my PC. I also tried with skipsoft toolkit to see if that would work. It also fails. I have posted screen shots in that thread if you'd like to see the error. Thanks
Click to expand...
Click to collapse
I'd suggest fastboot flash each image file separately (boot, sys, etc)

cam30era said:
I'd suggest fastboot flash each image file separately (boot, sys, etc)
Click to expand...
Click to collapse
I tried that and it seems to work but nothing changes

treIII said:
I tried that and it seems to work but nothing changes
Click to expand...
Click to collapse
What is it that you are expecting to change?

cam30era said:
What is it that you are expecting to change?
Click to expand...
Click to collapse
The build number and for OEM unlocking to be pickable. My bootloader is already unlocked so I thought flashing a different factory image would make it possible in developer options

treIII said:
The build number and for OEM unlocking to be pickable. My bootloader is already unlocked so I thought flashing a different factory image would make it possible in developer options
Click to expand...
Click to collapse
I agree. That's very strange. Does fastboot indicate success after flashing each image?

cam30era said:
I agree. That's very strange. Does fastboot indicate success after flashing each image?
Click to expand...
Click to collapse
Yes for some but the system image fails. Look in skipsoft tool thread and you'll see it. There are pictures

treIII said:
Yes for some but the system image fails. Look in skipsoft tool thread and you'll see it. There are pictures
Click to expand...
Click to collapse
If you don't use skipsoft, and in fastboot do:
fastboot flash system system.img
You still get this partition error?

cam30era said:
If you don't use skipsoft, and in fastboot do:
fastboot flash system system.img
You still get this partition error?
Click to expand...
Click to collapse
Yes

treIII said:
Yes
Click to expand...
Click to collapse
Very strange. I'm at a loss.

cam30era said:
Very strange. I'm at a loss.
Click to expand...
Click to collapse
So u have Verizon version? I'd like to see someone else try to flash a factory image to know where this goes

treIII said:
So u have Verizon version? I'd like to see someone else try to flash a factory image to know where this goes
Click to expand...
Click to collapse
No. Considering buying one. That's why I'm interested in this.

cam30era said:
No. Considering buying one. That's why I'm interested in this.
Click to expand...
Click to collapse
Yeah I wish someone else would chime in and try. I can't figure it out after trying for 4 hours last night and about two today. So I gave up and posted

I flashed the google factory image. . oem unlock will stay greyed out but that is not a big deal. bunch of people did this and discussion in this other thread. http://forum.xda-developers.com/pixel-xl/how-to/verizon-pixel-xl-unlocking-discussions-t3484497

zanoli99 said:
I flashed the google factory image. . oem unlock will stay greyed out but that is not a big deal. bunch of people did this and discussion in this other thread. http://forum.xda-developers.com/pixel-xl/how-to/verizon-pixel-xl-unlocking-discussions-t3484497
Click to expand...
Click to collapse
Not until you want to update to newer firmwares and there is no unlock method on those bootloaders. Converting to a GPS Pixel would be ideal if it is even possible.

joderme said:
Not until you want to update to newer firmwares and there is no unlock method on those bootloaders. Converting to a GPS Pixel would be ideal if it is even possible.
Click to expand...
Click to collapse
If you unlock now and update later your bootloader will remained locked unless Google finds a way to push a bootloader update with the coming OTA's that locks your bootloader after unlocking but that's highly unlikely. Plus, if you jump the gun and install the OTA before knowing the results of the OTA, you're kind of asking for something like this to happen. Hopefully Google doesn't find a deceitful way of pushing bootloader updates to lock us back up as you know they have already learned that a backdoor was found to unlock the Verizon bootloaders. They're not stupid and Jcase already said the sunshine guys were sending the exploit to Google so they would patch it. Vulnerabilities are too common these days on Android and these exploit seekers are quick to submit patches for them.

OK. Finally was able to flash the latest pixel factory image on my PXL. Minimal and fastboot and latest drivers from Google.

i sorta need help in this department as well... do i unzip the zip inside the zip??
im getting missing recovery.img and missing boot.sig i would like to make this a non verizon device. the flash-all.bat didnt work and i tried modifying it by removing -w but still same errors. spoon feed me please or teamview? its been 2 days

HELP! Re-locked Bootloader...No Recovery...No System....No Boot...NOTHING

SO I made a n00b mistake and accidentally reloacked bootloader trying to flash a fresh system image. I wanted to go back to stock after being rooted and unlocked.
Now i get the red screen of death and it just shuts off the phone. No recovery seems to be installed.
What do I do? Do I throw it in the garbage? Or is there a way to salvage this device?
Bootloader is locked and will not let me unlock again.
Thanks.

jdubya45 said:
SO I made a n00b mistake and accidentally reloacked bootloader trying to flash a fresh system image. I wanted to go back to stock after being rooted and unlocked.
Now i get the red screen of death and it just shuts off the phone. No recovery seems to be installed.
What do I do? Do I throw it in the garbage? Or is there a way to salvage this device?
Bootloader is locked and will not let me unlock again.
Thanks.
Click to expand...
Click to collapse
Can you boot into bootloader mode what so ever?

Yes only into bootloader. Can't unlock again though. Won't let me.

stevew84 said:
Can you boot into bootloader mode what so ever?
Click to expand...
Click to collapse
Only can get into bootloader but cannot unlock again. Everything else is gone.

jdubya45 said:
Yes only into bootloader. Can't unlock again though. Won't let me.
Click to expand...
Click to collapse
Have you tried to manually do this with ADB with the command prompt?
fastboot flashing unlock

stevew84 said:
Can you boot into bootloader mode what so ever?
Click to expand...
Click to collapse
stevew84 said:
Have you tried to manually do this with ADB with the command prompt?
fastboot flashing unlock
Click to expand...
Click to collapse
Yes. Fails. Remote fail and not allowed.

jdubya45 said:
Yes. Fails. Remote fail and not allowed.
Click to expand...
Click to collapse
I don't have the Pixel, so I'm going off of what I know from the 6P.
Does the Toolkit work for the Pixel? There has to be a way to get it working if you can get into bootloader.

stevew84 said:
I don't have the Pixel, so I'm going off of what I know from the 6P.
Does the Toolkit work for the Pixel? There has to be a way to get it working if you can get into bootloader.
Click to expand...
Click to collapse
I am not sure. I think I need Unlocked bootloader.

Actually i think you just need to reunlock using depixel8. That should unlock your bootloader and allow you to flash new firmware

Did you try using dePixel8 to to unlock your bootloader back? I would try that.
Sent from my Pixel XL using XDA Labs

Marghost said:
Did you try using dePixel8 to to unlock your bootloader back? I would try that.
Sent from my Pixel XL using XDA Labs
Click to expand...
Click to collapse
You have to be booted in Android for dePixel8 to work.

Am I missing something? why can't you just flash factory image again from the bootloader and then unlock your bootloader with the depixel8?
Sent from my Pixel XL using Tapatalk

MArtyChubbs said:
Am I missing something? why can't you just flash factory image again from the bootloader and then unlock your bootloader with the depixel8?
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
He said that he tried to unlock the bootloader again and it won't let him. With a locked bootloader, you can't flash the system images.
Sent from my Pixel XL using XDA-Developers mobile app

Moderator warning,
I have cleaned this thread. XDA does not allow users to discuss fraud on this site.

jdubya45 said:
SO I made a n00b mistake and accidentally reloacked bootloader trying to flash a fresh system image. I wanted to go back to stock after being rooted and unlocked.
Now i get the red screen of death and it just shuts off the phone. No recovery seems to be installed.
What do I do? Do I throw it in the garbage? Or is there a way to salvage this device?
Bootloader is locked and will not let me unlock again.
Thanks.
Click to expand...
Click to collapse
My mind is blown on how you accomplished this. Did you ERASE the partitions and then plan on flashing stock ones yourself? Why not just run the script (flash-all.bat) that would have automatically done the ENTIRE process for you, except re-locking the bootloader?
If all you did was re-lock the bootloader, it should have done a factory reset on the next boot and used the existing system partition. If you erased the system partition and then re-locked the bootloader, you are almost certainly screwed and had better hope Google has some mercy to let you RMA the phone.

Couple options you could try off the top of my head. The pixel has A/B patitions try adb sideloading an update zip to get it to switch to the backup partition that might still be there.
You could also try downloading the Factory images and extracting the system and go into fastboot and type
Code:
fastboot boot system system.img
and see if that works. Then if it boots on the temp image run deadpixel8 or whatever its called and reflash the stock image with the flash-all.bat.

have the same problem on my pixel after accidentally relocking after root before flashing back to stock.

Does anyone have the stock pixel xl recovery.img? I thinking if I boot into recovery "fast boot boot recovery.img" then I can add side load etc the ota from google.

jdubya45 said:
SO I made a n00b mistake and accidentally reloacked bootloader trying to flash a fresh system image. I wanted to go back to stock after being rooted and unlocked.
Now i get the red screen of death and it just shuts off the phone. No recovery seems to be installed.
What do I do? Do I throw it in the garbage? Or is there a way to salvage this device?
Bootloader is locked and will not let me unlock again.
Thanks.
Click to expand...
Click to collapse
Insert BRICK emoji here

Atlantian said:
Insert BRICK emoji here
Click to expand...
Click to collapse

Stuck in boot after unlocking bootloader and flashing twrp

Hey, I unlocked my bootloader using fastboot like I've done 100 times.
After that I flashed the newest TWRP for the 5x and then it wouldn't decrypt my data.
I figured I'd boot into android but it's just stuck in the boot animation, what can I do?
Edit:
I can't keep the bootloader unlocked, as soon as I reboot anywhere, it's locked again.

Shebee said:
Hey, I unlocked my bootloader using fastboot like I've done 100 times.
After that I flashed the newest TWRP for the 5x and then it wouldn't decrypt my data.
I figured I'd boot into android but it's just stuck in the boot animation, what can I do?
Edit:
I can't keep the bootloader unlocked, as soon as I reboot anywhere, it's locked again.
Click to expand...
Click to collapse
Can you boot into the bootloader? if you can try reflashing it back stock also when you flashed the latest TWRP, did you flash via fastboot or did you flash it in twrp?

dominoeflux said:
Can you boot into the bootloader? if you can try reflashing it back stock also when you flashed the latest TWRP, did you flash via fastboot or did you flash it in twrp?
Click to expand...
Click to collapse
Yes, I can boot, the issue seems to be that the bootloader won't stay unlocked.
As soon asni restart it's locked again. I think that's why twrp can't encrypt my partition. And that somehow messes up the Android installation.
Any ideas why the bootloader won't stay unlocked?

Shebee said:
Yes, I can boot, the issue seems to be that the bootloader won't stay unlocked.
As soon asni restart it's locked again. I think that's why twrp can't encrypt my partition. And that somehow messes up the Android installation.
Any ideas why the bootloader won't stay unlocked?
Click to expand...
Click to collapse
You have a phone with a replaced motherboard just like the individual in the link below. If the phone was recently replaced, I recommend getting another refurb. If that's not possible, the reddit link in this thread may be helpful for you:
https://forum.xda-developers.com/nexus-5x/help/secure-boot-enabled-rpmb-t3617929
Sent from my Nexus 5X using Tapatalk

SlimSnoopOS said:
You have a phone with a replaced motherboard just like the individual in the link below. If the phone was recently replaced, I recommend getting another refurb. If that's not possible, the reddit link in this thread may be helpful for you:
https://forum.xda-developers.com/nexus-5x/help/secure-boot-enabled-rpmb-t3617929
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Well that sucks :/
Guess I'll just wait for my next phone.

Bricked Pixel 2 XL Trying to root.

Here is what I did when I get my Pixel 2 XL out of the box today.
1. Followed the instructions at androidcentral.com/ how-root-google-pixel-2 and got a corrupt message after rebooting at the end. Only options were to try booting again or factory reset.
2. Figured that since I had 8.0.0 on the device and I used the latest 8.1.0 boot image, that was causing the problem. So I thought if I flashed 8.1.0, all would be good and I could start over.
3. Received several file not found errors when flashing. And my situation did not improve.
4. Can I just flash the original factory image and start over? Or am I totally screwed?
Thanks for any insight.

If you can boot into the bootloader you're most likely ok. Just download https://developers.google.com/android/images the image from google.

mikepopo99 said:
If you can boot into the bootloader you're most likely ok. Just download https://developers.google.com/android/images the image from google.
Click to expand...
Click to collapse
I can boot into the bootloader. My Internet connection has been a bit buggy, maybe the image was corrupted? Will try flashing a different image once it finally downloads.

Droid7of9 said:
I can boot into the bootloader. My Internet connection has been a bit buggy, maybe the image was corrupted? Will try flashing a different image once it finally downloads.
Click to expand...
Click to collapse
Here is the guide that many of us have used. Made by the legend himself :good:
https://forum.xda-developers.com/pixel-2-xl/how-to/guide-unlock-flash-root-pixel-2-xl-t3702418

Make sure your adb and fastboot files on the computer are up to date I had to do this on a Windows machine when I had similar results
Sent from my Pixel 2 XL using Tapatalk

gjkrisa said:
Make sure your adb and fastboot files on the computer are up to date I had to do this on a Windows machine when I had similar results
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
Thanks to all! Got it up and running again, maybe it was old fastboot/adb version. Might try and root again tomorrow. Will use that guide that was posted.

And now I am rooted, thanks again for the help. It must have been not having the latest adb/fastboot. Lesson learned.