New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can't write asteroid-image-tetra.ext4 to userdata #31
Comments
You may need to play around with the alignment of the partition AsteroidOS/meta-tetra-hybris@4e7def9 A value of 4 is needed for all qcom devices but this may be different on the SW3 |
SW3 probably need kind of recapitulation of mkbootimg as from MM bootloader. Will be checked out within fay/two |
Theres a warning on the site saying that Real Installation doesn't work while Temp Install does, however temp install just causes the device to get stuck during boot and not load the OS. |
It looks like @fergy 's "tested" pull request broke tetra AsteroidOS/meta-tetra-hybris#2 could anyone issue a local build with the commits in this PR reverted and confirm whether or not this was the cause of the problems on tetra? |
It wasn't possible to flash before My latest commit but be free to check |
I was refering to the IaYScI3eB1weQ1uIxeeG's temp installation bug. Flashing is a different problem |
I'd test an older version but I don't know how to use the ". ./prepare-build.sh" command with older versions, anybody know how? |
IaYScI3eB1weQ1uIxeeG: issue this command once and then cd to src/meta-tetra-hybris and git checkout the commit you want. But again, this has nothing to do with the initial problem here, which is related to the userdata partition size. This is a different problem. I suggest someone should try to define a new OE "partition type" using the usual ext4 partition but then using the img2simg tool. |
Real install still fails on newest nightly. Temp install however does work, that didn't work in the last nightly. |
So, Fergy is not suspects. :-)
Ramon-Tomislav Reberšak, mag.spec.mus.
…On Sep 21, 2017 20:28, "Ace" ***@***.***> wrote:
Real install still fails on newest nightly. Temp install however does
work, that didn't work in the last nightly.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#31 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAC-AN11GAX-BDP714QF601U5BftH2U9ks5skqqxgaJpZM4OHcsT>
.
|
I'm having the same issue on a Asus Zenwatch 2 (sparrow, wren). The watch is stuck in |
Real install still fails with build from today. |
Hi, an idea crosses my mind. Could you try to run img2simg on the downloaded image and see if the result can be flashed? If that fixes the issue, we'd have to close AsteroidOS/meta-asteroid#16 and compile simgs. However, those "simg" files can't be used for the temporary install method... So we would probably need to distribute two different images with two different instructions for tetra. Which is a pain |
Nope, it didn't help.
|
Thank you gmelchett, I'll consider other solutions then. |
Same issue like gmelchett here with today's nightly build |
there are builds for SW3? |
Updates regarding this issue as of today: tl;dr:
Details about the installation methods:
Details about the sparse format (reference: http://www.2net.co.uk/tutorial/android-sparse-image-format ):
Details about the tetra's bootloader:
Proposed workaround:
|
Is this issue just solved for the Sony Smartwatch 3 (tetra) or for any other Smartwatch as well? Because I was having the same issue on a Asus Zenwatch 2 (sparrow, wren). Does the latest nightly build for |
tristan-k: The instructions on the website have only been changed for the SW3. No one else ever reported this problem on the Zenwatch 2. Your messages here don't give enough details to help you, we don't know if you have a wren or a sparrow (those are two different watches). You don't detail what commands you use and what they output. You haven't tested the solution I detailed in my above comment. And if the bug still happens after using ext2simg, you should open a different issue. |
@FlorentRevest just used ext2simg from android-tools-native, as per proposed workaround, and can confirm that this worked fine for me with a Sony Smartwatch 3 and commit f20567e. |
This happens with the latest nightly. Not sure if it happens with the latest release
The image located here flashes fine (but doesn't work; it reboot loops). Back when I was on Android Wear, I was able to temporary-boot the latest nightly no problem.
This is for the Sony Smartwatch 3.
The text was updated successfully, but these errors were encountered: