Develop Bugs

[Q] Nexus stuck in boot loop. how get to install drivers?

Hey guys i've been looking through alot of google and can't seem to come up with anything so i turn to you awesome people.
My friend got a Galaxy Nexus GSM and he bought it with a boot loop problem. The phone is rooted and bootloader unlocked. I know because i can go to CWM recovery and also theres the unlock sign on it. However I can't get my computer to recognize it what so ever not even mount the storage. I figure i need to get the drivers to install but i need it to be recognized in device manager to do it through a rootkit. I tried to install the ADB drivers but also got no luck. I then tried to get to ODIN for it to work but ODIN won't recognize it either. Is there any way to install the drivers so i can put on a ROM on this. I think the person he bought it from formatted everything and messed it up. Is there anyway i can install the drivers without getting it to recognize first? I tried it in windows 7 and in windows 8. ANY HELP IS GREATLY APPRECIATED!!!

dnpmoney45 said:
Hey guys i've been looking through alot of google and can't seem to come up with anything so i turn to you awesome people.
My friend got a Galaxy Nexus GSM and he bought it with a boot loop problem. The phone is rooted and bootloader unlocked. I know because i can go to CWM recovery and also theres the unlock sign on it. However I can't get my computer to recognize it what so ever not even mount the storage. I figure i need to get the drivers to install but i need it to be recognized in device manager to do it through a rootkit. I tried to install the ADB drivers but also got no luck. I then tried to get to ODIN for it to work but ODIN won't recognize it either. Is there any way to install the drivers so i can put on a ROM on this. I think the person he bought it from formatted everything and messed it up. Is there anyway i can install the drivers without getting it to recognize first? I tried it in windows 7 and in windows 8. ANY HELP IS GREATLY APPRECIATED!!!
Click to expand...
Click to collapse
read the stickies
http://forum.xda-developers.com/showthread.php?t=1626895
Pay attention to Section A. Forget Odin, no need to be using that.

First off thanks so much for the reply and help it is very aprreciated!
Secondly i did come across this sticky however like i stated the phone is in a boot loop which means i cant get past the google logo in order to set it in developer mode and set usb-debugging neither can my computer recognize the phone when i plug it in, using the original cable i've tried every port there is on my desktop and laptop and nothing comes up in device manager. The phone is completely wiped and no OS is on it. Is there any way i can get a ROM on the phone?! This is one idea i have but i don't know if it'll work, I was thinking of buying a another working nexus install the drivers with that one and then i can get the bootloop one to get recognized? and return the new one. Will that work?

dnpmoney45 said:
First off thanks so much for the reply and help it is very aprreciated!
Secondly i did come across this sticky however like i stated the phone is in a boot loop which means i cant get past the google logo in order to set it in developer mode and set usb-debugging neither can my computer recognize the phone when i plug it in, using the original cable i've tried every port there is on my desktop and laptop and nothing comes up in device manager. The phone is completely wiped and no OS is on it. Is there any way i can get a ROM on the phone?! This is one idea i have but i don't know if it'll work, I was thinking of buying a another working nexus install the drivers with that one and then i can get the bootloop one to get recognized? and return the new one. Will that work?
Click to expand...
Click to collapse
You need to get adb to work with your device, which you can do in a custom recovery. You don't need to have USB debugging enabled, you would if you were booting into the OS, but not the recovery.
You can get drivers setup while in recovery or fastboot just as easy as if you were booted into the OS, so no you don't need another device.

cupfulloflol said:
You need to get adb to work with your device, which you can do in a custom recovery. You don't need to have USB debugging enabled, you would if you were booting into the OS, but not the recovery.
You can get drivers setup while in recovery or fastboot just as easy as if you were booted into the OS, so no you don't need another device.
Click to expand...
Click to collapse
thanks thats great news cause i dont have that kind of cash but how do i get ADB to work with the phone every installation guide i've looked at requires that i have the phone recognized om device manager. Is there anyway to install adb without having the device to recognize?

