Database Info

[Q] Bricked one

os deleted and just stuck on one+ logo can boot in to twrp or fast boot what can i do?

brooklynchildxbc said:
os deleted and just stuck on one+ logo can boot in to twrp or fast boot what can i do?
Click to expand...
Click to collapse
Push a custom rom via adb and flash in recovery or flash stock images via fastboot

acuicultor said:
Push a custom rom via adb and flash in recovery or flash stock images via fastboot
Click to expand...
Click to collapse
i tried adb won't work and fastboot not doing anything i keeping getting a error saying that bootloader locked or can't erase
what really pisses me off i didn't even brick it a dumbass friend of mine did thinking he knew what he was doing.

brooklynchildxbc said:
i tried adb won't work and fastboot not doing anything i keeping getting a error saying that bootloader locked or can't erase
what really pisses me off i didn't even brick it a dumbass friend of mine did thinking he knew what he was doing.
Click to expand...
Click to collapse
Is fastboot working? Unlock bootloader and push custom recovery there. Go to adb sideload and that should work eventually. I had an issue with HTC One M7 - someone deleted sytem, and cyanogenmod installer helped, because it pushed CWM recovery, maybe try that one as well?

boober78 said:
Is fastboot working? Unlock bootloader and push custom recovery there. Go to adb sideload and that should work eventually. I had an issue with HTC One M7 - someone deleted sytem, and cyanogenmod installer helped, because it pushed CWM recovery, maybe try that one as well?
Click to expand...
Click to collapse
thank you so much i gave up then tried what you said then all of a sudden adb connected and i sideloaded the update file and got it back

brooklynchildxbc said:
thank you so much i gave up then tried what you said then all of a sudden adb connected and i sideloaded the update file and got it back
Click to expand...
Click to collapse
No problem. I'm glad I could help
Sent from my One using Tapatalk

brooklynchildxbc said:
thank you so much i gave up then tried what you said then all of a sudden adb connected and i sideloaded the update file and got it back
Click to expand...
Click to collapse
Don't give up.... I was in the same position like you for a couple days....and now is fix by my self..... If you unlock your bootloader try to lock back (fastboot oem lock) now try to flash via fastboot Philz Recovery ( try until is rebooting himself into recovery) .... After that put on a memory stick the new system .... You may need to mount the USB flash drive ..... That's exactly what I have done....Good Luck ...

It is damn near IMPOSSIBLE to actualy, truly "brick" these devices. There are way too many safeguards in place.
Be careful before announcing that you are "bricked". Bootlooping (which is what your device was doing) is not "bricked". As long as you have fastboot, you can always reflash recovery, and then use recovery to reflash your custom ROM (or you can bypass all of that and reflash the factory images from fastboot).
Don't panic, you know more than you think you know. Just don't get freaked out, and read. You'll be fine.

Pixel won't turn on.

Hi, my friend failed to resize the partition on his Pixel 1 OG to install OxygenOS. Now the only thing he could boot into was fastboot. He tried to unlock the bootloader (It was unlocked before he tried to resize partition, but after it bricked, the bootloader got locked for some reason) using the "fastboot oem unlock" command but since it was a Verizon model, the command returns: "bootloader: oem unlock is not allowed". I will provide some screenshot below.
I also provide the result of the "fastboot get-var all" command and there is no partition size. Usually there should be something there but not this time.
The recovery is gone and the only thing that actually work is the "Show barcode" option in fastboot.
When my friend chose the Reboot or Recovery mode, the Google logo appear for a >0.6 second then turn it self off.
Also tried booting into EDL mode but didn't seems to work. It might required a EDL cable.
Any help would be appreciated since my friend is pretty much desperate at this point since quaratine prevent him from getting a step out of his house lol.
He also send me his Pixel through mail lol.
How to resize partition guide (Might be helpful if i provide a link here?)
http://lunarixus.party/oxygenosguide/part1.html

any help?

Please...

Sounds creepy
But nothing can you do on locked condition
Sent from my Pixel using XDA-Developers Legacy app

plokyz said:
Sounds creepy
But nothing can you do on locked condition
Sent from my Pixel using XDA-Developers Legacy app
Click to expand...
Click to collapse
D*mn, thats kinda sad. But the Pixel XL could boot into EDL mode but not on the Pixel OG. I think I need to find a way to boot this into EDL mode. Can you help me?

enderzip said:
D*mn, thats kinda sad. But the Pixel XL could boot into EDL mode but not on the Pixel OG. I think I need to find a way to boot this into EDL mode. Can you help me?
Click to expand...
Click to collapse
I have the SAME issue that you do, and have been looking for a while.
Like literally the same thing happened to me as well, except my Bootloader is unlocked.

