Related
been looking around on here. im stuck now
Ok iv unlocked and have root and can load into Clockwork 5.5.0.2
But when in Clockwork i get
E:can't mount /sdcard/
When i reboot the nexus now all i get is the Google Logo with the unlock Padlock.
Once it did load back into OS and then rebooted it self now stuck on Google logo and Unlock padlock... i Didnt copy over my ROM too the SDCard....
How do i get back into the OS
Flash the factory Google images via fastboot. Search the forum. There a quite a few threads with step by step instructions.
Sent from my Galaxy Nexus using xda premium
Try pressing the volume down button and power button until you reach recovery. When you a red triangle, press Vol+/Vol-/Power at the same time, you will now see a menu, select factory data reset.
I've been in your shoes, and I doubt a factory reset will help. If I were you, I would download the stock images first (lte or GSM nexus?). After that, try seeing if your drivers are configured and that tour phone is being recognized by your computer when it is plugged in with the USB cable. The drivers will need to be configured for when the phone is showing the Google logo, but also configured again when the phone is in the boot loader. (Ask if you need more instructions for this).
OK, what worked for me was locking and then unlocking my phone again. Type fast boot OEM lock, and if the drivers are good then the boot loader will lock. Then type fast boot OEM unlock and it will wipe everything--even Android backups. It shoud also delete the problem. After that you can push files to it from the computer but you might have to configure your drivers again (I did). Hope this helps, it worked for me.
??
throwbot said:
I've been in your shoes, and I doubt a factory reset will help. If I were you, I would download the stock images first (lte or GSM nexus?). After that, try seeing if your drivers are configured and that tour phone is being recognized by your computer when it is plugged in with the USB cable. The drivers will need to be configured for when the phone is showing the Google logo, but also configured again when the phone is in the boot loader. (Ask if you need more instructions for this).
OK, what worked for me was locking and then unlocking my phone again. Type fast boot OEM lock, and if the drivers are good then the boot loader will lock. Then type fast boot OEM unlock and it will wipe everything--even Android backups. It shoud also delete the problem. After that you can push files to it from the computer but you might have to configure your drivers again (I did). Hope this helps, it worked for me.
Click to expand...
Click to collapse
I can connect the phone and lock n unlock the bootloader. so the USB drivers ar working. but iv got no way of pushing the files onto it
NxsLS said:
I can connect the phone and lock n unlock the bootloader. so the USB drivers ar working. but iv got no way of pushing the files onto it
Click to expand...
Click to collapse
Have you tried flashing via fastboot? I would assume if fastboot oem unlock/lock works, then flashing using fastboot/android sdk should work.
...though, as a non dev, i have been wrong before
what do you mean by "pushing the files"? What are you trying to push?
Sent from my Galaxy Nexus using XDA App
Good, make sure you boot loader has been unlocked. You can use a program like the root toolkit (I don't think I can put a link to a different website) but he root toolkit for the nexus should help you push the stock image to your phone. Go to droid-life (.com, cough cough) and there is a set of instructions for returning back to stock. You can also use those same instructions to try and get her back up and running. Try the root toolkit they have on there, too. The only problem you might run into is having your phone set to USB debugging after unlocking the boot loader, bit it should still accept fast boot commands while I'm the bootloader
---------- Post added at 09:48 PM ---------- Previous post was at 09:42 PM ----------
sorry, by pushing the files I mean pushing the stock image file (the stock software, including the stock operating system, stock bootloader, and stock radios). A rom is a custom tweaked version of the stock software. When you unlock the bootloader, if you don't have stock software on there (which you wont if you were running a rom when it crashed) then it might erase everything, including the from you were running. You will have to push that stock software (stock image file) back to your phone using commands from your computer
no worrys o2 just sending me a new nexus :x
report lost n stolen :x only £30 ex
NxsLS said:
report lost n stolen :x only £30 ex
Click to expand...
Click to collapse
I hate that.. because you didn't know what you were doing and screwed up your phone someone is supposed to provide you with a new one? As a few posters have already said, it should be a fairly easy fix. You didn't even acknowledge that you tried any of the suggested fixes. If you're going to mess around with your phone make sure you know what you're doing, or at the very least exhaust all potential options to get yourself out of a soft brick. I'm sure an experienced Android user could have you up and running in 10 minutes. It's no wonder providers don't want to unlock bootloaders on some phones.. Jesus...
i tryed all i got it too boot back into the OS but reset itself and locked in google with unlocked padlock. so gave up and will not make the same mistake of not copying over the rom after the root n unlock.. i have flashed/unlocked my samsung s2 with ODIN which was easy but the Nexus i used Galaxy Nexus ToolKit
Hello! A friend of mine give me his phone to fix it. It was stuck on the Exclamation Mark and Phone image. I flashed it with Flashtool and LT15i_4.1.B.0.431_Generic.Central.Europe.1.1247-1041. Now, the phone works, it boots and so on.
1st problem : the wifi doesn't work, it gets stuck at turning on.
2nd problem : i can't access flash mode, i tried like a million times, no luck (it used to work though, now it just enters charge mode and that's it). Without flash mode, i can't flash a new FW or ROOT/install CWM to repair wifi.
3rd problem : the phone sees a new update, 4.1.B.0.587, but it can't install it over wap, and i can't flash it either.
4th problem : PCC/SEUS can't update the phone/nor repair it, tough the phone is seen and detected.
I'm open for advices on how to fix those issues. Thank you very much in advance.
Can you get it into fasboot mode?
pypcier said:
Can you get it into fasboot mode?
Click to expand...
Click to collapse
You mean press menu key and power? If so, no as far as i remember.
if PC companion dont recognize phone, first you need flash orginal rom, if I dont mistake after any flashing you again need check "unknown sources" and debugg in options. When you flash rom, next repair with PC companion
AW: Handful of problems!
FallenReb said:
if PC companion dont recognize phone, first you need flash orginal rom, if I dont mistake after any flashing you again need check "unknown sources" and debugg in options. When you flash rom, next repair with PC companion
Click to expand...
Click to collapse
the problem is (as i took it out of his post), that he can't flash anything.
did your friend unlocked his bootloader? if so, when he did it with the official method, then it is normal that seus doesn't recognize the phone...
Sent from my Xperia Arc S using xda premium
If you cannot use SEUS, then you prolly have an unlocked bootloader.
Flash a kernel with cwm like advanced stock and post back with info.
If you still get stuck, try to flash a rom from dev section, or/and post a logcat with the errors
Like i told in my original post : I CAN'T enter flash mode, and the phone IS SEEN by SEUS/PCC (but it can't repair, nor update it, since it requires flash mode)
About the unlocked bootloader, i don't know.
Klamatiel said:
Like i told in my original post : I CAN'T enter flash mode, and the phone IS SEEN by SEUS/PCC (but it can't repair, nor update it, since it requires flash mode)
About the unlocked bootloader, i don't know.
Click to expand...
Click to collapse
Well, it might be worth the idea to unlock the bl, download a custom rom, flash a custom kernel which fits with this rom, flash the rm, and afther that, flash back the generic firmware. IK, it's a crazy idea, but maybe it helps
ragards - Cartman
Edit: flash custom kernel via fastboot, (which is usual the way), so you do not need flashmode
I will unlock the bootloader, if it's really necessary (i think it's not unlocked). Though i'm pretty sure i CAN'T, since i can't use fastboot, same problem as flashmode.
AW: Handful of problems!
well, first unlock bl and try, if that won't work, then you have to live without wifi.
regards - Cartman
Sent from my girls pants
I have a Samsung galaxy S3 SGH-I747 ATT. I followed the steps on xda developers forum here to root and unlock bootloader using the samsung galaxy toolkit. I have not installed any custom roms as yet. I just copied the zip for Hyderdrive onto my phone and restarted it. Boom! Phone doesn't start. Tried recovery,download and just powering on, no luck. The phone doesn't get recognized on Odin. But, it still gets detected on the toolkit. But for me to do anything it asks me to enable USB debugging, which I am not able to cause the phone doesn't switch on. I tried just pluggin in and plugging out the usb cable. It makes the beep noise that we hear when we connect the phone to the system, but that's about it. Doesn't get recognized as a drive on the computer. Is this a hardbrick?
Edit: I don't think it's being recognized on the toolkit. I don't see any serial number on it.
Hyderdrive? whats that? You don't need to unlock the bootloader for the s3, it comes unlocked. Your phone can't be bricked just by copying a zip file to it.
What exactly did you do?
m82a1 said:
Hyderdrive? whats that? You don't need to unlock the bootloader for the s3, it comes unlocked. Your phone can't be bricked just by copying a zip file to it.
What exactly did you do?
Click to expand...
Click to collapse
That's pretty much exactly what happened.
Installed device drivers.
Backed up my data.
Rooted the phone by following all the steps. [ The problem is I do not remember if I chose Clockworkmod Recovery or TWRP Touch Recovery ]
Installed and Ran EZ-Unlock -- to unlock bootloader.
** At this point, My phone is rooted and I can access superU and EZ-Unlock apps.
**Here's the part I'm not too sure of.
From the main menu of the toolkit, I chose:
option 5 [Flash Custom Recovery via Odin] and chose option 1 [Flash Clockworkmod Recovery] -- This I am certain of.
So using Odin-->Pad-->I browse to the directory of the recovery file in the toolkit folder and Run it. I get the RESET Okay message on Odin. Should I be seeing a green PASS message on top? I'm not too sure. I only got a RESET in purple.
Exit out of odin.
Downloaded Hyperdrive RLS15 from here
Copied the Zip into my phone.
[Phone works perfectly fine till here]
I power off the phone and try to start in the recovery, download mode. Nothing works.
You ran an app to unlock a Verizon S3 bootloader, a process which 1. is unnecessary on an AT&T S3 and 2. will seriously mess with the bootloader which will hard brick your phone. If you take a look in this thread, you'll see that you pretty much have to send it somewhere to get it fixed.
FoxTrotz said:
You ran an app to unlock a Verizon S3 bootloader, a process which 1. is unnecessary on an AT&T S3 and 2. will seriously mess with the bootloader which will hard brick your phone. If you take a look in this thread, you'll see that you pretty much have to send it somewhere to get it fixed.
Click to expand...
Click to collapse
Well, that explains a lot. Thanks for your help. I'll probably have to send it in to get it fixed. FML.
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?
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.