dnpmoney45 said:
thanks thats great news cause i dont have that kind of cash but how do i get ADB to work with the phone every installation guide i've looked at requires that i have the phone recognized om device manager. Is there anyway to install adb without having the device to recognize?
Click to expand...
Click to collapse
again, read the thread i gave you. if you're still asking this question, read it again.

Isn't that for the nexus 4? And I did pay attention to section A but it told me how to install the drivers which is the same way as every other tutorial I've looked at. My device doesn't show up on my computer and I can't install their way. As for the fastboot driver installation idk what their talking about. I followed the instructions though and got no results. I didn't do the whole thing cause for part C I need the original rom for galaxy nexus and also I don't know if the platform tools zip is for my device so I haven't gone through with it just yet. I'm sorry it's not my phone so I don't want to mess it up even further. I've read about the part with it being in recovery mode with the volume up + power option but I'm at work and haven't tried that yet but I doubt that will work since the phone is clean. Can u please be a little more specific there's 99 pages that I have to go through for that sticky. If u can't it's ok I'll just have to go through it next week. Once again thanks for pointing me in the right direction and giving me some hope.
Sent from my Nexus 4 using xda premium

WTF, how in the hell did that thread get here, sorry man
This is the right one
http://forum.xda-developers.com/showthread.php?t=1626895
a maguro wrote this.

Oh ok thanks this makes a lot more sense. Sorry for not telling u that earlier lol.
seriously thanks ill try it tonight.
Sent from my Nexus 4 using xda premium

ok so i tried the link but im always stuck with part A. When i go into fastboot and then try the command "fastboot devices" it hangs on waiting for the device. I can't see the device anywhere on my computer to install the fastboot drivers as instructed by 1wayjonny in this post http://forum.xda-developers.com/showpost.php?p=20058157&postcount=1
Am i missing something here? i did everything in the other steps such as downloading all the files into the same directory and everything. Im using windows 7 and i updated all my drivers for usb and even tried different usb cables including the original and usb2.0 and 3,0 ports but still no dice. I also tried it on windows 8 and got the nada.

dnpmoney45 said:
I can't see the device anywhere on my computer to install the fastboot drivers as instructed by 1wayjonny in this post http://forum.xda-developers.com/showpost.php?p=20058157&postcount=1
Click to expand...
Click to collapse
You reboot the device into bootloader/fastboot mode, then you connect the USB, and there's no sign at all that a USB device has been installed?
Remove all drivers, reboot, and start over. Get a tool for Windows that allows you to really dig on all of the installed drivers and remove all Nexus devices drivers permanently. Rant: Umm, Windows sucks bad. Thanks Linus!

bk201doesntexist said:
You reboot the device into bootloader/fastboot mode, then you connect the USB, and there's no sign at all that a USB device has been installed?
Remove all drivers, reboot, and start over. Get a tool for Windows that allows you to really dig on all of the installed drivers and remove all Nexus devices drivers permanently. Rant: Umm, Windows sucks bad. Thanks Linus!
Click to expand...
Click to collapse
I've done it both ways just to ensure it wasn't something that simple. I uninstalled all drivers i can possibly find theres non no where i used CC to look for more and device deview and even unistalled the java se and eclipse and android SDK and all the packages and installed them again and still nothing. My nexus 4 however recognizes both in adb and fastboot ......

Anything at all? Anyone?
Sent from my Nexus 4 using xda premium

dnpmoney45 said:
Anything at all? Anyone?
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Well, maybe you could try omapflash. If you can't get several PCs to see the device, then something's wrong with the USB port?
Not even on Linux?
a manta wrote this.

bk201doesntexist said:
Well, maybe you could try omapflash. If you can't get several PCs to see the device, then something's wrong with the USB port?
Not even on Linux?
a manta wrote this.
Click to expand...
Click to collapse
I did a little looking up about omapflash and from what i can see so far there needs to be drivers installed first. I may be wrong but i have to do some more research on it and i dont have a linux pc my laptop is down thanks to a power pin connector pin being pulled out. and i dont know if the device port is good or bad i can get a charge but that doesnt mean its fine. What if i get another device and install drivers via that and then try to get it to recognize? would that work?

