Database Info

[Q] "key driver not found.. booting os"

hello
i'm new to this forum .
well here my probleme (if it's a problem):
i have a tf300t 32 giga 4.1,
i update ota to 4.2.1
i unlock, install TRWP the root the device.
every thing work just fine (i think), i can acces trwp and boot fine ...
but when i doing " power+volume down" plug or not to usb i got 3 rows:
"
key driver not found.. booting os
android cardhu-user bootloader <1.00 e> released by "us_epad-10.6.1.8-20130225" a03
Sarting Fastboot usb download protocol
"
everything seem to work fine.
the driver is ok (i guess) i can acces sd card and internal memory and windows reconize the tablette ....
thanks for help.

mitomon said:
hello
i'm new to this forum .
well here my probleme (if it's a problem):
i have a tf300t 32 giga 4.1,
i update ota to 4.2.1
i unlock, install TRWP the root the device.
every thing work just fine (i think), i can acces trwp and boot fine ...
but when i doing " power+volume down" plug or not to usb i got 3 rows:
"
key driver not found.. booting os
android cardhu-user bootloader <1.00 e> released by "us_epad-10.6.1.8-20130225" a03
Sarting Fastboot usb download protocol
"
everything seem to work fine.
the driver is ok (i guess) i can acces sd card and internal memory and windows reconize the tablette ....
thanks for help.
Click to expand...
Click to collapse
I have the same thing. is it a problem?

mitomon said:
hello
i'm new to this forum .
well here my probleme (if it's a problem):
i have a tf300t 32 giga 4.1,
i update ota to 4.2.1
i unlock, install TRWP the root the device.
every thing work just fine (i think), i can acces trwp and boot fine ...
but when i doing " power+volume down" plug or not to usb i got 3 rows:
"
key driver not found.. booting os
android cardhu-user bootloader <1.00 e> released by "us_epad-10.6.1.8-20130225" a03
Sarting Fastboot usb download protocol
"
everything seem to work fine.
the driver is ok (i guess) i can acces sd card and internal memory and windows reconize the tablette ....
thanks for help.
Click to expand...
Click to collapse
Uh oh..
no key driver means that your device is calling aliens to invade earth telling them that we have no key driver so we are all gonna be doomed!!! HOW COULD YOU DO SUCH A THING!?!?
Just kidding
Its normal. No need to worry. My tablet says it too. I think all of them do. I think thats what allows us to access fastboot. since there is no key driver, its pretty much allowing any device with fastboot to write to the tablet. Thats just my theory. But in the end, its normal and doesnt need to be worried about

I don't afraid , marcus and dom with all gears (gears of war) will do them the hell !!!!
Thanks for the help
Thanks to your forum i root my two tablettes and the cellphone of my niece

Can't upgrade to V10.6.1.15.3
I have unlocked my TF300T (and I regret that).
I always upgraded from the firmware found on Asus Support website, I just downloaded the latest one, unzipped and copied to the root of my sdcard and restarted the device using power + volume down ... and never had problem doing this way.
Now when I try to do the same thing from WW 10.6.1.8 it shows this message:
Key driver not found.. booting os
Android cardhu-user bootloader <1.00 e> released by "ww_epad-10.6.1.8-20130225" A03
Sarting Fastboot USB download protocol
And when I try to choose RCK it restarts, show that green android and then a red flag and stops =/
I tryed to use Fastboot, but there's no response, like no device attached, but it worked before...
Does anyone have a clue about this problem and how I can upgrade to latest firmware?
Since the 10.6.1.8 my tablet has a lot of bugs =/
Thank you so much for any help
Leo

Hi
I upgrade manually with fastboot to us.10.6.1.15.3 with an ulocked and rooted device.
After that trwp crash and iI had to reinstall it and of course re-root the device too ...

hugoleosp said:
I have unlocked my TF300T (and I regret that).
I always upgraded from the firmware found on Asus Support website, I just downloaded the latest one, unzipped and copied to the root of my sdcard and restarted the device using power + volume down ... and never had problem doing this way.
Now when I try to do the same thing from WW 10.6.1.8 it shows this message:
Key driver not found.. booting os
Android cardhu-user bootloader <1.00 e> released by "ww_epad-10.6.1.8-20130225" A03
Sarting Fastboot USB download protocol
And when I try to choose RCK it restarts, show that green android and then a red flag and stops =/
I tryed to use Fastboot, but there's no response, like no device attached, but it worked before...
Does anyone have a clue about this problem and how I can upgrade to latest firmware?
Since the 10.6.1.8 my tablet has a lot of bugs =/
Thank you so much for any help
Leo
Click to expand...
Click to collapse
Hi Leo, I had the same scenario happen on my tablet. If you install the TWRP recovery it will correct it.

Just confirming before doing something stupid
ENDonDESIGN said:
Hi Leo, I had the same scenario happen on my tablet. If you install the TWRP recovery it will correct it.
Click to expand...
Click to collapse
I was going to do this, but for precaucions I decided to look at xda for other people who installed twrp with this message and I found a LOT of folks that bricked their tablet, most of them few days ago .. so I got scared and started to look for others who successfully upgraded using another bootloader and I found just one telling he used fastboot .. .so I just wanted to confirm that I can use this or another method.
I really don't want to risk bricking my tablet.
So you confirm you were on 10.6.1.8 .. you couldn't upgrade using the normal method, so you installed twrp (which one?) and then used it to upgrade to 10.6.1.15.3 ?
Thank you a lot for helping =D
Leo

after upgrading the trwp crash so install it again then i rooted the device again
it's work fine like an android work

Got the same problem as hugoleosp
mitomon said:
after upgrading the trwp crash so install it again then i rooted the device again
it's work fine like an android work
Click to expand...
Click to collapse
I just encountered the same exact problem. In fastboot nothing happens, and twrp from Play requires root, for which I need to install a recovery image in order to aquire. Btw, it is a Tf300t tab. I have installed the stoc k4.2.1, and decided to install another rom. I've tried to update the drivers, but get an error telling me that it didn't succeed, so I uninstalled asus sync, and tried again, with same result. Any ideas are greatly appreciated. What are my options?
Thanks in advance. ^^
D4ffPower

Hi all,
I upgrade my tablet to cyanogenmod 4.3 stable and finaly the tablet is great, forget about stock rom ....
about the twrp i upgrade to the latest release, btw i stil have the same driver error.
Regards,
Mitomon

DaffPower said:
I just encountered the same exact problem. In fastboot nothing happens, and twrp from Play requires root, for which I need to install a recovery image in order to aquire. Btw, it is a Tf300t tab. I have installed the stoc k4.2.1, and decided to install another rom. I've tried to update the drivers, but get an error telling me that it didn't succeed, so I uninstalled asus sync, and tried again, with same result. Any ideas are greatly appreciated. What are my options?
Thanks in advance. ^^
D4ffPower
Click to expand...
Click to collapse
Are you unlocked? Do you have the universal Naked Drivers installed? Is fastboot installed on your computer?
---------- Post added at 09:47 PM ---------- Previous post was at 09:46 PM ----------
mitomon said:
Hi all,
I upgrade my tablet to cyanogenmod 4.3 stable and finaly the tablet is great, forget about stock rom ....
about the twrp i upgrade to the latest release, btw i stil have the same driver error.
Regards,
Mitomon
Click to expand...
Click to collapse
I don't think the message means anything, I get it on mine and it works fine.

cmendonc2 said:
Are you unlocked? Do you have the universal Naked Drivers installed? Is fastboot installed on your computer?
---------- Post added at 09:47 PM ---------- Previous post was at 09:46 PM ----------
I don't think the message means anything, I get it on mine and it works fine.
Click to expand...
Click to collapse
I'm unlocked yes, I tried to flash a couple of roms over the last few days, and then yesterday it didn't work. But this is first time I've heard of the UND thingie. Will that help? And how doI install this Naked driver?

DaffPower said:
I'm unlocked yes, I tried to flash a couple of roms over the last few days, and then yesterday it didn't work. But this is first time I've heard of the UND thingie. Will that help? And how doI install this Naked driver?
Click to expand...
Click to collapse
Look for the fastboot device in device manager and then when windows fails to find an updated driver, install these:
http://forum.xda-developers.com/showthread.php?t=2139767

there is no usb icon on boot screen, what is wrong ? driver?

marko.del said:
there is no usb icon on boot screen, what is wrong ? driver?
Click to expand...
Click to collapse
That means you are on a new 4.2 boot loader. Fastboot is automatically started when in this mode.
Sent from my unknown using xda app-developers app

Just wanted to say that after having this old transformer prime for years, and hanging on to it only because nobody else wanted it, I've given it new life! Thanks for all the work you have done, and now my tf201 is purring along wayyyy better than it ever did before!

elesbb said:
Uh oh..
no key driver means that your device is calling aliens to invade earth telling them that we have no key driver so we are all gonna be doomed!!! HOW COULD YOU DO SUCH A THING!?!?
Just kidding
Its normal. No need to worry. My tablet says it too. I think all of them do. I think thats what allows us to access fastboot. since there is no key driver, its pretty much allowing any device with fastboot to write to the tablet. Thats just my theory. But in the end, its normal and doesnt need to be worried about
Click to expand...
Click to collapse
Its normal ? Perhaps not. I had the same pb and lost the USB icon on this boot menu, with no possibility to install super user or to flash a ROM through ADB.
Using ADB as indicated by the tutos for the command "adb devices" no answer until, I read in the boot menu "fastboot" and tryed the command "fastboot devices" and received in the list of devices the id of my Asus tf201 after testing 'fastboot reboot bootloader" I could install what I want with the USB cable.

[Q] Padfone 2 bricked: invalid kernel

After a lot of reading on Xda and Modaco I am still not much further.
After rooting with Framaroot and installing TWRP through Goomanager I bricked my phone because I forgot to unlock the bootloader....
Is there any hope for this phone?
The phone cannot get into fastboot: power button + volume up.
Recovery menu (power button + volume down) is non-functional > I get the "invalid kernel" message again.
ADB and Fastboot and cmd in Windows are all very new to me but I have nothing to loose.
Thanks in advance for any advice.

"invalid kernel !!!" - I bricked my phone
Hello,
I have exactly the same problem... I've also red a lot without finding any suitable solution...
I rooted with Framaroot, installed TWRP and thats it - I bricked my phone (probably because I forgot to unlock the bootloader?)....
Same problem for me: the phone won't get into fastboot (Power+VolUp).
Recovery menu (Power+VolDown) doesn't work: I always get "invalid kernel !!!"

Hi Vakilando,
It seems we're on our own with this problem. Either no one has an answer or all knowledgeable people never had to deal with this problem.
We also choose a not-so-popular phone. The tablet-phone combi is too expensive and the tablet of mediocre specs.
I went for the too-good-to-be-true price for the phone-only... and after a lot of reading found out that quit a few people had problems with their phone.
Perhaps some code monkey (no disrespect) could tell me if we have more options when the phone is connected to a Linux system? Android is Linux based, so that would be a compatible pair. Windows can only see one partion on a flash card and, but I might be wrong, Windows cannot read EXT 3, 4 partitions.
Windows device manager does recognize the phone as "ASUS Android Bootloader Interface" so the phone is not completely non-responsive.
I also posted on a German site; Android-Hilfe where there's a dedicated forum with knowledgeable people so perhaps that gives more options.

do this!it will work!!!
gentle_giant said:
After a lot of reading on Xda and Modaco I am still not much further.
After rooting with Framaroot and installing TWRP through Goomanager I bricked my phone because I forgot to unlock the bootloader....
Is there any hope for this phone?
The phone cannot get into fastboot: power button + volume up.
Recovery menu (power button + volume down) is non-functional > I get the "invalid kernel" message again.
ADB and Fastboot and cmd in Windows are all very new to me but I have nothing to loose.
Thanks in advance for any advice.
Click to expand...
Click to collapse
jUst flash a cwm recovery with fastboot mod!it will work!my padfone 2 brick like this but now his alive

Sorry, for not well-advanced users - could you please describe step-by step how to flash phone in "invalid kernel" condition CWM recovery with fastboot? Tnanks!

Ola Goldenval, try this link, it worked for me.

This is first link I found in google & tried to follow. My problem is that PC (W7 ultimate) doesn't see the phone. So cmd window is hanging on message "waiting for device" forever. Problem isn't in PC, as I tried different PC, where another similar phone had been seen some time ago.

Hi Goldenval,
the onlything I can tell you is that it didn't work out for me the first time, just like you now. Then I found another, German, website with lots of information on the subject and I gave it another try. Second time I succeeded...
it is a long time since it happened so I can't recall all the details but keep on trying and you will succed.

Update
Instruction here : w.w.w.modaco.com/topic/365818-padfone-2-invalid-kernel/
If You upgrade to kitkat and bricked you phone .You have to download latest
update h.t.t.p://dlcdnet.asus.com/pub/ASUS/Mobile_Phone/PadFone2/WWE_PadFone2_user_11_8_4_12_UpdateLauncher.zip unzip and rename with instruction. Help for me
I can't put outside link I am under 10 posts .

Download last usb driver for padfone 2 and then u will see cmd work properly

Hi all,
sorry to resurrect this thread, but I have the same problem and cannot solve it.
I followed the instructions in modaco.com but no luck.
My phone keep rebooting with the Invalid Kernel...

First Time ROM Attempt - Stuck at Recovery Install / Root

[UPDATE - SOLVED - It was the USB cable. Tried another cable in another USB port on my PC, everything came up roses!]
Hi Everyone, I"ve been following XDA since I got my A700 in late 2012 and have finally decided to attempt rooting and flashing. I wanted to try something based on CM11, like the Omni, PacMan or base Cyanogen ROMs located here. I appreciate your patience with my noobness, I haven't programmed anything since my VB6/VBA days and that was a good decade ago!
First I tried the methods located here:
http://forum.xda-developers.com/showthread.php?t=1984566
Note that I have owned the tab for almost two years and have not modified it in any way. I did a full reset and wipe through Android in preparation for this.
I did get as far as unlocking the bootloader. However, when I attempted to install the recovery at this command:
fastboot flash recovery recovery.img
the tablet reboots and the text in the upper left blinks:
Bootloader vJB-XXXX(Unlock Mode): Starting Fastboot USB download protocol
And stops there. In my cmd window it mentions that it is flashing my recovery.img and the file size, but stops there. I am able to power off and reboot, at which point the cmd window says that it has failed to send the .img with this message:
FAILED (data transfer failure (Too many links))
finished. total time: XXXX s
Update: Another attempt gets be the following message:
FAILED (data transfer failure (Unknown error))
Do you have to root it first? I have since tried the Vorbeth Easyroot from here:
http://forum.xda-developers.com/showthread.php?t=1953917
And it still hangs at the same USB Download Protocol message above, also unable to send the boot.img to the tab.
I will try wiping and rebooting the tab again next. I have downloaded the Adnroid SDK and installed the Eclipse add-on as instructed.
Update: I've wiped again (though it still seems to stay in Unlock Mode) and tried the Root again, same results.
Any thoughts? Thanks in advance from an old-timer!
Mark

Impromark said:
Hi Everyone, I"ve been following XDA since I got my A700 in late 2012 and have finally decided to attempt rooting and flashing. I wanted to try something based on CM11, like the Omni, PacMan or base Cyanogen ROMs located here. I appreciate your patience with my noobness, I haven't programmed anything since my VB6/VBA days and that was a good decade ago!
First I tried the methods located here:
http://forum.xda-developers.com/showthread.php?t=1984566
Note that I have owned the tab for almost two years and have not modified it in any way. I did a full reset and wipe through Android in preparation for this.
I did get as far as unlocking the bootloader. However, when I attempted to install the recovery at this command:
fastboot flash recovery recovery.img
the tablet reboots and the text in the upper left blinks:
Bootloader vJB-XXXX(Unlock Mode): Starting Fastboot USB download protocol
And stops there. In my cmd window it mentions that it is flashing my recovery.img and the file size, but stops there. I am able to power off and reboot, at which point the cmd window says that it has failed to send the .img with this message:
FAILED (data transfer failure (Too many links))
finished. total time: XXXX s
Update: Another attempt gets be the following message:
FAILED (data transfer failure (Unknown error))
Do you have to root it first? I have since tried the Vorbeth Easyroot from here:
http://forum.xda-developers.com/showthread.php?t=1953917
And it still hangs at the same USB Download Protocol message above, also unable to send the boot.img to the tab.
I will try wiping and rebooting the tab again next. I have downloaded the Adnroid SDK and installed the Eclipse add-on as instructed.
Update: I've wiped again (though it still seems to stay in Unlock Mode) and tried the Root again, same results.
Any thoughts? Thanks in advance from an old-timer!
Mark
Click to expand...
Click to collapse
It should be a pretty straightforward process. Let's make sure you're doing it in order.
1) Turn on USB Debugging in your tabs Settings/development options
2) Plug in the tab to the PC
3) In the folder where you have the custom recovery.img, open a CMD window
4) Type adb devices and hit ENTER (should see a device listed, not offline)
5) Type adb reboot bootloader and hit ENTER (should reboot to the bootloader)
6) Type fastboot flash recovery recovery.img and hit ENTER (should go to download mode and transfer file)
Some things you might try;
Fresh boot your PC
Use a different USB port on the PC
Use a different USB cable
Use a win 7 pc, win 8 is ok, but win 8.1 can be a bit wonky
Now, some info for you. If you plan on installing a KitKat (4.4.x) rom, you will need to use a newer adb.exe file after installation. The older one won't work anymore. You can usually find the small package in some of the newer device forums that use Android 4.4.x. That's what I did. Generally you can find the small packages that contain adb.exe, fastboot.exe and the 4 or 5 .dll files. I think I snagged mine from a Samsung forum. But this is only after you get the 4.4.x ROM installed.
Also, make sure your recovery matches your Android version ROM you are using. If ICS, use an ICS recovery. If JB, use a JB based recovery, if Kit Kat 4.4.x, use the newest recovery. I believe the newest TWRP works well with KitKat ROMs.
You do not need to install the Android SDK. For what you are doing, you only need the small package. My and Vorbeths "Easy Root" threads have the necessary files for JB based roms, and also contain a compatible JB based recovery. But vorbeths download links are probably bad if I recall.
As for rooting, it's always best to root it first. This can be done with a modified boot.img and superuser, but I don't think it's necessary.
Hope this helps.

