Is the corrupt message (red warning triangle) being displayed on the fastboot mode/bootloader screen or is it a different screen?
And you cannot issue adb commands in fastboot/bootloader, only fastboot commands. Like fastboot devices
And how are you entering rescue mode?
Maybe in rescue mode try issue cmd: adb reboot bootloader
Or if that doesn’t work: adb reboot recovery
I’ve played with it a bit and I can get it into recovery and into sideload mode. And it shows a status of sideload when I run adb devices.
See below for an image of the menu.
I hope this helps.
That is the iodeOS (Lineage) recovery screen. The output at the bottom shows the installation failed and was aborted. I don’t know what the status code means.
Presumably you were trying to flash iode using the fastboot.zip?
If yes, then try to get back to bootloader mode to try flashing iode again.
From the recovery use the volume buttons to navigate and the power button to select an action. Touch screen may also work but it is easier to make a mistake in my opinion; so be careful to think about what you are going to touch if you do it that way.
Navigate to the Advanced options and select.
Navigate to Reboot to bootloader and select.
What do you see?
Here is what I see. And if I run fastboot devices in my command prompt, I see the device attached to USB in fastboot mode.
If yes to that: you should be good to try flashing iode from that screen.
Dont touch the phone until absolutely everything has been completed in terminal…except maybe it might offer for you to select locking bootloader at the end.
I was running the the flash-all.sh from the unzipped iode-6.6-20250729-shiba-fastboot.zip file. So I simply repeat this?
The first attempt in flashing my phone ended on this error. Does this indicate something that needs remediation before trying the flash?
Blockquote
extracting product.img (1207 MB) to disk… took 4.523s
archive does not contain ‘product.sig’
Resizing ‘product_b’ OKAY [ 0.016s]
Sending sparse ‘product_b’ 1/5 (262024 KB) OKAY [ 1.217s]
Writing ‘product_b’ OKAY [ 0.632s]
Sending sparse ‘product_b’ 2/5 (262080 KB) OKAY [ 1.096s]
Writing ‘product_b’ OKAY [ 0.549s]
Sending sparse ‘product_b’ 3/5 (262072 KB) OKAY [ 1.201s]
Writing ‘product_b’ FAILED (Status read failed (No such device))
fastboot: error: Command failed
< waiting for any device >
Believe me, I won’t. I’ve already made that mistake and have learned my lesson 
I see, something went wrong flashing product. I don’t know why that’s happening.
Sometimes cables can be problematic but its worked on your other installations.
You didn’t knock the phone or something at around the same time?
I’m not sure what to suggest. You could try again I suppose.
If it hangs at the same point use the menu in whatever screen was showing at the time to power it off and have a re-think.
I just completed it. There was a small glitch in the process. It stopped about 30% - 40% through the load and the phone rebooted. It went back to the same recovery menu I used to restart the image load. And the phone reconnected to the laptop and the process kicked off (picking up exactly where it had failed).
Other than that it seems to have worked flawlessly. I am at the re-locking of the bootloader menu on the phone. I will just reboot at this time to make sure I don’t have anything else to do.
It is still giving me some device is corrupt messages at boot-up. But it booted iodeOS and I have connected to my WiFi and am continuing through the iodeOS setup.
If you want, I will reboot and capture the error screens I see.
I don’t like the sound of that.
Please show me that message if it’s not too much trouble.
No problem at all!
I completed the full setup script and the phone actually shots down and starts up quickly. But, like you, I am concerned about the errors.
Here are the errors I get when I shut down.
Followed by
Yes it needs fixing.
Whatever happened with the interrupted first iode flashing has not been corrected subsequently.
Best to flash the google factory image ( not the ota) from the bootloader screen and boot it up and enable usb debugging again, etc.
So I follow the same process/procedures as the original flashing of the May 2025 shiba factory load followed by the sideload of the OTA image?
No, just the google fastboot.zip. This is the full image. Hopefully wiil repair.
Then iode fastboot.zip.
I’ve reloaded the Google May 2025 Android 15 factory image for chiba and when I attempt to run the iodeOS 6.6 fastboot via the flash-all.sh, I get waiting on devices. But if I run adb devices I se the phone attached with the status “device”.
If I force the phone to reconnect it is still waiting on devices. I feel that I am missing a command. Is there a fastboot command to get it into a flashing mode?
Never Mind!!!
I got it. I reloaded iodeOS 6.6 and it now starts up and shuts down without the corruption error message.
Thank you very much for your assistance as well as your patience!
Glad you got this sorted, but it seems harder than it should have been? If you put stock A15 on from flash.android.com, then if you have the unlocked bootloader and allow ADB debugging from that stock side, did you try the iodé graphical installer?
I really want to thank @chrisrg for his time on this. He was extremely giving with his time and expertise. It was harder than it should have been but that is largely on me rather than the product itself. I had played with another phone and had hard bricked it. Largely due to my lack of experience with the Android SDK Toolkit command interface. So I was moving very slowly and relying on Chris to guide me through the process. There was one glitch in the first load of iodéOS 6.6 and the load failed early. I misread (or didn’t pay enough attention to) the command output and rebooted the phone manually instead of recovering/restarting the load. But once that was fixed, the install was basically flawless.
But regards to installation, by “graphical installer”, I assume you mean the web-usb installer. My personal experience in updating/migrating things has been with large corporate databases with transactional/web front ends. So I don’t update anything unless I can download the install media first. That is how I did the stock A15 load as well as the iodéOS 6.6 install. In my working career I’ve been burned with corrupt downloads so I download and compare SHA256 checksums. I thought that downloading the zip and doing the flash-all.sh is a really solid way to do it.
Rik is referring to the iodeOS installer:
I’ll try that the next time. I will be transitioning to using the Pixel 8 I just loaded as my personal phone as my current Pixel 5 is starting to act erratically. So I’ll probably get another Amazon refurb Pixel 7 to play with.
