Database Info

[Q] ***HELP*** Bricked..Stuck in Boot Loop**

So here is what I did... Last night i successfully unlocked my bootloader on my AT&T HTC Onc X and established root. I was running the AT&T RUU_Evita_UL_Cingular_US-1.82.502. I then tried to update this morning to AT&T RUU_Evita_UL_Cingular_US-1.85.502(desktop installer type) it kept giving me errors and would not complete. Like an idiot i tried to flash CleanROM 2.0 -★| 1.85.502.3 | Tweaked! | Stable! | CWM Install! through CWM and it installed successfully but my WIFI would not work at all. So i decided to reload CleanROM DE 1.0 -★| which had worked fin in the past. At the end of the installer it said to do a factory reset and I did. After the reboot is where i noticed my problem. I am stuck on the boot animation screen. Not able to get into the phone at all now. I am able to get back to the bootloader menu.. boot into CWM but unable to reflash the room on the sdcard. It will not mount USB storage. None of the stock desktop installer will recognize my device is plugged in....... ANY SUGGETIONS...or am I screwed....

Is it in a boot loop or is it frozen on the HTC One screen? That happened to me last night but I was able to run the RUU installer. Did you make sure HTC Sync wasn't running, and that you killed adb by using adb kill-server before trying the RUU installer?
Apologies if you've done these things already, I'm just grasping at straws here.
If you can do adb reboot bootloader, you should be able to run the RUU installer from there, no?

it does not show the ONE X boot screen. Its shows i guess what is known as the Galaxy Nexus boot screen that just flashes the colorful boxes over and over the longest i let it go for was like 20 minutes. The RUU installer you talk about, is that the one that you run from ur desktop. If so how do i get it to recognize my device is even plugged in. I have tried it while it is on the boot animation screen and from the bootloader menu. At this point it just seems like I dont have a way to get my computer to detect my device is plugged in. Is there a way to do that from the Bootloader menu?

taterdog2 said:
it does not show the ONE X boot screen. Its shows i guess what is known as the Galaxy Nexus boot screen that just flashes the colorful boxes over and over the longest i let it go for was like 20 minutes. The RUU installer you talk about, is that the one that you run from ur desktop. If so how do i get it to recognize my device is even plugged in. I have tried it while it is on the boot animation screen and from the bootloader menu. At this point it just seems like I dont have a way to get my computer to detect my device is plugged in. Is there a way to do that from the Bootloader menu?
Click to expand...
Click to collapse
If you have adb on your computer (from the Android SDK) and the drivers installed, you should be able to access the device from fastboot (bootloader). RUU will work if you can get your device into fastboot. I'm doing it right now (I wanted to try it before telling you).
Just remember, if you were on an unlocked 1.82 when you borked it, you need to be locked again before you can use RUU. Just use fastboot oem lock from the command prompt.

If you can get to the bootloader screen you are not bricked. Why can't you run the RUU like normal from there? Just re-lock your bootloader first.
Poster above beat me to it while I was taking forever to post.