dnpmoney45 said:
What if i get another device and install drivers via that and then try to get it to recognize? would that work?
Click to expand...
Click to collapse
To really make sure that the issue isn't on the host side but rather the USB port on the device? Yeah, that would rule it out.
Also, I just remembered: you're not using the USB ports of your PC case are you? Make sure you're using the motherboards' own USB ports.
a maguro wrote this.

bk201doesntexist said:
To really make sure that the issue isn't on the host side but rather the USB port on the device? Yeah, that would rule it out.
Also, I just remembered: you're not using the USB ports of your PC case are you? Make sure you're using the motherboards' own USB ports.
a maguro wrote this.
Click to expand...
Click to collapse
Thats all it would do?! What about making me able to install the drivers and get the phone to be recognized? No wont work im dreaming?
And no im not using case ports at all i use them for charging and thats all i know at least that those arent reliable.

Windows 8 64-bit...drivers install...stuck
even I am stuck on the same roadblock. have my GNex stuck on the google logo. can access recovery mode though (TWRP 2.5.0.0). Now i just upgraded my PC to Windows 8 64-bit and cant seem to be able to install drivers.
the problem is that almost all the methods require:
1. GNex to be connected with USB Debugging ON
2. install ADB Drivers
3. get into Fastboot or Recovery
4. install Bootloader Drivers
since i cant get past the Google logo on my GNex...i cant perform Steps 1 & 2.
and if i directly try to install the bootloader drivers the OS returns an error (yellow exclamation next to the installed driver)
Added pictures to help explain better.
Thnx in advance.

rej_ares said:
even I am stuck on the same roadblock. have my GNex stuck on the google logo. can access recovery mode though (TWRP 2.5.0.0). Now i just upgraded my PC to Windows 8 64-bit and cant seem to be able to install drivers.
the problem is that almost all the methods require:
1. GNex to be connected with USB Debugging ON
2. install ADB Drivers
3. get into Fastboot or Recovery
4. install Bootloader Drivers
since i cant get past the Google logo on my GNex...i cant perform Steps 1 & 2.
and if i directly try to install the bootloader drivers the OS returns an error (yellow exclamation next to the installed driver)
Added pictures to help explain better.
Thnx in advance.
Click to expand...
Click to collapse
SOLVED (Dont know how but it worked):
1. Factory reset (TWRP)
2. Installed an old ROM which was already on the GNex
3. Restart...it gets stuck at the Google logo...remove battery
4. TWRP - Factory reset
5. reboot...

[Q] tried everything can't use fastboot - begging and pleading for help!

OK so I am using windows 8.1; have searched everywhere and tried just about everything imaginable but I still cant get fastboot to work with my HTC One. The phone is recognized fine when I type adb devices on the main screen, however, when I boot into fastboot the phone is simply not recognized by Windows any longer. I get the message USB DEVICE NOT RECOGNIZED. I am currently looking to update my HBOOT which is 1.54.0000 and was under the impression that I need to do a fastboot flash to do this. I am currently running Viper Rom 5.8.
I am desperate here and am willing to make a donation to the person who solves my issue.

MightyChigger said:
OK so I am using windows 8.1; have searched everywhere and tried just about everything imaginable but I still cant get fastboot to work with my HTC One. The phone is recognized fine when I type adb devices on the main screen, however, when I boot into fastboot the phone is simply not recognized by Windows any longer. I get the message USB DEVICE NOT RECOGNIZED. I am currently looking to update my HBOOT which is 1.54.0000 and was under the impression that I need to do a fastboot flash to do this. I am currently running Viper Rom 5.8.
I am desperate here and am willing to make a donation to the person who solves my issue.
Click to expand...
Click to collapse
You need a Windows 7 pc.

Chilidog said:
You need a Windows 7 pc.
Click to expand...
Click to collapse
Come on. There are other choices.
Download Ubuntu. You can run it from an installation medium without actually installing it.

Chilidog said:
You need a Windows 7 pc.
Click to expand...
Click to collapse
well unfortunately for me, I dont have one... can this be done on Windows 8.1?

