- #Minimal adb fastboot for bricked device update#
- #Minimal adb fastboot for bricked device android#
- #Minimal adb fastboot for bricked device Pc#
- #Minimal adb fastboot for bricked device windows#
If only I had my device I would had some of tried these things out.ġ: the issue is not some much the lack of a recovery image, even if one is not built as part of the current build, its a relatively straight forward task to put one together given that we have a git repo for the linux kernel src tree for the flatfish. I eventually found this as my ZTE One had no usable adb or fastboot mode for flashing.
#Minimal adb fastboot for bricked device windows#
They only provide a Windows client to upload files and it’s not in English either, but does the trick. This is accessed by pressing both volume keys when plugging in the USB and with battery removed.
#Minimal adb fastboot for bricked device Pc#
In this case the ZTE One has another mode in its Firmeware allowing upload from a PC using a client tool. I expect it is perfectly possible to screw up the images so that there is no way to boot at all.
As there appears to be no recovery.image shipped then perhaps if all the hardware support is there we just need to provide a recovery.img and it will work?. We need the manufacturer to sort this out. I assume it also provides adb and/or fastboot servers for access to allow recover from bad image flashing or OTA access for more techy users and devs.
This provides a relatively non technical way for users to factory reset the device if “bricked” during normal operation.
#Minimal adb fastboot for bricked device update#
#Minimal adb fastboot for bricked device android#
My ZTE One with Firefox OS has such an Android system recovery partition, accessed by holding the volume up key when turning on with the power button. I don’t think it is eve built however, but should be on the device and backed up. img files to be built as part of Firefox OS. The MDN docs mention this as one of the 4 key. This is usually a simple button access to boot a separate recovery.img which is a self contained minimal OS with simple text menu UI. Maybe this should go into the wiki somewhere as Yes, spot on. Hope that helps clear things up - sorry I really should have documented this earlier as its become a bit of a FAQ in irc and email discussions. etc) though there are others and I think AOSP comes with a simple default sample from Google iirc. I think the easier starting point will be just fastboot, as unless the nand partitioning scheme already includes a recovery partition, we’d need to change it to accomodate one.įinally terminology wise, in the android community, people often refer to CWM recovery, (ClockWorkMod) which is the most popular recovery image (linux kernel + app UI. I don’t have my tablet yet, but once I do I plan on trying to figure out how difficult it will be to modify the u-boot version installed on the flatfish to look for a hardware button combo to either go into fastboot mode or boot an alternative partition to boot.img which would be the recovery parition. Without that button combo, recovery would only be a step forward in that it would provide a nicer UI for people to use to update to newer builds without the need to have the fastboot exe installed on a separate notebook/desktop OS. However the problem with having a recovery partition for flatfish devices is the same as the one we currently have fastboot - the only way to boot into it is via an adb command, unlike on many android consumer devices, where there is a hardware button combo to press at boot, to make the bootloader boot into the recovery partition (or put the bootloader into fastboot mode). copy over new imgs onto the internal flash, reformat existing internal disk partitions, etc. This is somewhat similiar to “booting into fastboot” except where into fastboot means that the bootloader just stops its normal bootup process and doesn’t boot the normal OS and instead just sits there listening for fastboot commands on the USB port, recovery partitions are really an alternative tiny OS, with a separate Linux kernel and usually very basic app that gets run to provide a UI to do the same kinds of things as you would from fastboot, ie. I think when mentioned “recovery” he referring the the usual situation on android devcies, where there is a separate partition on a devices internal flash disk (nand) that you can boot into instead of booting into the normal OS (fxOS in our case).