That's fantastic MD, thanks for this! I'll try it over the next couple days (it's Canadian Thanksgiving, don'cha know) and report back. At the end of it, I hope to post some step-by-steps for newbies such as myself to go straight to a KK ROM, which is my ultimate goal.
Mark

Update - the problem was the USB cable. I had no idea that this could be a factor, as I had been using the same cable to transfer files to the tab all this time and it accepted my commands to unlock the bootloader just fine. Once I swapped out the .99 eBay cable for the nice thick one that came with my LG G-Pad 8.3 (which should be telling, really), everything was fine and I was able to root, flash CWM and then a ROM without issues.
Note that in my case I didn't need to update the ADB.exe file, the one I had downloaded was from 6/14/2014 and while I'm not at all sure where it comes into play, I had no problems flashing and using a Kitkat ROM.
Currently on the PacMan ROM, and it's like having a new tablet to play with, albeit with half the RAM I'm used to on my other tablet, and the ever-so-annoying touch response problems that came with the A700. Will be trying the Omni, CM11 nightly and others in due course.
Thanks again MD for the assist!
Mark

[Q] One Mini Update Utility fail at 95% (log attached)

Hello to all.
My first post was about One mini with unlocked bootloader and failed system. Situation changed so I describe all "story" wondering that sb clever would tell me what to do now...
At the beginning, I visited some "specialist", who applied me a fantasy about bootloader rebuilding and took cash for nothing. Because thay said that tried to flash European ROM on device bought in USA with ATT brand and S ON (look attach) I had to learn a little to do anything by myself.
First of all I flashed TWRP Recovery using AllinOne. First CMD window replied "device not found" but second one responded that Recovery was flashed succesfully. In fact TWRP run. And it was all.
Than I tried to do anything by ADB. Drivers were installed correctly but any command form adb responded "device not found"
Device manager showed QHSUSB DLOAD when connected not powered one mini. (Yes I know what it means)
Sideload in TWRP was not working too.
Flashing wih USB OTG mounted under TWRP was not working too.
Newest RUU_M4_UL_K44_SENSE60_MR_Cingular_US_4.13.502.3_ from htc site (.htc.com / us / support / htc-one-mini-att / news / ) was showing connection error at the beginngin but was detecting system version and suggested update. Always failed after reboot.
Today I tried to flash RUU.zip (ver same as installed on my bricked one mini). AllinOne asked about Bootloader lock so I relocked bootloader. Flashing failed so I started mentioned newest original RUU from HTC. Bootloader was rebooted and procedure started. (with unlocked bootloader it failed at this moment) Unfortunaelly it stopped at 95% with comunicate "signature error".
Cell restarted, htc logo appeared ("by android" sign was added) and device manager detected HTC device and mass memory. Unfortunetelly system havent boot up and now manager shows only "not recognized device" but QHSUSB DLOAD not appeared again
What would you advice to do now? Try to update again? When you check Fastboot reply at CMD screenshot than it seems to be ALMOST updated. But still sth is wrong
I read RUU log and edited fonts colour to make it more readable.
I can see that all time ADB has a problem with "adb devices" command and it asks fastboot (i coloured it on pink).
Later it flash two almost 400MB each zip files but after second one gives signature fail. If Update comes from HTC and almost all update was correct what may it mean now?
I attach
1 image with bootloader details when bought broken
2 image of ADB fastboot report after 95% Update to 4.13.502
3 log from Updater

