Edit If you are on Easy Installer v0.20.1 it is probably worth checking your log for the download location (depends on PC OS) … (this example from Windows)
AppData\Local\easy-installer\sources\<device>
Note the files in sources then try progressively deleting the checksum file(s), the ROM, all contents of sources, trying again each time. Perhaps this will bump Easy Installer into finding the correct files.
I am sorry, my typo . I think I shortened my first draft of a reply which might have expressed the idea that v0.21 may have a “full” fix for all devices, but I believe it is still in testing, vO.20.1 seems to have been producing fewer reports of failure.
I have corrected my first post – yours is the version where I think deleting source is worth a try.
hmm, that interesting i checked the SHA256 off all dev/stable version, none of them corresponds to the one wanted by easy installer…
deleting doesn’t change the outcome…
No, not on T (that is e-2.1-t-dev moving from e-1.17-s-dev) … we see that the S build terminated [1] and because OTA Upgrade of Android version only happens on stable.
[1] Post #6 as I say “Not very desirable as it is the last S build”.
So the manual instructions are expected to be accurate for the t-dev builds. Did you use your own platform-tools or did you contrive to use adb / fastboot supplied to you with Easy Installer, potentially hitting easy-installer: Old version of fastboot #7154 ? Or did Easy Installer actually transfer something to your phone at some point ?
Depending on the circumstances the message “can’t find valid operating system” is actually valid at the point where you are partway through flashing various partitions.
Not just
Since the device resets completely, you will need to re-enable USB debugging to continue.
after unlock?
One more thing, as you moved up to a T build (somewhat unexpectedly) did you satisfy
Before following these instructions please ensure that the device is on the latest Android 13 firmware.
It may be necessary to upgrade the firmware using a method described here https://developers.google.com/android/images. You have some reading to do on this page (worth spending a bit of time) before hitting Acknowledge at the apparent foot of the page; after which you can search the page for flame.
Edit@tiro on reflection, I think this has come up before and lack of USB debugging affects adb (and thus adb sideload) but not fastboot. I just switched off USB debugging on my OnePlus One and Moto G7 Power ocean and fastboot devices finds both devices. Does you phone boot into fastboot?
So at this point I think you need to determine if failure of fastboot devices is from the PC side or phone.
Nearly always if you have fastboot available on the device there is a way out.
(Which method did you use to upgrade ? Did you notice did it rely on fastboot ? There may be some lower level method to flash the SOC, I don’t recall the Pixel method.)
I notice that the OP seems to open a second thread “Update Solved”. His remarks on a fully charged battery are interesting, and I believe important particularly when you have to have a second run at a problem.
In some searching I found also https://pixelrepair.withgoogle.com/ but without a Google account / login I could not further research the tool.
I downloaded the latest stable build & checksums, and inserted into Easy Installer (EasyInstaller.app/Contents/MacOS/bin/sources/flame/) from: https://images.ecloud.global/stable/flame/
Easy Installer ignores this and just tries to download all over again, and fails.
Anyone got a way through this? Upgrading to 2.0 shouldn’t be this difficult
When /e/OS is installed on a device, you also already have the recovery-e installed, so you simply have to boot in recovery mode to easily update/upgrade…
done !
using the traditionnal way skipping the easy installer
one thing that surprise me and scared a bit was
fastboot flashing unlock
i was a bit reassured by the “ignoring” word,
but english and android are not my native language,
so, @aibd@tcecyk or others i don’t think about at this moment,
. I think I shortened my first draft of a reply which might have expressed the idea that v0.21 may have a “full” fix for all devices, but I believe it is still in testing, vO.20.1 seems to have been producing fewer reports of failure.