Hi! Recently I tried to install android 12 on my Pixel. Well, I enrolled into android 12 beta program, and didn't recieve any OTA update. I thought: "Hmpf, Nothing can stop me from getting beta on my phone!", so I downloaded OTA image on my PC, and started trying to apply update. I was happy, percents of progress was ticking, and after a while, this happened:
Code:
C:\adb>adb sideload D:\Downloads\crosshatch-ota-spb3.210618.016-2ca916ef.zip
serving: 'D:\Downloads\crosshatch-ota-spb3.210618.016-2ca916ef.zip' (~94%) adb: failed to read command: No error
I panicked little bit, but remembered A/B thing. So now I guess my B slot is wasted (or not?). I presume it'll somehow heel itself, right?
So, main question is: Why I am unable to apply OTA via usb using PC?
p.s: thank god phone booted up, i quickly turned on oem unlocking, just in case :/
p.s2: So I tried applying current ota (like current version), and now it works perfectly fine. Phone booted to b slot, despite that that error appeared again. Now I think maybe my phone is wrong, since android R works good, but not android S. I guess it's just beta, so i'll try to wait patiently until release. But still, could you answer question? I still don't know what the hell it was.
Can you unlock your bootloader? Flashing full factory image works great, and 12 runs well afterwards.
Related
Hi Guys,
so this morning my SW3 told me there was a system update, cool, so i said yes to the update and let it do its thing.
on coming back, the os version was still the same (LDZ22D) which i thought was odd.
I then did a search and found that there was indeed a new version out (LCA43) and thought something sus was afoot.
I got the twrp from this post http://forum.xda-developers.com/smartwatch-3/development/lwx49k-rooting-easy-t3107501 and booted from twrp
i then pushed the rom i downloaded form here http://www.xperiablog.net/2015/08/2...-update-lca43-intros-interactive-watch-faces/ and promptly tried to flash it like i would any custom rom i would normally flash on any of my other android devices.
I got an error, saying it was expecting "test keys" from a LAZ22D device or a LWX49K device, and that I had LRX22G test keys.
I also tried an ADB sideload which also didn't work.
Am i doing something wrong? Has anyone else ever encountered this?
Full disclosure, I also installed supersu a few months ago, but have had many factory resets since then (new roms on the paired fone) which i wouldn't have thought was an issue?
Cheers for any help you can give
That update only works on stock recovery. Go to my rollback thread and install the complete system of 5.0.1. I put links and directions to all the files. Then roll forward.
Thanks for that @lekofraggle, but I found an easier option, install Sony companion software, reflash "latest" firmware (apparently LAZ22D) then sideload the original update zip. Worked just fine. Just to clarify, I never flashed twrp, just hot booted from it, wondering if root did break ota...
Sent from my Nexus 7 WIFI using Tapatalk
Yes, root breaks most otas, but adb sideload usually works. Glad it was simpler than my doomsday thoughts.
I fixed (to a certain degree) a bootlooped watch by installing a stock Lollipop Rom. It does not work though, because watch cannot connect with Android wear and therefore not complete installation. (It does pair up with the phone and says wait a minute) Any suggestions?
baronimus said:
I fixed (to a certain degree) a bootlooped watch by installing a stock Lollipop Rom. It does not work though, because watch cannot connect with Android wear and therefore not complete installation. (It does pair up with the phone and says wait a minute) Any suggestions?
Click to expand...
Click to collapse
Our watches must be brothers as I have had the exact same scenario. I did however get it back going to LP, paired, etc to the smartphone. What I had to do was fastboot format cache, then userdata, then fastboot reboot. I then fastboot flash the .simg file, the recovery.img file and the boot.img file, then fastboot reboot. I then connected to XC which did not work all the way through, but gave me access to be able to use twrp.img (for some reason, twrp would not boot in LP). Then in twrp I adb pushed the LP rom that is signed and after pushed, installed it. Then, I had to leave it alone for the battery drain as it was locked up or something. After it drained, which was evident because it was not warm, I charged it and it is now working again...but only in LP. I cannot get MM installed.
IF you happen to get MM installed and working, please advise your steps.
golfnut22 said:
Our watches must be brothers as I have had the exact same scenario. I did however get it back going to LP, paired, etc to the smartphone. What I had to do was fastboot format cache, then userdata, then fastboot reboot. I then fastboot flash the .simg file, the recovery.img file and the boot.img file, then fastboot reboot. I then connected to XC which did not work all the way through, but gave me access to be able to use twrp.img (for some reason, twrp would not boot in LP). Then in twrp I adb pushed the LP rom that is signed and after pushed, installed it. Then, I had to leave it alone for the battery drain as it was locked up or something. After it drained, which was evident because it was not warm, I charged it and it is now working again...but only in LP. I cannot get MM installed.
IF you happen to get MM installed and working, please advise your steps.
Click to expand...
Click to collapse
Thank you for your reply. I will certainly let you know of any progress. The procedure I followed was somewhat more simple. I flashed the twrp with fastboot, booted twrp up, transferred the downloaded rom image from the pc to the watch and booted the rom from twrp. It then starts up but fails to play with wear.
baronimus said:
Thank you for your reply. I will certainly let you know of any progress. The procedure I followed was somewhat more simple. I flashed the twrp with fastboot, booted twrp up, transferred the downloaded rom image from the pc to the watch and booted the rom from twrp. It then starts up but fails to play with wear.
Click to expand...
Click to collapse
Regarding the pairing with phone, I had to go in the phone settings, application manager, open android wear, and clear the data and cache in order for it to recognize my watch. I had previously had it linked to another phone and had the phone connected to a different watch so I think it was getting confused.
Regarding getting past the 5.0.1 update, I have found this post http://forum.xda-developers.com/smartwatch-3/orig-development/tut-how-to-fix-swr50-fastboot-t3258918 and am currently getting OTA updates as I write. I don't know how far I will get, but so far I have had two updates. I did not flash the updates, only the original rom. Then I went into the watch settings, about, and pressed the software or system update (I've been doing it manually each time).
Edit: It allowed me to update all the way to MM, however I got the 4 dots /symbols again when it was rebooted. Up to that point, which the last update was the LCA43, the watch appeared to be working fine. I did not test it much as I was just trying to get all the updates I could. So, while it did not go all the way thru to MM, I still was very happy that I got up to that update.
golfnut22 said:
Regarding the pairing with phone, I had to go in the phone settings, application manager, open android wear, and clear the data and cache in order for it to recognize my watch. I had previously had it linked to another phone and had the phone connected to a different watch so I think it was getting confused.
Regarding getting past the 5.0.1 update, I have found this post http://forum.xda-developers.com/smartwatch-3/orig-development/tut-how-to-fix-swr50-fastboot-t3258918 and am currently getting OTA updates as I write. I don't know how far I will get, but so far I have had two updates. I did not flash the updates, only the original rom. Then I went into the watch settings, about, and pressed the software or system update (I've been doing it manually each time).
Edit: It allowed me to update all the way to MM, however I got the 4 dots /symbols again when it was rebooted. Up to that point, which the last update was the LCA43, the watch appeared to be working fine. I did not test it much as I was just trying to get all the updates I could. So, while it did not go all the way thru to MM, I still was very happy that I got up to that update.
Click to expand...
Click to collapse
I now succeeded in pairing up with the phone. What I did was to flash another Rom which I found in the forum. It's called ROM_SW3_5.1.1.2_LCA43. Now the watch works just fine on Lollipop and updates automaticly. I am going to try and upgrade to MM but I fear its going to get stuck on the infamous four symbols when I do. I am happy though to have the watch up and running again, it was deemed paperweight for a while
Ok stuck again. Still at Lollipop version 5.1.1.2
baronimus said:
I now succeeded in pairing up with the phone. What I did was to flash another Rom which I found in the forum. It's called ROM_SW3_5.1.1.2_LCA43. Now the watch works just fine on Lollipop and updates automaticly. I am going to try and upgrade to MM but I fear its going to get stuck on the infamous four symbols when I do. I am happy though to have the watch up and running again, it was deemed paperweight for a while
Ok stuck again. Still at Lollipop version 5.1.1.2
Click to expand...
Click to collapse
Does yours actually have 5.1.1.2 in the about section? Mine says 5.1.1 with the build as LCA43.
golfnut22 said:
Does yours actually have 5.1.1.2 in the about section? Mine says 5.1.1 with the build as LCA43.
Click to expand...
Click to collapse
Indeed it does. The Rom comes from here: http://forum.xda-developers.com/smartwatch-3/orig-development/rom-sony-smartwatch-3-rom-t3367728
Since the problem occurs only when updating to MM I am led to think that we have a kernel issue?
baronimus said:
Indeed it does. The Rom comes from here: http://forum.xda-developers.com/smartwatch-3/orig-development/rom-sony-smartwatch-3-rom-t3367728
Since the problem occurs only when updating to MM I am led to think that we have a kernel issue?
Click to expand...
Click to collapse
I may have stopped updating one to early. Anyway, my watch updated by itself last night all the way to MM, now it is stuck again. I'll have to search and see if there is a way to stop the automatic OTA updates.
I have seen where people have flashed only the kernel. I have not. At this point, it would be nice just to keep it at the last LP. I'll let you know if I find anything. Thanks.
Hi everyone,
I've been having issues updating my Pixel 3 XL since September 2020, when a security update came out. I tried to classicaly update my phone but kept getting the "Couldn't update - Installation problem" error. Since then I haven't been able to get any new feature.
Now that android 12 is out, I'd like to update my Pixel to have it, but the same error keeps showing up. I've tried to factory reset but still not working.
I'm not an experienced developer and this is my first experience, so all that I've tried is downloading the full OTA image (12.0.0 (SP1A.210812.015, Oct 2021), and sideload it. After doing that, it seems to work, but the android version remains the same after rebooting, CMD output is:
Code:
serving: 'D:\Downloads\crosshatch-ota-spb3.210618.016-2ca916ef.zip' (~94%) adb: failed to read command: No error
So, my question is if there is a safe way to get the latest version, and if possible keep getting all updates as it should normally work.
Thanks in advance for any help.
The past few years, I usually install the ota manually on my pixels if they don't come right away on my phone (they usually do in CA). I keep my bootloader unlocked (just in case things go haywire) but haven't modified or rooted in many years. So today, because the update was so large (more reasoning below), I decided to flash the factory image and remove the "-w" command so it wouldn't wipe the phone. Done this many times.
So my usual process is to flash both slots one after the other. I flashed the current slot it was on (b) then switched to the (a) slot. Been doing the same since Android 4 (and A9 for a/b slots), hundreds of times. After flashing slot (a), it restarted like it's supposed to. I then get the dreaded "Your device is corrupt" message. First time I've seen this on any of my 4 Nexus and 5 Pixel phones. Okay so I decided to try flash it again, this time with the wipe command (recovery wouldn't work, same message). Flashing completes, same message. Then tried the flash.android.com - flashed all slots, wiped options on - same thing. The " pixelrepair.withgoogle.com " website doesn't recognize the phone which is odd because flash.android.com does. I tried flashing the original image from November and 2 other build versions. Still no go.
Not sure what happened here. I don't think anything is wrong with the latest image. The reason I flashed this image was because I had a thought today - does flashing the "ota zip" update the bootloader and other firmware versions (they were different different versions this update). So I guess my curiosity killed the cat ... I should have just ran the ota first to see if the bootloader/radio versions updated, but of course the ota updates them (or they would never get updated otherwise). Ahh well. Now I will have to deal with the silly carrier warranty circus.
Also - I never thought an update could cause a phone to completely corrupt itself where it can't be fixed by the user. All of these posts on xda/red_dit etc over the years - I really didn't think it was possible. I always thought corruption must have been there before, but now I'm not so sure.
update: flashed the last build from November using flash.android.com and was able to get my system back. 2nd flash for that build worked.
Alekos said:
The past few years, I usually install the ota manually on my pixels if they don't come right away on my phone (they usually do in CA). I keep my bootloader unlocked (just in case things go haywire) but haven't modified or rooted in many years. So today, because the update was so large (more reasoning below), I decided to flash the factory image and remove the "-w" command so it wouldn't wipe the phone. Done this many times.
So my usual process is to flash both slots one after the other. I flashed the current slot it was on (b) then switched to the (a) slot. Been doing the same since Android 9, hundreds of times. After flashing slot (a), it restarted like it's supposed to. I then get the dreaded "Your device is corrupt" message. First time I've seen this on any of my 4 Nexus and 5 Pixel phones. Okay so I decided to try flash it again, this time with the wipe command (recovery wouldn't work, same message). Flashing completes, same message. Then tried the flash.android.com - flashed all slots, wiped options on - same thing. The " pixelrepair.withgoogle.com " website doesn't recognize the phone which is odd because flash.android.com does. I tried flashing the original image from November and 2 other build versions. Still no go.
Not sure what happened here. I don't think anything is wrong with the latest image. The reason I flashed this image was because I had a thought today - does flashing the "ota zip" update the bootloader and other firmware versions (they were different different versions this update). So I guess my curiosity killed the cat ... I should have just ran the ota first to see if the bootloader/radio versions updated, but of course the ota updates them (or they would never get updated otherwise). Ahh well. Now I will have to deal with the silly carrier warranty circus.
Also - I never thought an update could cause a phone to completely corrupt itself where it can't be fixed by the user. All of these posts on xda/red_dit etc over the years - I really didn't think it was possible. Corruption must have been there before, but now I'm not so sure.
If anyone has any fastboot tricks - I'd try anything at this point.
Click to expand...
Click to collapse
All you got to do is go to the factory image page. Click on the Android flash tool and follow that it'll bring you back
mac796 said:
All you got to do is go to the factory image page. Click on the Android flash tool and follow that it'll bring you back
Click to expand...
Click to collapse
Not sure if I wasn't clear:
Okay so I decided to try flash it again, this time with the wipe command (recovery wouldn't work, same message). Flashing completes, same message.
I tried flashing 4 different Factory Image builds (flashing manually the Factory Image not ota). The android flash tool (webiste) completes but same message appears after it restarts.
Alekos said:
Not sure if I wasn't clear:
Okay so I decided to try flash it again, this time with the wipe command (recovery wouldn't work, same message). Flashing completes, same message. Then tried the flash.android.com - flashed all slots, wiped options on - same thing. The " pixelrepair.withgoogle.com " website doesn't recognize the phone which is odd because flash.android.com does. I tried flashing the original image from November and 2 other build versions. Still no go.
I tried flashing 4 different Factory Image builds. The android flash tool completes but same message appears after it restarts.
Click to expand...
Click to collapse
You're trying to flash with fastboot right? Use that Android flash tool. You'll see a link to it in the factory image page. I went through the same thing you did, I got the corrupt device. at the very end It'll ask you to Lock the bootloader just don't do it if you want to stay unlocked.
Oh maybe I misunderstood you tried that and it's not recognizing it
mac796 said:
Oh maybe I misunderstood you tried that and it's not recognizing it
Click to expand...
Click to collapse
flash.android.com recognizes it and it completes but the corrupt message still appears.
I'm going to try the original build from October, using the flash.android.com website - and pick all the Advanced Options, see how it goes (disable verity and verification, force debuggable and flash all partitions). I guess it's worth a try. pixelrepair website doesn't recognize the phone.
Alekos said:
flash.android.com recognizes it and it completes but the corrupt message still appears.
I'm going to try the original build from October, using the flash.android.com website - and pick all the Advanced Options, see how it goes (disable verity and verification, force debuggable and flash all partitions). I guess it's worth a try. pixelrepair website doesn't recognize the phone.
Click to expand...
Click to collapse
That's no good. Hope it works out. I had a hell of a time getting mine back too
mac796 said:
That's no good. Hope it works out. I had a hell of a time getting mine back too
Click to expand...
Click to collapse
ok what the hell. what a mess. it was weird, long-pressing the power button would never restart the device. it took multiple tries. I've learned over the years to remove the case because it can hinder the restart sequence. But even just getting into fastboot was difficult.
Anyhow it looks like I'm back.
2nd time flashing this exact image, but this time it worked - I used the flash tool website and flashed the November SD1A.210817.037 (non vzw build). I just chose options "All Partitions, and full wipe"(my next step was to try disabling verity and debugging but this worked).
a few reports on red_dit of corruption on the 6 Pros. hopefully Google pulls it soon. if people don't have the "oem unlocking" option enabled, their toast.
Alekos said:
ok what the hell. what a mess. it was weird, long-pressing the power button would never restart the device. it took multiple tries. I've learned over the years to remove the case because it can hinder the restart sequence. But even just getting into fastboot was difficult.
Anyhow it looks like I'm back.
2nd time flashing this exact image, but this time it worked - I used the flash tool website and flashed the November SD1A.210817.037 (non vzw build). I just chose options "All Partitions, and full wipe"(my next step was to try disabling verity and debugging but this worked).
Lots of reports on red_dit of corruption on the 6 Pros. hopefully Google pulls it soon. if people don't have the "oem unlocking" option enabled, their toast.
Click to expand...
Click to collapse
I'm glad you got out of it
I also had the pixel 6 pro briked when I put the root of the last base.
I have revived it by putting the ota december by sideload from recovery in the adb section
victoraran said:
I also had the pixel 6 pro briked when I put the root of the last base.
I have revived it by putting the ota december by sideload from recovery in the adb section
Click to expand...
Click to collapse
so if I didn't have "OEM unlocking" enabled - I'd have a brick right now. just actually trying to help someone else that also got the corruption message and can't get back into Android to enable oem unlock. Recovery doesn't work (like my situation).
What a mess...
That's what can happen when we're inpatient and not willing to wait for the right version to actually push to the device.
Battery life is awesome, still on 44% at half 10 at night from half 6 this morning
prohibido_por_la_ley said:
That's what can happen when we're inpatient and not willing to wait for the right version to actually push to the device.
Click to expand...
Click to collapse
seriously? the right version? I installed the right version, and others also had the same issue just by updating normally through Android interface.
you shouldn't be able to "corrupt a system" just by updating to the official update build. this isn't 2012... anyway, I mostly posted and updated for others who might have had issues also.
Alekos said:
seriously? the right version? I installed the right version, and others also had the same issue just by updating normally through Android interface.
you shouldn't be able to "corrupt a system" just by updating to the official update build. this isn't 2012... anyway, I mostly posted and updated for others who might have had issues also.
Click to expand...
Click to collapse
Well in the 4 years of me being on Android I've never had it happen.
I literally just got my Pixel 6 Pro and attempted the December update and got a firmware corrupt. The only options is try again or factory reset. I just finished going through the first time setup and already got this.
JodyBreeze901 said:
I literally just got my Pixel 6 Pro and attempted the December update and got a firmware corrupt. The only options is try again or factory reset. I just finished going through the first time setup and already got this.
Click to expand...
Click to collapse
same
Alekos said:
seriously? the right version? I installed the right version, and others also had the same issue just by updating normally through Android interface.
you shouldn't be able to "corrupt a system" just by updating to the official update build. this isn't 2012... anyway, I mostly posted and updated for others who might have had issues also.
Click to expand...
Click to collapse
Why not just adb sideload the OTA image, rather then flashing on both slots the factory image? It just sounds a bit of a hassle to me.
I know, I used to fastboot flash without -w my nexuses as well, but that was before the OTA images were available.
prohibido_por_la_ley said:
Well in the 4 years of me being on Android I've never had it happen.
Click to expand...
Click to collapse
yeah it's super rare. been flashing images and ota's since Nexus 4. But it happens.
I usually get the updates right away but sometimes I'll update the ota. I usually reflash the factory image every year after the beta. just seems odd how it corrupted the device. couldn't get into the system at all (or recovery/rescue modes).
yolandabecool said:
same
Click to expand...
Click to collapse
apparantly it has something to do with Bluetooth? I don't know how, but if you can get into safe mode and disable Bluetooth, clear cache/data for it and update all your google service apps, it can fix it (keeping Bluetooth off while restarting phone in regular mode) - but I couldn't load Android.
The trick to getting into Safe Mode is this: Turn off the device. Hold down power and and as soon as you see the "G" Logo, hold volume down. it will directly boot you to Safe mode. cool little trick. you'll have to manually enable wifi because it gets turned off.
At this point, if you can, enable OEM Unlocking. at least you'll be able to save the device if anything serious happens (like what I went through). the pixel repair website also works but I couldn't get into "Rescue Mode"
Per the title I tried to go to A13 to see if it would fix the low ringer volume on my Unlocked Pixel 6 Pro, or whether I have a hardware issue. It did not. I decided to go back to A12 and wait until the stable release and trying to flash via adb tells me I can't downgrade. When I try the Android Flash Tool and select the A12 build I need, it starts and then shows a "HEAD request failed: Unknown network error" and stops.
I'm soft-bricked now. I get a message that the device is corrupt and may not work properly, then the bootloader unlocked warning I've always gotten after I unlocked that. After that I At best I get to a white screen with the Google logo or bootloader mode.
Has anyone worked through this error or does anyone have a solution on how to recover my phone? Thanks!
Reflash A13 and make a backup then flash - wipe A12
Paz9 said:
Reflash A13 and make a backup then flash - wipe A12
Click to expand...
Click to collapse
Thanks - that's exactly what I did. I was traveling and trying to get my phone working again and you are on the right track. I got it fixed fairly quickly, but I left the thread open to give another instance of hope to folks who may stumble across this in the future. I'm guessing I was flashing the OTA image and not the factory image, and it was confusing because it would partially succeed and then fail with no obvious indication of the reason for the failure. I've since flashed the factory image several times and while it too has the .sig files missing errors that appears to be a non-issue, it works just fine and I'm back in business.
It may be related to what we seen today with A13 being released. The Bootloader cant be rolled back to earlier version.
Someone posted today they can get Android 12 installed back, AS LONG as they edit the factory image script to skip the bootloader flash part.
chaco81 said:
It may be related to what we seen today with A13 being released. The Bootloader cant be rolled back to earlier version.
Someone posted today they can get Android 12 installed back, AS LONG as they edit the factory image script to skip the bootloader flash part.
Click to expand...
Click to collapse
It's not, he was on the Android 13 beta and was trying to flash the full OTA when the recovery does not permit flashing a lower firmware than what is already running. He only had to instead flash the firmware from the bootloader to downgrade from the beta.
However yes, if you take the Android 13 release bootloader you cannot downgrade back to Android 12's bootloader. How long the Android 13 bootloader will continue to boot Android 12 or if they will put another antirollback measure in is unknown.