1. Hold down your Volume Down Button and your power button
2. Wait for the device to turn off and keep holding the combination until you boot into the bootloader (It might take a couple tries, don't give up)
3. Plug your device into your computer via the OEM USB Cable
4. Use the Volume Up/Down keys and the Power button to select the Fastboot Option
5. Wait till the device is recognized (The text on screen where it said Fastboot should become Fastboot USB)
6. Go to the folder where you have fastboot installed and type:
fastboot oem lock
7. Go back to the bootloader and into fastboot when its done with relocking. Make sure the text on the top of the screen says "Relocked" or "Locked" (under the Tampered flag)
8. Run the RUU while in fastboot mode. Use version 1.85.

I sorry for being a NOOB... step 6. Go to the folder where you have fastboot installed and type:
fastboot oem lock...
when you refer to "having fastboot installed" I am taking it that you are not refering to the RUU installer... where do I get this FASTBOOT file from to install?

I think I figured it out... will let yall know in a few minutes

I looks to be that the 1.85 RUU is flashing properly... do I use the same method that I originally used to unlock the bootloader again?

taterdog2 said:
I looks to be that the 1.85 RUU is flashing properly... do I use the same method that I originally used to unlock the bootloader again?
Click to expand...
Click to collapse
Yes. You may need another unlock code. I did, but other people didn't. They just tried several times until it worked.

jmattp said:
Yes. You may need another unlock code. I did, but other people didn't. They just tried several times until it worked.
Click to expand...
Click to collapse
how u get unlock code again....i believe htcdev asking token right...? how do i get token back...? last time i try before one click came up device not found....kinda mess up my adb...? any link to re DL adb or android sdk platform tool again...thanks in ADV

ted77usa said:
how u get unlock code again....i believe htcdev asking token right...? how do i get token back...? last time i try before one click came up device not found....kinda mess up my adb...? any link to re DL adb or android sdk platform tool again...thanks in ADV
Click to expand...
Click to collapse
If you got device not found, you might not have USB Debugging enabled.
I don't think it's possible for something to "mess up" adb. For the Android SDK, just Google it.
When you run the one click CID tool again, just go through it all the exact way you did the first time.
I just spend about four hours on here answering questions and uploading mods. I'm going to take a shower and enjoy the rest of my Saturday. Good luck.

jmattp said:
If you got device not found, you might not have USB Debugging enabled.
I don't think it's possible for something to "mess up" adb. For the Android SDK, just Google it.
When you run the one click CID tool again, just go through it all the exact way you did the first time.
I just spend about four hours on here answering questions and uploading mods. I'm going to take a shower and enjoy the rest of my Saturday. Good luck.
Click to expand...
Click to collapse
so one click unlock bootloader tool work on 1.85 base from designgears that post by Kpenn.....? did u trying using that also...? ENJOY YOUR SAT....HAVE A NICE LONG WEEKEND....HAPPY MEMORIAL DAY...

ted77usa said:
so one click unlock bootloader tool work on 1.85 base from designgears that post by Kpenn.....? did u trying using that also...? ENJOY YOUR SAT....HAVE A NICE LONG WEEKEND....HAPPY MEMORIAL DAY...
Click to expand...
Click to collapse
I think as long as you're relocked, not factory locked (meaning, you unlocked 1.82 and then locked it again) you should be able to use the one click tool again. That's how I did it.

jmattp said:
I think as long as you're relocked, not factory locked (meaning, you unlocked 1.82 and then locked it again) you should be able to use the one click tool again. That's how I did it.
Click to expand...
Click to collapse
assuming it work how u get CWM recovery....are u using one click tool also...? and how u re-root....? are u flashing paulobrien superSU script from recovery?

ted77usa said:
assuming it work how u get CWM recovery....are u using one click tool also...? and how u re-root....? are u flashing paulobrien superSU script from recovery?
Click to expand...
Click to collapse
Once you unlock your bootloader on 1.85 you will not need root to flash CWM Recovery

USB problem. Help Please. Cant root!!!

So... I have a Nexus S And it was fine, Rooted, had Cynogen mod 9 everything was glorious.
Then Jellybean came out. before it was released on my phone with my carrier (Mobilicity, Vancouver), I got a nightly, of Cynogen, Jellybean. Bit laggy. Stock was released the next day. So I reverted to a back up file of Stock (gingerbread) then did the Google update from the device until I had jellybean. It was fine for a while, initially put on all my music... Etc.
Now i plug it in to my computer. it says USB device not recognized. tried uninstalling drivers, it says the drivers did not install properly. Tried manual install, it says i already have the best drivers. tried turning off device, and on, same, tried using on a friends computer, same thing.
Then I tried booting in bootloader (Which it still didnt mount although it said usb init ended) and tried going in to Recovery (maybe i could go back to the stock gingerbread. all I got was the little green android man with the red triangle exclamation point thing. tried resetting phone, same stuff.
Any help would be appreciated. all the places I looked i couldnt find anything.
Nexus S is meant to be rooted. I am literally STUCK on Jellybean stock, Unrooted.
Please Help!!!!! I have no developer powers (plus, I tried clicking USB debugging on/off)
Anyway to mount via command prompt or something?:crying:

jesusroks said:
So... I have a Nexus S And it was fine, Rooted, had Cynogen mod 9 everything was glorious.
Then Jellybean came out. before it was released on my phone with my carrier (Mobilicity, Vancouver), I got a nightly, of Cynogen, Jellybean. Bit laggy. Stock was released the next day. So I reverted to a back up file of Stock (gingerbread) then did the Google update from the device until I had jellybean. It was fine for a while, initially put on all my music... Etc.
Now i plug it in to my computer. it says USB device not recognized. tried uninstalling drivers, it says the drivers did not install properly. Tried manual install, it says i already have the best drivers. tried turning off device, and on, same, tried using on a friends computer, same thing.
Then I tried booting in bootloader (Which it still didnt mount although it said usb init ended) and tried going in to Recovery (maybe i could go back to the stock gingerbread. all I got was the little green android man with the red triangle exclamation point thing. tried resetting phone, same stuff.
Any help would be appreciated. all the places I looked i couldnt find anything.
Nexus S is meant to be rooted. I am literally STUCK on Jellybean stock, Unrooted.
Please Help!!!!! I have no developer powers (plus, I tried clicking USB debugging on/off)
Anyway to mount via command prompt or something?:crying:
Click to expand...
Click to collapse
First of all look for drivers u can try this:
http://junefabrics.com/android/download.php
When the drivers are installed, flash cmw recovery image via fastboot, then install the simple root zip in cmw.
You have jelly bean and you are rooted.
Also you can restore your backup....or flash any other ROM..
root.zip:
http://android.kcomputerzone.com/extras/Simple-Root-v1.0.zip

shivasrage said:
First of all look for drivers u can try this:
When the drivers are installed, flash cmw recovery image via fastboot, then install the simple root zip in cmw.
You have jelly bean and you are rooted.
Also you can restore your backup....or flash any other ROM..
root.zip:
Click to expand...
Click to collapse
Well, actually I already tried reinstalling drivers. Think it's a problem with my device, as it won't work on another computer as well. My phone was rooted, but when I did stock update I lost root and cwm. Everything is stock. I'm not sure what fastboot is or how to get in to it.

jesusroks said:
Well, actually I already tried reinstalling drivers. Think it's a problem with my device, as it won't work on another computer as well. My phone was rooted, but when I did stock update I lost root and cwm. Everything is stock. I'm not sure what fastboot is or how to get in to it.
Click to expand...
Click to collapse
OK i don´t think its a hardware/device problem....you could fix it yourself for sure...but its some work to do...
the question is would you like to do this ?
http://dottech.org/tipsntricks/2153...ows-computer-for-use-with-your-android-phone/
read this ...install it....http://dottech.org/downloads/adb_fastboot_and_other_tools.zip
and then flash a clean jelly bean image, then cmw, then root if you have any question i´l help you if you want...
S.R.

shivasrage said:
OK i don´t think its a hardware/device problem....you could fix it yourself for sure...but its some work to do...
the question is would you like to do this
read this ...install it....
and then flash a clean jelly bean image, then cmw, then root if you have any question i´l help you if you want...
S.R.
Click to expand...
Click to collapse
Hmm I'll try it. It does say that it has an error for installing the drivers. Then when I try to install manually it says I currently have the best drivers for the device 'unknown'

jesusroks said:
Hmm I'll try it. It does say that it has an error for installing the drivers. Then when I try to install manually it says I currently have the best drivers for the device 'unknown'
Click to expand...
Click to collapse
Also, where would I find a fresh jellybean image. How can I get cm on it

jesusroks said:
Also, where would I find a fresh jellybean image. How can I get cm on it
Click to expand...
Click to collapse
Her is a link for the JB images from google:
https://developers.google.com/android/nexus/images
for cm search the forum..

shivasrage said:
Her is a link for the JB images from google:
for cm search the forum..
Click to expand...
Click to collapse
Ok, well, I tried opening it up via command Prompt. It still doesnt recognize my phone is even hooked up. I tried manually installing the drivers, using have disk, and it said i should make sure those drivers are compatable for a 64 bit computer (which they ARE, because they were the ones I used before. Essentially, My issue is this. when i hook up my android device, when I go to (on my computer) Start> computer>Manage> Device manager... I should see android Device, Instead I see... Unknown device. I cant enter my phone via command prompt or anything. Its literally like my phone is only charging and not connected in anyway to my computer. This... really... sucks.... this is almost how i first rooted my phone. Except, then it worked.

Dont know if this is relevant, but in my bootloader it says at the bottom USB control Init and right underneath on the bottom left it says... USB control init End

jesusroks said:
Dont know if this is relevant, but in my bootloader it says at the bottom USB control Init and right underneath on the bottom left it says... USB control init End
Click to expand...
Click to collapse
Last thing you can try....
http://hotfile.com/dl/142977444/8d38a89/Downloader_v1.81.rar.html
download this....then push vol- and vol+ and power together then you are entering download mode....
run odin exe (the other file you can erase)....connect your phone to your pc then ...
if you had right connection a yellow sign appears at left side of the window...please report

shivasrage said:
Last thing you can try....
download this....then push vol- and vol+ and power together then you are entering download mode....
run odin exe (the other file you can erase)....connect your phone to your pc then ...
if you had right connection a yellow sign appears at left side of the window...please report
Click to expand...
Click to collapse
So I tried.
Maybe Im retarded. Not sure when i push the volume up plus Vol Down key. In the bootloader? before i turn on phone, On the home screen?
Anyways. Tried it while on, the phone registered me as pressing the volume keys and thats it, not the power key, not much happened. all that happened is the smae thing, it said USB device not recognized. which sucks.

jesusroks said:
So I tried.
Maybe Im retarded. Not sure when i push the volume up plus Vol Down key. In the bootloader? before i turn on phone, On the home screen?
Anyways. Tried it while on, the phone registered me as pressing the volume keys and thats it, not the power key, not much happened. all that happened is the smae thing, it said USB device not recognized. which sucks.
Click to expand...
Click to collapse
So my solution, in the end.
I bought a Galaxy nexus!!!!!
Such a sweet phone...........

My external speaker broke. Can you fix mine like you did yours?
Need new Android!
Sent from my Nexus S using xda app-developers app

RUU Error 171 Stuck on waiting for boot loader

As the title says, RUU attempts booting my phone but it never comes back on. Even selecting restart boot loader in fastboot or a command it doesn't power itself back on. I have read through other forums and nothing has worked for me yet.
EDIT: I should probably clarify fastboot usb WORKS. Ruu must see my phone considering it detects the ROM version and turns the phone off in attempt to reboot. Anything that I do that requires a reboot doesn't work. I have tried unlocking the bootloader again, everything is fine until it comes to rebooting then I must turn the phone on myself and nothing changes...... IT DOESN'T REBOOT ITSELF therefore seemingly nothing wants to work. And the HTC boot screen is gone??
More background information: http://forum.xda-developers.com/showthread.php?p=39046436#post39046436

What we're your steps exactly? Did you relock your bootloader

a box of kittens said:
What we're your steps exactly? Did you relock your bootloader
Click to expand...
Click to collapse
Yes I did through fast boot with the oem lock command. I've tried installing RUU with a Windows 7 laptop (has HTC sync software) and Windows 8 desktop (basic drivers). Both failed, tried using Windows XP/Vista in compatibility modes and running as an admin with the same results.

Error 171 is a connection error, meaning the RUU can't connect to/find your phone.
Try uninstalling HTC Sync, rebooting your pc, and installing it again. If you've got the Android SDK installed, be sure it's also fully updated.

iElvis said:
Error 171 is a connection error, meaning the RUU can't connect to/find your phone.
Try uninstalling HTC Sync, rebooting your pc, and installing it again. If you've got the Android SDK installed, be sure it's also fully updated.
Click to expand...
Click to collapse
No luck. And I believe it does see the phone in the beginning of the installation. It makes it reboot to the boot loader and that's where it loses the connection. The phone just isn't booting itself back up. I appreciate the reply, if you have anymore ideas please let me know.

Could be something got corrupted. Try redownloading the ruu. Does adb see the phone?

iElvis said:
Could be something got corrupted. Try redownloading the ruu. Does adb see the phone?
Click to expand...
Click to collapse
Re-downloaded RUU and still no go. And adb doesn't see my phone, will it on the fastboot menu? I'm not to familiar with it.

Does anybody else have some more ideas?

Okkoto said:
And adb doesn't see my phone, will it on the fastboot menu? I'm not to familiar with it.
Click to expand...
Click to collapse
No. If adb doesn't see it, fastboot won't either. Does the command "adb devices" (no quotes) show the device as connected?
It sounds like the connection might be working for a few things (like rebooting the phone, as you mentioned). But I still think a connection issue is the main problem.

redpoint73 said:
No. If adb doesn't see it, fastboot won't either. Does the command "adb devices" (no quotes) show the device as connected?
It sounds like the connection might be working for a few things (like rebooting the phone, as you mentioned). But I still think a connection issue is the main problem.
Click to expand...
Click to collapse
Fastboot does see it but adb does not. And what I mean by rebooting the phone in my last post is RUU attempts rebooting it from the boot loader which does turn the phone off but it stays turned off. I've used other commands to reboot the phone from the fastboot screen and those too turn off the phone then again it doesn't come back on like a reboot should do.

I have about completely gave up and going back to using a regular feature phone. I have watched a video about a jtag repair service and was wondering about that or just selling the phone as bricked on ebay.

Okkoto said:
I have about completely gave up and going back to using a regular feature phone. I have watched a video about a jtag repair service and was wondering about that or just selling the phone as bricked on ebay.
Click to expand...
Click to collapse
don't sell it as bricked since it is obviously not bricked. you could get more money just saying you dont wtf your doing and gave up on it. but ill buy it as a bricked phone =) ill give you 50 bucks.

DvineLord said:
don't sell it as bricked since it is obviously not bricked. you could get more money just saying you dont wtf your doing and gave up on it. but ill buy it as a bricked phone =) ill give you 50 bucks.
Click to expand...
Click to collapse
Well if it's not bricked then I sure wish somebody would lead me to the right direction. I have tried 5 different PCs (which all show as connected through fastboot) and they all came with the same error. I've tried everything I could possibly think of and I haven't seen anyone else with quite the same problem I'm having.
I still have not completely gave up and have already decided against selling it as "bricked". The bootloader still comes up so there is at least some hope.

i just had the same problem. the solution was simple - i switch usb-port from front one to the backside one which is directly on motherboard.

Okkoto said:
Well if it's not bricked then I sure wish somebody would lead me to the right direction. I have tried 5 different PCs (which all show as connected through fastboot) and they all came with the same error. I've tried everything I could possibly think of and I haven't seen anyone else with quite the same problem I'm having.
I still have not completely gave up and have already decided against selling it as "bricked". The bootloader still comes up so there is at least some hope.
Click to expand...
Click to collapse
when you say it shows connected through fastboot what do you mean?
how are you getting the device into fastboot - through recovery??
oh, and what was on your device before you tried loading the RUU?

kkm68 said:
i just had the same problem. the solution was simple - i switch usb-port from front one to the backside one which is directly on motherboard.
Click to expand...
Click to collapse
Yes this + if you're on a usb3 port try usb2. Also make sure you're using the cable that came with the phone as I understand other cables may cause issues like this. Also, avoid using a hub or usb extension.

Solution to error 171
I had the same problem and after many attempts I finally got it to work!
-Uninstall anything HTC related from your computer such as HTC Sync Manager and Drivers. Also delete any HTC folders from your program files.
-Make sure you leave the sdk and adb stuff that you downloaded.
-Connect your device via USB to your computer and let it recognize it. It will automatically install default drivers.
-A pop-up asking to install HTC Sync will appear, just ignore it.
-Make sure you set Fast Boot OFF on your phone, and Debugging ON.
-Leave your phone ON and run the RUU set up.
-Then follow the steps on the wizard and everything should work just fine!

diegoyabishh said:
I had the same problem and after many attempts I finally got it to work!
-Uninstall anything HTC related from your computer such as HTC Sync Manager and Drivers. Also delete any HTC folders from your program files.
-Make sure you leave the sdk and adb stuff that you downloaded.
-Connect your device via USB to your computer and let it recognize it. It will automatically install default drivers.
-A pop-up asking to install HTC Sync will appear, just ignore it.
-Make sure you set Fast Boot OFF on your phone, and Debugging ON.
-Leave your phone ON and run the RUU set up.
-Then follow the steps on the wizard and everything should work just fine!
Click to expand...
Click to collapse
I have a similar problem with my HTC One. I am stuck in the bootloader and any action I take leads straight into a boot loop. If I try to reboot, reboot-bootloader, go into recovery (twrp), or factory reset it goes into a boot loop. Also I can't lock the bootloader and flashing my recovery doesn't help, even though it says its a success. I've tried three computers and deleted and reinstalled drivers but still the computers only find my phone in fastboot usb and can't find it using adb.
This solution above won't help me since I can't get my phone on for the life of me. I tried running RUU and All-in-One Toolkit but no luck. RUU fails finding the bootloader since my phone gets stuck in its boot loop. I am fresh out of ideas so any other ways to fix this issue would be greatly appreciated.
BTW I found my phone is this condition when I pulled it out of my pocket. I never installed custom ROMs on it. It is unlocked and rooted though running 4.2.2 (3.05.651.6) hoot 1.55. The only thing I can think of is that an OTA update got pushed to my phone and bricked it. That or for some strange reason something went wrong with phone from the rooting process after two weeks of it working perfectly.

jondon156 said:
I have a similar problem with my HTC One. I am stuck in the bootloader and any action I take leads straight into a boot loop. If I try to reboot, reboot-bootloader, go into recovery (twrp), or factory reset it goes into a boot loop. Also I can't lock the bootloader and flashing my recovery doesn't help, even though it says its a success. I've tried three computers and deleted and reinstalled drivers but still the computers only find my phone in fastboot usb and can't find it using adb.
This solution above won't help me since I can't get my phone on for the life of me. I tried running RUU and All-in-One Toolkit but no luck. RUU fails finding the bootloader since my phone gets stuck in its boot loop. I am fresh out of ideas so any other ways to fix this issue would be greatly appreciated.
BTW I found my phone is this condition when I pulled it out of my pocket. I never installed custom ROMs on it. It is unlocked and rooted though running 4.2.2 (3.05.651.6) hoot 1.55. The only thing I can think of is that an OTA update got pushed to my phone and bricked it. That or for some strange reason something went wrong with phone from the rooting process after two weeks of it working perfectly.
Click to expand...
Click to collapse
Nobody here can help you as we don't have any experience with your device. You'd be much better off asking in the HTC One forum which you'll find here:
http://forum.xda-developers.com/htc-one
Sent from my Evita

Heisenberg said:
Nobody here can help you as we don't have any experience with your device. You'd be much better off asking in the HTC One forum which you'll find here:
http://forum.xda-developers.com/htc-one
Sent from my Evita
Click to expand...
Click to collapse
hi all..
facing same problem with HTC Desire 816 n 4g... have anyone got any solution??
plz pass it..
thank you

[Q] Asus tf700 JB 4.2 NOT WORKING

Hey guys, first time on here.
I've been trying to root my unlocked Asus tf700 running JB 4.2.1 for days and have been following all the xda guides with no luck.
I've tried to flash CMW on it through fastboot to no avail. Everything I see says, once you get into the bootloader or whatever, to press Vol Down until you get to the USB icon and then press volume up but there isn't any USB icon. Right when I get into the bootloader, after I hold Vol Down and Pwr, the first thing it reads on the top left corner of the screen is "Key driver missing." But I have downloaded the drivers from the asus website. Any suggestions about why this is happening? I also tried just using Motochopper (http://forum.xda-developers.com/showthread.php?t=2230763) but when it ran it said failure. I booted it up and I had SuperSU but I tried to open it and it said "no SU binary found! This is a problem!". Any suggestions on how to root this and flash a recovery on it would be greatly appreciated, because none of the other forums guides seem to work? help out a noob!

npf24 said:
Hey guys, first time on here.
I've been trying to root my unlocked Asus tf700 running JB 4.2.1 for days and have been following all the xda guides with no luck.
I've tried to flash CMW on it through fastboot to no avail. Everything I see says, once you get into the bootloader or whatever, to press Vol Down until you get to the USB icon and then press volume up but there isn't any USB icon. Right when I get into the bootloader, after I hold Vol Down and Pwr, the first thing it reads on the top left corner of the screen is "Key driver missing." But I have downloaded the drivers from the asus website. Any suggestions about why this is happening? I also tried just using Motochopper (http://forum.xda-developers.com/showthread.php?t=2230763) but when it ran it said failure. I booted it up and I had SuperSU but I tried to open it and it said "no SU binary found! This is a problem!". Any suggestions on how to root this and flash a recovery on it would be greatly appreciated, because none of the other forums guides seem to work? help out a noob!
Click to expand...
Click to collapse
If your device is unlocked you don’t need MotoChopper for rooting, just flash TWRP Recovery and it will ask you if you want to root your device (in case it detect that root is missing).
For the "Key driver missing" error, just ignore it, Fastboot will work just fine as long as you are sure that the drivers are installed just fine.

Pretoriano80 said:
If your device is unlocked you don’t need MotoChopper for rooting, just flash TWRP Recovery and it will ask you if you want to root your device (in case it detect that root is missing).
For the "Key driver missing" error, just ignore it, Fastboot will work just fine as long as you are sure that the drivers are installed just fine.
Click to expand...
Click to collapse
Thanks, but I'm still confused. I thought you needed GooManager to install TWRP, and GooManager won't work unless you have a rooted device.

npf24 said:
Thanks, but I'm still confused. I thought you needed GooManager to install TWRP, and GooManager won't work unless you have a rooted device.
Click to expand...
Click to collapse
Goo Manager is not mandatory, you can still flash the TWRP via fastboot.You can find more info on the TWRP website.

Sounds like a driver issue to me. If you can't fastboot cwm or use motochopper something is up.
Could also be your usb connection. Try another cable or port or another pc.

lafester said:
Sounds like a driver issue to me. If you can't fastboot cwm or use motochopper something is up.
Could also be your usb connection. Try another cable or port or another pc.
Click to expand...
Click to collapse
yeah ive tried two differ pcs already so I dont think its that. It definitely could be the drivers. Ive tried to install them from the asus site a bunch of times though so idk whats up.

npf24 said:
yeah ive tried two differ pcs already so I dont think its that. It definitely could be the drivers. Ive tried to install them from the asus site a bunch of times though so idk whats up.
Click to expand...
Click to collapse
If you have recently updated your firmware to xxxx.10, you will "not" be able to run motochopper (there is nothing wrong with your PC or cables), Ausus closed the Moto root opening with the latest firmware. However, you can still root following the TWRP instructions.....as indicated above.

just some more info
So i tried re installing the drivers one more time to my PC, and everything went okay, so I'm sure it can't be the drivers, although the error still comes up. And just to tell you guys, when moto chopper runs it says, "waiting for device, daemon not running, starting it now on port 5057, daemon started successfully." Don't know if that helps at all to what the problem is, but just some more info. Now I'll try flashing twrp and rooting that way.

Nothing works at all
dishinit said:
If you have recently updated your firmware to xxxx.10, you will "not" be able to run motochopper (there is nothing wrong with your PC or cables), Ausus closed the Moto root opening with the latest firmware. However, you can still root following the TWRP instructions.....as indicated above.
Click to expand...
Click to collapse
So I went to the TWRP website to try and install twrp 2.6.0. The three options on how to do this were:
1. Via GooManager - which I can't do because my device isn't rooted.
2. Through fastboot (it says to click on the usb icon) - there isn't any usb icon.
3. The terminal method.
I just tried the terminal method, and that didn't work either because when I typed in what it said I was supposed to type in, it said "permission denied."
So yeah.

npf24 said:
So I went to the TWRP website to try and install twrp 2.6.0. The three options on how to do this were:
1. Via GooManager - which I can't do because my device isn't rooted.
2. Through fastboot (it says to click on the usb icon) - there isn't any usb icon.
3. The terminal method.
I just tried the terminal method, and that didn't work either because when I typed in what it said I was supposed to type in, it said "permission denied."
So yeah.
Click to expand...
Click to collapse
I vaguely remember running Motochopper & getting the same message.....it you are on .8 or earlier firmware (in 4.2.1), Motochopper should run.
I think I turned off my tablet, left it connected to PC & then ran motochopper & tablet self booted.....lots of ABD's out of date messages, but Moto worked it's way through them and rooted my device.
I have read of problems with Win 7 (my OS) & Motochopper, but none if used with XP.
Good luck, & Let us know how t goes

npf24 said:
2. Through fastboot (it says to click on the usb icon) - there isn't any usb icon.
Click to expand...
Click to collapse
Recent bootloaders do not have a USB icon because they activate fastboot already while the boot menu is visible (read the tiny text in the top left corner).

dishinit said:
I vaguely remember running Motochopper & getting the same message.....it you are on .8 or earlier firmware (in 4.2.1), Motochopper should run.
I think I turned off my tablet, left it connected to PC & then ran motochopper & tablet self booted.....lots of ABD's out of date messages, but Moto worked it's way through them and rooted my device.
I have read of problems with Win 7 (my OS) & Motochopper, but none if used with XP.
Good luck, & Let us know how t goes
Click to expand...
Click to collapse
I tried what you said. The tablet didn't self-boot when I ran Motochopper again. It just stayed powered off. I turned it on, and the exact same thing happened. except there was another error in motochopper this time. it said "FAILURE ALREADY EXISTS." any other suggestions?

_that said:
Recent bootloaders do not have a USB icon because they activate fastboot already while the boot menu is visible (read the tiny text in the top left corner).
Click to expand...
Click to collapse
Okay that's what I thought. So if I do that second method on twrp, I guess I should just skip when it says to press the USB icon because fast boot is already running??

npf24 said:
Okay that's what I thought. So if I do that second method on twrp, I guess I should just skip when it says to press the USB icon because fast boot is already running??
Click to expand...
Click to collapse
Correct.

_that beat me to it - again. )

I f up

My twrp is gone after an ota update on my sailfish. So I thought I'll tried out flashify because I don't have a pc or a laptop. For some reason I thought that flashify can install twrp back. I tried to install it using flashify but it says it ran to a problem, so my stupid brain decide to I flash gapps first using the app because I have deleted some of the gapps. I deleted google playstore with the gmscore. Then my phone stucked on a bootloop, so I did a factory reset and my phone did reboot but now I'm stuck on the android setup which cannot open without google playstore. (f'in great) I cant reboot to bootloader and I cant connect to pc with usb debugging (greatest thing that can happen) Now, does anybody know how to fix this?
Edit: you know maybe im a genius, i fix it by myself
1. Boot to bootloader (mine work again after I type adb reboot bootloader on the terminal. Volume down + power button
2. I tried to reboot to lineage recovery but apparently it seems to ignore it so I flash twrp fastboot flash (I drag my twrp file here)
3. On twrp I reboot to recovery to get to lineage is recovery
4. I tapApply update and the From adb
5. On the terminal I type adb sideload (I drag lineage system file here)
4. And that's it,

aL_09 said:
My twrp is gone after an ota update on my sailfish. So I thought I'll tried out flashify because I don't have a pc or a laptop. For some reason I thought that flashify can install twrp back. I tried to install it using flashify but it says it ran to a problem, so my stupid brain decide to I flash gapps first using the app because I have deleted some of the gapps. I deleted google playstore with the gmscore. Then my phone stucked on a bootloop, so I did a factory reset and my phone did reboot but now I'm stuck on the android setup which cannot open without google playstore. (f'in great) I cant reboot to bootloader and I cant connect to pc with usb debugging (greatest thing that can happen) Now, does anybody know how to fix this?
Click to expand...
Click to collapse
Hey there, what happens when you try to get into the bootloader?
I don't want to be rude but next time please refrain from using unconventional methods because these may not give you the results you want if you don't know how to use them correctly. Also, Gapps packages are only meant to be used on custom ROMs that don't bring any Google apps by default.

All-In-One said:
Hey there, what happens when you try to get into the bootloader?
I don't want to be rude but next time please refrain from using unconventional methods because these may not give you the results you want if you don't know how to use them correctly. Also, Gapps packages are only meant to be used on custom ROMs that don't bring any Google apps by default.
Click to expand...
Click to collapse
Hi, I'm new and I'm actually on lineage os and I flashed mindthegapps included and also I'm stupid. Bootloader did not open when I press the power button during reboot

aL_09 said:
Hi, I'm new and I'm actually on lineage os and I flashed mindthegapps included and also I'm stupid. Bootloader did not open when I press the power button during reboot
Click to expand...
Click to collapse
Hey there, to access the bootloader you have to press Power + Volume Down for a few seconds. Try that.

All-In-One said:
Hey there, to access the bootloader you have to press Power + Volume Down for a few seconds. Try that.
Click to expand...
Click to collapse
Well yeah, it seems to be ignoring it too if I do that and also there is a screen that says press power button to open up bootloader during reboot.

aL_09 said:
Well yeah, it seems to be ignoring it too if I do that and also there is a screen that says press power button to open up bootloader during reboot.
Click to expand...
Click to collapse
Is there any chance you can take a photo and show me that screen? Never heard of it before.

All-In-One said:
Is there any chance you can take a photo and show me that screen? Never heard of it before.
Click to expand...
Click to collapse
Edit: I fix it myself with adb sideload, apparently bootloader work again but still thank u

aL_09 said:
Edit: I fix it myself with adb sideload, apparently bootloader work again but still thank u
Click to expand...
Click to collapse
Hey aL, that's good to hear. As I've told you before, I think you should stick to normal flashing methods just so you can be sure of what you're doing.
Also, it would be nice if you can post a little walkthrough of what you've done to get your device working again as it can be useful if anyone else reads this thread looking for a solution. Do not forget to contact a mod so it can be closed after a solution is posted.

All-In-One said:
Hey aL, that's good to hear. As I've told you before, I think you should stick to normal flashing methods just so you can be sure of what you're doing.
Also, it would be nice if you can post a little walkthrough of what you've done to get your device working again as it can be useful if anyone else reads this thread looking for a solution. Do not forget to contact a mod so it can be closed after a solution is posted.
Click to expand...
Click to collapse
Who's the mod?
https://forum.xda-developers.com/attachment.php?attachmentid=4929067&stc=1&d=1579303524