I just got my new asus transformer tf300t-bl and wanted to root and install either twrp or cwm on it,I unlocked it and when i went to reboot it i hit the volume up on the RCK and now its stuck on RCK and it didnt boot into the usb like it says it will on the forums. Now when i reboot it,it says " key driver not found.. booting os android cardhu-user bootloader < 1.00 e> released by "us_epad-10.6.1.8-20130225" a03 starting Fastboot usb download protocol. does anyone know what i can do? i would greatly appreciate ANYONES HELP THAT KNOWS IF THEY'VE DONE THIS TO THEIRS AND IF THIS IS FIXABLE. I USE THIS FOR COLLEGE AND JUST PAID $ 400 and cant afford to buy another one. Somebody please tell me i havent screwed the pooch and that it still can be flashed into recovery and rooted. Thanks you guys. As i rooted and flashed my transform ultra perfectly because of you guys and used the megatron 6 and love it.
No you haven't you need to download fastboot and connect the tablet to your computer, on that screen just let it sit their.
Download the asus firmware. Follow the flashing fastboot guides here. You need to flash the blob file.
flashing recovery/ ref: help me
sevenalive said:
No you haven't you need to download fastboot and connect the tablet to your computer, on that screen just let it sit their.
Download the asus firmware. Follow the flashing fastboot guides here. You need to flash the blob file.
Click to expand...
Click to collapse
im a lil new to doing this so would you please give me a detailed list of exactly what to do. and what firmware do i need to download from asus. And can all of this be done using a mac? and how do i flash it all to my comp. or from it to the tablet.
It should help you :https://www.google.pl/webhp?sourcei....r_qf.&bvm=bv.43828540,d.ZWU&biw=1274&bih=856
need your help plz
Hazard17 said:
It should help you :https://www.google.pl/webhp?sourcei....r_qf.&bvm=bv.43828540,d.ZWU&biw=1274&bih=856
Click to expand...
Click to collapse
i did everything it stated to do and when i get to the last steps to root my tf300t, it says adb cannot run as root in production builds. Im at a loss as to what to do at all. IM a noob, and i follow each command on terminal perfectly and everything executes till the last or itll say permission denied. What do i do or am i doing wrong. Im following the instructions of post forum.xda-developers.com/showthread.php?t=1720980
Hi, I have the exact same error message after installing the latest firmware from asus (ww_epad-10.6.1.8-20130225) and flashing cwm recovery.
Flashing via fastboot works fine and I have already reflashed the blob file and reflashed cwm recovery. still the same issue: "Key driver not found" and upon chosing entering RCK it freezes. OS boots fine, no issue here. Any clues? Should I flash the stock kernel from Asus?
re: help me
philmg said:
Hi, I have the exact same error message after installing the latest firmware from asus (ww_epad-10.6.1.8-20130225) and flashing cwm recovery.
Flashing via fastboot works fine and I have already reflashed the blob file and reflashed cwm recovery. still the same issue: "Key driver not found" and upon chosing entering RCK it freezes. OS boots fine, no issue here. Any clues? Should I flash the stock kernel from Asus?
Click to expand...
Click to collapse
how did you flash fastboot and cwm and reflashed the blob files to your asus? on my terminal on my mac itll say cant execute root on production models and requests a password. Have you had the same problems? can u give me a step by step how u flashed cwm and fastboot and the blob files. and how did you install the latest firmware
420Misfit said:
how did you flash fastboot and cwm and reflashed the blob files to your asus? on my terminal on my mac itll say cant execute root on production models and requests a password. Have you had the same problems? can u give me a step by step how u flashed cwm and fastboot and the blob files. and how did you install the latest firmware
Click to expand...
Click to collapse
well, I am using a win xp machine for fastboot. so I don't have the same issues. fastboot works fine, so that I use the normal fastboot process to flash the system and the recovery kernel.
I finally got it to work again by flashing the newest TWRP instead of CWM. It seems CWM does not yet work on the latest firmware.
I followed this guide for flashing TWRP with fastboot. This version actually also just asked me, if I want to root the device, I clicked yes and it was rooted. Perfect.
http://forum.xda-developers.com/showthread.php?t=2187982
philmg said:
Hi, I have the exact same error message after installing the latest firmware from asus (ww_epad-10.6.1.8-20130225) and flashing cwm recovery.
Flashing via fastboot works fine and I have already reflashed the blob file and reflashed cwm recovery. still the same issue: "Key driver not found" and upon chosing entering RCK it freezes. OS boots fine, no issue here. Any clues? Should I flash the stock kernel from Asus?
Click to expand...
Click to collapse
I am in EXACTLY the same boat as you. The only difference is that I flashed TWRP instead of CWM. I finally decided that it was time to root my tablet...got tired of the lag. IIRC I've gotten the "key driver not found.. booting OS" error message since doing the OTA update to 4.2 (I did this prior to rooting.) Everything SEEMS to be working okay, but this bugs the heck outta me, and I'm sure it can't be a good thing. Hoping somebody will chime in with a fix for this. I've searched and searched to no avail.
First time post and it's been a hell of a day. I need to figure out how to either sideload the factory ROM, load a 3rd party ROM, or actually factory reset my phone to stock.
I unlocked my bootloader and installed TWRP and SuperSU earlier in the day. I then wanted to try to load Cyanogen11, but there were issues with the load, it constantly failed. I made a backup before I did this, but when I attempted to load the backup, nothing happened, it would just continually boot to recovery.
I attempted a few other things, clearing caches, doing wipes, powering the phone off for 5~ minutes, etc. etc.
Nothing is working, I can't load any ROM now and phone is either stuck at a bootcycle or the HTC Splash screen (Aside from being able to load bootloader/CWP)
jdolbeer said:
First time post and it's been a hell of a day. I need to figure out how to either sideload the factory ROM, load a 3rd party ROM, or actually factory reset my phone to stock.
I unlocked my bootloader and installed TWRP and SuperSU earlier in the day. I then wanted to try to load Cyanogen11, but there were issues with the load, it constantly failed. I made a backup before I did this, but when I attempted to load the backup, nothing happened, it would just continually boot to recovery.
I attempted a few other things, clearing caches, doing wipes, powering the phone off for 5~ minutes, etc. etc.
Nothing is working, I can't load any ROM now and phone is either stuck at a bootcycle or the HTC Splash screen (Aside from being able to load bootloader/CWP)
Click to expand...
Click to collapse
Are you still having issues? If so, PM me and I'll help you out.....
Got everything sorted with the great help of Nelvin. I had previously gone to the twrp support IRC and after answering a few questions, they just stopped talking... Glad there are people out there still willing to help! He spent a good hour or so with me making sure everything was working.
Hey you two!
Did you solve your problem via PM, then maybe send me the log of it please.
I dont know exactly if we have the same problem, but i'll try to explain mine:
I wanted to put a ROM on my mini, because it is branded.
I unlocked the bootloader on the htc one mini and then put the twrp recovery on it. It seems to work.
Next i wanted to put super su on it, but I'm already stuck in a bootcircle, so i cant put any files onto the phone. I tried to move files with Qick ADB Pusher, but always when I try to send the file from PC(win7) to one mini it says "Opeartion Failed! Exit Code 1". I tried this when i was in Bootloader. When I am in Recovery ADB doesnt even recognize the phone via USB.
If there is more explanation needed, please feel free to ask.
Thank you for your help in advance!
Greetins,
just2lose.
just2lose said:
Hey you two!
Did you solve your problem via PM, then maybe send me the log of it please.
I dont know exactly if we have the same problem, but i'll try to explain mine:
I wanted to put a ROM on my mini, because it is branded.
I unlocked the bootloader on the htc one mini and then put the twrp recovery on it. It seems to work.
Next i wanted to put super su on it, but I'm already stuck in a bootcircle, so i cant put any files onto the phone. I tried to move files with Qick ADB Pusher, but always when I try to send the file from PC(win7) to one mini it says "Opeartion Failed! Exit Code 1". I tried this when i was in Bootloader. When I am in Recovery ADB doesnt even recognize the phone via USB.
If there is more explanation needed, please feel free to ask.
Thank you for your help in advance!
Greetins,
just2lose.
Click to expand...
Click to collapse
Hi, can you let me know: Which ROM you want to flash, if you have attempted to s-off, and that you can boot to recovery?
Also, i'd advise against using utilities like the "pusher", please download this http://d-h.st/qmi and create a directory called c:\adb\ - move your ROM and SuperSU zip files here and extract the adb_windows.zip file to the directory.....
I did not attempt s-off, just normal htc dev bootloader.
First i wanted to flash Magio R4, but then i was thinking about Stock Rom Sense 5.5, which tr1gg3r84 uploaded.
i created folder and moved rom there. i also extracted the adb_windows zip there. what to do next? (i just wanna ask, because im a little scared of totaly breaking the phone now)
Thanks for now!
just2lose said:
I did not attempt s-off, just normal htc dev bootloader.
First i wanted to flash Magio R4, but then i was thinking about Stock Rom Sense 5.5, which tr1gg3r84 uploaded.
i created folder and moved rom there. i also extracted the adb_windows zip there. what to do next? (i just wanna ask, because im a little scared of totaly breaking the phone now)
Thanks for now!
Click to expand...
Click to collapse
Boot to recovery, then
adb push therom.zip /sdcard/
adb push UPDATE-SuperSU.zip /sdcard/
Remember to extract the boot.img from the ROM zip file, and after flashing the ROM and SuperSU, boot to bootloader and FASTBOOT menu then:
fastboot flash boot boot.img
you mean to push with the quick ADB Pusher? but in this programm (on PC) it doesnt find the phone whilie it is is recovery boot.
just2lose said:
you mean to push with the quick ADB Pusher? but in this programm (on PC) it doesnt find the phone whilie it is is recovery boot.
Click to expand...
Click to collapse
No, use the adb binary from the download link I posted......
If your phone isn't found, check the windows device manager and verify that you have ADB Android device listed..... if not, download adb drivers for windows and install - then plug your phone back in.....
You are using TWRP 2.6.0.0 recovery image from here right? http://forum.xda-developers.com/showthread.php?t=2418938
the adb.exe just pops up the cmd console, showing a lot of commands for half a second and then its gone again.
the android device is listed on device manager.
no, i did not use this one(twrp). i used some explanation how to do it from another forum and another file.
should i use this one now? how exactly to do that? theres no explanation :/
Open a command prompt in Windows and cd to c:\adb
Then when your phone is in recovery, type the adb commands I posted earlier.....
Sent from my HTC One mini using XDA Premium 4 mobile app
terdingb all
cmd says that the command is wrong or misstyped
(im in c:/adb typing: adb push rom.zip /sdcard/)
Is your ROM zip file called rom.zip? Can you post a screenshot?
Sent from my HTC One mini using XDA Premium 4 mobile app
ok got it.
now the rom and the supersu.zip are on the phone.
i cleared cache and dalvik and flashed both files(Stock Sense 5.5 4.3 Rooted Odex/Deodex;UPDATE-SuperSU-v1.86; both zip files) and , after that i went into fastboot and tried (fastboot folder) "fastboot flash boot boot.img" but cmd only says "waiting for device"
just2lose said:
ok got it.
now the rom and the supersu.zip are on the phone.
i cleared cache and dalvik and flashed both files(Stock Sense 5.5 4.3 Rooted Odex/Deodex;UPDATE-SuperSU-v1.86; both zip files) and , after that i went into fastboot and tried (fastboot folder) "fastboot flash boot boot.img" but cmd only says "waiting for device"
Click to expand...
Click to collapse
Check device manager on your pc, most likely the adb driver device isn't listed - if not, reboot your pc and try again.... This has happened to me several times......
ok now it worked. writing boot and so on .. finished. total time: 2.717.
i shut it down and started the phone again.
now it almost made the starting sound. after 5 boot cycles it played the whole starting sound and also showed the second screen with the "o1ne" and "beatsaudio" on the bottom.
but thats it. boot cycling in a different way now .
seems like it just doesnt want to work.
i'm so sorry that I am bothering you for so long now..
another idea?
thanks again!
edit: im gonna go through everything again with magio rom r5...
ok got it now. thanks a lot dude!
i deleted the rom files now from the phone but still there is 9gb used on the phone. this is way to much, isnt it?
is there a safe method to clean the whole phone .. something like c:format ?
thanks ³
No problem dood.....
Download an app called diskusage from the store - start it and choose storage card.... Post a screenshot please!
Sent via a weather balloon towed by a flock of seagulls. That's how this messaging stuff works, right?
after the phone went out of battery, it was in a boot cycle again after loading and rebooting.
flashed super su.zip again, but it didnt help. stupid me didnt do a backup yet. so do i have to install the rom again and do all the configs from scretch?
What's your hboot status? Locked/unlocked, s-on/s-off etc
Also, did you do, or install anything before your phone powered off?
Sent from my HTC One mini using XDA Premium 4 mobile app
Hey guy's only wanted to do a factory reset but I idiot just wiped everything...
So nothing was anymore on it. I downloaded this file:
OTA_M4_UL_K44_SENSE60_MR_HTC_Europe_4.09.401.3-3.10.401
As I have 4.09.401, CID-HTC__102...
So I was very lost and extracted firmware.zip out of it and flashed it over "fastboot oem rebootRUU" - "fastboot flash zip firmware.zip"
It is also now "Relocked" with S-OFF....
I'm stuck, I need my phone the next few days very often...
I dont know what to do anymore if I try to do the same with the OTA zip file it says FAILED (remote: 24 parsing android-info fail)
(When I tried before with TWRP ADB Sideload before I flashed the firmware.zip, it told me "file_getprop failed to stat /system/build.prop"
What can I do now to get my phone working again
Which version of hboot?
Which version of TWRP?
Are you able to connect to your phone via fastboot?
Are you able to connect to your phone via adb (from within TWRP)?
jollywhitefoot said:
Which version of hboot?
Which version of TWRP?
Are you able to connect to your phone via fastboot?
Are you able to connect to your phone via adb (from within TWRP)?
Click to expand...
Click to collapse
- HBOOT 2.22.000
- openrecovery-twrp-2.7.1.0-m4.img (It's the only version where I even can see my devices with "adb devices")
- Yes I am
- Not really I can go with ADB Sideload but using "adb sideload" does not work...
It tells me:
sending: 'rom.zip' 100%
On my phone it's saved under /data/media/sideload.zip but it tells me:
file_getprop: failed to stat "/system/build.prop": No such file or directory
E: Error executing updater binary in zip '/data/media/sideload.zip'
Click to expand...
Click to collapse
I had a similar issue. Adb only seemed to work on older version of twrp, except in reality, it wasn't working at all. First thing you need to do is get adb working fully to where you can push a Rom to your phone. The problem is likely your Windows drivers and not your phone, so quit trying to flash firmware to fix your phone. For me, I installed a clean copy of Windows xp on an old computer and then set fastboot and Adb up on it. I've also gotten adb and fastboot working using ubuntu live CD. I'll try and find instructions for that method (it's super easy and will run on your CD drive, so you don't need to format hd out install anything).
Once adb works, you can just push any sense6 Rom and then install in twrp and you'll be good to go.
Edit: read posts 17 & 22 here for information on getting ubuntu live CD to work.
http://forum.xda-developers.com/htc-one-mini/help/help-urgent-os-recovery-t2859034/page2
jollywhitefoot said:
I had a similar issue. Adb only seemed to work on older version of twrp, except in reality, it wasn't working at all. First thing you need to do is get adb working fully to where you can push a Rom to your phone. The problem is likely your Windows drivers and not your phone, so quit trying to flash firmware to fix your phone. For me, I installed a clean copy of Windows xp on an old computer and then set fastboot and Adb up on it. I've also gotten adb and fastboot working using ubuntu live CD. I'll try and find instructions for that method (it's super easy and will run on your CD drive, so you don't need to format hd out install anything).
Once adb works, you can just push any sense6 Rom and then install in twrp and you'll be good to go.
Edit: read posts 17 & 22 here for information on getting ubuntu live CD to work.
http://forum.xda-developers.com/htc-one-mini/help/help-urgent-os-recovery-t2859034/page2
Click to expand...
Click to collapse
The problem is that I cant install the ROM.
I've push'ed it do the ROM but as you can see my post above TWRP only gives me error :/
LuvMyHTC21 said:
Hey guy's only wanted to do a factory reset but I idiot just wiped everything...
So nothing was anymore on it. I downloaded this file:
OTA_M4_UL_K44_SENSE60_MR_HTC_Europe_4.09.401.3-3.10.401
As I have 4.09.401, CID-HTC__102...
So I was very lost and extracted firmware.zip out of it and flashed it over "fastboot oem rebootRUU" - "fastboot flash zip firmware.zip"
It is also now "Relocked" with S-OFF....
Click to expand...
Click to collapse
just try to flash not OTA, but ROM
version 2 from here will be Ok
Sweet Jesus, finally after 9 hours (no joke) I got it working, thank you so much !
Hi,
I have a problem with my r7plusf.
I tried to install lineageOs, with the CM recovery I just got a "zip signature verification" problem. To avoid this problem i flashed TWRP and tried installing it without checking the zip signature. When doing that i got a "table error".
I try to reflash back the rom I had and now I am in trouble :
when i flash it it boots on TWRP instead of the rom.
I tried installing the colorOs recovery and it did not work (I just saw a message telling me "formating data and cache")
/*And now twrp is always telling me "can't mount /data".*/
I resolved this problem by formating the data partition
Does anyone know what i can do to reuse my phone?
Thank you by advance for all the help you could give me.
Little update :
I tried to build lineageOS by hand with this link : https://wiki.lineageos.org/r7plus_build.html to see if there was the cyanogenmod/lineage recovery included but when I try to brunch, I just get this error :
Code:
"ninja: error: '/home/user/android/system/out/target/product/r7plus/obj_arm/SHARED_LIBRARIES/libtime_genoff_intermediates/export_includes', needed by '/home/user/android/system/out/target/product/r7plus/obj_arm/SHARED_LIBRARIES/libandroid_servers_intermediates/import_includes', missing and no known rule to make it"
After looking at the files I just saw that the folder named "obj_arm" does not exists. For info Iam on archlinux whith linux kernel version 4.9.6-1 and I have GCC 6.3.1 .
Does anyone know how to solve this bug or has anyone got the cyanogenmod recovery?
UPDATE : I tried with the cyanogenmod recovery that someone gave to me and it didn't work either, the phone still boots on the recovery. I don't have anymore ideas anymore
Some one oppo forum just gave me the way to save my phone, i just had to boot in fastboot mode, plug the phone in my computer, open a command prompt and type the command "fastboot continue", everything just work fine now.
f22217 said:
Some one oppo forum just gave me the way to save my phone, i just had to boot in fastboot mode, plug the phone in my computer, open a command prompt and type the command "fastboot continue", everything just work fine now.
Click to expand...
Click to collapse
That just helped med A LOT
Hey. Following issue: I used to have my phone rooted and wanted to update it. Since I couldn't get a zip file from the official OnePlus webpage I used the download button from the system update and got it from there. Of course it also automatically removes your root so I had to try to flash twrp again. My bootloader is still unlocked (debugging and oem both activated) so that wasn't any issue. I got the newest enchilada and tried the flash boot command with the twrp enchilada image, however after a short message including hoot and and an ok at the end my phone goes into the fastboot icon and is stuck there until I restart it. Twrp doesn't start whatsoever. I also tried the fastboot --set-active= command but that didn't help as well. Adb is also on the newest version and I also got the newest enchilada. Any ideas?
P.S: already searched a lot on the forum but none of the aforementioned solutions did anything thanks for any help regardlessly
Gosick1337 said:
Hey. Following issue: I used to have my phone rooted and wanted to update it. Since I couldn't get a zip file from the official OnePlus webpage I used the download button from the system update and got it from there. Of course it also automatically removes your root so I had to try to flash twrp again. My bootloader is still unlocked (debugging and oem both activated) so that wasn't any issue. I got the newest enchilada and tried the flash boot command with the twrp enchilada image, however after a short message including hoot and and an ok at the end my phone goes into the fastboot icon and is stuck there until I restart it. Twrp doesn't start whatsoever. I also tried the fastboot --set-active= command but that didn't help as well. Adb is also on the newest version and I also got the newest enchilada. Any ideas?
P.S: already searched a lot on the forum but none of the aforementioned solutions did anything thanks for any help regardlessly
Click to expand...
Click to collapse
What version rom is currently installed
MrSteelX said:
What version rom is currently installed
Click to expand...
Click to collapse
Oxygenos 10.3.0 on my oneplus6.
https://forum.xda-developers.com/on...overy-unofficial-twrp-touch-recovery-t3860815 has everything you need to install twrp