Question Phone bricked trying to update December patch - Google Pixel 6 Pro

Hey guys, so I used googles flash tool to update December patch and it keeps failing at writing to phone 1 of 11.
It's now in a bootloop but can access fastboot.
Ive tried to completely reset the phone manually using adb but it fails. It just doesn't work and aborts basically the phone rejects all data transmission.
What am I doing wrong or can I get a more detailed way to reset the phone completely.
-Edit-
I was also rooted and was following the guide for rooted December 12.
The main error is
(Error reading sparse file)

Why did you use the flash tool? General recommendation is, as long as you're running stock, just use the full OTA packages.
For the flash tool to be usable you need to OEM unlock your phone (while it's in a working state!).
If you can access fastboot you should be able to access recovery as well, where you can flash the full OTA, which should fix your issue.

fonix232 said:
Why did you use the flash tool? General recommendation is, as long as you're running stock, just use the full OTA packages.
For the flash tool to be usable you need to OEM unlock your phone (while it's in a working state!).
If you can access fastboot you should be able to access recovery as well, where you can flash the full OTA, which should fix your issue.
Click to expand...
Click to collapse
Because I'm rooted and recovery doesn't work.
I should have just done it manually instead of the flash tool method published here.
I just don't get why the system image isn't flashing now, the bootloader and radio flash work, but not the actual update. It's the correct version and all.

If the online flash tool isn't working for you, download the factory image from google's website and use the flash-all.bat to flash the device. Ensure that you modify the flash-all.bat file to not wipe data before running. This can be done by modifying one line in the file. Which is the following:
Code:
fastboot -w update image-raven-....zip
to
Code:
fastboot update --disable-verity --disable-verification image-raven-....zip
When flashing ensure that phone is in bootloader first.

So I got it to work after several hours. Literally just worked after trying another Google USB cable that was USB c to USB c, or maybe it worked cause of something else. Not sure, I don't like how finicky pixels have become. I discovered it's sometimes a luck thing when it wants to flash or not according to many people when searching the internet for solutions.

So i got a lil problem. i updated the pixel 6 pro to december update but upon booting up it says your phone is corrupted and sits at the google bootup screen. i can still use fastboot and whatnot but every img i tried i get the same message and it sits again?

holla420 said:
So i got a lil problem. i updated the pixel 6 pro to december update but upon booting up it says your phone is corrupted and sits at the google bootup screen. i can still use fastboot and whatnot but every img i tried i get the same message and it sits again?
Click to expand...
Click to collapse
edit---
first try this method that was posted - sometimes you can save your phone this way. if that doesn't work: you can download the factory image and remove the "-w" command in the flash-all.bat file (save it properly) - this will prevent wiping your phone. you'll need adb/fastboot tool and drivers. if you need help with this just reply.
if that doesn't work, you can go this route (but it will wipe your phone) you can use the "flash" link on the factory image page here. if you press the "flash" link in blue, it will take you to the correct build at flash.android.com (click on the build version 12.0.0 (SD1A.210817.037, Nov 2021) - that's the one that worked for me.

ok the problem im havin is it sstill sayinbg courrpt. it cant be trusted and may not work

holla420 said:
ok the problem im havin is it sstill sayinbg courrpt. it cant be trusted and may not work
Click to expand...
Click to collapse
What method did you use to update? Are you rooted? If so, what version of Magisk did you use?

V0latyle said:
What method did you use to update? Are you rooted? If so, what version of Magisk did you use?
Click to expand...
Click to collapse
no root, just unlocked bootloader i manually installed using adb

holla420 said:
no root, just unlocked bootloader i manually installed using adb
Click to expand...
Click to collapse
Use the Android Flash Tool to flash the latest December update. Don't check any of the boxes.

ayye thanks this method worked

holla420 said:
ok the problem im havin is it sstill sayinbg courrpt. it cant be trusted and may not work
Click to expand...
Click to collapse
You'll always get this message upon reboot once the bootloader is unlock.
It's normal, and you can disregard it entirely (unless you want the absolutely most secure device possible, then you should lock the bootloader, and this message will go away)

Az Biker said:
You'll always get this message upon reboot once the bootloader is unlock.
It's normal, and you can disregard it entirely (unless you want the absolutely most secure device possible, then you should lock the bootloader, and this message will go away)
Click to expand...
Click to collapse
oh i know but this was a different message. it was in red and wouldnt boot pass the bootup screen,

coilbio said:
So I got it to work after several hours. Literally just worked after trying another Google USB cable that was USB c to USB c, or maybe it worked cause of something else. Not sure, I don't like how finicky pixels have become. I discovered it's sometimes a luck thing when it wants to flash or not according to many people when searching the internet for solutions.
Click to expand...
Click to collapse
sounds like a user error; if it's fixed you might want to update your first post with solutions in case others have similar issues.

coilbio said:
So I got it to work after several hours. Literally just worked after trying another Google USB cable that was USB c to USB c, or maybe it worked cause of something else. Not sure, I don't like how finicky pixels have become. I discovered it's sometimes a luck thing when it wants to flash or not according to many people when searching the internet for solutions.
Click to expand...
Click to collapse
There are definitely better and worse USB-C cables. I've successfully fully flashed my P6P connected to a powered USB-A (3.2 Gen 2) Hub in one room through a USB extension cable 10-15 feet from my computer in another room. The hub and the extension cable are reasonably "robust", and I've found them reliable, but they're not particularly reputable name brands by any means. The USB-A -> USB-C cable I have connected to that hub is from my old HTC 10, too.

Related

First bricked fire tv??

Not sure if its really bricked or not but Its all messed and wont fully boot so it doesnt have lan access anymore for ssh and adb over wifi. I have a male to male usb cable and my pc is recognizing when its plugged in but there are no device drivers installed and adb/fastboot wont recognize (no usb debugging enabled?) so it just hangs on <waiting on device> any idea how I can install devices drivers and move forward with restoring backup of the file I fuxored? Thx guys!
Have you tried disconnecting that A to A cable? When I tried using an A A cable from my laptop to the Fire, it hung when it booted.
It powered on, went to the first white on black Amazon logo, and halted. Disconnecting the cable and power cycling let it complete the boot cycle.
Havnt got that far yet myself but the way i tinker i will be there shortly .. but as a warning to others, if you are not 100% sure what you are doing, dont muck around especially if you remount /system as rw.
Playing around will be much safer once we get recovery..
Building a recovery shouldnt be too difficult.. its booting a custom recovery that will be the trick.. Jcase had allready said he has figured it out perhaps he will share now that root is out.
roustabout said:
Have you tried disconnecting that A to A cable? When I tried using an A A cable from my laptop to the Fire, it hung when it booted.
It powered on, went to the first white on black Amazon logo, and halted. Disconnecting the cable and power cycling let it complete the boot cycle.
Click to expand...
Click to collapse
Ive got fastboot connected now so it appears it was some funky unknown issue. Fastboot isnt like adb tho and the only time ive ever used it was to re-write whole img files so is that my only option or is there some way I can push stuff through fastboot? The OTA firmware links posted a few weeks back are now dead too..
You can download the OTA updates (they are complete roms). http://forum.xda-developers.com/showthread.php?t=2709811 - links still work, i just redownloaded them (not sure where I put my old ones).
Only problem is the recovery looks for them at /cache/, which isn't writable w/o root. I'm not sure of the functions available via fastboot w/ Fire TV (don't have a cable), but if you can't get into the recovery from fastboot, you can always try to boot a dumped recovery.img from fastboot... but still not sure how you can work around the stock recovery looking for the update file at /cache/
edit: actually don't think fastboot will be of much use with a locked bootloader.
Luxferro said:
You can download the OTA updates (they are complete roms). http://forum.xda-developers.com/showthread.php?t=2709811 - links still work, i just redownloaded them (not sure where I put my old ones).
Only problem is the recovery looks for them at /cache/, which isn't writable w/o root. I'm not sure of the functions available via fastboot w/ Fire TV (don't have a cable), but if you can't get into the recovery from fastboot, you can always try to boot a dumped recovery.img from fastboot... but still not sure how you can work around the stock recovery looking for the update file at /cache/
edit: actually don't think fastboot will be of much use with a locked bootloader.
Click to expand...
Click to collapse
Im rooted already, but basically what youre saying is to wait until bootloader is unlocked then flash that via fastboot and then flash recovery via fastboot. I feel like there has to be an easier way lol but im a noob so who knows.
Im not have any luck with those links either ive even tried assigning a static public dns to make sure my opendns stuff was no longer blocking. Does anyone have an alternate link?
alwaysbless said:
Im rooted already, but basically what youre saying is to wait until bootloader is unlocked then flash that via fastboot and then flash recovery via fastboot. I feel like there has to be an easier way lol but im a noob so who knows.
Click to expand...
Click to collapse
Nah, not saying that at all - would love for an unlocked bootloader, but you might be waiting forever.
this is also one of the reasons that jcase hasn't released what he had (according to his G+ page). since if you bork the stock rooted rom, you'll have a hard time getting it fixed (since the rooted rom is the only current way in). If you can't boot the rom, then you can't fix anything. I'm no expert, so maybe one will chime in. But I think the next step after rooting, is to have a custom recovery, and a way to boot into it if the rom breaks - which we don't have yet.
I had a similar instance. Gained root messed around too much and got it to not boot. Amazon is sending a replacement... But if there is a way around that in the future I would love to just fix it my self.
Sent from my Nexus 5 using XDA Premium 4 mobile app
Luxferro said:
Nah, not saying that at all - would love for an unlocked bootloader, but you might be waiting forever.
this is also one of the reasons that jcase hasn't released what he had (according to his G+ page). since if you bork the stock rooted rom, you'll have a hard time getting it fixed (since the rooted rom is the only current way in). If you can't boot the rom, then you can't fix anything. I'm no expert, so maybe one will chime in. But I think the next step after rooting, is to have a custom recovery, and a way to boot into it if the rom breaks - which we don't have yet.
Click to expand...
Click to collapse
So I couldnt even take the system.img and rewrite it using fastboot without having an unlocked bootloader? Sounds like the only way this thing will recover is install cwm/twrp recovery.img whenever that becomes available and then reflash w/ custom recovery.
alwaysbless said:
So I couldnt even take the system.img and rewrite it using fastboot without having an unlocked bootloader? Sounds like the only way this thing will recover is install cwm/twrp recovery.img whenever that becomes available and then reflash w/ custom recovery.
Click to expand...
Click to collapse
Except you won't be able to install a custom recovery since only your ROM has root access and it doesn't boot.
Sent from my Nexus 5 using Tapatalk
Luxferro said:
Except you won't be able to install a custom recovery since only your ROM has root access and it doesn't boot.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Got you now. So this is def the first bricked fire tv lol. Guess ill just sit it to the side and see if someone smarter than I can figure something like this out in the future.
Have you tried fastboot boot commands? Like fastboot boot blahblahblah.img? If it is softbricked i guess it can't hurt to try rite?
I don't know if this will work or not, but if you've already tried pulling the power, pulling USB and powering on the next thing I'd try is to obtain a 1 gig or so USB drive, format it fat32 and copy the OTA update to it.
- Leave it zipped.
- Name it update.zip
- pull the plug on the FTV
- put the USB stick in
- power it on and leave it for a bit. Watch it - is the power LED going out? If so, it may doing a recovery install of the signed OTA and rebooting - many Android devices will install anything on the sdcard called Update.zip if it's there at boot time.
What you're hoping is that the USB mass storage is mounted as a possible recovery source at power on and that the OTA is isntalled via the stock recovery. If it works, great, if it doesn't, too bad.
another brick on the wall ?
Dear OP ' i think you are not the only one .
im not sure if im bricked or plain noob
after i rooted successfully and did the blocking through host editor guide in fire tv news and for a good measure i run this command "su
pm disable com.amazon.dcp" . all was good and i had an issue with audio in xbmc and in my great wisdom i did a reset to factory settings.
since then i can not register to amazon i believe because it can not accsses amazon site for verification. so im stuck in there.
i tried to SSH and through command line no device was recognized .
any assistance to this stupidity will be much appericiated
thanks yigo
Yigo said:
after i rooted successfully and did the blocking through host editor guide in fire tv news and for a good measure i run this command "su pm disable com.amazon.dcp" .
Click to expand...
Click to collapse
Afraid I can't help you, but in light of preventing other people (and me) to have the same issues:
I assume the /etc/hosts file will survive factory-resets, it's a file that probably is not restored (so immediatly removed the host-lines from mine), but wonder if the pm disable dcp will also survice a reset ? I assume not (core funcationality for amazon, likely in factory-reset group), but you never know, esp. not in the v1 versions we are running.
Anybody knows if this is the case ? I like the pm disable solution, but if this means that borking up my installation will prevent me from ever restoring it (as unable to connect to amazon), I'll have to fall back to the router-blockage solution, and would suggest other ppl to do that as well
Deregistering AFTV may help with registration issue.
I had problems registering after factory reset.
I only disabled my amazon.dcp nad had dns and router blocks to prevent updates.
I did not edit my host file.
To de-register your Fire TV-
1 - log on to your amazon account
2 - Hold the mouse over where it says 'Your Account" but do not click. You will get a list of options.
3 - Click "Manage Your Content and Devices"
4 - Click the center tab "Your Devices"
5 - Click on your Fire TV.
6 - Click "Deregister" right below your Fire TV.
You will ge a message saying it there may be a delay for it to take effect.
[email protected] said:
I had problems registering after factory reset.
I only disabled my amazon.dcp nad had dns and router blocks to prevent updates.
I did not edit my host file.
Click to expand...
Click to collapse
So (while you need to de register the FTV itself within amazon), it looks like you can factory reset after disabling the amazon.dcp service.
Which is good news, as this allows easier disabling of update checks on machine level instead of router level (which not everybody will be able to do) and disabling the update service is better then overlooking a (hidden) fallback URL.
N=1 though, so'll have to wait if more confirmations come in, or somebody will be brave enough to try it
Still Learning - Passing it on.
JPDeckers said:
So (while you need to de register the FTV itself within amazon), it looks like you can factory reset after disabling the amazon.dcp service.
Which is good news, as this allows easier disabling of update checks on machine level instead of router level (which not everybody will be able to do) and disabling the update service is better then overlooking a (hidden) fallback URL.
N=1 though, so'll have to wait if more confirmations come in, or somebody will be brave enough to try it
Click to expand...
Click to collapse
I read your other posting about update blocking.
Seems I did not have my amazon.dcp disabled.
I was not in SU mode when executing command and amazon.dcp was just killed not disabled.
Sorry for any confusion. Thanks
JPDeckers said:
So (while you need to de register the FTV itself within amazon), it looks like you can factory reset after disabling the amazon.dcp service.
Which is good news, as this allows easier disabling of update checks on machine level instead of router level (which not everybody will be able to do) and disabling the update service is better then overlooking a (hidden) fallback URL.
N=1 though, so'll have to wait if more confirmations come in, or somebody will be brave enough to try it
Click to expand...
Click to collapse
I hope one of the folks with a softbricked device gets a chance to see what happens with the over the air update file copied to a fat32 formatted USB stick and renamed update.zip.
With luck, at power on if there is media present, the stock recovery is looking to removable media to see if there's a file named update.zip it can process.
I don't want to softbrick mine to test, though.
So if I am understanding correctly, you should enable updates before you factory reset?

Nexus 5x display is scrambled after rolling back from android n developer preview2

Hi All,
Request all to provide any suggestions related to the below issue:
I rolled back from android n preview 2 to android m after which my display is scrambled.I am not able to view any thing on it.
But I am getting calls and able to pick them when I roughly expect the place where I can swipe the dialer right to pick the call.
Few things that I want to highlight is :
1)I had unstable wifi connection while downloading the android m OTA.
2)I removed the unlock bootloader check before rolling back in the developer options.
3)I can also sense that i am able to take screen shots when I am holding the power button and the volume down button based on the sound it normally makes (while capturing screenshots)
I am not able to come to conclusion whether this a hardware issue?(may be i need the replacement of the screen) or can it be due to corrupt ota file update?
Any suggestions would be much appreciated.
thanks
I would first see if flashing the m factory image solves the issue. Then look at hardware.
k.s.deviate said:
I would first see if flashing the m factory image solves the issue. Then look at hardware.
Click to expand...
Click to collapse
thank you but the problem is I am not able to see the screen at all and hence I am not able to go to the fastboot mode or recovery mode.
NeverBackDown said:
thank you but the problem is I am not able to see the screen at all and hence I am not able to go to the fastboot mode or recovery mode.
Click to expand...
Click to collapse
use "adb reboot bootloader" from command prompt to enter bootloader or if you know the device is off, press power + vol up + vol down for roughly 5sec, thatll get into bootloader. than flash factory image.
or last case scenario use wug fresh toolkit to force flash the image, make sure you select the device fails to boot box (I think that's what its called, the only other one states "device on/normal" <-- so NOT that one)
k.s.deviate said:
use "adb reboot bootloader" from command prompt to enter bootloader or if you know the device is off, press power + vol up + vol down for roughly 5sec, thatll get into bootloader. than flash factory image.
or last case scenario use wug fresh toolkit to force flash the image, make sure you select the device fails to boot box (I think that's what its called, the only other one states "device on/normal" <-- so NOT that one)
Click to expand...
Click to collapse
Thanks I am first looking for type c to usb to connect it to my computer,I will try for it tomorrow and also the first option you provided will work only if usb debugging is already enabled on my phone ,right?
NeverBackDown said:
Thanks I am first looking for type c to usb to connect it to my computer,I will try for it tomorrow and also the first option you provided will work only if usb debugging is already enabled on my phone ,right?
Click to expand...
Click to collapse
yes, the adb command will only work if debugging is on. Once in bootlader, use fastboot commands, debugging doesn't matter at that point.
k.s.deviate said:
yes, the adb command will only work if debugging is on. Once in bootlader, use fastboot commands, debugging doesn't matter at that point.
Click to expand...
Click to collapse
Hi All,
I got the cable ,I had everything to flash the official factory images.But the problem is as mentioned earlier I haven't checked the oem unlock in the developer option and this is not allowing to flash the factory images and fastboot flashing unlock is failing.
Is there any work around for this please?
NeverBackDown said:
Hi All,
I got the cable ,I had everything to flash the official factory images.But the problem is as mentioned earlier I haven't checked the oem unlock in the developer option and this is not allowing to flash the factory images and fastboot flashing unlock is failing.
Is there any work around for this please?
Click to expand...
Click to collapse
Not that I'm aware of. Sorry, there is a thread on here that may prove useful that deals with bricked phones with OEM unlocked off. The info there might help you at least get back to stock.
k.s.deviate said:
Not that I'm aware of. Sorry, there is a thread on here that may prove useful that deals with bricked phones with OEM unlocked off. The info there might help you at least get back to stock.
Click to expand...
Click to collapse
In that case ,do you think the service center guys have some other means to deal with if it is a software issue?
NeverBackDown said:
In that case ,do you think the service center guys have some other means to deal with if it is a software issue?
Click to expand...
Click to collapse
Possibly, I have no experience dealing with a service center unfortunately.
NeverBackDown said:
In that case ,do you think the service center guys have some other means to deal with if it is a software issue?
Click to expand...
Click to collapse
I also want to highlight that,I am getting a black screen on the fastboot mode too,i cant see nothing there..Only way i am able to identify that my device is in fastboot mode is by giving fastboot devices command.
So can this be a software issue?
NeverBackDown said:
Hi All,
I got the cable ,I had everything to flash the official factory images.But the problem is as mentioned earlier I haven't checked the oem unlock in the developer option and this is not allowing to flash the factory images and fastboot flashing unlock is failing.
Is there any work around for this please?
Click to expand...
Click to collapse
You might want to look into android screencast.
I don't know if it still works with the latest android releases, but back in kitkat days if I had a screen that wouldn't display I could use screencast and I'd get the framebuffer displaying on the PC. While viewing on PC I could then do touchscreen "guesses" more accurately and presumably you'd be able to enable OEM unlocked bootloader so you can flash factory images.

No way to unbrick this phone

Hey guys,
I've got a Oneplus 3 that freezes every time it tries to boot. Fastboot and recovery are still working, factory reset makes no difference. After sideloading the latest OxygenOs the screen just goes blank after the Oneplus splash screen and recovery doesn't work anymore. The MsmDownloadTool only gets me where I started, back at the bootloop. So the old OOS gives me bootloop with recovery and fastboot while the new OOS only gives me fastboot and a blank screen.
New system with old working boot and recovery gives "md5 checksum failed".
The bootloader is locked and as long as I can't get in the settings there is no way to unlock it, so my options are pretty limited here.
I've contacted Oneplus but they aren't really helping either.
Is there any way to get this thing back to life?
Robert1852 said:
Hey guys,
I've got a Oneplus 3 that freezes every time it tries to boot. Fastboot and recovery are still working, factory reset makes no difference. After sideloading the latest OxygenOs the screen just goes blank after the Oneplus splash screen and recovery doesn't work anymore. The MsmDownloadTool only gets me where I started, back at the bootloop. So the old OOS gives me bootloop with recovery and fastboot while the new OOS only gives me fastboot and a blank screen.
New system with old working boot and recovery gives "md5 checksum failed".
The bootloader is locked and as long as I can't get in the settings there is no way to unlock it, so my options are pretty limited here.
I've contacted Oneplus but they aren't really helping either.
Is there any way to get this thing back to life?
Click to expand...
Click to collapse
https://forum.xda-developers.com/on...mega-unbrick-guide-hard-bricked-t3405700/amp/
That always works.. use method 2
dmilz said:
https://forum.xda-developers.com/on...mega-unbrick-guide-hard-bricked-t3405700/amp/
That always works.. use method 2
Click to expand...
Click to collapse
Not this time... That is the tool I mentioned, only gets me back to the bootloop
Robert1852 said:
Not this time... That is the tool I mentioned, only gets me back to the bootloop
Click to expand...
Click to collapse
I know what you talking about.. Went through that too when i used method one.. use method 2..it will flash stock OOS and you will boot successfully
If you already did..try once more..download the tools over again
dmilz said:
I know what you talking about.. Went through that too when i used method one.. use method 2..it will flash stock OOS and you will boot successfully
If you already did..try once more..download the tools over again
Click to expand...
Click to collapse
Yeah already tried method 2 multiple times, downloaded the tools again but it still doesn't work on this phone..
Robert1852 said:
Yeah already tried method 2 multiple times, downloaded the tools again but it still doesn't work on this phone..
Click to expand...
Click to collapse
Ooh ok.. i see.. hope you will find a way out
Robert1852 said:
Yeah already tried method 2 multiple times, downloaded the tools again but it still doesn't work on this phone..
Click to expand...
Click to collapse
Probably a stupid question but have you tried flashing oxygen os recovery and then tried to flash stock ROM?
Xceeder said:
Probably a stupid question but have you tried flashing oxygen os recovery and then tried to flash stock ROM?
Click to expand...
Click to collapse
That unbrick tool also flashes the stock recovery. I cant flash anything using fastboot because the bootloader is locked
Robert1852 said:
That unbrick tool also flashes the stock recovery. I cant flash anything using fastboot because the bootloader is locked
Click to expand...
Click to collapse
And why is it locked then? Why would you ever relock your bootloader? You should be able to unlock it anyway without going in to settings. Are you sure you are using the correct drivers? Windows installs the wrong once by default.
Puddi_Puddin said:
And why is it locked then? Why would you ever relock your bootloader? You should be able to unlock it anyway without going in to settings. Are you sure you are using the correct drivers? Windows installs the wrong once by default.
Click to expand...
Click to collapse
It has never been unlocked. In the settings is the "Allow OEM Unlock" option which you should check before you can unlock the bootloader. As long as I can't boot the phone I can't check this option, or someone must know a workaround. Yes I'm pretty sure I'm using the correct drivers
Robert1852 said:
It has never been unlocked. In the settings is the "Allow OEM Unlock" option which you should check before you can unlock the bootloader. As long as I can't boot the phone I can't check this option, or someone must know a workaround. Yes I'm pretty sure I'm using the correct drivers
Click to expand...
Click to collapse
If you plug your phone in how does it show up under Device Manager? Have you also tried "fastboot OEM Unlock"?
Puddi_Puddin said:
If you plug your phone in how does it show up under Device Manager? Have you also tried "fastboot OEM Unlock"?
Click to expand...
Click to collapse
When it's in the bootloader menu it shows up as "Android Bootloader Interface", when it's in EDL mode it shows up as "Qualcomm HS-USB QDLoader 9008 (COM3)". It connects fine with the pc and flashes everything without problems as far as I can see. Yeah it says "FAILED (remote: oem unlock is not allowed)" probably because the allow oem unlock option in the settings isn't checked.
Most likely won't do anything, but have you tried a different computer? Seems like it would make no difference but tiny things like that have saved me in the past.
ZVNexus said:
Most likely won't do anything, but have you tried a different computer? Seems like it would make no difference but tiny things like that have saved me in the past.
Click to expand...
Click to collapse
Yea I know what you mean I tried it on a few different computers, even with different cables but it doesn't make a difference...
Robert1852 said:
Yea I know what you mean I tried it on a few different computers, even with different cables but it doesn't make a difference...
Click to expand...
Click to collapse
Pretty sure you are using wrong drivers. You should be able to unlock the bootloader even tho it is remote. When I first bricked my phone I forgot about the drivers aswell. My phone booted up and showed. System: Failed, Userdata:Failed. This means it failed to detect those partitions which you can find in unbrick program itself called system.img, userdata.img. You can actually flash these manually with fastboot flash system system.img but I also got the "Remote is not allowed error". After booting into disabled Driver Signature Enforcement mode and changing the drivers from on the guide I could actually flash these partitions. Your phone has to show up as Qualcomm 9008 or something close and not as Android Interfere Device. I have helped multiple people fixing their phone with this guide and they also had a locked bootloader and they also did not have the correct drivers.
Boot into https://www.google.com/amp/s/www.ho...so-that-you-can-install-unsigned-drivers/amp/ then install the driver linked on the Unbrick Guide. Your phone should show up correctly. Then run the unbrick guide as admin and it should go through flawless.
Puddi_Puddin said:
Pretty sure you are using wrong drivers. You should be able to unlock the bootloader even tho it is remote. When I first bricked my phone I forgot about the drivers aswell. My phone booted up and showed. System: Failed, Userdata:Failed. This means it failed to detect those partitions which you can find in unbrick program itself called system.img, userdata.img. You can actually flash these manually with fastboot flash system system.img but I also got the "Remote is not allowed error". After booting into disabled Driver Signature Enforcement mode and changing the drivers from on the guide I could actually flash these partitions. Your phone has to show up as Qualcomm 9008 or something close and not as Android Interfere Device. I have helped multiple people fixing their phone with this guide and they also had a locked bootloader and they also did not have the correct drivers.
Boot into https://www.google.com/amp/s/www.ho...so-that-you-can-install-unsigned-drivers/amp/ then install the driver linked on the Unbrick Guide. Your phone should show up correctly. Then run the unbrick guide as admin and it should go through flawless.
Click to expand...
Click to collapse
Tried everything it says in the guide about the drivers (even the last part about installing the certificates) but it just keeps showing up as qualcomm hs-usb qdloader 9008, even though I'm pretty sure they are installed correctly. It just won't show up as Qualcomm 9008, as it is supposed to, whatever I try. But it looks like these drivers are only for the EDL mode, and as far as I know it is normal for the phone to show up as Android Bootloader Interface when it's in the bootloader menu. And you can't use fastboot from EDL mode... Will try it later again on a different pc though, really hope you are right about the drivers after all
Hi Robert,
I am having same problem with my oneplus3. I also tried both unbrick methods and tried different oxygen ROMs.
Are you able to fix your phone?
Thanks in Advance,
Anil
Have you tried this http://www.androidbrick.com/oneplus-one-two-3-3t-5-mega-unbrick-guide-twrp-flashing/
Robert1852 said:
Hey guys,
I've got a Oneplus 3 that freezes every time it tries to boot. Fastboot and recovery are still working, factory reset makes no difference. After sideloading the latest OxygenOs the screen just goes blank after the Oneplus splash screen and recovery doesn't work anymore. The MsmDownloadTool only gets me where I started, back at the bootloop. So the old OOS gives me bootloop with recovery and fastboot while the new OOS only gives me fastboot and a blank screen.
New system with old working boot and recovery gives "md5 checksum failed".
The bootloader is locked and as long as I can't get in the settings there is no way to unlock it, so my options are pretty limited here.
I've contacted Oneplus but they aren't really helping either.
Is there any way to get this thing back to life?
Click to expand...
Click to collapse
Hi
Go back to an older Version...3.xx
worked for me
be warned ..3.xxx formats internal memory
I also have the same problem, I'll try to restore to old version too.
Do you also have artifacts on the screen?

Need Some Clarifications

Hi all,
After reading many posts i got a little confused and i'm not getting any result. Please help.
What i want?: Flash stock rom and later consider rooting, and flashing haden or lineagos. (already found guidance but..)
The issue?: It doesn't get recognized through USB with my PC. (drivers installed, cable connected but...)
My questions? (correct me if wished):
1) In Odin mode (which i enter) is the usb port enabled by default? or it depends on the phone configuration.
2) In recovery mode i still cannot see the phone through the USB so is it open by default on stock recovery?
3) Finally can i flash stock rom i downloaded from sammobile through SD card? i found that to be my last resort but i think odin actual proper way or not?
I first thought it was the cable...since is not the original but it seems not be the case...which leads me to think its the phone's usb port....but with the cable i can charge the phone although i cannot see it through my PC.
So bottom line if the answer to my questions are that is always open (accesible through usb port) then it HAS to be the cable right?
If last quesiton is possible then i will conclude my searchings to be ended for now.
Thanks to all the posts within this tree.
Findings
Is it normal that when boot to bootloader from stock recovery the ADB console keeps <waiting for device> while phone actually boots normaly?
I found that bootloader booting is accesible through fastboot independently from USB debugging option...
I'm considering buying official usb cable but store guy confirmed it works for data/power uses...
There definitely is a way to flash stock via TWRP, i once did that myself. However you need a dedicated tool on the PC to create a flashable zip, because the firmware can't be flashed by itself
Edit: i saw that you have FRP-lock enabled. Search for a guide on how to disable it and try again
verdugon said:
Is it normal that when boot to bootloader from stock recovery the ADB console keeps <waiting for device> while phone actually boots normaly?
I found that bootloader booting is accesible through fastboot independently from USB debugging option...
I'm considering buying official usb cable but store guy confirmed it works for data/power uses...
Click to expand...
Click to collapse
Are you on Samsung? If so, they don't have fastboot. Nor can you boot to bootloader. Do
Do you have the drivers installed? I have yet to see an unofficial cable not work for data transfer. Excepting damaged ones.
Light at the end of the tunnel!!!
PMFRTT said:
There definitely is a way to flash stock via TWRP, i once did that myself. However you need a dedicated tool on the PC to create a flashable zip, because the firmware can't be flashed by itself
Edit: i saw that you have FRP-lock enabled. Search for a guide on how to disable it and try again
Click to expand...
Click to collapse
Thanks PMFRTT!! I finally disabled FRP-lock and phone is usable again. I now will try to unlock OEM bootloader and enable USB debugging to see what happens. Thanks
Light at the end of the tunnel!!!
SnowFuhrer said:
Are you on Samsung? If so, they don't have fastboot. Nor can you boot to bootloader. Do
Do you have the drivers installed? I have yet to see an unofficial cable not work for data transfer. Excepting damaged ones.
Click to expand...
Click to collapse
Thanks @SnowFuhrer for your reply.
To answer your question yes its SMSUNG. I didn't know about that Thx.
The cable is brand knew but i noticed now that the phone is usable that is claims its on slow charge...may be my PC is quite old now....
Like i said i will try to unlock bootloader and make it accesible to odin to later see what to do.
verdugon said:
Thanks @SnowFuhrer for your reply.
To answer your question yes its SMSUNG. I didn't know about that Thx.
The cable is brand knew but i noticed now that the phone is usable that is claims its on slow charge...may be my PC is quite old now....
Like i said i will try to unlock bootloader and make it accesible to odin to later see what to do.
Click to expand...
Click to collapse
And to unlock the bootloader, just enable OEM unlock in the dev settings and it's ready to flash twrp. I remember when I got my Samsung and I was trying to fastboot unlock it lol.
Thanks to both of you! I will keep the thread on just in case...anyway may be it helps someone else.
verdugon said:
Thanks PMFRTT!! I finally disabled FRP-lock and phone is usable again. I now will try to unlock OEM bootloader and enable USB debugging to see what happens. Thanks
Click to expand...
Click to collapse
Good luck! Let me know how it went.