Voltz100999 said:
I have the SAME issue that you do, and have been looking for a while.
Like literally the same thing happened to me as well, except my Bootloader is unlocked.
Click to expand...
Click to collapse
I wish I have a unlocked bootloader . If I did, I will boot it into TWRP and try to repair the damaged file system. But that was far from what I currently can do.

enderzip said:
I wish I have a unlocked bootloader . If I did, I will boot it into TWRP and try to repair the damaged file system. But that was far from what I currently can do.
Click to expand...
Click to collapse
I would expect you to not be able to boot into TWRP, because I can't, even with an unlocked bootloader.

Voltz100999 said:
I would expect you to not be able to boot into TWRP, because I can't, even with an unlocked bootloader.
Click to expand...
Click to collapse
Did you get the WriteFailed error? Maybe fastboot were unable to detect the partition?

enderzip said:
Did you get the WriteFailed error? Maybe fastboot were unable to detect the partition?
Click to expand...
Click to collapse
Yes, fastboot cannot see a partition size for both boot slots.

Voltz100999 said:
Yes, fastboot cannot see a partition size for both boot slots.
Click to expand...
Click to collapse
Thats strange...

enderzip said:
Thats strange...
Click to expand...
Click to collapse
Yes, but that's what it was. Couldnt flash boot either. I just replaced it with an XL, as from what I've seen there's no hope for it.

Flashed the wrong boot.img

I ****ed up and flashed the wrong boot.img. I can't boot and I somehow lost my authorization for the PC so it won't let me issue the commands I need to flash the right boot.img, is it possible to fix?

Pasini said:
I ****ed up and flashed the wrong boot.img. I can't boot and I somehow lost my authorization for the PC so it won't let me issue the commands I need to flash the right boot.img, is it possible to fix?
Click to expand...
Click to collapse
It's a poor description to get a good helping attempt.
Anyway, generally speaking the way to fix this is using the official tool or a tool that works with your device and flash the official stock ROM.

SubwayChamp said:
It's a poor description to get a good helping attempt.
Anyway, generally speaking the way to fix this is using the official tool or a tool that works with your device and flash the official stock ROM.
Click to expand...
Click to collapse
Sorry, I'm not very good at this obviously. I am using platform-tools right now. I am getting "device unauthorized" when issuing adb reboot bootloader. I can boot to fastboot through recovery but when I try to flash the boot.img it just says < waiting for any device >. Earlier I fixed this by issuing "adb reboot-fastboot" and then flashing. But now I just get "$ADB_VENDOR_KEYS is not set" returned. That's why I'm wondering if theres any way to authorize the pc without a successful boot.

Pasini said:
Sorry, I'm not very good at this obviously. I am using platform-tools right now. I am getting "device unauthorized" when issuing adb reboot bootloader.
Click to expand...
Click to collapse
Not sure if you are mixing some things there, you are saying that you have "unauthorized device" through ADB commands but ADB works when device is on...but if you flashed a wrong boot image, could you boot to system some way?
Pasini said:
I can boot to fastboot through recovery but when I try to flash the boot.img it just says < waiting for any device >. Earlier I fixed this by issuing "adb reboot-fastboot" and then flashing.
Click to expand...
Click to collapse
You can't flash the boot image through recovery.
Pasini said:
But now I just get "$ADB_VENDOR_KEYS is not set" returned. That's why I'm wondering if theres any way to authorize the pc without a successful boot.
Click to expand...
Click to collapse
Because of a wrong (and also an unsigned image for your device) you have this message.
Which device you have? And have the bootloader unlocked?

Question Booting fine but showing "Your Device Is Corrupt" screen if bootloader is unlocked

I got a 6a today, with the intent of learning about rooting. I've never rooted before, but was pretty involved with iOS jailbreaking so kinda a similar vein.
I wanted to get to Android 13 to get a fresh start (as opposed to rooting on A12 and upgrading), so i downloaded the factory image. I used the flash-all.sh script, but it got stuck on "Rebooting into fastboot." It then booted into the "Your Device Is Corrupt" screen, and would get stuck on the Google logo when it was booting. I finally got the A13 factory image to boot, but the "Your Device Is Corrupt" screen still showed every time i boot *as long as the bootloader is unlocked*. When I lock the bootloader it seems to be fine. After talking to a couple friends that have been rooting for a while, they somewhat think that I've done something to the NAND and should send back the device for a replacement. I'm not sure what to do now. Any suggestions?

You're fine...all androids have a warning screen after being unlocked.

