Database Develop

[Q] Can't fastboot because of driver problems

Hello everyone. I want to install CyanogenMod to my Sony Xperia SP 12.1.A.1.205.
I already unlocked the bootloader, I already rooted it, and even my PC (using Linux) detects it, but I just can't get fastboot to recognize the device. If I type in the command line
Code:
adb devices
CB51240CAW device
But if I try to do fastboot flash boot boot.img to install CyanogenMod I always get "Waiting for device". If I type fastboot devices I get no response (of course I restart my phone holding volume up to fastboot).
Is it even possible that my PC recognize my device using adb but not using fastboot?
Thank you in advance.

Nevermind, I did it in Windows 8.1 following this:http://forum.xda-developers.com/showthread.php?t=2588979

bbabel said:
Nevermind, I did it in Windows 8.1 following this:http://forum.xda-developers.com/showthread.php?t=2588979
Click to expand...
Click to collapse
U can install the fastboot drivers on windows 8 or 8.1 by signing off of the drivers in advance reboot of the PC.:good:

[Bricked][Asus Zenfone/Zenforce 4] Boot loop on Asus logo

Hey,
Since multiple flashing operation (fastboot), the phone was turned into 'brick' and seems now looping on Asus logo at start..
After pressing power button + vol up the phone is well entering into droidboot but with this log message : 'E:Unable to open debricking'.
The phone stills open with USB cable (fastboot/adb) but I've already experienced some 'signature mismatching' during flash?
Any idea to recover ?
Thanks!
Product : TW_ZENFON (not WW)
Droidboot ver : 4.3.10.0

[Bricked][Asus Zenfone/Zenforce 4] fastboot flash fastboot fastboot.img
W4sh said:
Hey,
Since multiple flashing operation (fastboot), the phone was turned into 'brick' and seems now looping on Asus logo at start..
After pressing power button + vol up the phone is well entering into droidboot but with this log message : 'E:Unable to open debricking'.
The phone stills open with USB cable (fastboot/adb) but I've already experienced some 'signature mismatching' during flash?
Any idea to recover ?
Thanks!
Product : TW_ZENFON (not WW)
Droidboot ver : 4.3.10.0
Click to expand...
Click to collapse
After flashing the device with fastboot flash fastboot fastboot.img the output log are now : E:flash_fastboot_kernel : check_sign_key fail no allow to update kernel
Well, it seems that a specific firmware is needed and droidboot is checking for a key signature? If no match, it cannot allow an overwritting or something.

hi
Please forgive me English is not very good. You determine your own model, the Asus machine has some need to correct the file name, for example, k012, the file name is k012_sdupdate.zip. Then look at your card is correct brush pack

The device has been flashed once again with fastboot -> fastboot flash fastboot fastboot.img
The fastboot.img file was included from the official firmware zip archive UL_ASUS_T00Q_TW_4_3_2.zip
The operation was done succesfully without any error... meanwhile the boot is now going to blank (Android robot is fading to blank) and loop continuously...
If I restart the phone, the boot stuck as well on the Asus logo... So no more droidboot menu available..
@Chinaxiao4 : do you mean to rename the firmware (ie : UL_ASUS_T00Q_TW_4_3_2.zip) with the device model number ? Afterwards do we need to play with adb/fastboot ?

hi
You try, some machines need to change the name ASUS, please forgive me English is very bad, can not help you get more information

Chinaxiao4 said:
You try, some machines need to change the name ASUS, please forgive me English is very bad, can not help you get more information
Click to expand...
Click to collapse
No worries for your English, well.. my machine/device is an 'Asus T00i'

W4sh said:
No worries for your English, well.. my machine/device is an 'Asus T00i'
Click to expand...
Click to collapse
..so far it might be a firmware like this UL_ASUS_T00I_TW_4_X_X.zip

To resume, the Asus Zenforce/Zenfone 4 (T00I) TW model has been bricked since some flashing operation with firmware.
- used firmware : UL_ASUS_T00Q_TW_4_3_2.zip
- command line : fastboot flash fastboot fastboot.img
- result : No more boot menu... the droidboot is fading to blank, boot loop on model logo (bricked)
- Looking for (maybe) : UL_ASUS_T00I_TW_4_x_x.zip and droidboot with recovering mode
Linux to help by mounting the device and doing some repartionning job? Let's go further!!

When plug on USB the device is now unrecognized due of his previous flashing... (no matched Drivers)
Any help so far?

Boot Loop and no more driver to recognize the phone
https://www.youtube.com/watch?v=eUOTnIkXMvY&feature=youtu.be

RE
W4sh said:
https://www.youtube.com/watch?v=eUOTnIkXMvY&feature=youtu.be
Click to expand...
Click to collapse
As said from the vid, "better to replace the initial droidboot by another recovery mod before doing anything "