Question Can't do anything with a device, looking for a help!

So I've got into a big trouble... I wanted to manually update my Pixel 6 Pro to the latest version using an official OTA (since the update wasn't available yet for my country and I wanted to stay up-to-date). It was all fine until it said 74 % done... and the power in my house has completely turned off... The device hasn't given me any error and rebooted, hower it got stuck on a Google logo. I rebooted to the recovery mode how it was suggested and did a clean factory reset, then rebooted again... and nothing changed, only the logo background has changed (white vs black). The BIGGEST problem is, the device OEM is NOT unlocked I tried entering the fastboot mode and flashing the device with a recovery image but it obviously didn't work as it required OEM to be unlocked... I am in a big depression now, somehow I fear that it's not fixable... But if some awesome soul could suggest a way to try out, that would be great! Thanks in advance.
I would try the android flash tool and flash the whole full ROM onto the phone. Expect to lose your data though.
mkhcb said:
I would try the android flash tool and flash the whole full ROM onto the phone. Expect to lose your data though.
Click to expand...
Click to collapse
Doesn't your phone have to be unlocked to use the flash tool?
The data is all backed up so it's not a problem to lose it. The problem is actually making the phone to boot past the logo... I will try that Android Flash Tool but I fear that the phone should be unlocked first
Try this tool: https://pixelrepair.withgoogle.com/carrier_selection
Not sure if its any different to the android flash tool.
As expected, Android Flash Tool requires you to to have the device unlocked. At this point I am out of ideas and is truly disappointed. The tool mentioned above probably works the same way.
Maybe try sideloading OTA again. Are you able to do that?
mclarence said:
Try this tool: https://pixelrepair.withgoogle.com/carrier_selection
Not sure if its any different to the android flash tool.
Click to expand...
Click to collapse
McNaccken said:
As expected, Android Flash Tool requires you to to have the device unlocked. At this point I am out of ideas and is truly disappointed. The tool mentioned above probably works the same way.
Click to expand...
Click to collapse
Unfortunately, someone else in another thread reported that the Pixel Repair site (not the Android Flash Tool) hasn't been updated for the P6P.
McNaccken said:
So I've got into a big trouble... I wanted to manually update my Pixel 6 Pro to the latest version using an official OTA (since the update wasn't available yet for my country and I wanted to stay up-to-date). It was all fine until it said 74 % done... and the power in my house has completely turned off... The device hasn't given me any error and rebooted, hower it got stuck on a Google logo. I rebooted to the recovery mode how it was suggested and did a clean factory reset, then rebooted again... and nothing changed, only the logo background has changed (white vs black). The BIGGEST problem is, the device OEM is NOT unlocked I tried entering the fastboot mode and flashing the device with a recovery image but it obviously didn't work as it required OEM to be unlocked... I am in a big depression now, somehow I fear that it's not fixable... But if some awesome soul could suggest a way to try out, that would be great! Thanks in advance.
Click to expand...
Click to collapse
If you can still get into recovery mode, maybe try sideloading the OTA again?
EDIT: Ninja'd by @znel52
Lughnasadh said:
If you can still get into recovery mode, maybe try sideloading the OTA again?
EDIT: Ninja'd by @znel52
Click to expand...
Click to collapse
Yeah I'm afraid since he did a factory reset debugging got disabled. Worth a shot though.
znel52 said:
Yeah I'm afraid since he did a factory reset debugging got disabled. Worth a shot though.
Click to expand...
Click to collapse
Oh crap, didn't think about that.
I know not everyone has access to a laptop but if you do always use that over a desktop. In the event of something like this you will have the battery power to carry you through.
I'm sorry this happened to you. The only option may be to send it to Google for repairs.
Sorry for your phone. I experienced this on a nexus 6 that didn't have USB debugging or OEM unlock enabled. I tried sideload, put the update package on the phone storage, try to update with Android recovery. Nothing worked. Stuff happens with phones. I hope you can get a new phone.
God bless.
Sorry to hear this. It seems that I need to open USB debugging option just in case for my Pixel 6, which finally arrived across the ocean after a month.
McNaccken said:
So I've got into a big trouble... I wanted to manually update my Pixel 6 Pro to the latest version using an official OTA (since the update wasn't available yet for my country and I wanted to stay up-to-date). It was all fine until it said 74 % done... and the power in my house has completely turned off... The device hasn't given me any error and rebooted, hower it got stuck on a Google logo. I rebooted to the recovery mode how it was suggested and did a clean factory reset, then rebooted again... and nothing changed, only the logo background has changed (white vs black). The BIGGEST problem is, the device OEM is NOT unlocked I tried entering the fastboot mode and flashing the device with a recovery image but it obviously didn't work as it required OEM to be unlocked... I am in a big depression now, somehow I fear that it's not fixable... But if some awesome soul could suggest a way to try out, that would be great! Thanks in advance.
Click to expand...
Click to collapse
Since the Repairtool has not been updated for your needs and considering that your device is not unlocked, your only option is to contact Google (/your seller). Maybe they can offer you an updated version of the tool (unlikely) or replace your device.
You just described, btw, my horror scenario when updating the BIOS of my PC. The lights going out, when doing a firmware update o.o
Oh my. I'm so sorry for you to have experienced that.
Ok, so I did a CMOS reset on my main PC, since it also failed to load after the lost power accident. Loaded my PC then just fine and tried connecting the phone again. Got to recovery mode and tried "adb devices" command... and it listed my Pixel device !! I tried the "adb sideload" command but it's stuck at 5% for at least 20-30 mins. The phone's last message is "Verifying update package". Not sure if it's a good sign, but afaik if USB debugging is off etc, you can not use adb commands. What would you guys suggest, try waiting for another 30 mins or unplug the phone, restart PC and try again? I am using USB-A to USB-C cable btw, maybe I could use USB-C to USB-C.
McNaccken said:
Ok, so I did a CMOS reset on my main PC, since it also failed to load after the lost power accident. Loaded my PC then just fine and tried connecting the phone again. Got to recovery mode and tried "adb devices" command... and it listed my Pixel device !! I tried the "adb sideload" command but it's stuck at 5% for at least 20-30 mins. The phone's last message is "Verifying update package". Not sure if it's a good sign, but afaik if USB debugging is off etc, you can not use adb commands. What would you guys suggest, try waiting for another 30 mins or unplug the phone, restart PC and try again? I am using USB-A to USB-C cable btw, maybe I could use USB-C to USB-C.
Click to expand...
Click to collapse
My apologies for asking the obvious - did you select "adb sideload" in the recovery menu ? At least I was blind enough to oversee that I need to select this option first
Can you boot into fastboot from the recovery ? If yes you could also try installing a factory image instead of the update package.... I read you cannot because your device is locked, but you can unlock in fastboot (you can always relock later).... only downside is that this will clear all data on the phone for sure....
McNaccken said:
So I've got into a big trouble... I wanted to manually update my Pixel 6 Pro to the latest version using an official OTA (since the update wasn't available yet for my country and I wanted to stay up-to-date). It was all fine until it said 74 % done... and the power in my house has completely turned off... The device hasn't given me any error and rebooted, hower it got stuck on a Google logo. I rebooted to the recovery mode how it was suggested and did a clean factory reset, then rebooted again... and nothing changed, only the logo background has changed (white vs black). The BIGGEST problem is, the device OEM is NOT unlocked I tried entering the fastboot mode and flashing the device with a recovery image but it obviously didn't work as it required OEM to be unlocked... I am in a big depression now, somehow I fear that it's not fixable... But if some awesome soul could suggest a way to try out, that would be great! Thanks in advance.
Click to expand...
Click to collapse
I had a similar issue with applying ota updates and have seen quite a few reports of users having trouble. Not sure what the deal is, but for some reason this phone seems super finicky with updates. Are you still in the return window? You may want to reach out to Google support or one of their "authorized repair shops".
For me, I ran the flash all bat, rebooted, got a message saying my device can't be trusted. So I rebooted, wiped data, rebooted again and got the same thing. So I rebooted, ran the flash all bat file again, rebooted phone, and screen went black and it never powered on again. Suspect circuit board may have fried some how. Anyways, long story short, contacted Google and had a replacement sent out with minimal hassle.
McNaccken said:
Ok, so I did a CMOS reset on my main PC, since it also failed to load after the lost power accident. Loaded my PC then just fine and tried connecting the phone again. Got to recovery mode and tried "adb devices" command... and it listed my Pixel device !! I tried the "adb sideload" command but it's stuck at 5% for at least 20-30 mins. The phone's last message is "Verifying update package". Not sure if it's a good sign, but afaik if USB debugging is off etc, you can not use adb commands. What would you guys suggest, try waiting for another 30 mins or unplug the phone, restart PC and try again? I am using USB-A to USB-C cable btw, maybe I could use USB-C to USB-C.
Click to expand...
Click to collapse
so you can get through this... you'll be fine. pick adb sideload and it will say waiting, then run the command.
you can also change slots at the bootloader menu or try running the unlock oem command to see if it will allow you to unlock..... not sure if you can change slots without unlocking bootloader. try different USB ports on your computer (and restart your computer just in case) along with using the latest platform tools (adb/fastboot) and USB driver directly from Google (not third party apps or websites.
download the OTA zip again (and just open and close it quickly to verify it isn't corrupt).. and also make sure you have 5-10GB of space free on your computer.
usually the boot slot is changed whenever an OTA is flashed. it will tell you what slot you're in at the bootloader menu (where it says fastboot and device state locked).
can you try holding power button (when it's not plugged in) and as soon as you see then Google logo, hold volume down. that will get you to safe mode. and as quickly as you can, enable "OEM Unlocking" - which will allow you to flash a full factory image.
sorry for this comment being all over the place. if you need help, just reply, and I'll be more methodical next time
s3axel said:
I read you cannot because your device is locked, but you can unlock in fastboot (you can always relock later).... only downside is that this will clear all data on the phone for sure....
Click to expand...
Click to collapse
I don't think the problem is that his bootloader is locked - it's unlocked, however, they factory reset the device which likely caused USB Debugging to be turned off, as it defaults to after a factory reset.
I'm so glad years ago I swore to use Uninterruptible Power Supplies (UPS) for all the PCs I build for myself or my wife.

Categories

Resources