Disappointing
$ fastboot --version
fastboot version 28.0.2-debian
Installed as /usr/lib/android-sdk/platform-tools/fastboot
could we just throw away ths 28 version ? I officially hate the number 28 !!! 
Well I am very sorry about that … but we do want it to test your very own flash-all.sh. 
Please change to your working directory bull … and
fastboot --version
fastboot devices
./flash-all.sh
Bearing in mind that this must be your modified version of flash-all.sh
1 Like
Please change to your working directory bull
But l was in bull
Not good ?
I get this now
$ fastboot --version
fastboot devices
./flash-all.sh
fastboot version 28.0.2-debian
Installed as /usr/lib/android-sdk/platform-tools/fastboot
0271e789ba5bb3a3 fastboot
Sending ‘bootloader’ (4610 KB) OKAY [ 0.307s]
Writing ‘bootloader’ OKAY [ 0.147s]
Finished. Total time: 0.514s
Rebooting into bootloader OKAY [ 0.008s]
Finished. Total time: 0.059s
< waiting for any device >
Sending ‘radio’ (56630 KB) OKAY [ 2.736s]
Writing ‘radio’ OKAY [ 0.541s]
Finished. Total time: 3.597s
Rebooting into bootloader OKAY [ 0.000s]
Finished. Total time: 0.051s
< waiting for any device >
Bootloader Version…: BHZ32c
Baseband Version…: M8994F-2.6.42.5.03
Serial Number…: 0271e789ba5bb3a3
extracting android-info.txt (0 MB) to RAM…
Checking ‘product’ OKAY [ 0.014s]
Checking ‘version-bootloader’ OKAY [ 0.015s]
Checking ‘version-baseband’ OKAY [ 0.012s]
extracting boot.img (11 MB) to disk… took 0.214s
archive does not contain ‘boot.sig’
Sending ‘boot’ (11781 KB) OKAY [ 0.642s]
Writing ‘boot’ OKAY [ 0.127s]
archive does not contain ‘dtbo.img’
archive does not contain ‘dt.img’
extracting recovery.img (17 MB) to disk… took 0.343s
archive does not contain ‘recovery.sig’
Sending ‘recovery’ (17425 KB) OKAY [ 0.903s]
Writing ‘recovery’ OKAY [ 0.224s]
archive does not contain ‘vbmeta.img’
archive does not contain ‘vbmeta_system.img’
archive does not contain ‘super_empty.img’
archive does not contain ‘odm.img’
archive does not contain ‘product.img’
archive does not contain ‘product_services.img’
extracting system.img (1909 MB) to disk… took 54.762s
archive does not contain ‘system.sig’
Sending sparse ‘system’ 1/4 (508768 KB) OKAY [ 26.872s]
Writing ‘system’ OKAY [ 6.116s]
Sending sparse ‘system’ 2/4 (524238 KB) OKAY [ 27.906s]
Writing ‘system’ OKAY [ 6.067s]
Sending sparse ‘system’ 3/4 (501061 KB) OKAY [ 26.631s]
Writing ‘system’ OKAY [ 6.608s]
Sending sparse ‘system’ 4/4 (421469 KB) OKAY [ 22.040s]
Writing ‘system’ OKAY [ 4.662s]
extracting vendor.img (185 MB) to disk… took 5.068s
archive does not contain ‘vendor.sig’
Sending ‘vendor’ (190332 KB) OKAY [ 9.052s]
Writing ‘vendor’ OKAY [ 2.706s]
Erasing ‘userdata’ OKAY [ 0.439s]
mke2fs 1.46.5 (30-Dec-2021)
/tmp/TemporaryFile-PQ2xv3: Unimplemented ext2 library function while setting up superblock
/usr/lib/android-sdk/platform-tools/mke2fs failed with status 1
fastboot: error: Cannot generate image for userdata
Was the error we get using fastboot 28 and the marshmallow firmware
This is the same but different … from your first report which included
mke2fs 1.46.6 (1-Feb-2023)
Creating filesystem with 6661115 4k blocks and 1667904 inodes
Filesystem UUID: f93e8528-8282-48dc-aa30-ebcbb2ff3cca
No we are using latest Oreo. I don’t plan to change the ROM but maybe worth I am unsure about downgrading platform-tools again as from Post #55 it would seem like a June 2018 platform-tools would be a satisfactory match with a November 2018 ROM.
We could try to test this by restoring the original flash-all.sh with the “test” included again.
However I think this is a treat we should save for tomorrow, if that would be ok with you Catrine.
1 Like
Yes its fine by me
Goodnight everybody
1 Like
You are right @piero that we should have ensured the phone was left on to charge overnight and if the phone gives a reliable indicator of charge level in normal charging mode.
@Catrine if still online ?
The mke2fs errors could maybe be ameliorated by
fastboot -w
… maybe
fastboot erase userdata
… but I am unsure if fastboot can do similar to format data ??
an answer from https://xdaforums.com/t/q-fastboot-erase-userdata.2020098/ (but device is Google Nexus 4)
fastboot format userdata
1 Like
Hello…
Im just back now and l will only have time tonight to explore the commands world… but l put the phone to charge hopefully fully till then
Have a nice day everyone lm gonna be horseriding in the snow 
1 Like
after / if / when
- stock gogolOS-O works and
- dev /e/OS-R works,
- you should try unofficial /e/OS-T
Hello
So now the phone has charged for hours and it gives a full battery icon, also when l tried a normal boot i did get the google for a few seconds then a circle with a slow colors swirl on a black background with the word “erasing” below the circle… it went on for a few seconds then it was back on its loop…
cant remember what this circle is is it google starting ?
then l plugged it and srated the usual recovery mode and from the terminal in the bull folder l copied the commands and here is the result
$ fastboot -w
Erasing ‘userdata’ OKAY [ 0.554s]
mke2fs 1.46.5 (30-Dec-2021)
/tmp/TemporaryFile-Ixe3R4: Unimplemented ext2 library function while setting up superblock
/usr/lib/android-sdk/platform-tools/mke2fs failed with status 1
fastboot: error: Cannot generate image for userdata
cate@cate-1011PX:~/Downloads/Bull/bullhead-opm7.181205.001-factory-5f189d84/bullhead-opm7.181205.001$ fastboot erase userdata
******** Did you mean to fastboot format this ext4 partition?
Erasing ‘userdata’ OKAY [ 0.449s]
Finished. Total time: 0.473s
cate@cate-1011PX:~/Downloads/Bull/bullhead-opm7.181205.001-factory-5f189d84/bullhead-opm7.181205.001$ fastboot format userdata
mke2fs 1.46.5 (30-Dec-2021)
/tmp/TemporaryFile-EH4JHu: Unimplemented ext2 library function while setting up superblock
/usr/lib/android-sdk/platform-tools/mke2fs failed with status 1
fastboot: error: Cannot generate image for userdata
cate@cate-1011PX:~/Downloads/Bull/bullhead-opm7.181205.001-factory-5f189d84/bullhead-opm7.181205.001$
are we making progress?
Good evening,
I am now wondering if there is anything in the phone’s history that might have happened, like an attempted install of some software that might have caused this ?
yes I think l tried to install lineage OS a long time ago and maybe l did irreparable damage?
I get also this
I would be surprised that could cause it, the XDA thread I quoted talked of fastboot quirks …
So is that image something not seen before – this is OK as in normal, not a sign of a fault, please let it play out for a minute or so …
If we can enter adb
adb devices
maybe we can use other tools to format userdata
$ adb devices
- daemon not running; starting now at tcp:5037
- daemon started successfully
List of devices attached
cate@cate-1011PX:~/Downloads/Bull/bullhead-opm7.181205.001-factory-5f189d84/bullhead-opm7.181205.001$
I never saw the erase circle before and l tried to start over again so I could take a photo with my phone but it does not come up anymore…
Please tell me about the image you posted, is it new, what happened next?
No this image is what l get when l try to start and it begins with it everytime, the check for corruption impossible, what happens next is this google…
I suggest we try your script again. Please show the output of
fastboot --version
before running the script … maybe we can tell something from the sequence of userdata errors, so I suggest you just run the script one time.