jpradley said:
Come on. There are other choices.
Download Ubuntu. You can run it from an installation medium without actually installing it.
Click to expand...
Click to collapse
Don't know anything about Ubuntu....would probably create more issues trying to figure this out. One way or another, I need to get fastboot working on my machine right??

MightyChigger said:
Don't know anything about Ubuntu....would probably create more issues trying to figure this out. One way or another, I need to get fastboot working on my machine right??
Click to expand...
Click to collapse
After sending to HTC to have the camera sensor fixed I could no longer get fastboot to work and I had to suffer with stock for a couple of months. I finally resolved this by updating sdk having read recent Windows 7 updates could be the culprit, maybe it was a usb driver update, but was still having issues.I read to try turning usb debug off and on which in the end may have been all that was required. Finally back to S-off running Viper 6.1 which team Viper deserves major props on for a brilliant job. BTW I'm on Windows 7 Ultimate with usb 3 ports only.

Go here and watch the first video: http://forum.xda-developers.com/showthread.php?t=2703585

[SCRIPT][BATCH][TOOL]Motorola Moto 360 Super Tool bootloader unlock, root, & Restore

[SCRIPT][BATCH][TOOL]Motorola Moto 360 Super Tool bootloader unlock, root, & Restore
Motorola Moto 360 Super Tool
View attachment 2962247
View attachment 2962248
WARNING USE THIS TOOL AT YOUR OWN RISK. I AM NOT RESPONSIBLE FOR ANY DAMAGE OR BRICKED DEVICES.
That Being said I have tested this on my device many times without any problems
Download the Super Tool HERE
Motorola Moto 360 Super Tool Options
1. Install adb and fastboot drivers from motorola and test them
2. unlock the bootloader of the watch
3. relock the bootloader of the watch
4. flash stock wear recovery image
5. flash stock wear boot image
6. restore your Moto 360 to stock KGW42N official
7. Root the Moto 360
8. flash TWRP recovery
9. boot to TWRP recovery from bootloader mode
VIDEO ON USING THIS TOOL
http://youtu.be/FMrywAnwqZ0
Latest Super Tool Version 5
CHANGE LOG
Version 1
based on KGW42N Firmware
Version 2
based on KGW42R Firmware
CLeaned up batch file script
Version 2.1
Added TWRP recovery
Added Lollipop Root with TWRP recovery and supersu.zip
Added boot to TWRP from Bootloader and removed boot to stock recovery from bootloader
Version 3
Based on LWX48T Firmware Lollipop android 5.0.1
Version 4
Based on LWX49L Firmware Lollipop android 5.0.2
Version 5
Based on LDZ22O Firmware Lollipop android 5.1.1
Requirements to use this Motorola Moto 360 Super tool
USB interface cable. if you need one watch this video on how to make it
Download the Super Tool HERE at RootJunkysdl.com
Know how to remove the watch band. check this VIDEO
May have a Video coming on how to use this tool soon

i downloaded version 2 and again it cannot send the boot.img
i tried to flash stock firmware and on the sending 'motoboot' it says FAILED data transfer failure (too many links)
The only thing i can do is lock and unlock the bootloader.

vincenzo697 said:
i downloaded version 2 and again it cannot send the boot.img
i tried to flash stock firmware and on the sending 'motoboot' it says FAILED data transfer failure (too many links)
Click to expand...
Click to collapse
It sounds like you didn't unlock your bootloader yet. That or your fastboot drivers are not installed. Run the driver test in the tool

The only thing i can do is lock and unlock my bootloader. Its weird because i follow all your steps

vincenzo697 said:
The only thing i can do is lock and unlock my bootloader. Its weird because i follow all your steps
Click to expand...
Click to collapse
I have a idea to clean up any problems you might be having. In my tool folder there is a program called rsdlite install it and then connect the device in bootloader / fastboot mode. Then it will show up in rsd lite. next select the XML file in the folder and flash the watch to factory. See if this fixes the problems

Tomsgt said:
I have a idea to clean up any problems you might be having. In my tool folder there is a program called rsdlite install it and then connect the device in bootloader / fastboot mode. Then it will show up in rsd lite. next select the XML file in the folder and flash the watch to factory. See if this fixes the problems
Click to expand...
Click to collapse
Thanks my friend. When I will go home I will try it and report back.