Zaxx32 said:
You're fine...all androids have a warning screen after being unlocked.
Click to expand...
Click to collapse
I hear you, but this is a prompt that showed before the typical bootloader warning. It says "Your device is corrupt. It can't be trusted and may not work properly. Visit this link on another device: https://g.co/ABH"
If I click the power button it continues on the the regular bootloader warning
My friends who have been rooting for years say that this is irregular and shouldn't happen aside from the first boot. It happens every single boot as long as the bootloader is unlocked

CobreDev said:
I hear you, but this is a prompt that showed before the typical bootloader warning. It says "Your device is corrupt. It can't be trusted and may not work properly. Visit this link on another device: https://g.co/ABH"
If I click the power button it continues on the the regular bootloader warning
My friends who have been rooting for years say that this is irregular and shouldn't happen aside from the first boot. It happens every single boot as long as the bootloader is unlocked
Click to expand...
Click to collapse
That specific "corrupt" message you are getting when your bootloader is unlocked sounds more ominous than it really is. If you peruse through the Pixel 6 and 6 Pro forums you'll see that many people have encountered this message without any negative side effects and there are a few ways to get rid of it. In the simplest terms it's basically just a hash mismatch.
One method that seems to work well is to sideload the OTA during the next update. Even just updating via the "normal" OTA may get rid of the corrupt message.

Lughnasadh said:
That specific "corrupt" message you are getting when your bootloader is unlocked sounds more ominous than it really is. If you peruse through the Pixel 6 and 6 Pro forums you'll see that many people have encountered this message without any negative side effects and there are a few ways to get rid of it. In the simplest terms it's basically just a hash mismatch.
One method that seems to work well is to sideload the OTA during the next update. Even just updating via the "normal" OTA may get rid of the corrupt message.
Click to expand...
Click to collapse
Ah interesting, so probably not corrupted NAND then. One friend told me to go ahead and sideloaded the Android 13 OTA (I’m on Android 13 currently), but i noticed in the root guide it specifically said *don’t* sideloaded the ota before rooting. If i sideloaded the A13 OTA now will i mess up anything for rooting, or should i just live with the error until the next update?

CobreDev said:
Ah interesting, so probably not corrupted NAND then. One friend told me to go ahead and sideloaded the Android 13 OTA (I’m on Android 13 currently), but i noticed in the root guide it specifically said *don’t* sideloaded the ota before rooting. If i sideloaded the A13 OTA now will i mess up anything for rooting, or should i just live with the error until the next update?
Click to expand...
Click to collapse
Nah you NAND is fine.
The very first thing you should do before doing anything is make sure you have flashed the A13 bootloader to both slots to avoid having problems with the new ARB and bricking your device, if you haven't already.
Not sure what root guide you are referring to and in what context they are saying that, but sideloading an OTA shouldn't mess anything up relating to being able to root. It's really up to you what you do. You can live with that message for another couple of weeks (Sept. 6 is when the next stable update should be released), sideload the OTA or even dirty flash the factory image again (that might get rid of the message).
But whatever you decide to do, don't forget to flash the A13 bootloader to both slots before anything!!! I've seen a handful of people already brick their phone because they did not do this.

Lughnasadh said:
Nah you NAND is fine.
The very first thing you should do before doing anything is make sure you have flashed the A13 bootloader to both slots to avoid having problems with the new ARB and bricking your device, if you haven't already.
Not sure what root guide you are referring to and in what context they are saying that, but sideloading an OTA shouldn't mess anything up relating to being able to root. It's really up to you what you do. You can live with that message for another couple of weeks (Sept. 6 is when the next stable update should be released), sideload the OTA or even dirty flash the factory image again (that might get rid of the message).
But whatever you decide to do, don't forget to flash the A13 bootloader to both slots before anything!!! I've seen a handful of people already brick their phone because they did not do this.
Click to expand...
Click to collapse
Alright, i’ll try sideloading the OTA. I’ve tried flashing the factory image several times and it hasn’t fixed it.
To flash the bootloader to both slots, i follow the instructions on the Factory Image download page where it says:
# If your active slot is ‘a’
fastboot --slot=other flash bootloader bootloader-raven-slider-1.2-8739948.img
fastboot set_active b
fastboot reboot bootloader
fastboot set_active a
fastboot reboot bootloader
fastboot reboot
# If your active slot is ‘b’
fastboot --slot=other flash bootloader bootloader-raven-slider-1.2-8739948.img
fastboot set_active a
fastboot reboot bootloader
fastboot set_active b
fastboot reboot bootloader
fastboot reboot
Is that correct? Thanks for your help!

