Related
I was unrooting my phone and I must've skipped a few steps but now my phone is bricked I guess. All I can do at the moment is get into the bootloader but whenever I try and flash anything (recovery,roms etc) I don't permission since I locked my bootloader (it said in a tutorial.. whoops). I tried to follow the unbricking guide here on XDA but it tells you to install weird qualcomm drivers and whenever I try and apply it to my device in device manager it just says that it's not compatible with my device.
So yeah, my bootloader is locked but I need to flash a recovery to get me out of this mess, what do I do?
Have you tried fastboot oem unlock?
It "might" work even if the related setting (in Developer Options) is disabled.
After doing that, try to normally restore the stock firmware.
Ps note that you'll definitely lose all data
Simone98RC said:
Have you tried fastboot oem unlock?
It "might" work even if the related setting (in Developer Options) is disabled.
After doing that, try to normally restore the stock firmware.
Ps note that you'll definitely lose all data
Click to expand...
Click to collapse
Yeah but it just fails
edit- i'll retry the unbricking guide tomorrow
The guide still doesn't work for me, I'm just having problem with the drivers you're meant to use.
I posted on there my issue on more detail.
Update- I fixed it.
I wasn't going into proper recovery mode (I had to turn it off completely and hold volume while plugging in). Then, it popped up on device manager under USB and the drivers worked. Afterwards, I just followed the rest of the tutorial haha.
you see, I made a bad installation of a rom and my phone no longer turns on (I can not enter bootloader or recovery mode) try to restore it by my flash. I recognize my flash device as COM but at the time of starting the flash it asks for an MI account (I log in with the account which is synchronized to the phone) but it always sends me error. I have been told that there is a solution through something called test point, but as far as I understand this is for the computer to recognize the phone. which I already do. Any advice or tutorial?
(sorry my english, I speak spanish.)
Modularkarma said:
you see, I made a bad installation of a rom and my phone no longer turns on (I can not enter bootloader or recovery mode) try to restore it by my flash. I recognize my flash device as COM but at the time of starting the flash it asks for an MI account (I log in with the account which is synchronized to the phone) but it always sends me error. I have been told that there is a solution through something called test point, but as far as I understand this is for the computer to recognize the phone. which I already do. Any advice or tutorial?
(sorry my english, I speak spanish.)
Click to expand...
Click to collapse
Error doesnt say much.. atleast write what does the error say... And yes, there is also qfil flashing method, which can revive basically dead device. But you have to open up device, take off back panel, and touch 2 metal thingies with a tweezers or something similar to enter qfil. I made a huge mistake few months ago, accidentally flashed firmware of another device onto RN5 and it just went through it, then it turned off, and was completely dead. No signs of life whatsoever, so i revived it using qfil method and flash stock firmware again. There are guides in this forum.
No
Incogn said:
Error doesnt say much.. atleast write what does the error say... And yes, there is also qfil flashing method, which can revive basically dead device. But you have to open up device, take off back panel, and touch 2 metal thingies with a tweezers or something similar to enter qfil. I made a huge mistake few months ago, accidentally flashed firmware of another device onto RN5 and it just went through it, then it turned off, and was completely dead. No signs of life whatsoever, so i revived it using qfil method and flash stock firmware again. There are guides in this forum.
Click to expand...
Click to collapse
what type of firmware did you install, because I try it with the official firmware of the page and it does not leave me, it asks me for a miui account but when I put it it tells me to authenticate failed edl
Modularkarma said:
No
what type of firmware did you install, because I try it with the official firmware of the page and it does not leave me, it asks me for a miui account but when I put it it tells me to authenticate failed edl
Click to expand...
Click to collapse
Yes, i also had authentication errors, thats why i had to open device, short 2 contacts, then phone entered edl mode, and i succesfully fixed it using qfil method of which there is a guide in this forum
Incogn said:
Yes, i also had authentication errors, thats why i had to open device, short 2 contacts, then phone entered edl mode, and i succesfully fixed it using qfil method of which there is a guide in this forum
Click to expand...
Click to collapse
I did all the test point process, I tried to flash several fastboots but the phone does not turn on, it flashes normally but when I try to turn it on, it does not turn on. I have the redmi note 5, I bought it in Colombia.
Incogn said:
Yes, i also had authentication errors, thats why i had to open device, short 2 contacts, then phone entered edl mode, and i succesfully fixed it using qfil method of which there is a guide in this forum
Click to expand...
Click to collapse
I did all the test point process, I tried to flash roms fastboots but the phone does not turn on, it flashes normally but when I try to turn it on, it does not turn on. I have the redmi note 5, I bought it in Colombia.
Hello,
My phone got hard bricked yesterday after the MIUI 11 update. It was running fine before on lastest MIUI10 global ROM with persistent TWRP, root and magisk. Bootloader is unlocked.
The phone dont turn on anymore and just show a white notification led when plugged to a PC. No recovery or fastboot access
If i press volume up when i plug it to my pc, it show up as "Mediatek USB Port" and disappear after 5 seconds.
I tried to open the phone/ removing battery, shorting EDL test points, but nothing happens.
My only solution appears to be using Sp_flash_tool but seems like i need an authorized Mi account flash the stock ROM.
Do someone know where i can get acces to one of those account ?
Thanks for your replies guys !
Redmi Note 8 Pro Hard Bricked
I'm in the same situation.
please help me
Hello,
The same thing happened to me when I installed the Orange FOX recovery, it didn't go into Fastboot mode, so I had to press the 3 buttons and wait for it to turn off completely, open the ADB control console and then connect it to the PC via USB by pressing the volume + button.
The latter I did on several occasions (Turn it off completely and connect by USB). Until I recognized it, when I recognized them, I had to flash the SYSTEM, CUST, RECOVERY. One by one, in total it took almost 5 minutes.
After that the phone started normal, obviously without root, nor custom recovery.
I'm also in the same situation as all of you, the PC doesn't recognize me and I can't go into fastboot
Hey,
I tried everything I could (battery connected/unplugged), my phone seems to have a corrupted preloader and only start the boot rom. That's why it shows up as "Mediatek USB PORT", if the preloader was'nt corrupted, it should be named "MediaTek PreLoader USB VCOM port" or something similar.
The only way to recover it imo is to flash a healthy preloader using SPFlashTool low level flash mode and next flash a full rom when "MediaTek PreLoader USB VCOM port" appears in the device manager.
Unfortunately, xiaomi ask for a certified account for low level flashing. I found one but the guy ask for 40$ for just logging it into my pc with teamviewer.
I buyed a Samsung Note10+ in replacement and i'll just wait someone find a solution to sell my 10-day-used redmi if I can revive it one day.
I got hundreds $ of Xiaomi home automation products in my home, but that was my first phone from this brand. I think it will also be the last.
I'm sad to see that their security policy on the phones is so frustrating to the people who just want to have a full acces on their devices.
Authorise can be done with professional tools
Tools like umt, hydra tool, miracle xiaomi tool, does the authorization. And i think mtk cpu Auth will only be available in miracle xiaomi tool, be aware every Auth cost credit of 4 to 10 u will have but credit separate from the tool.. Hope this will help
MOD EDIT: quote removed help our devlopers lmao to get atleast one rom ??
They only need to unbrick sometimes.
girishjangir7 said:
MOD EDIT: name removed help our devlopers lmao to get atleast one rom ??
They only need to unbrick sometimes.
Click to expand...
Click to collapse
Where is this post??
Some hours ago an user MOD EDIT: name removed offers help to unbrick devices but all threads was deleted??? Why?
djzero86 said:
Where is this post??
Some hours ago an user MOD EDIT: name removed offers help to unbrick devices but all threads was deleted??? Why?
Click to expand...
Click to collapse
It's against forum rules to post paid services
Y0annC said:
Hello,
My phone got hard bricked yesterday after the MIUI 11 update. It was running fine before on lastest MIUI10 global ROM with persistent TWRP, root and magisk. Bootloader is unlocked.
The phone dont turn on anymore and just show a white notification led when plugged to a PC. No recovery or fastboot access
If i press volume up when i plug it to my pc, it show up as "Mediatek USB Port" and disappear after 5 seconds.
I tried to open the phone/ removing battery, shorting EDL test points, but nothing happens.
My only solution appears to be using Sp_flash_tool but seems like i need an authorized Mi account flash the stock ROM.
Do someone know where i can get acces to one of those account ?
Thanks for your replies guys !
Click to expand...
Click to collapse
I Faced The Same Problem Of Bricked Phone Of Redmi Note 8 Pro, I Was Unable To Enter Fastboot Mode, Recovery Mode & Even Can't Enter Into The System Because I Flash Wrong Boot.img File, Thereafter I Tried To Use SP Flash Tool But Failed Due To Xiaomi Authorised Account Issue. Then I Emailed Xiaomi For Getting My Account Authorised And They Emailed Back And Told Me That They Can't Authorise My Account..
Then I Decided To Visit Mi Service Centre As My Phone Was In Warranty, The Funniest Fact Is The Technicians Existed There Were Failed To Detect The Problem. I Told Them That My Phone Was Automatically Got Dead After Installing An Update Just For Making Them Unaware From The Real Fact.
I Told Them That There Is No Hardware Issue Only Need To Flash Original Firmware But They Are Freak And Didn't Listen To Me And Opened Up Every Part Of The Phone, Now They Told Me That The Phone Will Need 7 Days Of Repairing Take The Phone After 7 Days.
I Tried To Teach Them The Way By Which The Phone Could Be Repaired But They Only Listen To Me And Did Nothing, They Were Behaving Like A Beginner In Repairing Phone,
They Didn't Know That The Phone Can Also Be Reapired During Switched Off.
Now I Have To Wait For 7 Days, So Guys Flash Anything Carefully Otherwise You Will Face The Same Situation.
Thanks
Well I guess I won't unlock my device... To be honest I have no reason to do so. The phone is running great and I have adguard and removed all the apps I don't like using adb.
petenoni said:
Well I guess I won't unlock my device... To be honest I have no reason to do so. The phone is running great and I have adguard and removed all the apps I don't like using adb.
Click to expand...
Click to collapse
I Also Had Adguard But I Was Still Not Satisfied
I Wanted My Phone To Be Rooted And Use The Custom ROMs If Build In Future.
Hemant Singh Rajput said:
I Faced The Same Problem Of Bricked Phone Of Redmi Note 8 Pro, I Was Unable To Enter Fastboot Mode, Recovery Mode & Even Can't Enter Into The System Because I Flash Wrong Boot.img File, Thereafter I Tried To Use SP Flash Tool But Failed Due To Xiaomi Authorised Account Issue. Then I Emailed Xiaomi For Getting My Account Authorised And They Emailed Back And Told Me That They Can't Authorise My Account..
Then I Decided To Visit Mi Service Centre As My Phone Was In Warranty, The Funniest Fact Is The Technicians Existed There Were Failed To Detect The Problem. I Told Them That My Phone Was Automatically Got Dead After Installing An Update Just For Making Them Unaware From The Real Fact.
I Told Them That There Is No Hardware Issue Only Need To Flash Original Firmware But They Are Freak And Didn't Listen To Me And Opened Up Every Part Of The Phone, Now They Told Me That The Phone Will Need 7 Days Of Repairing Take The Phone After 7 Days.
I Tried To Teach Them The Way By Which The Phone Could Be Repaired But They Only Listen To Me And Did Nothing, They Were Behaving Like A Beginner In Repairing Phone,
They Didn't Know That The Phone Can Also Be Reapired During Switched Off.
Now I Have To Wait For 7 Days, So Guys Flash Anything Carefully Otherwise You Will Face The Same Situation.
Thanks
Click to expand...
Click to collapse
mine only take 3 hours at the service center in Jaipur
Y0annC said:
Hello,
My phone got hard bricked yesterday after the MIUI 11 update. It was running fine before on lastest MIUI10 global ROM with persistent TWRP, root and magisk. Bootloader is unlocked.
The phone dont turn on anymore and just show a white notification led when plugged to a PC. No recovery or fastboot access
If i press volume up when i plug it to my pc, it show up as "Mediatek USB Port" and disappear after 5 seconds.
I tried to open the phone/ removing battery, shorting EDL test points, but nothing happens.
My only solution appears to be using Sp_flash_tool but seems like i need an authorized Mi account flash the stock ROM.
Do someone know where i can get acces to one of those account ?
Thanks for your replies guys !
Click to expand...
Click to collapse
hi
does anyone find a solution for this?
please help
Well there is now a way to bypass the need for an authorized account, if you device is unbricked. Basically if you flash this before you brick your phone, it allows you to use sp flash to unbrick it without authorized account.
Read this thread:
https://forum.xda-developers.com/redmi-note-8-pro/how-to/guide-redmi-note-8-pro-megathread-t4056527
JuanM2020 said:
Well there is now a way to bypass the need for an authorized account, if you device is unbricked. Basically if you flash this before you brick your phone, it allows you to use sp flash to unbrick it without authorized account.
Read this thread:
https://forum.xda-developers.com/redmi-note-8-pro/how-to/guide-redmi-note-8-pro-megathread-t4056527
Click to expand...
Click to collapse
doesn't work
samadsaba said:
doesn't work
Click to expand...
Click to collapse
This is only for unbricked devices.... As I stated. If your device was already bricked it won't help you.
I also faced this problem... I used paid service to unbrick it... I must pay 35USD for the service.. but just wait.. If it works I will post here again. I bricked my phone when flashed anti brick on Android 10.. I forgot downgrade it to Android 9
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.
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.