A bit darky but the idea seems ok, hoping for a next further release of Clockworkmod recovery
https://www.youtube.com/watch?v=OQ1gE9TpZ60
Meanwhile no idea to get outta my bootLoop locking screen...

Hi,
Is there any update solution, hint? My zenfone 4 also in brick bootloop intel logo status, can't enter to fastboot mode using key combination Power and Volume. It also cannot be detected using USB in PC.

coffeelover said:
Hi,
Is there any update solution, hint? My zenfone 4 also in brick bootloop intel logo status, can't enter to fastboot mode using key combination Power and Volume. It also cannot be detected using USB in PC.
Click to expand...
Click to collapse
me 2 same prblm dude got any solution
pls reply us

Flash image failure(FAILED (remote: ERROR: Image-SKU: 'TW_Zenfone' Device-SKU: 'WW_Zenfone'))
I get this error message while flashing using AFT

[Q] Memopad 7 170C root fails. help!

I'm trying too root my Asus memo pad 7 (170C), I've tried EVERY method, using KingoRoot, SuperOneClick, Frameroot, motochopper. None of them worked.
So I decided to do the rooting stuff myself, first I tried on Windows 8, the fastboot driver was not recognized, I installed the PdaNet, It recognizes the device now, the problem is when I run "fastboot oem unlock" or "fastboot oem unlock0x0b05" (ASUS VendorID), it returns : "FAILED (remote: unknown OEM command)"
I enter bootloader with "adb reboot bootloader" or by pressing Volume Up and Power.
I have also tried in Ubuntu 14.04, It doesn't even recognize the device in fastboot, and yes I run fastboot as root, still no chance "fastboot devices" returns nothing, and "fastboot oem unlock" returns "Waiting for device"
I did run "usbls" command, and it was clear that the OS has recognized the tablet, but why the fastboot does not?
Here is some information of my specs: ASUS MemoPad 7 (170C) Windows 8.1 64bit AND/OR Ubuntu 14.04
Bootloader: DroidBoot Provision Os, DroidBoot Ver: WW_MeMO_Pad-11.2.3.28-20141230 IFWI Version: 64.25
PLEASE somebody save my life as I'm stuck with it for a very long time!

arman92 said:
I'm trying too root my Asus memo pad 7 (170C), I've tried EVERY method, using KingoRoot, SuperOneClick, Frameroot, motochopper. None of them worked.
So I decided to do the rooting stuff myself, first I tried on Windows 8, the fastboot driver was not recognized, I installed the PdaNet, It recognizes the device now, the problem is when I run "fastboot oem unlock" or "fastboot oem unlock0x0b05" (ASUS VendorID), it returns : "FAILED (remote: unknown OEM command)"
I enter bootloader with "adb reboot bootloader" or by pressing Volume Up and Power.
I have also tried in Ubuntu 14.04, It doesn't even recognize the device in fastboot, and yes I run fastboot as root, still no chance "fastboot devices" returns nothing, and "fastboot oem unlock" returns "Waiting for device"
I did run "usbls" command, and it was clear that the OS has recognized the tablet, but why the fastboot does not?
Here is some information of my specs: ASUS MemoPad 7 (170C) Windows 8.1 64bit AND/OR Ubuntu 14.04
Bootloader: DroidBoot Provision Os, DroidBoot Ver: WW_MeMO_Pad-11.2.3.28-20141230 IFWI Version: 64.25
PLEASE somebody save my life as I'm stuck with it for a very long time!
Click to expand...
Click to collapse
Because these Asus tablets use Intel processors, I do not believe that fastboot works. You did not indicate that you had tried the RootZenFone tool in your post above. See this thread:
http://forum.xda-developers.com/memo-pad-7/help/me170cx-k01a-root-t2985421
I have rooted two of these tablets using this method, and it worked perfectly on both of them.

CYoung234 said:
Because these Asus tablets use Intel processors, I do not believe that fastboot works. You did not indicate that you had tried the RootZenFone tool in your post above. See this thread:
http://forum.xda-developers.com/memo-pad-7/help/me170cx-k01a-root-t2985421
I have rooted two of these tablets using this method, and it worked perfectly on both of them.
Click to expand...
Click to collapse
Yes I did try the RootZenFone tool, but it didn't work either.
Unfortunately I forgot to "Forget the wireless networks" (I just disabled the WiFi), and the RootZenFone failed rooting my device...
Is there any way to get it work again?

HELP ME!!
Anybody got an idea?
Would it be helpful if I Re-Flash the Asus official ROM to my tablet and start over? If it is, how can I do that?
PLEASE somebody help me!

