Develop Bugs

[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.

[Q] Note 2

Hi
I have a Note 2 (international GT-N7100) that does not start. It shows a firmware upgrade error (attached) when i switch it on. I can only enter download mode (attached). I am being told the phone suffered SDS but in download mode you can still see the product name (attached). Prior to the problem i have never been rooted or had a custom ROM installed. It simply rebooted one day all by itself and when booting showed the upgrade error
I have tried re flashing via Odin in everyday possible, including the PIT file. All methods fail. A friend as said the bootloader is corrupt. I tried re flashing that but also no luck.
Is there a way of using an external SD card to get up and running? Or any other ideas out there.
Thanks and much appreciated.
Geoff

grwalker said:
Hi
I have a Note 2 (international GT-N7100) that does not start. It shows a firmware upgrade error (attached) when i switch it on. I can only enter download mode (attached). I am being told the phone suffered SDS but in download mode you can still see the product name (attached). Prior to the problem i have never been rooted or had a custom ROM installed. It simply rebooted one day all by itself and when booting showed the upgrade error
I have tried re flashing via Odin in everyday possible, including the PIT file. All methods fail. A friend as said the bootloader is corrupt. I tried re flashing that but also no luck.
Is there a way of using an external SD card to get up and running? Or any other ideas out there.
Thanks and much appreciated.
Geoff
Click to expand...
Click to collapse
Have you tried doing as it says? As in install Drivers on your PC and use Samsung Kies Software to restore it?

Coconuttyguy said:
Have you tried doing as it says? As in install Drivers on your PC and use Samsung Kies Software to restore it?
Click to expand...
Click to collapse
Yes i have. The phone does not connect to Kies. Kies wont recognise my phone. See attached.
Any other suggestions please?
Thanks

grwalker said:
Yes i have. The phone does not connect to Kies. Kies wont recognise my phone. See attached.
Any other suggestions please?
Thanks
Click to expand...
Click to collapse
You're using the wrong version of Kies, Kies 3 is for the Note 3 and devices made after it. Try downloading the original Kies http://www.samsung.com/uk/support/usefulsoftware/KIES/#none

Coconuttyguy said:
You're using the wrong version of Kies, Kies 3 is for the Note 3 and devices made after it. Try downloading the original Kies http://www.samsung.com/uk/support/usefulsoftware/KIES/#none
Click to expand...
Click to collapse
Tried that version of Kies. Kies tries to connect for about 10 minutes then says is cant connect.
Any other ideas please?
Thanks

grwalker said:
Tried that version of Kies. Kies tries to connect for about 10 minutes then says is cant connect.
Any other ideas please?
Thanks
Click to expand...
Click to collapse
Have you tried other versions of Odin/ USB cables / Computers?

Coconuttyguy said:
Have you tried other versions of Odin/ USB cables / Computers?
Click to expand...
Click to collapse
Yes, yes and yes, including a PC running XP
Thanks

grwalker said:
Yes, yes and yes, including a PC running XP
Thanks
Click to expand...
Click to collapse
Can you enter stock recovery mode?

Coconuttyguy said:
Can you enter stock recovery mode?
Click to expand...
Click to collapse
No. The phone can only enter download mode. (Vol down, Home and Power).
Vol up, Home and Power keeps taking me to the firmware upgrade error screen.
Removing battery and pressing power on button also takes me to the firmware upgrade error screen.
Thanks

grwalker said:
No. The phone can only enter download mode. (Vol down, Home and Power).
Vol up, Home and Power keeps taking me to the firmware upgrade error screen.
Removing battery and pressing power on button also takes me to the firmware upgrade error screen.
Thanks
Click to expand...
Click to collapse
Since your Knox counter is still untripped, I'd recommend contacting Samsung as I'm pretty sure the SDS has no software fix.

Coconuttyguy said:
Since your Knox counter is still untripped, I'd recommend contacting Samsung as I'm pretty sure the SDS has not software fix.
Click to expand...
Click to collapse
Already done that. Samsung say there is no warranty. Phone is 18 months old.
Thanks

grwalker said:
Already done that. Samsung say there is no warranty. Phone is 18 months old.
Thanks
Click to expand...
Click to collapse
Okay could you try and include Odin screenshots

Coconuttyguy said:
Okay could you try and include Odin screenshots
Click to expand...
Click to collapse
Here are some screenshots
Thanks

grwalker said:
Here are some screenshots
Thanks
Click to expand...
Click to collapse
Hey have you tried Odin 3v1.87 I know that the partition error is very common on the later Odin clients.
Also make sure to uninstall Kies before using Odin as it nearly always interferes.

Coconuttyguy said:
Hey have you tried Odin 3v1.87 I know that the partition error is very common on the later Odin clients.
Also make sure to uninstall Kies before using Odin as it nearly always interferes.
Click to expand...
Click to collapse
Yes i have tried. Flashing PIT and Odin just hangs.

SM-T800 Soft Bricked, PC Won't Recognized and "Yes, I already tried that"

Samsung SM-T800 is basically a paperweight.
Out the outset, let me just say that I have already:
-voided my warranty and tripped KNOX (it was rooted before all of this happened)
-Tried different USB ports and USB cables
-Tried different USB drivers
My PC won't recognize it, and I have tried Universal Drivers, and Samsung USB drivers, which means Odin and ADB can't help
I can only boot into download mode
When I tr to boot into recovery, I get the "Firmware upgrade encountered an issue" message
And to add insult to injury, I can't even turn the damned thing off. Every "battery pull" (Power+Volume down) leads back to "Firmware upgrade encountered an error" message
I have been wrestling with this thing for 2 days already, scouring these forums. And every one ends with "Oh I just reloaded my stock ROM with Odin" ARGHHHHH!
Thanks in advance

OK I'm gonna start off by saying I'm trying to help you. If you get smart and angry then I'll leave you to it.
Why am I saying this? Because I've been down this road many times with people saying this that and the other doesn't work when in the end in most cases it turns out to be user error and I can tell you're frustrated.
I've read your post regarding what you've tried but you're still gonna have to bear with it if you want help.
The first thing I need to ask is, you know the difference between download mode and recovery mode? No I'm not trying to treat you like an idiot.
Sometimes the firmware error can be cleared by booting to recovery and wiping cache.
How did you end up in this scenario?
If the above doesn't work the first thing you need to do is put the tablet in download mode.
Connect the USB cable, navigate to device manager, look for something along the lines of Samsung mobile USB composite device under USB devices.
If you see an exclamation mark instead then you will have to manually install the USB composite driver.
Once you see that device listed you are ready to use odin in download mode.

ashyx said:
OK I'm gonna start off by saying I'm trying to help you. If you get smart and angry then I'll leave you to it.
Why am I saying this? Because I've been down this road many times with people saying this that and the other doesn't work when in the end in most cases it turns out to be user error and I can tell you're frustrated.
I've read your post regarding what you've tried but you're still gonna have to bear with it if you want help.
The first thing I need to ask is, you know the difference between download mode and recovery mode? No I'm not trying to treat you like an idiot.
Sometimes the firmware error can be cleared by booting to recovery and wiping cache.
How did you end up in this scenario?
If the above doesn't work the first thing you need to do is put the tablet in download mode.
Connect the USB cable, navigate to device manager, look for something along the lines of Samsung mobile USB composite device under USB devices.
If you see an exclamation mark instead then you will have to manually install the USB composite driver.
Once you see that device listed you are ready to use odin in download mode.
Click to expand...
Click to collapse
First of all, thanx for the reply. I appreciate, and i probably shouldn't have written the post after being up all night and bieng pissed...probably came off a little snarky...
Having said all of that, yeah, I'm definitely in download mode:
(on screen right now)
ODIN MODE
Product Name: SM-T800
Current Binary: Samsung Official
System Status: Official
Secure Download: Enabled
KNOX WARRANTY VOID: 1 (0x0000)
AP SWREV: A1
[Picture of Android icon]
Downloading...Do not turn off target
So, that bit is sorted out
UPDATE: I did not have my SD card in the tablet before...now I put it in and I got the "USB devices not recognized"
I go to Device Manager, find the device with the yellow exclamation, right click,
"Update driver software"
"Browse computer for driver software:
Navigate to "Program Files/Samsung/USB Drivers"
The best software for your device is already installed
Any suggestions?
And again, apologies for sounding like a jerk before
"

UPDATE 2
OK, so I took another swig at it..
downloaded "Samsung USB Driver V1..5.59"
Rebooted
Opened ODIN
[Added]
Started reinstaling firmware
[Removed]
ODIN lost connection and I got the "USB device not recognized message" again
Used a cpl different ports, no change
I am wondering if maybe it is a battery issue at this point? Because as I stated before, I havent been able to turn the tablet off...
Either it is in download mode, or it is in "FIrmware upgrade encountered an issue" on screen
Thanks in advance

Destro728 said:
UPDATE 2
OK, so I took another swig at it..
downloaded "Samsung USB Driver V1..5.59"
Rebooted
Opened ODIN
[Added]
Started reinstaling firmware
[Removed]
Click to expand...
Click to collapse
OK this looks like you have the driver installed so you shouldn't have the exclamation mark in device manager.
You can however install the driver manually.
Right click the device with exclamation mark, choose browse my computer, let me pick from a list of drivers. Look for Samsung Mobile CDC composite device, click next.
Driver should now install.
There are several reasons for the USB not recognized error. Most common is a bad USB cable, bad USB port or driver conflicts.
Ensure the ports are native and not an add-on card.
I suggest a completely different cable first.
Whatever happens don't move the device or cable when flashing.
Also get some charge in the device with the stock charger.
If you still get issues installing the stock Firmware then I suggest trying to install my latest build of TWRP.
With this we have more options and can install the stock Firmware with it.

Thanks for response
Ok, I used a totally different laptop and ODIN worked fine, I dunno what the deal was...but now i have a different problem...
I seem to be stuck in a "Wifi Turning on..." loop
The Wifi never comes on though
I have seen other posts about this, but they all seems to come back to " factory reset" (which I did two more times today) or verify the date on the device (which I have also done)
Is it possible to download a radio image ONLY? Because I am wondering if that is the problem....

Destro728 said:
Thanks for response
Ok, I used a totally different laptop and ODIN worked fine, I dunno what the deal was...but now i have a different problem...
I seem to be stuck in a "Wifi Turning on..." loop
The Wifi never comes on though
I have seen other posts about this, but they all seems to come back to " factory reset" (which I did two more times today) or verify the date on the device (which I have also done)
Is it possible to download a radio image ONLY? Because I am wondering if that is the problem....
Click to expand...
Click to collapse
Most likely a baseband issue.
You need to use the correct firmware for your device and region.
Did you flash the whole firmware?

Yeah, downloaded the whole firmware
Couldn't find version for USA proper...ended up using XEF (which is France I think)
Build number LRX22G.T800XXU1BOCC (Lollipop)

Destro728 said:
Yeah, downloaded the whole firmware
Couldn't find version for USA proper...ended up using XEF (which is France I think)
Build number LRX22G.T800XXU1BOCC (Lollipop)
Click to expand...
Click to collapse
USA is XAR(Cellular South)
http://www.sammobile.com/firmwares/download/64107/T800XXU1BOL1_T800XAR1BOK1_XAR/

Ah, I didn't think I should use that one since my tablet is the WiFi model, not the LTE model
But I will give it a shot!
Thanks!

Destro728 said:
Ah, I didn't think I should use that one since my tablet is the WiFi model, not the LTE model
But I will give it a shot!
Thanks!
Click to expand...
Click to collapse
That is for the wifi model. LTE model is T805.

ashyx said:
That is for the wifi model. LTE model is T805.
Click to expand...
Click to collapse
Ah. The "Cellular South" part threw me off
Unfortunately, still didn't work as far as getting the WiFi and Bluetooth working.
I refrlashed the firmware
Did a cpl factory resets
Still nothing
I'm thinking I should root it and see if some file permissions are screwed up or something. ..
Sent from my SAMSUNG-SM-G870A using XDA-Developers mobile app

UPDATE: I rooted with CF AutoRoot and installed Custom recovery TWRP
did another factory reset
and still no Wifi/Bluetooth
I'm out of ideas at this point....

Destro728 said:
UPDATE: I rooted with CF AutoRoot and installed Custom recovery TWRP
did another factory reset
and still no Wifi/Bluetooth
I'm out of ideas at this point....
Click to expand...
Click to collapse
Did the wifi work before you obtained this device?
If all partitions flashed successfully then the wifi should be working.
What is your baseband build number reported as in settings?
Also check your IMEI no.
If that is the default IMEI instead of the original then someone may have trashed the EFS partition.
By the way are you certain this is a t800 and not a t805 or t807?

The Wifi went out a few days ago, tried a factory reset first
Then I remembered the last time this happened I did a firmware re-flash to fix it
It was during the re-flash where I ran into problems and I came to the forum.
I attached a screenshot. Model definitely SM-T800, but no IMEI and no Baseband build...
Thanks!

Destro728 said:
The Wifi went out a few days ago, tried a factory reset first
Then I remembered the last time this happened I did a firmware re-flash to fix it
It was during the re-flash where I ran into problems and I came to the forum.
I attached a screenshot. Model definitely SM-T800, but no IMEI and no Baseband build...
Thanks!
Click to expand...
Click to collapse
Baseband probably doesn't show because it's wifi only model.
However it's strange there is no Status page.
You can get this info using an app called Samsung phone info on play.

ashyx said:
Baseband probably doesn't show because it's wifi only model.
However it's strange there is no Status page.
You can get this info using an app called Samsung phone info on play.
Click to expand...
Click to collapse
Ironically, with no WIfi access...hahahahaa....

I will try to find the apk and sideload it

I sideloaded the Samsung phone info app...
Attached screenshots of the tablet info

What's immediately apparent is no IMEI number. This is a problem.
Is your EFS folder accessible?

Help!! I tried update my phone for Android 10, by odin

I tried and the error is: "An error has occurred while updating the device software. Use the Emergency recovery function in the Smart Switch PC software".
The phone don't entry in mode recovery and the download mode, I tried many times...
The software (Smart Switch PC) does not recognize the phone.
Can anybody help me!

juninromualdo said:
I tried and the error is: "An error has occurred while updating the device software. Use the Emergency recovery function in the Smart Switch PC software".
The phone don't entry in mode recovery and the download mode, I tried many times...
The software (Smart Switch PC) does not recognize the phone.
Can anybody help me!
Click to expand...
Click to collapse
THis happend to me a while back and it is easy to fix. All you have to do is close Odin. Then restart odin and load the correct files into each of the slots - then plug your phone into the USB/PC - you should see the phone connect in Odin - then just click start and run ODIN to update the files you added to the slots in odin.
When you get that error message, the phone is technically still in download mode and odin will still recognize the phone and allow you to update using the files for your phone. Be sure you are using the correct firmware - be sure you add each of the files into the appropriate slot.
Good Luck.

Geekser said:
THis happend to me a while back and it is easy to fix. All you have to do is close Odin. Then restart odin and load the correct files into each of the slots - then plug your phone into the USB/PC - you should see the phone connect in Odin - then just click start and run ODIN to update the files you added to the slots in odin.
When you get that error message, the phone is technically still in download mode and odin will still recognize the phone and allow you to update using the files for your phone. Be sure you are using the correct firmware - be sure you add each of the files into the appropriate slot.
Good Luck.
Click to expand...
Click to collapse
The ondin do not recognize :crying::crying::crying: but I can try, thanks

What version of Odin are you using? What version N10+ do you have? Where did you get the firmware from? I have seen downloads that were corrupt and needed to be redownloaded. Make sure when you extract it it’s the right firmware for your phone as well. Report back and I’m sure we can help you. These phones are tough to brick.
Sent from my iPad using Tapatalk

italbomber said:
What version of Odin are you using? What version N10+ do you have? Where did you get the firmware from? I have seen downloads that were corrupt and needed to be redownloaded. Make sure when you extract it it’s the right firmware for your phone as well. Report back and I’m sure we can help you. These phones are tough to brick.
Click to expand...
Click to collapse
Thank you, but I took earlier today at Samsung, there they solved the problem and even changed the battery. The biggest problem is that I wasn't entering the download screen anymore, I don't know what magic they did ...

Adm close the topic okay, Thank you

Geekser said:
THis happend to me a while back and it is easy to fix. All you have to do is close Odin. Then restart odin and load the correct files into each of the slots - then plug your phone into the USB/PC - you should see the phone connect in Odin - then just click start and run ODIN to update the files you added to the slots in odin.
When you get that error message, the phone is technically still in download mode and odin will still recognize the phone and allow you to update using the files for your phone. Be sure you are using the correct firmware - be sure you add each of the files into the appropriate slot.
Good Luck.
Click to expand...
Click to collapse
THANKS SO MUCH! Simple but everything I needed to know! I had no idea I was still IN download mode!

juninromualdo said:
Adm close the topic okay, Thank you
Click to expand...
Click to collapse
sometimes it is best to just leave the topic and post going - other people might have a similar problem - read the post - see what others have said and find that they can fix their phone. In the post right after the one you said to ask Admin to close the thread, someone else posted a thank you because they discovered they could fix their phone. Proof that sometimes it is best to just let it go - if no one reads it - it will fade out all on it's own. Just a thought.

Geekser said:
THis happend to me a while back and it is easy to fix. All you have to do is close Odin. Then restart odin and load the correct files into each of the slots - then plug your phone into the USB/PC - you should see the phone connect in Odin - then just click start and run ODIN to update the files you added to the slots in odin.
When you get that error message, the phone is technically still in download mode and odin will still recognize the phone and allow you to update using the files for your phone. Be sure you are using the correct firmware - be sure you add each of the files into the appropriate slot.
Good Luck.
Click to expand...
Click to collapse
YOU ROCK!!!! Thanks a Bunch!!!!

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.