vincenzo697 said:
Thanks my friend. When I will go home I will try it and report back.
Click to expand...
Click to collapse
Good luck hopefully you have used rsd lite before.

Tomsgt said:
Good luck hopefully you have used rsd lite before.
Click to expand...
Click to collapse
I tried it but again it doesnt pass the first step. If you come with another idea please tell me.

Unfortunately, My comp doesnt reconize the watch. It just comes up with unreconized device. I have tried 2 diff cables, 3 diff comps, uninstalled, reinstalled drivers multiple times. ANY ideas what could be the issue??

suzook said:
Unfortunately, My comp doesnt reconize the watch. It just comes up with unreconized device. I have tried 2 diff cables, 3 diff comps, uninstalled, reinstalled drivers multiple times. ANY ideas what could be the issue??
Click to expand...
Click to collapse
manually install the motorola adb and fastboot drivers in device manager on the computer. the computer will say that they arent compatible but they will work.

Tomsgt said:
manually install the motorola adb and fastboot drivers in device manager on the computer. the computer will say that they arent compatible but they will work.
Click to expand...
Click to collapse
Well, where are the drivers????? I have the packages in the download, but there are no seperate drives. Thanks for the reply

suzook said:
Well, where are the drivers????? I have the packages in the download, but there are no seperate drives. Thanks for the reply
Click to expand...
Click to collapse
in device manager you will see update devices click it then click manually install. next look at both compatible and uncompatible drivers until you find the motorola drivers. then pick one if it works good and if not then try a different one.
Some times i have to install them manually like this. also make sure usb debugging is turned on on the moto 360 watch. the computer will not see it without this step.

Tomsgt said:
in device manager you will see update devices click it then click manually install. next look at both compatible and uncompatible drivers until you find the motorola drivers. then pick one if it works good and if not then try a different one.
Some times i have to install them manually like this. also make sure usb debugging is turned on on the moto 360 watch. the computer will not see it without this step.
Click to expand...
Click to collapse
Thanks, i have tried all that...im just about out of options.

suzook said:
Thanks, i have tried all that...im just about out of options.
Click to expand...
Click to collapse
Are you sure you are connecting the cable to the correct 4 pins on the watch? This can be confusing because if you flip it over to connect the cable the connections flip also.

Tomsgt said:
Are you sure you are connecting the cable to the correct 4 pins on the watch? This can be confusing because if you flip it over to connect the cable the connections flip also.
Click to expand...
Click to collapse
Yup, double checked wiring, pin, 3 diff comps, everything. Guess I wont have root if I can never get the proper drivers installed. Bummer, thanks for your time.

Hello
Download link is dead
upload new link pls

scumpicule said:
Hello
Download link is dead
upload new link pls
Click to expand...
Click to collapse
download link works fine try again

No more USB after Root??
I was able to unlock the BL and Root my Moto 360 with your tool, thank you very much for the "easy way"!! My concern is that now I cannot reconnect via USB. I have even made 2 more connectors and nothing, not even the USB connection sound. Is this a normal side effect? or did I screw it up? I'm leaning on user error because I was pulling the connector off the watch before unplugging it from the computer and it zapped, shut down the PC and rebooted the watch. Watch seems to be fine, no noticeable issues after it rebooted. So I dunno...

burkebacar said:
I was able to unlock the BL and Root my Moto 360 with your tool, thank you very much for the "easy way"!! My concern is that now I cannot reconnect via USB. I have even made 2 more connectors and nothing, not even the USB connection sound. Is this a normal side effect? or did I screw it up? I'm leaning on user error because I was pulling the connector off the watch before unplugging it from the computer and it zapped, shut down the PC and rebooted the watch. Watch seems to be fine, no noticeable issues after it rebooted. So I dunno...
Click to expand...
Click to collapse
you probably need to uninstall the device in device manager then let the drivers install again

Tomsgt said:
you probably need to uninstall the device in device manager then let the drivers install again
Click to expand...
Click to collapse
I'll give that a shot! Thanks
I'll report back with how it goes.

