$ fastboot --version
fastboot version 28.0.2-debian
Installed as /usr/lib/android-sdk/platform-tools/fastboot
If you have not yet run the script … I suggest a modification. Please open the script in a text editor and adjust the final line which reads
fastboot -w update image-bullhead-opm7.181205.001.zip
to
fastboot update image-bullhead-opm7.181205.001.zip
That is edit out -w and be sure to Save the file.
this screen could be google erasing the new recovery.
Im lost
is it the .profile the .baschr or else ?
the flash-all.sh of course !
there is also a flash - original file…
but ok l run that…
please don’t run Please edit.
ok i only edited the file
Once confident that you edited and saved flash-all.sh then please go ahead and run it.
flash-all.sh
and l get command not found but the terminal is from the folder
./flash-all.sh
we need the dot dash
Ok l found the right one from the conversation from yesyerday…
It is now waiting for device
Found the device
Doing a lot of writing right now
I ll copy paste when its done…
Done
the phone booted few time with the images l sent you before+ the erasing circle that l missed to photograph sorry then the usual loop and now its off
as for the terminal
$ ./flash-all.sh
< waiting for any device >
Sending 'bootloader' (4610 KB) OKAY [ 0.280s]
Writing 'bootloader' OKAY [ 0.140s]
Finished. Total time: 0.530s
Rebooting into bootloader OKAY [ 0.005s]
Finished. Total time: 0.055s
< waiting for any device >
Sending 'radio' (56630 KB) OKAY [ 2.685s]
Writing 'radio' OKAY [ 0.558s]
Finished. Total time: 3.565s
Rebooting into bootloader OKAY [ 0.004s]
Finished. Total time: 0.054s
< 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.010s]
extracting boot.img (11 MB) to disk… took 0.228s
archive does not contain ‘boot.sig’
Sending ‘boot’ (11781 KB) OKAY [ 0.620s]
Writing ‘boot’ OKAY [ 0.124s]
archive does not contain ‘dtbo.img’
archive does not contain ‘dt.img’
extracting recovery.img (17 MB) to disk… took 0.535s
archive does not contain ‘recovery.sig’
Sending ‘recovery’ (17425 KB) OKAY [ 0.905s]
Writing ‘recovery’ OKAY [ 0.201s]
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 53.678s
archive does not contain ‘system.sig’
Sending sparse ‘system’ 1/4 (508768 KB) OKAY [ 27.155s]
Writing ‘system’ OKAY [ 6.239s]
Sending sparse ‘system’ 2/4 (524238 KB) OKAY [ 27.742s]
Writing ‘system’ OKAY [ 6.081s]
Sending sparse ‘system’ 3/4 (501061 KB) OKAY [ 26.765s]
Writing ‘system’ OKAY [ 6.592s]
Sending sparse ‘system’ 4/4 (421469 KB) OKAY [ 21.969s]
Writing ‘system’ OKAY [ 4.685s]
extracting vendor.img (185 MB) to disk… took 5.161s
archive does not contain ‘vendor.sig’
Sending ‘vendor’ (190332 KB) OKAY [ 8.946s]
Writing ‘vendor’ OKAY [ 2.777s]
Rebooting OKAY [ 0.018s]
Finished. Total time: 202.249s
Please try to get the phone to Recovery.
If this fails then fastboot then
fastboot reboot recovery
and please can you add three backticks ``` before and after your terminal output or “preformatted” </>
fastboot reboot recovery
and now the phone is black after doing its loop…no erasing this time…
i put it back to the recovery mode
It is not clear is the phone stable in recovery ?
If yes can you do
adb devices
Then l get list of devices attached but no list of devices under…
Then my prompt line
Its when l enter a command it makes the phone loop sometimes and not always back to recovery mode
Well maybe there is a solution to come …
It seems all is reasonably ok with this version of fastboot, but userdata is corrupted.
I believe this could be enough to prevent boot to either system or recovery. So the next task is to find some intervention which would repair userdata.
Some technique which would check the partition and format it with some repair not included in fastboot …
1 Like
Maybe this can help ?
https://xdaforums.com/t/how-i-fixed-my-bricked-nexus-5-corrupted-userdata-bootlooping.2903593/
I will come back to your new link … but from your first work this evening Post #113 the only command that was ok was
fastboot erase userdata
Will that work now followed by
fastboot reboot recovery