CobreDev said:
Alright, i’ll try sideloading the OTA. I’ve tried flashing the factory image several times and it hasn’t fixed it.
To flash the bootloader to both slots, i follow the instructions on the Factory Image download page where it says:
# If your active slot is ‘a’
fastboot --slot=other flash bootloader bootloader-raven-slider-1.2-8739948.img
fastboot set_active b
fastboot reboot bootloader
fastboot set_active a
fastboot reboot bootloader
fastboot reboot
# If your active slot is ‘b’
fastboot --slot=other flash bootloader bootloader-raven-slider-1.2-8739948.img
fastboot set_active a
fastboot reboot bootloader
fastboot set_active b
fastboot reboot bootloader
fastboot reboot
Is that correct? Thanks for your help!
Click to expand...
Click to collapse
No problem and yep, that's correct. Just make sure you don't boot into the slot which still has A12 on it. Good luck!

CobreDev said:
Alright, i’ll try sideloading the OTA. I’ve tried flashing the factory image several times and it hasn’t fixed it.
To flash the bootloader to both slots, i follow the instructions on the Factory Image download page where it says:
# If your active slot is ‘a’
fastboot --slot=other flash bootloader bootloader-raven-slider-1.2-8739948.img
fastboot set_active b
fastboot reboot bootloader
fastboot set_active a
fastboot reboot bootloader
fastboot reboot
# If your active slot is ‘b’
fastboot --slot=other flash bootloader bootloader-raven-slider-1.2-8739948.img
fastboot set_active a
fastboot reboot bootloader
fastboot set_active b
fastboot reboot bootloader
fastboot reboot
Is that correct? Thanks for your help!
Click to expand...
Click to collapse
Slight correction in case you haven't done it already. They instruct you to go use "adb reboot fastboot" at the beginning. That is wrong because that will put you in fastbootd and you can't flash the bootloader from fastbootd. Instead, at the beginning use "adb reboot bootloader". This is if you use Option 2 in their directions.

Lughnasadh said:
Slight correction in case you haven't done it already. They instruct you to go use "adb reboot fastboot" at the beginning. That is wrong because that will put you in fastbootd and you can't flash the bootloader from fastbootd. Instead, at the beginning use "adb reboot bootloader". This is if you use Option 2 in their directions.
Click to expand...
Click to collapse
Figured that out, thanks. Unfortunately sideloading the OTA didn't fix it, so i'll wait for the september update to see if that fixes it. Thanks everyone for the help!

CobreDev said:
Figured that out, thanks. Unfortunately sideloading the OTA didn't fix it, so i'll wait for the september update to see if that fixes it. Thanks everyone for the help!
Click to expand...
Click to collapse
Did you manage to solve the problem? If you still have not got it I will tell you that the same thing happened to me and I tried to flash in all ways and in both slots without getting it and in the end I managed to solve it by flashing the latest rom with the pixel flasher, checking the option to flash in both slots and checking the two boxes "disable verity and disable (anotherone)", at the end of the flashing I did not get back what was corrupt, I hope it helps you, greetings and good luck!

dannyzamora said:
Did you manage to solve the problem? If you still have not got it I will tell you that the same thing happened to me and I tried to flash in all ways and in both slots without getting it and in the end I managed to solve it by flashing the latest rom with the pixel flasher, checking the option to flash in both slots and checking the two boxes "disable verity and disable (anotherone)", at the end of the flashing I did not get back what was corrupt, I hope it helps you, greetings and good luck!
Click to expand...
Click to collapse
i haven’t fixed it yet, because the September update hasn’t come out for Pixel 6a.
I’ll keep that in mind, thanks for the tip!

CobreDev said:
i haven’t fixed it yet, because the September update hasn’t come out for Pixel 6a.
I’ll keep that in mind, thanks for the tip!
Click to expand...
Click to collapse
Try with the last update

CobreDev said:
i haven’t fixed it yet, because the September update hasn’t come out for Pixel 6a.
Click to expand...
Click to collapse
??? It came out earlier this week. https://developers.google.com/android/images#bluejay

Ah, must've missed that thanks

CobreDev said:
Ah, must've missed that thanks
Click to expand...
Click to collapse
Did you manage to solve it?

dannyzamora said:
Did you manage to solve it?
Click to expand...
Click to collapse
I did, though fixed it by accidentally wiping it out. Oh well, it’s fixed now

CobreDev said:
I did, though fixed it by accidentally wiping it out. Oh well, it’s fixed now
Click to expand...
Click to collapse
Good news! Congratulations

Just got, just rooted, now on A13 Oct. and looking to "fix" this screen shouting to anyone who sees my phone boot, "come and get lunch".
Is this still the way?
ty

