Hey guys, My brother gave me a tablet to use for my etextbooks at college and I haven't used the tablet too often tbh. I saw that there was an update and the entire tablet froze during the process and now is stuck in a bootloop. I'm completely new to abd and every time I run it, it doesn't recognize the commands. I tried side loading and got this error through adb "adb server version (31) doesn't match this client (39) killing."
This is the only way I can see it on my computer. I was able to get around the adb server error by using my new laptop but now I'm stuck because it's stock so the bootloader is locked.
https://imgur.com/JKZ79sy
Sideload an OTA image with stock recovery: -
https://developers.google.com/android/ota
You can't use ADB commands while in fastboot mode ("fastboot devices" is the correct command in that mode).
Related
Should I be able to find my adb device while my phone is only booting to HBOOT 0.93.0001?
Been stuck on this for days...and it's killing me!
PS. When I plug my phone in to
PC it says "Android ADB interface installed" "Ready to use"
But when I cmd the adb to find devices "adb devices" it shows blank
P.S. Phone: HTC Desire
Unrooted
S-ON
Unable to boot, can only get to HBOOT.(so cant turn debugging on)
Trying to get a goldcard to flash a new rom and see if i can unbrick
Reason for unable to boot is - It had been rebooting itself for weeks, slowly getting worse, until now, when I cant get it booted at all.
budron said:
Should I be able to find my adb device while my phone is only booting to HBOOT 0.93.0001?
Been stuck on this for days...and it's killing me!
PS. When I plug my phone in to
PC it says "Android ADB interface installed" "Ready to use"
But when I cmd the adb to find devices "adb devices" it shows blank
P.S. Phone: HTC Desire
Unrooted
S-ON
Unable to boot, can only get to HBOOT.(so cant turn debugging on)
Trying to get a goldcard to flash a new rom and see if i can unbrick
Reason for unable to boot is - It had been rebooting itself for weeks, slowly getting worse, until now, when I cant get it booted at all.
Click to expand...
Click to collapse
adb won't work when you are in bootloader (It won't work until Linux is up). "fastboot" will work over USB in bootloader->Fastboot.
I believe RUU will work on fastboot mode.
Hello Everyone, this is one of my first posts so go easy on me.
I used the method in this thread to flash JB onto my TF201, and now i cannot boot to recovery (get the android on his back/side with the red exclamation) and fastboot shows up as a device in device manager in windows, but when i run the "fastboot devices" command with the up to date SDK nothing is listed. ADB works, but for osme reason superuser was installed as a system process and will not uninstall, and will not issue any sort of root command to anything, including ADB. any ideas?
I boot my Acer Iconia Tab A200 into fastboot mode (robot lying down and RED exclamation mark over it). I plug it into my Windows 7 (64bit) desktop computer with SDK installed, and from the directory with fastboot.exe I type FASTBOOT DEVICES but the device is not being seen, it just goes back to the prompt, like the command executed but didn't do anything. I assume this is because the drivers aren't installed. But I don't know how to install the "adb drivers". How is this done?
Go to Acer support page, you'll get the drivers there.
This device will not fully boot. It gets stuck at an "encryption unsuccessful" message. I'm trying to flash a rom image from my desktop computer using fastboot, but when my tablet is in fastboot mode, my desktop computer won't recognize it. ie adb devices command doesn't show that there is any device connected, and I think it's because the drivers aren't installed. I think those Acer drivers only work if the tablet can be fully booted.
Installed the Google USB Drivers from the SDK Manager already. Don't know what's wrong.
Alright I figured out how to get fastboot to interface with my Android tablet. The problem was that I wasn't getting the tablet into fastboot mode to recieve commands.
But now it's working. However, I'm trying to unlock the bootloader and it gives me an errors that says:
SetUnlockedMode: Error occured while unlock the device ...
Fastboot: Failed to set unlock mode
I have to unlock the bootloader before I flash an image to the tablet, right ?
Yep, surely.
Any help would be greatly appreciated. I have been reading the forums for several days and believe that I am completely stuck. My son rooted his KFHDX 7" and was messing with different apks. It was still working at this point.
He thought it was running slow so he put it into recovery mode (power and volume up) and chose to reset it back to factory settings. Now it just boots to the Gray Kindle Fire bootup screen. Now the ADB is not enabled, he lost his root, and the device is locked.
When I plug the device into my computer (Windows 7) it won't even recognize it. Instead it gives me MTP Devices with error. I have loaded all of the device drives and Android SDK with no luck.
The only adb functions that appear to work are:
adb devices -------> This only gives me the generic serial# 01234569789ABCDE
adb reboot -------> This will reboot the kindle but it won't go past the gray logo
adb reboot-bootloader -------> This will put me into fastboot mode
adb kill-server
adb start-server -------> This will restart the ports but has not affect on the other commands
In fastboot mode I am to access all of the normal commands:
fastboot devices -------> This only gives me my actual serial#
fastboot reboot
fastboot oem unlock -------> It says it is unlocked but it is still locked
fastboot oem lock
However I can't use the following commands since it says my device is locked:
fastboot -i 0x1949 oem device-info
fastboot flash recovery twrp-2.8.x.x-xxx.img
fastboot boot twrp-2.8.x.x-xxx.img
I tried the 1-Click automated file and it got me all the way through until it asked me to enable the ADB debugging which I couldn't do since I am stuck at the boot screen. And I can't use a tool kit to fix it since I can't downgrade to a lower release.
Therefore I can not unlock my bootloader without downgrading which is impossible without a working system and functioning recovery. I can't root my devices without ADB enabled. And I can not flash a new working ROM due to the locked bootloader. Did I miss anything or is there still something I can do?
Please help, I am trying to get this working before Christmas.
Thanks.
DadSteveo said:
Any help would be greatly appreciated. I have been reading the forums for several days and believe that I am completely stuck. My son rooted his KFHDX 7" and was messing with different apks. It was still working at this point.
He thought it was running slow so he put it into recovery mode (power and volume up) and chose to reset it back to factory settings. Now it just boots to the Gray Kindle Fire bootup screen. Now the ADB is not enabled, he lost his root, and the device is locked.
When I plug the device into my computer (Windows 7) it won't even recognize it. Instead it gives me MTP Devices with error. I have loaded all of the device drives and Android SDK with no luck.
The only adb functions that appear to work are:
adb devices -------> This only gives me the generic serial# 01234569789ABCDE
adb reboot -------> This will reboot the kindle but it won't go past the gray logo
adb reboot-bootloader -------> This will put me into fastboot mode
adb kill-server
adb start-server -------> This will restart the ports but has not affect on the other commands
In fastboot mode I am to access all of the normal commands:
fastboot devices -------> This only gives me my actual serial#
fastboot reboot
fastboot oem unlock -------> It says it is unlocked but it is still locked
fastboot oem lock
However I can't use the following commands since it says my device is locked:
fastboot -i 0x1949 oem device-info
fastboot flash recovery twrp-2.8.x.x-xxx.img
fastboot boot twrp-2.8.x.x-xxx.img
I tried the 1-Click automated file and it got me all the way through until it asked me to enable the ADB debugging which I couldn't do since I am stuck at the boot screen. And I can't use a tool kit to fix it since I can't downgrade to a lower release.
Therefore I can not unlock my bootloader without downgrading which is impossible without a working system and functioning recovery. I can't root my devices without ADB enabled. And I can not flash a new working ROM due to the locked bootloader. Did I miss anything or is there still something I can do?
Please help, I am trying to get this working before Christmas.
Thanks.
Click to expand...
Click to collapse
Unfortunately, there is no known recovery from this type of failure. I don't say that casually and wish there was a solution. The symptoms you report are both common and tell tale. The device is bricked.
I just replaced the motherboard on my hdx 8.9
It worked, I had to order a daughterboard also.
Total cost around $50 from where I got them.
Worth looking into. Watch teardown videos on YouTube and get the right tools.
Sent from my SM-N920T using Tapatalk
Too late?
DadSteveo said:
In fastboot mode I am to access all of the normal commands:
fastboot devices -------> This only gives me my actual serial#
fastboot reboot
fastboot oem unlock -------> It says it is unlocked but it is still locked
fastboot oem lock
And I can not flash a new working ROM due to the locked bootloader. Did I miss anything or is there still something I can do?
Click to expand...
Click to collapse
Since fastboot appears to respond as expected on your device,
I'd be **very** interested in testing my long-standing theory
that 'fastboot update' __might__ work even on locked devices.
The "gotcha" is that we'd need to prepare the right package for
your Kindle. So, I gather it's an HDX 7" (3rd Gen?), i.e. "thor" model.
Do you remember what version of Fire OS you had installed?
Long story short: installed custom rom, went into TWRP bootloop, tried to flash back to stock ended with bootloop.
Is there a way to enter into fastboot? So I can at least flash TWRP back.
Currently it's booting, displaying the boot screen with the orange state warning and almost immediately rebooting
Fastboot on Android side gets activated by bootloader. Hence you should be able to run Fastboot commands.
To test this you run on Windows computer
Code:
fastboot devices
jwoegerbauer said:
Fastboot on Android side gets activated by bootloader. Hence you should be able to run Fastboot commands.
To test this you run on Windows computer
Code:
fastboot devices
Click to expand...
Click to collapse
Tried to spam sudo fastboot devices on linux, but to no avail.
Trying on windows as soon as I find the drivers
Installed the drivers from here and rebooted: https://gsmmobiledriver.com/umidigi-f1
Spammed fastboot.exe devices in admin power shell, but again no output at all
While it doesn't respond to fastboot, I noticed that, while booting, lsusb displays the preloader:
Bus 003 Device 010: ID 0e8d:2000 MediaTek Inc. MT65xx Preloader
Is there a way to interact with it?
It seems it's possible to unbrick the phone with SP Flash Tool, I can't find a guide or how to do it however...
Edit: all guides I had foudn require to device to be powered off. Given that my case is a bootloop, I will try to wait until the battery has dried up
Ended up following this: https://forum.xda-developers.com/t/stuck-in-a-boot-loop-and-cant-access-recovery-mode.3818742/
Standard procedure with SPFlashTool: no preloader, download all else. Results in a "PMT changed for the rom; it must be downloaded", so I probably have a faulty firmware copy
Edit: wrong firmware, my phone uses the global instead of the EU one for some reason