Jump to content
PaulOBrien

Bootloader issue

Recommended Posts

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

Share this post


Link to post
Share on other sites

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

Share this post


Link to post
Share on other sites

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.

Share this post


Link to post
Share on other sites

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. 

Share this post


Link to post
Share on other sites

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.rar

intel-fastboot-adb.part2.rar

Edited by uub
  • Upvote 1

Share this post


Link to post
Share on other sites

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.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×

Important Information

By using this site, you agree to our Terms of Use.