Related
Would it be possible to modify the .bin in an OTA sideload for a root? Am I missing a key point in how this works? Or is it just, no one's done it yet?
Edit: I guess it just took a passion and a situation. See thread for unlock.
Edit Part 2: Electric Boogaloo: Just a quick recap of what's happened here. From the bootloader screen on my Pixel 2 (Walleye) I ran the
Code:
Fastboot flashing lock_critical
command, which then gave me a menu asking if I really want to lock it, or unlock it, I clicked unlock, and here we are. So far, only @zinchalk has confirmed this working. I would love for more people to try this out on their Verizon Pixel 2's and come back with the results. This was either the weirdest fluke of all time, or the best mistake Verizon has ever made. Either way, I hope it works for you
Edit 3: Well there's the January Patch This looks like it 'fixes' the bypass.
Correction: Nevermind, nothing is confirmed yet. And the people have decided there is no way this could be patched that quickly.
Edit 4: I'm seeing way too many people posting about bricked phones. Please don't do this UNLESS YOU KNOW WHAT YOU ARE DOING. I cannot live knowing that someone ruined their phone with this method. Please be safe.
@SoloTSi97 has confirmed this does work on the January 5th security patch!
Edit 5: There it is, we have people confirming the Verizon OTA being pushed this late January is patching the fastboot unlock method. Keep this in mind down the road guys.
D3RP_ said:
Would it be possible to modify the .bin in an OTA sideload for a root? Am I missing a key point in how this works? Or is it just, no one's done it yet?
Click to expand...
Click to collapse
Have you found a way to unlock the bootloader on a Verizon phone?
Or are you thinking modify the .bin would achieve unlocking the bootloader?
As far as I've read, no one has bothered since you can purchase direct from Google and OEM unlock the bootloader. Then root through Magisk is simple.
Sent from my Pixel 2 using Tapatalk
Diesel_Jeremiah said:
Have you found a way to unlock the bootloader on a Verizon phone?
Or are you thinking modify the .bin would achieve unlocking the bootloader?
As far as I've read, no one has bothered since you can purchase direct from Google and OEM unlock the bootloader. Then root through Magisk is simple.
Sent from my Pixel 2 using Tapatalk
Click to expand...
Click to collapse
lmao not that I know of. But I know it's possible to update any android through adb sideload. I'm really just grasping for straws. But because of my current situation I have a Pixel 2 from Verizon, and i'm gonna have it for a while.
I've been out of the android game for a long time; just switched back from iPhone 7, to a Pixel 2 used with Verizon. Am I correct in assuming that the device is unable to be unlocked, etc.?
tailsthecat3 said:
I've been out of the android game for a long time; just switched back from iPhone 7, to a Pixel 2 used with Verizon. Am I correct in assuming that the device is unable to be unlocked, etc.?
Click to expand...
Click to collapse
Unless you know some magic way, it is locked. I don't even know where to start with this thing.
Sell the Verizon one to someone who doesn't care for root and buy one from Google?
I used Sunshine Root for my HTC m8 years ago. They might be an option in the future. Yet again, since the Google version is easily unlocked & rooted, I don't think anyone has even tried.
Sent from my Pixel 2 using Tapatalk
Thanks. Glad I didn't try using the method I saw on YouTube, etc.
tailsthecat3 said:
Thanks. Glad I didn't try using the method I saw on YouTube, etc.
Click to expand...
Click to collapse
Just a small update. From the fastboot menu, I did
Code:
Fastboot flashing lock_critical
Which gave me the option to ''unlock bootloader'. It can't be this easy, but uhhh. I'll keep this thread updated...
Surely it can't be that easy. I'd say start a thread if this hasn't been noted.
---------- Post added at 18:55 ---------- Previous post was at 18:54 ----------
D3RP_ said:
Just a small update. From the fastboot menu, I did
Code:
Fastboot flashing lock_critical
Which gave me the option to ''unlock bootloader'. It can't be this easy, but uhhh. I'll keep this thread updated...
Click to expand...
Click to collapse
^^
tailsthecat3 said:
Surely it can't be that easy. I'd say start a thread if this hasn't been noted.
---------- Post added at 18:55 ---------- Previous post was at 18:54 ----------
^^
Click to expand...
Click to collapse
OEM unlocking says Bootloader is unlocked. So uh, it was that easy... Gonna root and install TWRP in a second.
Final Update
So that worked. Currently rooted with TWRP on my Verizon Pixel 2. Spread the word, or don't.
D3RP_ said:
So that worked. Currently rooted with TWRP on my Verizon Pixel 2. Spread the word, or don't.
Click to expand...
Click to collapse
Can you give some screenshot proof on this?
Interesting. I've been watching to see if someone gets the bootloader unlocked for the Verizon Pixel 2. In looking at the manpage for the fastboot commands, all you've really done is tell the system to lock the critical partitions (bootloader) during flashing. Pretty cool that it brought up the unlock menu.
What happens if you run `fastboot flashing get_unlock_ability`?
lps1014 said:
Can you give some screenshot proof on this?
Click to expand...
Click to collapse
Does that prove anything?
D3RP_ said:
Does that prove anything?
Click to expand...
Click to collapse
This doesn't prove anything. Show us the bootloader screen with your phone's info. There will be a baseband number and the status of the bootloader. Cover your serial number.
[Edit]
You do have a custom kernel flashed though.. so I guess.
xtacocorex said:
Interesting. I've been watching to see if someone gets the bootloader unlocked for the Verizon Pixel 2. In looking at the manpage for the fastboot commands, all you've really done is tell the system to lock the critical partitions (bootloader) during flashing. Pretty cool that it brought up the unlock menu.
What happens if you run `fastboot flashing get_unlock_ability`?
Click to expand...
Click to collapse
Sorry for the late reply. When I do that, I get
Code:
(bootloader) get_unlock_ability: 0
I made a thread about this in the original Pixel XL section. In the OP I quickly jolted down what you did, can you go and explain in detail as it might also work with the OG Pixel's.
Thanks in advance :
https://forum.xda-developers.com/pixel-xl/how-to/verizon-pixel-bootloader-unlocked-t3726672
How did the OP pass the cert check and update checks?
TonikJDK said:
How did the OP pass the cert check and update checks?
Click to expand...
Click to collapse
edit
lps1014 said:
Can you give some screenshot proof on this?
Click to expand...
Click to collapse
I just ran the command like OP said and the "unlock bootloader prompt" appeared. I ran this from a stock verizon on 8.0. I now flashed twrp, magisk and have the current google 8.1 ota. I will give proof if you tell me what will suffice.
Hi all,
I have an OG Verizon Pixel that's now stuck at the bootloader. I haven't done any unlocking or ROM modifications. It was stock 8.1 and it broke pretty close to the January update.
Recovery mode says "Failed to boot to recovery mode".
Starting from the bootloader just loads back into it, but the screen gets off-centered (I can attach pics if it helps).
When the phone was working, I'd never done any of the in-OS tools to start the bootloader unlocking process. I'm not really sure what I should be trying, but nothing I have tried from fastboot seems to work because it's locked. I feel if I could reimage it all, maybe it would work again, but it doesn't look like I have that kind of access.
Verizon's only option was $150 to replace it out of warranty (and then only provided a 90-day warranty). I declined that and got a Pixel 2, but now I have the old phone. Is there anything I can do with it? Or is it just junk?
Thanks,
TBK
TromboneKenny said:
Hi all,
I have an OG Verizon Pixel that's now stuck at the bootloader. I haven't done any unlocking or ROM modifications. It was stock 8.1 and it broke pretty close to the January update.
Recovery mode says "Failed to boot to recovery mode".
Starting from the bootloader just loads back into it, but the screen gets off-centered (I can attach pics if it helps).
When the phone was working, I'd never done any of the in-OS tools to start the bootloader unlocking process. I'm not really sure what I should be trying, but nothing I have tried from fastboot seems to work because it's locked. I feel if I could reimage it all, maybe it would work again, but it doesn't look like I have that kind of access.
Verizon's only option was $150 to replace it out of warranty (and then only provided a 90-day warranty). I declined that and got a Pixel 2, but now I have the old phone. Is there anything I can do with it? Or is it just junk?
Thanks,
TBK
Click to expand...
Click to collapse
Try reflashing the same factory image ur on
If the bootloader isn't unlocked it is probably bricked. With an unlocked bootloader you could reflash a factory image and get it working but you cant do that with a locked bootloader.
shagbag913 said:
If the bootloader isn't unlocked it is probably bricked. With an unlocked bootloader you could reflash a factory image and get it working but you cant do that with a locked bootloader.
Click to expand...
Click to collapse
I could be wrong but I think u might be able to sideload like an Oreo preview build without bl unlock, idr though but yeah tl:;dw: your device is likely as bricked as a house so you should attempt to request and RMA
KittyRgnarok said:
I could be wrong but I think u might be able to sideload like an Oreo preview build without bl unlock, idr though but yeah tl:;dw: your device is likely as bricked as a house so you should attempt to request and RMA
Click to expand...
Click to collapse
You can sideload ota updates in the stock recovery, but I'm pretty sure that's it. He could try sideloading this months update and see. I could be wrong
shagbag913 said:
You can sideload ota updates in the stock recovery, but I'm pretty sure that's it. He could try sideloading this months update and see. I could be wrong
Click to expand...
Click to collapse
Yeah that's what I'm thinking. OP test this and if anything breaks report back
That's pretty odd that it would just break like that. If he hasn't messed with anything software related it could be a hardware issue
shagbag913 said:
You can sideload ota updates in the stock recovery, but I'm pretty sure that's it. He could try sideloading this months update and see. I could be wrong
Click to expand...
Click to collapse
I can't even get into recovery mode. It errors (see OP for the message). Would it be different if I initiated recovery mode from fastboot or adb?
TromboneKenny said:
I can't even get into recovery mode. It errors (see OP for the message). Would it be different if I initiated recovery mode from fastboot or adb?
Click to expand...
Click to collapse
I don't think it would be different. This sounds like a hardware issue, not software.
Today I made a mistake and possibly broke my Pixel permanently.
The bootloader was unlocked, TWRP was installed and the system was rooted and modified.
I intended to reset the device completely to factory settings (with the factory image), but locked the bootloader without thinking BEFORE restoring the system. This caused the Pixel to go into a boot loop, neither system nor recovery were available, I could only get into the bootloader, so it was soft-bricked. That wouldn't be a problem, I should be able to unlock the bootloader and install the factory image. But this is not possible, because for some reason I can't unlock the bootloader anymore.
"fastboot oem unlock" or "fastboot flashing unlock" fails with "oem unlock is not allowed".
I don't know exactly why the bootloader is locked without system, but it definitely is. I can also not boot anything, not the system and not any recovery. If anything other than the bootloader is loaded, the Google logo flashes briefly, then the Pixel reboots. I can't use adb because there is no recovery or system available, and practically all fastboot commands are locked because the bootloader is locked.
I've been looking for solutions, but haven't found any. Is the Pixel definitely broken, or is there maybe some way to make it usable again? I don't care if I would lose data, but it would be a real bummer if the Pixel would be broken now.
Thanks in advance for any suggestions (even if it's just to throw the phone away and move on).
You could try the Deuces script. It was designed for the Pixel 2. If you're hesitant to run the script, you can look at it in a text editor, and run the commands yourself while following along.
Although it shouldn't be needed, you could try fasboot flashing unlock_critical.
Another thing which may help is to use fastboot to simply boot: fastboot boot boot.img. If you are able to boot, you may be able to go back into the developer options to toggle allowing unlock.
post-mortem said:
You could try the Deuces script. It was designed for the Pixel 2. If you're hesitant to run the script, you can look at it in a text editor, and run the commands yourself while following along.
Click to expand...
Click to collapse
That unfortunatly doesn't work. It's only for unlocked or at least unlockable deviced. I still tried it, but most fastboot commands require the bootloader to be unlocked. flashing unlock, flashing unlock_critical oem unlock, flash, format, boot, --set-active all don't work with a non-unlockable bootloader.
Although it shouldn't be needed, you could try fasboot flashing unlock_critical.
Click to expand...
Click to collapse
Also fails with 'oem unlock is not allowed'.
Another thing which may help is to use fastboot to simply boot: fastboot boot boot.img. If you are able to boot, you may be able to go back into the developer options to toggle allowing unlock.
Click to expand...
Click to collapse
Fails with 'Command is not supported. Please unlock device to enable this command.'
This may be worth a punt
https://forum.xda-developers.com/pixel/help/help-asap-pixel-bricked-t3518905
junglism93 said:
This may be worth a punt
https://forum.xda-developers.com/pixel/help/help-asap-pixel-bricked-t3518905
Click to expand...
Click to collapse
No luck there. In my case I can't even boot to the system anymore (with fastboot continue), since anything else than bootloader just briefly flashes the boot animation, then my phone shuts off.
Marvin0509 said:
No luck there. In my case I can't even boot to the system anymore (with fastboot continue), since anything else than bootloader just briefly flashes the boot animation, then my phone shuts off.
Click to expand...
Click to collapse
Damn, well it was worth a shot. Hopefully someone with a bit more knowledge might pipe up with a solution at some point.
Sent from my Pixel using XDA Labs
junglism93 said:
Damn, well it was worth a shot. Hopefully someone with a bit more knowledge might pipe up with a solution at some point.
Click to expand...
Click to collapse
I found nothing that could help me, so I contacted Google, and they offered me a free RMA, which I gladly accepted.
Marvin0509 said:
I found nothing that could help me, so I contacted Google, and they offered me a free RMA, which I gladly accepted.
Click to expand...
Click to collapse
Definitely seems a non recoverable scenario and happy days on getting it RMA'd for free :good:
Sent from my Pixel using XDA Labs
Marvin0509 said:
I found nothing that could help me, so I contacted Google, and they offered me a free RMA, which I gladly accepted.
Click to expand...
Click to collapse
It's over a year old right?? And they RMAed it for free?
aholeinthewor1d said:
It's over a year old right?? And they RMAed it for free?
Click to expand...
Click to collapse
Over two years old, actually. I was really surprised as well, especially since it's my own fault that it doesn't work anymore. I don't know exactly why, but I certainly won't say no to this offer.
Marvin0509 said:
Over two years old, actually. I was really surprised as well, especially since it's my own fault that it doesn't work anymore. I don't know exactly why, but I certainly won't say no to this offer.
Click to expand...
Click to collapse
Interesting. Did you tell them you were messing with the bootloader, or did you play stupid?
post-mortem said:
Interesting. Did you tell them you were messing with the bootloader, or did you play stupid?
Click to expand...
Click to collapse
No, I told them the whole truth, that I rooted it, modified the system, and that it doesn't work at all anymore.
Marvin,
What google support did you contact? Can you share the link or contact details perhaps? I have exactly the same problem and I have not been able unlock the bootloader and fear I have a hard bricked device, with Google being the only solution...
Thanks
HeinrichSpy said:
Marvin,
What google support did you contact? Can you share the link or contact details perhaps? I have exactly the same problem and I have not been able unlock the bootloader and fear I have a hard bricked device, with Google being the only solution...
Thanks
Click to expand...
Click to collapse
I have a subscription for Google One, so I contacted support from one.google.com. They quickly talked to me, then added a Pixel support employee to the conversation. I think I could have also contacted Pixel support directly on this page: support.google.com/pixelphone/contactflow. However I'm not sure if this will work in your country, I'm from Germany and the page wants me to select my Pixel, then I could contact a support employee via chat or wait for a callback, but if I change the language to English, the page seems broken and is just blank.
Marvin0509 said:
Today I made a mistake and possibly broke my Pixel permanently.
The bootloader was unlocked, TWRP was installed and the system was rooted and modified.
I intended to reset the device completely to factory settings (with the factory image), but locked the bootloader without thinking BEFORE restoring the system. This caused the Pixel to go into a boot loop, neither system nor recovery were available, I could only get into the bootloader, so it was soft-bricked. That wouldn't be a problem, I should be able to unlock the bootloader and install the factory image. But this is not possible, because for some reason I can't unlock the bootloader anymore.
"fastboot oem unlock" or "fastboot flashing unlock" fails with "oem unlock is not allowed".
I don't know exactly why the bootloader is locked without system, but it definitely is. I can also not boot anything, not the system and not any recovery. If anything other than the bootloader is loaded, the Google logo flashes briefly, then the Pixel reboots. I can't use adb because there is no recovery or system available, and practically all fastboot commands are locked because the bootloader is locked.
I've been looking for solutions, but haven't found any. Is the Pixel definitely broken, or is there maybe some way to make it usable again? I don't care if I would lose data, but it would be a real bummer if the Pixel would be broken now.
Thanks in advance for any suggestions (even if it's just to throw the phone away and move on).
Click to expand...
Click to collapse
i tried flashing a stock ota image...it was successful, but on reboot, nothing has changed. still the same. u know of a solution? i cant find it anywhere. thanks
Hi,
Unfortunaltelly my magisk cant hide gpay (safetynet true). Im wondering about unroot my pixel3.
Please tell me, which way is the best to unroot/lock bootloader? If I flash blueline-image with - w in flash-all.bat, can i lock bootloader with any problems (bricks)? Sorry for my english.
Thx for advice.
Wysłane z mojego Pixel 3 przy użyciu Tapatalka
If you successfully flashed the factory image (no errors) without removing the -w flag you should be able to relock the bootloader, yes. I believe locking the bootloader will induce another wipe so be sure you have things backed up if you have used the phone since flashing the factory image.
I have not rooted my devices since Pixel 1 and things have changed since then so someone else can chime in to confirm, but flashing the full factory image should be a reliable way to return to pure stock.
I would strongly suggest you DO NOT lock the bootloader! Many who have ended up with a brick if something goes wrong. Unroot your device and see if gpay will work. You can flash the flash all batch file with the -w removed. But don't lock the bootloader.
jd1639 said:
I would strongly suggest you DO NOT lock the bootloader! Many who have ended up with a brick if something goes wrong. Unroot your device and see if gpay will work. You can flash the flash all batch file with the -w removed. But don't lock the bootloader.
Click to expand...
Click to collapse
Unrooted and unlocked will cause Google Pay not to work. I would suggest to just leave "Allow OEM unlocking" enabled.
'
83097markcynt said:
Unrooted and unlocked will cause Google Pay not to work. I would suggest to just leave "Allow OEM unlocking" enabled.
'
Click to expand...
Click to collapse
That's good to know. I don't use gpay so didn't know that.
Unlocking Verizon Bootloader
First off, is this even possible? Currently I don't know if I even want to, I'm mostly just curious. I do know that when I buy new phones I like to mess around with my old one. I currently have an AT&T sim working in the phone, have since I bought it at BestBuy. Secondly, if it is possible, how so? I figure there's gotta be a way.
jkday3 said:
First off, is this even possible? Currently I don't know if I even want to, I'm mostly just curious. I do know that when I buy new phones I like to mess around with my old one. I currently have an AT&T sim working in the phone, have since I bought it at BestBuy. Secondly, if it is possible, how so? I figure there's gotta be a way.
Click to expand...
Click to collapse
I'm not sure what you're asking? Is what possible?
jkday3 said:
First off, is this even possible? Currently I don't know if I even want to, I'm mostly just curious. I do know that when I buy new phones I like to mess around with my old one. I currently have an AT&T sim working in the phone, have since I bought it at BestBuy. Secondly, if it is possible, how so? I figure there's gotta be a way.
Click to expand...
Click to collapse
jd1639 said:
I'm not sure what you're asking? Is what possible?
Click to expand...
Click to collapse
You cannot unlock the bootloader on a Verizon device. It's software locked based on IMEI. The ones sold at Best Buy are Verizon versions and are fully locked.
Gpay works fine with magisk. If it's not working for you, I'd dig into why before unrooting and relocking.
If you don't want to do that, just flash the magisk uninstaller to get rid of root and then flash a custom kernel. Pretty much all custom kernels will hide an unlocked bootloader and allow you to pass safety net.
New here to this community.
I bought a pixel 3xl a few weeks ago and i wanted to root just to see what's new, but i now realize I don't need to root this almost perfect phone. I unrooted the phone with magisk. I have the factory img. File to use incase i did something wrong when rooting. I just want to be able to let my phone boot up normally again. Can someone please help me?
NightWingJbr said:
I bought a pixel 3xl a few weeks ago and i wanted to root just to see what's new, but i now realize I don't need to root this almost perfect phone. I unrooted the phone with magisk. I have the factory img. File to use incase i did something wrong when rooting. I just want to be able to let my phone boot up normally again. Can someone please help me?
Click to expand...
Click to collapse
I'm not sure what you mean by boot up normally? Do you mean the bootloader unlock warning when it first starts to boot? You can get rid of that by locking the bootloader but before I'd do that I'd flash the full factory image, including wiping the device with the -w not removed in the flash-all batch file.
jd1639 said:
I'm not sure what you mean by boot up normally? Do you mean the bootloader unlock warning when it first starts to boot? You can get rid of that by locking the bootloader but before I'd do that I'd flash the full factory image, including wiping the device with the -w not removed in the flash-all batch file.
Click to expand...
Click to collapse
Yes and thank you for your reply. J just want to know how to wipe the device" with the -w not removed in the flash-all batch file". That's the only thing i don't understand. If you could explain. So i can go back to boot up without the warning.
NightWingJbr said:
Yes and thank you for your reply. J just want to know how to wipe the device" with the -w not removed in the flash-all batch file". That's the only thing i don't understand. If you could explain. So i can go back to boot up without the warning.
Click to expand...
Click to collapse
See the "Factory reset via fastboot" section at https://forum.xda-developers.com/pixel-3/how-to/complete-pixel-3-how-to-guide-newbie-t3922269
This will not remove the warning at boot, but is a necessary step. To lock the bootloader, read all the posts (especially the ones that detail the consequences of relocking) at https://forum.xda-developers.com/pixel-3-xl/help/how-to-lock-bootloader-t3866074 and pick a method.
I strongly recommend against relocking the boot loader, though. It is easy to brick your phone during the relock process. Also, a locked bootloader severely limits your ability to recover a bricked phone. Just ignore the warning at boot message. Removing it may come at a high cost.
Thank you so much. I will ignore then..
what is -w..
jd1639 said:
I would strongly suggest you DO NOT lock the bootloader! Many who have ended up with a brick if something goes wrong. Unroot your device and see if gpay will work. You can flash the flash all batch file with the -w removed. But don't lock the bootloader.
Click to expand...
Click to collapse
i was wondering what -w is? probably a dumb question but i couldnt find anything on google about it
comic_nightwing said:
i was wondering what -w is? probably a dumb question but i couldnt find anything on google about it
Click to expand...
Click to collapse
In the flash-all batch file in the factory image the -w (part of a line in the batch file) controls whether it wipes clean or does a dirty install leaving apps and data (user).
Hello all,
I did a big mistake, I wanted to go back from DP 3 to Android 11 and once I was going to do the CMD steps, I downloaded the wrong Firmware for the Pixel 5
I didnt see that mistake until I started the steps and the phone turned off and did not turn on anymore.
I know I made a big mistake, but can I do to revert this? I try to restart the phone but nothing, not via power button for 10 or 20 or 30 sec.
Please help
vlc_marcos said:
Hello all,
I did a big mistake, I wanted to go back from DP 3 to Android 11 and once I was going to do the CMD steps, I downloaded the wrong Firmware for the Pixel 5
I didnt see that mistake until I started the steps and the phone turned off and did not turn on anymore.
I know I made a big mistake, but can I do to revert this? I try to restart the phone but nothing, not via power button for 10 or 20 or 30 sec.
Please help
Click to expand...
Click to collapse
No duplicated thread are permitted
Please help us to keep the forums neat
Thanks
vlc_marcos said:
I downloaded the wrong Firmware for the Pixel 5
Click to expand...
Click to collapse
So you used a firmware that was older or one that was for a different device?
Is the bootloader unlocked?
What exactly did you download?
Does the phone charge?
l7777 said:
So you used a firmware that was older or one that was for a different device?
Is the bootloader unlocked?
What exactly did you download?
Does the phone charge?
Click to expand...
Click to collapse
I used the firmware of pixel 4a 5g and I wanted to go from DP3 to android 11.
I cannot see the phone charging . I try long press in any of the buttons and different combinations and nothing. Zero signs of life
vlc_marcos said:
I used the firmware of pixel 4a 5g and I wanted to go from DP3 to android 11.
I cannot see the phone charging . I try long press in any of the buttons and different combinations and nothing. Zero signs of life
Click to expand...
Click to collapse
when its plugged into a computer does the computer see it at all?
thewraith420 said:
when its plugged into a computer does the computer see it at all?
Click to expand...
Click to collapse
not at all is there some kind of hard unbrick??
vlc_marcos said:
not at all is there some kind of hard unbrick??
Click to expand...
Click to collapse
Unfortunately i think your only option will be to send it in to google at this point.. wish you luck though maybe someone has an idea.
thewraith420 said:
Unfortunately i think your only option will be to send it in to google at this point.. wish you luck though maybe someone has an idea.
Click to expand...
Click to collapse
Mine bricked about a month ago and Google suggested uBreakiFix. They tried to do a force flash on it but it didn't work. They ended up replacing the motherboard which fixed it, but now my proximity sensor is always on. I don't know if they can fix that or if it will require another motherboard.
I have same problem, but i can go to bootloader. The problem my phone is locked bootloader and i don't have recovery mode. And when i try to flash it because of locked bootloader i can't do anything. Is there any solution for unbrick locked bootloader?
p_a_r_s_a7 said:
I have same problem, but i can go to bootloader. The problem my phone is locked bootloader and i don't have recovery mode. And when i try to flash it because of locked bootloader i can't do anything. Is there any solution for unbrick locked bootloader?
Click to expand...
Click to collapse
Did you use any special way to even turn on the phone or reach the bootloader?
vlc_marcos said:
Did you use any special way to even turn on the phone or reach the bootloader?
Click to expand...
Click to collapse
I did everything, unfortunately my bootloader is locked and that's problem. With locked bootloader i can't do anything. I had same problems with other phones before and i could unbrick. But for pixel devices i can't find some tool to unbrick.
p_a_r_s_a7 said:
I did everything, unfortunately my bootloader is locked and that's problem. With locked bootloader i can't do anything. I had same problems with other phones before and i could unbrick. But for pixel devices i can't find some tool to unbrick.
Click to expand...
Click to collapse
how did you end up with it like that with bootloader locked? what caused it?
I have the same issue like p_a_r_s_a7 with my Pixel 5.
Only fastboot mode: can't find valid operating system
After flashing the 'right' OTA image for Android 12 DP3 the device cannot be restored anymore.
The image was successfully flashed by 'adb sideload' as recommended.
Seems that a locked bootloader is not 100% save from 'flashed to death'
600 EURO paperwight.
I had this same issue on my 4a 5g and after many hours I managed to fix it. I don't recall exactly but I went through every option of flashing stock via fastboot and android flash tool it eventually worked this was 2 months ago
Cj719 said:
I had this same issue on my 4a 5g and after many hours I managed to fix it. I don't recall exactly but I went through every option of flashing stock via fastboot and android flash tool it eventually worked this was 2 months ago
Click to expand...
Click to collapse
But you could reach fastboot right?
Cj719 said:
I had this same issue on my 4a 5g and after many hours I managed to fix it. I don't recall exactly but I went through every option of flashing stock via fastboot and android flash tool it eventually worked this was 2 months ago
Click to expand...
Click to collapse
Android flash tool immediately detect the locked bootloader and stopped without flashing.
I've tried to check/uncheck every option but no luck. I've used Windows 10.
Did you used the common USB driver requested by Android flash tool ?
Anything else that could be special, eg Linux environment ( what distro, version .. )
Any detail could help..
speo said:
Android flash tool immediately detect the locked bootloader and stopped without flashing.
I've tried to check/uncheck every option but no luck. I've used Windows 10.
Did you used the common USB driver requested by Android flash tool ?
Anything else that could be special, eg Linux environment ( what distro, version .. )
Any detail could help..
Click to expand...
Click to collapse
Windows 10 laptop, adb minimal drivers, made sure device was detected, attempted through fastboot and android flash tool, that's the only things I remember my apologies.
speo said:
I have the same issue like p_a_r_s_a7 with my Pixel 5.
Only fastboot mode: can't find valid operating system
After flashing the 'right' OTA image for Android 12 DP3 the device cannot be restored anymore.
The image was successfully flashed by 'adb sideload' as recommended.
Seems that a locked bootloader is not 100% save from 'flashed to death'
600 EURO paperwight.
Click to expand...
Click to collapse
I send back to Google, i couldn't fix it
Cj719 said:
Windows 10 laptop, adb minimal drivers, made sure device was detected, attempted through fastboot and android flash tool, that's the only things I remember my apologies.
Click to expand...
Click to collapse
thank you anyway, it was a little light on the horizon at least ;-)
p_a_r_s_a7 said:
I send back to Google, i couldn't fix it
Click to expand...
Click to collapse
have you been charged ?
Mine is from another dealer, will see..