jackfrost909 said:
Just got, just rooted, now on A13 Oct. and looking to "fix" this screen shouting to anyone who sees my phone boot, "come and get lunch".
Is this still the way?
ty
Click to expand...
Click to collapse
Unless there's an FBI agent out to get you, nobody will care. Most people won't even know what an unlocked bootloader is. If you're scared of hackers so much, reflash stock and relock

Question Why i cant updated latest QPR A13 for my pixel 6a

after download and reboot apprear this error..refer photo..

Try shutting it down, entering fastboot mode and flashing it from here.

bfsr83 said:
Try shutting it down, entering fastboot mode and flashing it from here.
Click to expand...
Click to collapse
ok thanks..no need unlockboot loader rite?

Boi. said:
ok thanks..no need unlockboot loader rite?
Click to expand...
Click to collapse
You can't flash anything with a locked bootloader

ctfrommn said:
You can't flash anything with a locked bootloader
Click to expand...
Click to collapse
ok thanks..hmmm..

Boi. said:
ok thanks..no need unlockboot loader rite?
Click to expand...
Click to collapse
For Android Flash Tool you need to have OEM unlocking enabled in developer options, but don't need to actually have the bootloader unlocked beforehand. The tool will unlock your bootloader during the process (assuming you are able to unlock the bootloader, e.g. not a Verizon model). It will also lock it afterwards if you choose to do so.

bfsr83 said:
Try shutting it down, entering fastboot mode and flashing it from here.
Click to expand...
Click to collapse
already try..still not work

Boi. said:
already try..still not work
Click to expand...
Click to collapse
You probably need to be more specific. What exactly happened after using Android Flash Tool? How did you initially try to install QPR1B1? Are you using the latest Platform Tools? Do you have the latest USB drivers installed? Have you tried using an A to C cable using a USB 2.0 port?
If you're flashing environment is set up correctly, you can also try sideloading the OTA image.

bfsr83 said:
Try shutting it down, entering fastboot mode and flashing it from here.
Click to expand...
Click to collapse
Thank you!
For the last 4 years I was updating my Pixels by downloading full official image and flashing without -w option, then patching boot.img via magisk and this process worked flawlessy every time. Tried same method with my new Pixel 6a on bluejay-tp1a.220624.021.a1 and every time I'd flash September's update bluejay-tp1a.220905.004.a2 my phone wouldn't boot and I would get "Your device is corrupt. It can't be trusted" error followed by google boot image and then boot loop. OK I thought, I'll wait until I've got time for a clean flash and that will solve it. To my surprise, it did not... Flashed clean image with full wipe and still same issue So now I did it via Android Flash Tool and it worked! For curiosity, then flashed the same image I had issues with via ADB and it also works now So what was the cause of the problem remains a mistery to me...

Pakabidu said:
Thank you!
For the last 4 years I was updating my Pixels by downloading full official image and flashing without -w option, then patching boot.img via magisk and this process worked flawlessy every time. Tried same method with my new Pixel 6a on bluejay-tp1a.220624.021.a1 and every time I'd flash September's update bluejay-tp1a.220905.004.a2 my phone wouldn't boot and I would get "Your device is corrupt. It can't be trusted" error followed by google boot image and then boot loop. OK I thought, I'll wait until I've got time for a clean flash and that will solve it. To my surprise, it did not... Flashed clean image with full wipe and still same issue So now I did it via Android Flash Tool and it worked! For curiosity, then flashed the same image I had issues with via ADB and it also works now So what was the cause of the problem remains a mistery to me...
Click to expand...
Click to collapse
Update:
I think I was able to flash that image with ADB after doing with Android Flash Tool first is because it was the same image. Later tried flashing next month's update via ADB and had same issue again. So today decided to sideload November's update via ADB instead of flashing full image and that worked.
Just wonder what did I mess up for me not to be able to flash with ADB...

Pakabidu said:
Update:
I think I was able to flash that image with ADB after doing with Android Flash Tool first is because it was the same image. Later tried flashing next month's update via ADB and had same issue again. So today decided to sideload November's update via ADB instead of flashing full image and that worked.
Just wonder what did I mess up for me not to be able to flash with ADB...
Click to expand...
Click to collapse
That is really weird behaviour for a Pixel device. I update using the stock rom method for all my pixels and never had issues. I have the Pixel 6 and the only instance I got the device is corrupt when I tried to roll back the November update to the October update causing a bootloop.
I wonder if there is something wrong with the 6A and some people having issues with the oem unlocking being greyed-out. Hopefully, Google will fix the issue with a future patch or monthly update.