[Completed] How do I fix my boot verified failed error on Acer A500?

I was recently trying to update my Acer Iconia A500 and it appears I made a mistake...I had my tablet rooted and I was using the Acer recovery tool to try to use cwm to update. I was running stock OTA ICS. Acer recovery tool warned that my bootloader should be updated to version 1.03 (Acer recovery tool said I had 0.03.12-ICS). I was trying to update the bootloader and initiated a reboot and I haven't been able to boot since. When I try to boot, I see "boot verified failed...". I've tried several fixes from what I've found searching. The hard reset with power/volume/screen lock does not work and I still see the boot verified failed. I tried copying every version of update.zip I could find to a microsd card and booting by holding power+volume down - same result. If I boot by holding power+volume down+screen lock I get a message saying "bootloader: v.03.12-ICS: Starting Fastboot USB download protocol", but nothing happens. If I plug the tablet into my computer in this state, it makes a noise recognizing a connected device, but I cannot view the drives (drivers are current) - also in this same state if I use the list devices command in adb fastboot no device is displayed.
Any feedback or advice would be greatly appreciated. I'm not experienced and I am simply trying to piece together information from various sources. Normal solutions would be hard reset or booting with update.zip, but neither are working.

XDA Visitor said:
I was recently trying to update my Acer Iconia A500 and it appears I made a mistake...I had my tablet rooted and I was using the Acer recovery tool to try to use cwm to update. I was running stock OTA ICS. Acer recovery tool warned that my bootloader should be updated to version 1.03 (Acer recovery tool said I had 0.03.12-ICS). I was trying to update the bootloader and initiated a reboot and I haven't been able to boot since. When I try to boot, I see "boot verified failed...". I've tried several fixes from what I've found searching. The hard reset with power/volume/screen lock does not work and I still see the boot verified failed. I tried copying every version of update.zip I could find to a microsd card and booting by holding power+volume down - same result. If I boot by holding power+volume down+screen lock I get a message saying "bootloader: v.03.12-ICS: Starting Fastboot USB download protocol", but nothing happens. If I plug the tablet into my computer in this state, it makes a noise recognizing a connected device, but I cannot view the drives (drivers are current) - also in this same state if I use the list devices command in adb fastboot no device is displayed.
Any feedback or advice would be greatly appreciated. I'm not experienced and I am simply trying to piece together information from various sources. Normal solutions would be hard reset or booting with update.zip, but neither are working.
Click to expand...
Click to collapse
Hard/factory reset would have been my first answer too.
Is your issue similar to this one: Boot verified failed after update PLEADE HELP?
Maybe you can unbrick it like described here: [GUIDE] How to unbrick Acer Iconia A500.
And if you need further help, please register on xda and ask in the thread directly.
Good luck !

Thread closed. Thank you!