ZenFone 2 Bootloader problem. Need help.

I recently recoverd from a brick using the usual xfstk downloader asus flash tool ect... i think i quit the asus flash tool too early and it left me with a buggy android. my problem is. there is no bootloader! when i try get to it ( even through adb) theres nothing there! but theres a fully working android. I tried to use xfstk downloader again, and when it says "continuing to os" all it does is put me in android with no bootloader. I really want a way to fully wipe my device so i can start fresh again. Is this safe? is there a better way?

that's why i always recommend to use commands method to flash after xfstk. any ways enable developer option and usb debugging. then connect to pc and run command adb reboot recovery. most probably you will boot into recovery factory reset there and sideload latest firmware downloaded from asus website.
if you are rooted then you can flash bootloader via dd commands

sukhwant717 said:
that's why i always recommend to use commands method to flash after xfstk. any ways enable developer option and usb debugging. then connect to pc and run command adb reboot recovery. most probably you will boot into recovery factory reset there and sideload latest firmware downloaded from asus website.
if you are rooted then you can flash bootloader via dd commands
Click to expand...
Click to collapse
I tried to do the adb thing. and it just took me into the os
i am not rooted. is there any hope for me?

aceaidan said:
I tried to do the adb thing. and it just took me into the os
i am not rooted. is there any hope for me?
Click to expand...
Click to collapse
then do xfstk again and flash raw via commands

sukhwant717 said:
then do xfstk again and flash raw via commands
Click to expand...
Click to collapse
I know it sounds like allot, but can you tell me how to do these things. I'm a total noob and you sound like a nice guy.

sukhwant717 said:
then do xfstk again and flash raw via commands
Click to expand...
Click to collapse
Also the xfstk won't complete because when it says continuing to os. It just takes me back to android.

I recommend to use this guide
https://forum.xda-developers.com/showthread.php?p=68477856
It's the only way to get my ZE551ML run again.
After using xfstk, go forward without AsusFlashTool and do all steps manually as described in the guide. It helped me to get my bricked ZF2 run again with newest MM.
Good luck.

aceaidan said:
Also the xfstk won't complete because when it says continuing to os. It just takes me back to android.
Click to expand...
Click to collapse
here are few things you can do! wipeout ifwi on emmc. and then use latest MM ifwi on marshmallow. if still same open back panel of the phone disconnect battery connector and place small paper under connector leave it like 7 days and after that try xfstk again with original files

mobil_z said:
I recommend to use this guide
https://forum.xda-developers.com/showthread.php?p=68477856
It's the only way to get my ZE551ML run again.
After using xfstk, go forward without AsusFlashTool and do all steps manually as described in the guide. It helped me to get my bricked ZF2 run again with newest MM.
Good luck.
Click to expand...
Click to collapse
Can you please link me to the manual files for mm in stuck on the first stock android.

aceaidan said:
Can you please link me to the manual files for mm in stuck on the first stock android.
Click to expand...
Click to collapse
didnt get you point!
what does you mean by first stock android?
what files you are asking for MM?
what exactly you want to do?

aceaidan said:
Also the xfstk won't complete because when it says continuing to os. It just takes me back to android.
Click to expand...
Click to collapse
It may be a fault in some other guides by addressing in xfstk.
The right address is 0x80000807, some other guides show 0x800000807, one 0 too much!
The guide I linked to does it right.

sukhwant717 said:
didnt get you point!
what does you mean by first stock android?
what files you are asking for MM?
what exactly you want to do?
Click to expand...
Click to collapse
My acrossim running android 5.0 and I want my bootloader back and then I want the mm files like system.img ect... So I can get mm

aceaidan said:
So I can get mm
Click to expand...
Click to collapse
If you finally want to go to MM, you can install it directly if your phone is broken now. So you will get a very clean MM without messed up from updading from LP! Really recommend.

hey ,i have same problem with my asus zenphone 2 , had you got any perfect solution? please help!!
every time i tried to flash files using xfstk is show countinuing to os and then show error - enable to connect with device!!

Question Phone bricked trying to update December patch

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.