Guest PaulOBrien Posted October 13, 2014 Report Posted October 13, 2014 This is a weird one.I can get to bootloader by doing 'adb reboot bootloader', but doing power-on with both volume buttons held starts the bootloader but never loads fully (commands don't work).This is problematic for hacking the device, as I have it in a non-booting state but can't fix it from bootloader as it won't load. ARGH! :(P
Guest Posted October 13, 2014 Report Posted October 13, 2014 You've probably already tried it - but does the strange 'safe mode' still work?
Guest PaulOBrien Posted October 13, 2014 Report Posted October 13, 2014 Safe mode? Not familiar with that! I think the device may have fastboot and Droidboot as 2 different things and that's what I'm seeing... P
Guest PaulOBrien Posted October 13, 2014 Report Posted October 13, 2014 Ah, that safe mode... No, that won't help sadly! P
Guest sville Posted October 14, 2014 Report Posted October 14, 2014 Many manufacturers disable Fastboot from boot, to prevent people compromising unattended devices. If it's on KitKat you can still ADB sideload a signed (unless it's rooted) OTA ZIP from recovery mode to un-brick your device.
Guest PaulOBrien Posted October 19, 2014 Report Posted October 19, 2014 For that you'd need a signed full ROM update zip which we don't have. P
Guest PaulOBrien Posted October 19, 2014 Report Posted October 19, 2014 Root itself also doesn't affect that requirement for the zip to be signed. P
Guest vermillions Posted October 21, 2014 Report Posted October 21, 2014 Is there a way we can modify the boot.img to get red of the recovery partition check and give us full fastboot via button press. The Teclast x98 seems very similar could we compare the boot images and mod ours from it.
Guest PaulOBrien Posted October 21, 2014 Report Posted October 21, 2014 No, that's not how it works sadly. P
Guest uub Posted November 4, 2014 Report Posted November 4, 2014 (edited) fastboot is not broken, we do not have access to the bootloader/bios as such, the fastboot server is actually run from user-level on this device as opposed to the boot level, holding volume up+down+power does not invoke the bootloader it actually starts a fastboot server that is looking for an update zip on an sdcard and an installer script. I'd be interested to know exactly what steps you took to brick yours Paul. I have attached a copy of Intel's modified version of the adb and fastboot client which also has the tcp-ip option not available in the AOSP version. intel-fastboot-adb.part1.rarintel-fastboot-adb.part2.rar Edited November 5, 2014 by uub
Guest vermillions Posted November 5, 2014 Report Posted November 5, 2014 fastboot is not broken, we do not have access to the bootloader/bios as such, the fastboot server is actually run from user-level on this device as opposed to the boot level, holding volume up+down+power does not invoke the bootloader it actually starts a fastboot server that is looking for an update zip on an sdcard and an installer script. I'd be interested to know exactly what steps you took to brick yours Paul. I have attached a copy of Intel's modified version of the adb and fastboot client which also has the tcp-ip option not available in the AOSP version. Without the installer script and update zip (which I assume will need to be signed) it is no better than the recovery menu option to use update zip. Unless you are saying that you have working fastboot access via tcp-ip at the point the fastboot server is running after being invoked by button press.
Guest vermillions Posted November 6, 2014 Report Posted November 6, 2014 It would be interesting to see if we could edit the installer-script to reboot bootloader
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now