arman92 said:
Anybody got an idea?
Would it be helpful if I Re-Flash the Asus official ROM to my tablet and start over? If it is, how can I do that?
PLEASE somebody help me!
Click to expand...
Click to collapse
Yes, you can go into bootloader mode and restore the factory rom, which will likely downgrade you to 4.3 again. Then you can do the OTA update and use the RootZenFone again. This time, remember to follow the instructions EXACTLY, and you should do fine.
Edit: I do not have the two I set up right now, but they both were visible to my desktop in fast boot mode. They responded to fast boot device. Beyond that, I never tried fastboot oem unlock. Did you try just typing fastboot to see the comand set? You might try that.

Done! I'm Root
CYoung234 said:
Yes, you can go into bootloader mode and restore the factory rom, which will likely downgrade you to 4.3 again. Then you can do the OTA update and use the RootZenFone again. This time, remember to follow the instructions EXACTLY, and you should do fine.
Edit: I do not have the two I set up right now, but they both were visible to my desktop in fast boot mode. They responded to fast boot device. Beyond that, I never tried fastboot oem unlock. Did you try just typing fastboot to see the comand set? You might try that.
Click to expand...
Click to collapse
I've followed the instructions in this page : http://forum.xda-developers.com/android/help/instructions-reviving-me170c-me170cx-t3017466
I successfully made it flash the Asus official ROM, but every time the freaking "Unfortunately Asus Demo has stopped" showed up.
I tried 4 different ROMs, still I got the error. I tried the RootZenFone-1.4.6r.apk everytime, no chance. The rooting process was interrupted by the "Unfortunately Asus Demo has stopped"
Then I figured out that when the tablet is connected to a power source (e.g. USB charge or PC), the error come up more frequent, so I disconnected the USB cable and tried the RootZenFone again, after a fresh ROM recovery, this time it successfully finished the rooting process. Huurrraaaay!!
So for every one else that has the same issue: just disconnect the USB cable and you are good to go!
Thanks for everyone that helped.

[ HELP ] Motorola XT1068 not booting up after rooting [ URGENT ].

I just installed KingoRoot in my Motorola XT1068 and rooted the device.
after rebooting, following errors are arousing while rebooting.
> hab check failed for boot
> Failed to varify hab image boot
> failed to validate boot image
Fastboot Reason: Fall-through from normal boot mode:crying:
While connecting to PC, device not showing in My Computer.
OS in PC : Windows 10.
ROM in Device: STOCK Marshmellow.
Things I have tried:
1. Installing Motorola Drivers to my PC.
2. Using ADB and FASTBOOT on Computer.
3. Tried using FASTBOOT but it is not showing any device being connected.
Kindly Help as soon as possible. :crying::crying:

nomoreusernameplz said:
I just installed KingoRoot in my Motorola XT1068 and rooted the device.
after rebooting, following errors are arousing while rebooting.
> hab check failed for boot
> Failed to varify hab image boot
> failed to validate boot image
Fastboot Reason: Fall-through from normal boot mode:crying:
While connecting to PC, device not showing in My Computer.
OS in PC : Windows 10.
ROM in Device: STOCK Marshmellow.
Things I have tried:
1. Installing Motorola Drivers to my PC.
2. Using ADB and FASTBOOT on Computer.
3. Tried using FASTBOOT but it is not showing any device being connected.
Kindly Help as soon as possible. :crying::crying:
Click to expand...
Click to collapse
please try to plug the charger in and hold the power and volume down button simaltaniously for 120 secs, this will boot it in a mode that adb will recognize.. then try the normal boot option (if it doesnt work try it again for a couple of times) please report if you have stability issues, wich might require a reset/ rom reflash
please be carefull in recovery mode!
ohh and, please dont mess it up if you decide to reflash the rom.. its impossible to fix..

You used KingRoot. It's incompatible with locked devices. Reflash a factory image and then unlock your bootloader and try again.

Redmi 4a - brick...Need help!

Hi everyone!
I need help, please.
Xiaomi Redmi 4A - 2/16 Gb. Boot unlocked.
Problem after flashing miui 11 with error:
1. TWRP - don`t aviable now and I can`t flash it;
2. Fastboot - I can enter in Fastboot mode, but smartphone not detected by computer (win 7/64) and notebook (win 10/32). all drivers - ADB, Quallcom - installed correctly;
3. I try to enter EDL mode - with two test points on a motherboard. I tried to connect them - without effect - my PC and Notebook can`t detect device...
What can I do ?

Try my suggestions
If you have another smartphone please download apk
https://play.google.com/store/apps/details?id=eu.sisik.hackendebug
Bring your bricked phone to fastboot mode. Using bugjaeger apk you can flash and anyhow you told that bootloader is unlocked if your bootloader is locked then whole procedure will not work
I am providing YouTube link try it
https://youtu.be/G_E8ImOoQZM
Video is about 7:54 Watch the video 4:00 carefully
Dont Flash any custom ROM or recovery
flash all files which is in stock ROM only (zip or rar or tgz)
and don't lock bootloader.
After flashing try to restart phone
If the procedure didn't work
Sorry for wasting your time.