Asus Nexus 7 (flo) ubuntu-device-flash
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical System Image |
New
|
Undecided
|
Unassigned |
Bug Description
The starting point was an install of Android by Asus Service Australia. - Then updates were applied by myself once connected to Wi-Fi.
Instructions were followed to the letter: https:/
jonathan@
2015/09/25 13:27:53 Expecting the device to be in the bootloader... waiting
2015/09/25 13:27:53 Device is |flo|
2015/09/25 13:27:55 Flashing version 1 from ubuntu-
6.25 MB / 6.25 MB [======
54.60 MB / 54.60 MB [======
285.87 MB / 285.87 MB [======
2015/09/25 14:25:16 Start pushing /home/jonathan/
2015/09/25 14:25:16 Start pushing /home/jonathan/
2015/09/25 14:25:16 Start pushing /home/jonathan/
2015/09/25 14:25:16 Start pushing /home/jonathan/
2015/09/25 14:25:16 Start pushing /home/jonathan/
2015/09/25 14:25:16 Start pushing /home/jonathan/
2015/09/25 14:25:17 error pushing: failed to copy '/home/
The Nexus 7 (flo) remains connected to Ubuntu in the case that installation can be resumed or it can be unbricked by myself.
tags: | added: flo |
tags: | added: ubuntu-device-flash |
I have successfully downgraded the bootloader to 4.02 using 'flash-all.sh' and "fastboot flash bootloader bootloader- flo-flo- 04.02.img" .
Meanwhile using 'flash-all.sh' and by invoking the commands directly for each of the image files for the operating system lead to the Nexus 7 showing only the white 'Google' logo and unlocked padlock.
I also have an Asus Nexus 7 (tilapia) which was unbricked by Asus Service Australia whom installed Android 5.1.1 on to it and this same flo.
Do I need to have Asus Service Australia to downgrade the tilapia to Android 4.4.4 and unbrick the flo for me?