i have tried way to many times to root this phone and have failed over and over. atleast once every 3 months i try with zero results. the phone is unlocked using the OneX v2.5 tool kit here. when i try to do perm root it says " User C not recognized as an external or internal command, operable program or batch file". ive tried putting the tool kit directly in C: and 86x. nothing works. what do i need to do to root this freaking phone. im fixing to get a bat to this phone!
Have you tried a different version, reinstall/redownload and running it as an admin?
Sent from my EndeavorU using XDA Premium 4 mobile app
Bl4ckX said:
Have you tried a different version, reinstall/redownload and running it as an admin?
Sent from my EndeavorU using XDA Premium 4 mobile app
Click to expand...
Click to collapse
no. i havent. do you have a recommendation for a different root system?
both programs ive used says "phone not connected". i dont get it. ive tried debugging and recovery. i have never had an android this hard to root. samsung galaxy s2 was very easy.
have you tried to flash a custom recovery and root package. that's how i did for mine and i was done within 10 minutes
You have a custom recovery ? Just install the SU.zip via recovery then. Tried that ?
mrbtree98 said:
have you tried to flash a custom recovery and root package. that's how i did for mine and i was done within 10 minutes
Click to expand...
Click to collapse
ive tried the all in one unlock and root kit. didnt work. could you post a link to what you used?
I never root stock rom. I'm always on a custom rom.
Just check for the superuser zip and install it in the custom recovery
Mr Hofs said:
I never root stock rom. I'm always on a custom rom.
Just check for the superuser zip and install it in the custom recovery
Click to expand...
Click to collapse
how do you use custom recovery? i tried everything on the all in tool kit(custom recovery to) and says phone not detected or what i posted up top. this is crazy. never have i seen and android phone so hard to root!!!
MPH33 said:
both programs ive used says "phone not connected". i dont get it. ive tried debugging and recovery. i have never had an android this hard to root. samsung galaxy s2 was very easy.
Click to expand...
Click to collapse
Do you get any output with "adb devices"? When you don't (and your phone has debugging enabled), it may as well be a driver problem.
(quick tip: add the antroid-tools folder to your PATH)
I personally can't find my phone on Windows anymore after the 4.2 update, so I just use an Ubuntu liveUSB for adb/fastboot purposes.
Sent from my HTC One X using Tapatalk
My opinion ? Don't use a toolkit. Straight commands from the prompt.
Download android sdk bundle, unpack it and go the the platform tools folder. Put there the recovery (recovery.img) open a command prompt there and type
Fastboot flash recovery recovery.img
Fastboot erase cache
Mr Hofs said:
My opinion ? Don't use a toolkit. Straight commands from the prompt.
Download android sdk bundle, unpack it and go the the platform tools folder. Put there the recovery (recovery.img) open a command prompt there and type
Fastboot flash recovery recovery.img
Fastboot erase cache
Click to expand...
Click to collapse
done as directed. went to cmd typed fastboot. still says internal or external not recognized. man this sux
Have you already followed the instructions on htcdev.com? You have to unlock your phone first before you can flash a recovery
Sent from my HTC One X using Tapatalk
svenvv said:
Have you already followed the instructions on htcdev.com? You have to unlock your phone first before you can flash a recovery
Sent from my HTC One X using Tapatalk
Click to expand...
Click to collapse
yes. the phone is unlocked. it's been unlocked for like 8 months. just cant seem to root it.
Are the drivers correctly installed, download the latest HTC sync. And also check if java and .net.frameworks are installed on the pc
Mr Hofs said:
Are the drivers correctly installed, download the latest HTC sync. And also check if java and .net.frameworks are installed on the pc
Click to expand...
Click to collapse
yes. sync manager is fully updated. maybe its my computer. i built it. running on windows 7 ultimate. hell, i dont know. this is weird. like i said before... my old samsung was so much easier. i just wanna root to get rid of all this bloat.
MPH33 said:
done as directed. went to cmd typed fastboot. still says internal or external not recognized. man this sux
Click to expand...
Click to collapse
That seems like you're not in the correct directory.
To get rid of that error forever just put the contents of platform-tools in your C:\windows\system32 and C:\windows\syswow64 folders
Then you can run the commands from anywhere.
Now:
Install HTC sync drivers.
Put your phone in fastboot mode.
Put a recovery image in the path that the cmd shows when you start it (eg. C/users/USER/) or "cd" to the recovery image.
Then:
fastboot flash recovery recoveryname.img
When that gives decent output we're getting somewhere.
In that case put the supersu zipfile on you phones storage and flash it from recovery.
Sent from my HTC One X using Tapatalk
Try updating or reinstalling drivers for the phone check if your cable is good and connects it to PC
[Knowledge from tegra 2 device you must have APT or NVflash driver and whne phone is off with custom key combination enters flash mode i guss is similar to this]
screw this. phone works great just wanted to root. mint condition, will sell cheap. pm me if interested.
it isn't due to the phone...it's because windows don't know for what this command is...so install again the latest java for your win7 ....you are definitely doing something wrong...you could also try to google that error which you get after typing fastboot bla bla
it works for all other ppl so should also work for you even with my non genuine win8.1 pro it's working fine
Related
Well, it seems I have bricked my phone with Visionary app(not pointing fingers). Problem is, I have ADB drivers installed but I can't use it because I can't get passed the HTC boot screen. I've tried using it in Recovery but the device is registered as Offline. My only other option of saving my phone I guess is with Fastboot. I've searched the forums for help but I'm getting nowhere fast. I'm accepting all help and ideas.
1. Did ADB work before (meaning do you have the proper ADB drivers installed)?
2. Does fastboot work?
3. If you can access recovery, why don't you just wipe?
Stryder5 said:
1. Did ADB work before (meaning do you have the proper ADB drivers installed)?
2. Does fastboot work?
3. If you can access recovery, why don't you just wipe?
Click to expand...
Click to collapse
1. I installed the correct drivers using the PDAnet method.
2. Fastboot does work, I just don't have any images to flash.
3.Apparently Visionary installed another system file that when I wipe, it does nothing for me.
Can you flash the PC101.OMG, or whatever its called whatever file to restore to original rom?
Sent from my HTC Vision using XDA App
creid2352 said:
2. Fastboot does work, I just don't have any images to flash.
Click to expand...
Click to collapse
Then go get some. Check one of the stickies for links to downgrade and see if that works for you.
This is what I get when I try to:
Code:
fastboot update update.zip
I've also tried
Code:
fastboot flash system update.zip
Stryder5 said:
Then go get some. Check one of the stickies for links to downgrade and see if that works for you.
Click to expand...
Click to collapse
I will see if I can find the thread.
http://forum.xda-developers.com/showthread.php?t=842495
No help here?
Ok, so I have the PC10IMG...zip file, but how do I use this with fastboot? I can't use adb to push the file to the sd card.
You're supposed to use fastboot to flash .img files, not .zip files. Zip files are flashed through recovery.
Sent from my HTC Vision using XDA App
I was trying to install a new rom but I wanted to reformat my sdcard first. I planned on reformatting, mounting the sdcard so my pc would pick it up, moving the rom I chose to the freshly formatted sdcard, then flashing the rom. I started by doing a full wipe of everything, then wiped the internal sdcard. The problem is when I try to mount the sdcard to transfer files nothing happens. I tried doing a restore using odin but it gets stuck at setup connection. Is there anything else I can do or is it completely bricked?
chaotic646 said:
I was trying to install a new rom but I wanted to reformat my sdcard first. I planned on reformatting, mounting the sdcard so my pc would pick it up, moving the rom I chose to the freshly formatted sdcard, then flashing the rom. I started by doing a full wipe of everything, then wiped the internal sdcard. The problem is when I try to mount the sdcard to transfer files nothing happens. I tried doing a restore using odin but it gets stuck at setup connection. Is there anything else I can do or is it completely bricked?
Click to expand...
Click to collapse
I'm not the guy who can tell you what you need to do, but I will tell you that I have read other posts by people in your position. There are ways to push the necessary files to your phone, either toolkits or command prompt type setups, sorry but that's all I have. Google is your friend though. Galaxy Nexus toolkit, start with that, it's around here somewhere
Sent from my Galaxy Nexus using Tapatalk 2
You cannot mount the sd on the gnex through recovery. There is no SD to mount.
To move a file to your phone you must push it with adb
adb push nameofzip /storage/sdcard0
Sent from my Nexus 7 using xda premium
El Daddy said:
You cannot mount the sd on the gnex through recovery. There is no SD to mount.
To move a file to your phone you must push it with adb
adb push nameofzip /storage/sdcard0
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Since there's no rom on my phone, would I need to be in recovery or bootloader to do that?
ADB wont even open up. This sucks.
chaotic646 said:
Since there's no rom on my phone, would I need to be in recovery or bootloader to do that?
Click to expand...
Click to collapse
Yes, you do that on recovery mode.
Swyped on my Galaxy Nexus running AOKP with Franco Kernel, overclocked to 1.4GHz
chaotic646 said:
Since there's no rom on my phone, would I need to be in recovery or bootloader to do that?
Click to expand...
Click to collapse
do it in recovery.
chaotic646 said:
Since there's no rom on my phone, would I need to be in recovery or bootloader to do that?
ADB wont even open up. This sucks.
Click to expand...
Click to collapse
Have you installed adb drivers? You probably should have done this already, unless you used a toolkit to unlock and root...
To install drivers, download the naked driver located here: http://forum.xda-developers.com/showpost.php?p=20058157&postcount=1
Then, follow this guide to install them correctly.http://forum.xda-developers.com/showpost.php?p=29044502&postcount=735
If they are set up correctly you will be able to push the rom to your internal storage booted in recovery with adb. A list of adb commands is here: http://forum.xda-developers.com/showthread.php?t=1812959
If you aren't comfortable with that I recommend that you flash the stock images to your phone with fastboot following this guide: http://forum.xda-developers.com/showthread.php?t=1626895
This should be all the info you need. I'll be around to answer questions you may have. Just post them here.
Good Luck.
It fails because it says Im using an insecure bootloader
chaotic646 said:
It fails because it says Im using an insecure bootloader
Click to expand...
Click to collapse
What fails and when?
El Daddy said:
What fails and when?
Click to expand...
Click to collapse
The Galaxy Nexus Toolkit, which uses adb to push files to the phone. It gets about halfway through the process then fails because it says Im using an insecure bootloader
None of the info I gave you has anything to do with the toolkit. If you want to use it I cannot help you. Sorry. If you want to read my thoughts about toolkits check my sig.
However, If you follow what I posted in post #7 I will help you though the process as long as it takes.
El Daddy said:
None of the info I gave you has anything to do with the toolkit. If you want to use it I cannot help you. Sorry. If you want to read my thoughts about toolkits check my sig.
However, If you follow what I posted in post #7 I will help you though the process as long as it takes.
Click to expand...
Click to collapse
I cant follow the guide you linked to install the drivers, because it instructs me to enable usb debugging...I have no rom installed on my phone so I cant enable it.
OK. I'm not sure if you can install the driver without debugging activated. But, I know you can install the fastboot driver when booted in the bootloader because I have done it.
1) Boot into the bootloader. (power + vol. up and down)
2) Connect to your pc
3) Open your device manager and you should see "android 1.0"
4) Right click on that and choose update driver.
5) Choose install from my computer and then install the naked driver.
6) Click done and then it should show Galaxy Nexus Bootloader Interface.
You will now be ready to flash the stock google image. Follow this guide.
You'll be up and running again. You can then flash a custom recovery and ROM if you so choose. OR just roll with stock.
chaotic646 said:
I was trying to install a new rom but I wanted to reformat my sdcard first. I planned on reformatting, mounting the sdcard so my pc would pick it up, moving the rom I chose to the freshly formatted sdcard, then flashing the rom. I started by doing a full wipe of everything, then wiped the internal sdcard. The problem is when I try to mount the sdcard to transfer files nothing happens. I tried doing a restore using odin but it gets stuck at setup connection. Is there anything else I can do or is it completely bricked?
Click to expand...
Click to collapse
Use Odin bro...its in the forum
Sent from my Galaxy Nexus using xda premium
Dafuqq guys. The easiest way is flashing the stock fastboot images from google. Just flash them.in fastboot.
Sent from my Galaxy Nexus using Tapatalk 2
I'd stick with el daddy. .he seems to be directing you in a way that gets you away from that stupid kit and you're learning the proper way.. .with adb. Next time something happens you'll be far better off.
I got it situated and fixed with a different toolkit but I appreciate all the help. I couldnt get it going with adb, everytime I would try to open adb in command prompt it would open for a split second then crash. The toolkit I used uses the adb on my pc though and it worked just fine.
chaotic646 said:
I got it situated and fixed with a different toolkit but I appreciate all the help. I couldnt get it going with adb, everytime I would try to open adb in command prompt it would open for a split second then crash. The toolkit I used uses the adb on my pc though and it worked just fine.
Click to expand...
Click to collapse
Because you're not supposed to open up adb by double clicking on it.
You're supposed to navigate to the location where it is using CMD and do commands from there.
chaotic646 said:
I got it situated and fixed with a different toolkit but I appreciate all the help. I couldnt get it going with adb, everytime I would try to open adb in command prompt it would open for a split second then crash. The toolkit I used uses the adb on my pc though and it worked just fine.
Click to expand...
Click to collapse
Go to the directory where you have adb.exe
Shift+Right Click the blank space (Don't click any files)
Click Open Command Prompt Here
Now you can use all the adb commands there.
Good luck
El Daddy said:
OK. I'm not sure if you can install the driver without debugging activated. But, I know you can install the fastboot driver when booted in the bootloader because I have done it.
1) Boot into the bootloader. (power + vol. up and down)
2) Connect to your pc
3) Open your device manager and you should see "android 1.0"
4) Right click on that and choose update driver.
5) Choose install from my computer and then install the naked driver.
6) Click done and then it should show Galaxy Nexus Bootloader Interface.
You will now be ready to flash the stock google image. Follow this guide.
You'll be up and running again. You can then flash a custom recovery and ROM if you so choose. OR just roll with stock.
Click to expand...
Click to collapse
You are a very patient person. I hope you help me when I get in a jam. You make these forums what they are - awesome. Thanks.
Sent from my Galaxy Nexus using Tapatalk 2
Hi everyone, i have medium to advanced experience with flashing tools, android drivers, adb, fastboot, recovery mode and so on.
This evening once i installed the OTA Update for my Galaxy Nexus (which was running Android 4.2) the process failed at the end (as usual -.-) and i got stuck at bootloader.
I've wiped it completely ending up with no OS installed on it, nothing on SDCARD (Internal storage in this case).
The problem is that, i have no drivers installed on my PC for this phone.
I've already downloaded the latest version of Android 4.2 to flash (.zip), but there's no way i can transfer the file to the phone without the drivers.
I already tried GNex toolkit but it's stuck on "waiting adb device" (i have no fastboot drivers installed and can't install them because i can't find a easy way to do so).
NexusRootToolkit fails on pushing the zip to the phone and flash also won't work.
Any idea of what can i do now?
I may even pay on paypal for a quick help to get my phone back on working
Get into the bootloader and use fastboot, or if you have a custom recovery installed (sounds like you don't) then you can adb push from there. ADB doesn't exist in the bootloader, only fastboot. Those are your options.
ttabbal said:
Get into the bootloader and use fastboot, or if you have a custom recovery installed (sounds like you don't) then you can adb push from there. ADB doesn't exist in the bootloader, only fastboot. Those are your options.
Click to expand...
Click to collapse
Actually i do have a custom recovery which is CMW, but i can't seem to get my internal storage mounted using i'ts options.
I will try to push the .zip using the ADB on the recovery mode.
After checking the logs i can now see :
Enable to mount /usb-otg
(Using NexusRootToolkit i just flashed TWRP as recovery mode)
Solved : adb push <romname.zip> /sdcard/<romname.zip>
After the push was completed, i flashed the new .zip using TWRP in recovery mode.
Has anyone found a solution to this? Same thing has happened to me and I'm freaking out.
NPasta said:
Has anyone found a solution to this? Same thing has happened to me and I'm freaking out.
Click to expand...
Click to collapse
You mean besides the post right above yours?
Solved : adb push <romname.zip> /sdcard/<romname.zip>
After the push was completed, i flashed the new .zip using TWRP in recovery mode.
Click to expand...
Click to collapse
Save the pain, just flash the stock ROM from fastboot already....
Mach3.2 said:
Save the pain, just flash the stock ROM from fastboot already....
Click to expand...
Click to collapse
This. I don't see what the problem is here.
marcelloLins said:
i have medium to advanced experience with flashing tools, android drivers, adb, fastboot, recovery mode and so on.
I already tried GNex toolkit but it's stuck on "waiting adb device" (i have no fastboot drivers installed and can't install them because i can't find a easy way to do so).
NexusRootToolkit fails on pushing the zip to the phone and flash also won't work.
Click to expand...
Click to collapse
If you have the experience you say you have why do you use a Toolkit? Just learning for myself.
Look for efrant posts, they are the best and most comprehensive even for medium-advanced experience.
With him you will learn everything you need to know, including getting out of trouble and out of.............toolkit.
Just in case (you never know in life) do you have android-sdk installed on your pc?
Good luck in your learning curve ( I am still and will always be in it)
help-a-noob
Having similar problem: no OS installed. Got bootloader and TWRP. adb push doesn't work: computer can't find device. how do I get to fastboot? HALP!
HALP...
That's classic..
Read this:
http://forum.xda-developers.com/showthread.php?t=1812959
Then follow this:
http://forum.xda-developers.com/showthread.php?t=1626895
gunner1937 said:
If you have the experience you say you have why do you use a Toolkit? Just learning for myself.
Look for efrant posts, they are the best and most comprehensive even for medium-advanced experience.
With him you will learn everything you need to know, including getting out of trouble and out of.............toolkit.
Just in case (you never know in life) do you have android-sdk installed on your pc?
Good luck in your learning curve ( I am still and will always be in it)
Click to expand...
Click to collapse
Yep, i do have it installed, mainly because i'm a developer myself ; )
I've solved it already, as i've said, pushing the rom using ADB.
The upgrade to 4.2.1 probably failed because i've had the phone rooted.
Thanks for all the support and links by the way
marcelloLins said:
The upgrade to 4.2.1 probably failed because i've had the phone rooted.
Click to expand...
Click to collapse
You are mistaken, root doesn't stop a system update. I can vouch for that myself, even though i know that it doesnt matter just from reading some people's posts around here.
You weren't exactly explicit on your first post, so I presume you didnt/dont have the correct baseband version for that specific OTA to apply. Very common.
Oh and if you've never been able to OTA update successfully, it's not "usual" for the rest of us. You should work towards becoming more verbose and objective when troubleshooting. That will make you more experienced.
Sent from my i9250
marcelloLins said:
Yep, i do have it installed, mainly because i'm a developer myself ; )
I've solved it already, as i've said, pushing the rom using ADB.
The upgrade to 4.2.1 probably failed because i've had the phone rooted.
Thanks for all the support and links by the way
Click to expand...
Click to collapse
Hey, I have this exact problem. My os is gone and all i have is my cwm.
I am also having trouble installing adb, my comp doesn't recognize my nexus.
Please help, thanks!
dicksonjoe said:
Hey, I have this exact problem. My os is gone and all i have is my cwm.
I am also having trouble installing adb, my comp doesn't recognize my nexus.
Please help, thanks!
Click to expand...
Click to collapse
Try installing the ADB Drivers manually in order for your PC to recognize it.
Have you tried putting it other modes such as Download Mode and check if your pc installs any driver?
You will have to ADB PUSH the OS image to your internal memory and use CW to flash the rom from the sdcard, but you will need the drivers installed or adb wont be able to see your phone
i have the same problem you had...
i read some stuff and installed adb, sdk and whatever...
im trying the " adb push" command, but i think im doing something wrong.
the rom is on c:\users\edgar\downloads
rom name is abc.zip (i renamed)
what is the correct command format i must type??
thanks guys...
edgarzin said:
i have the same problem you had...
i read some stuff and installed adb, sdk and whatever...
im trying the " adb push" command, but i think im doing something wrong.
the rom is on c:\users\edgar\downloads
rom name is abc.zip (i renamed)
what is the correct command format i must type??
thanks guys...
Click to expand...
Click to collapse
Use "adb sideload c:\users\edgar\downloads\abc.zip". "adb push" is for transferring files from PC to phone, not flashing.
AndyYan said:
Use "adb sideload c:\users\edgar\downloads\abc.zip". "adb push" is for transferring files from PC to phone, not flashing.
Click to expand...
Click to collapse
thanks, but isnt it what am i supposed to do? transfer the zip file to sdcard and then flash using twrp?
for example usb mount via twrp dont work for me
edgarzin said:
thanks, but isnt it what am i supposed to do? transfer the zip file to sdcard and then flash using twrp?
Click to expand...
Click to collapse
adb sideload does both transferring and flashing within a single command. The "sideloaded" ZIP gets saved as "sideload.zip" under the root of the storage.
Sent from Samsung Galaxy Nexus @ CM11
AndyYan said:
adb sideload does both transferring and flashing within a single command. The "sideloaded" ZIP gets saved as "sideload.zip" under the root of the storage.
Sent from Samsung Galaxy Nexus @ CM11
Click to expand...
Click to collapse
Thanks!! Now its working! in twrp, advanced mode, adb sideload, then i executed the command you told me!!! saved my phone
I have a problem with my computer, I have a GNEX and I cannot get the commands from ADB to work. Once I tried to root my phone manually and I did not work, then I tried Wug's tool and it did not work either. I tried another computer and it worked. Both PC's have win7 and the drivers installed correctly. ADB does detect the phone.
When I type a command, the cursor just blinks and nothing happens. I can keep typing characters and still nothing happens.
Sounds like you're not running the command prompt as admin.
diobando said:
I have a problem with my computer, I have a GNEX and I cannot get the commands from ADB to work. Once I tried to root my phone manually and I did not work, then I tried Wug's tool and it did not work either. I tried another computer and it worked. Both PC's have win7 and the drivers installed correctly. ADB does detect the phone.
When I type a command, the cursor just blinks and nothing happens. I can keep typing characters and still nothing happens.
Click to expand...
Click to collapse
running what? 4.0.1, 4.2.2? ....
have you updated ADB/android-sdk?
To root a Nexus "manually", you just need fastboot, a custom recovery, and a superuser or supersu flashable zip. you don't even need ADB (if the zip flashable has been copied to /sdcard/ before)
bk201doesntexist said:
running what? 4.0.1, 4.2.2? ....
have you updated ADB/android-sdk?
To root a Nexus "manually", you just need fastboot, a custom recovery, and a superuser or supersu flashable zip. you don't even need ADB (if the zip flashable has been copied to /sdcard/ before)
Click to expand...
Click to collapse
I have 4.2.2 right now, but I tried it before with 4.0.2, 4.0.4 and 4.1.1. I have updated de sdk and the commands still do not work.
diobando said:
I have 4.2.2 right now, but I tried it before with 4.0.2, 4.0.4 and 4.1.1. I have updated de sdk and the commands still do not work.
Click to expand...
Click to collapse
Premise not to use almost never win7 ... I still tried for the first time tonight sdk-platform-tools on windows and adb and fastboot commands work normally ... the phone must have the bootloader unlocked (otherwise fastboot does not work ) is launched from the promt with administrator privileges and inside the folder where resides and the phone must be in fastboot / bootloader mode to acknowledge the command but also the drivers for the Nexus should be properly installed (try uninstalling and riinstallarli maybe installing some toolkit - gnextoolkit or Nexus Root Toolkit)
bk201doesntexist said:
running what? 4.0.1, 4.2.2? ....
have you updated ADB/android-sdk?
To root a Nexus "manually", you just need fastboot, a custom recovery, and a superuser or supersu flashable zip. you don't even need ADB (if the zip flashable has been copied to /sdcard/ before)
Click to expand...
Click to collapse
Maxmaximus said:
Premise not to use almost never win7 ... I still tried for the first time tonight sdk-platform-tools on windows and adb and fastboot commands work normally ... the phone must have the bootloader unlocked (otherwise fastboot does not work ) is launched from the promt with administrator privileges and inside the folder where resides and the phone must be in fastboot / bootloader mode to acknowledge the command but also the drivers for the Nexus should be properly installed (try uninstalling and riinstallarli maybe installing some toolkit - gnextoolkit or Nexus Root Toolkit)
Click to expand...
Click to collapse
Bootloader is unlocked. The phone is not the problem, I was able to unlock, root and push updates and ROMs in another computer. I just can get the commands to work in my computer. I tried doing any of this procedures with Wug's toolkit, and that does not work either.
At the risk of sounding silly, do you have usb debugging enabled?
bodh said:
At the risk of sounding silly, do you have usb debugging enabled?
Click to expand...
Click to collapse
Yes
Sent from my Galaxy Nexus using xda premium
Try another USB cable and/or port, and be sure you are running ADB with admin privilege.
Sent from my Galaxy Nexus using xda app-developers app
diobando said:
Bootloader is unlocked. The phone is not the problem, I was able to unlock, root and push updates and ROMs in another computer. I just can get the commands to work in my computer. I tried doing any of this procedures with Wug's toolkit, and that does not work either.
Click to expand...
Click to collapse
sounds like a problem with the toolkit not being updated.
considering you just said you got it to work on your pc with command prompt.
Zepius said:
sounds like a problem with the toolkit not being updated.
considering you just said you got it to work on your pc with command prompt.
Click to expand...
Click to collapse
Sorry, I had a typo. I meant I can't in "I just can get the commands to work in my computer..."
Hi, I have a rooted Desire 816 currently running unofficial CM12. Before this, it will detect my phone, and thats how I root it and install custom recovery, but now, I tried to go back to stock but I couldn't get adb to work. It kept saying ADB error no device found.
Any help? I've already installed the HTC driver, same. Went to fastboot mode, on the phone it says fastboot USB but nothing happened.
In CM12 did you go into developer settings and enable adb?
yes i did. and it even showed up in the status bar. but still the same.
brightivan said:
yes i did. and it even showed up in the status bar. but still the same.
Click to expand...
Click to collapse
Then you don't have the proper drivers. You know adb and fastboot are different right? The rooting process doesn't involve adb, only fastboot. They're separate things and require separate programs to work.
Yes. But fastboot not working either. It's stuck at <waiting for device> and I can't lock the bootloader or flash the firmware.
brightivan said:
Yes. But fastboot not working either. It's stuck at <waiting for device> and I can't lock the bootloader or flash the firmware.
Click to expand...
Click to collapse
Try to redownload fastboot, and uninstall then reinstall the HTC drivers. If that doesn't work your screwed.
Try this, its a program that tethers internet from your phone to your pc. It has all the drivers you can possibly need. I use it when I cant find the drivers to my phone online. Friends use this when adb devices dosnt show up with anything. Its worked for me 100% of the time. http://pdanet.co/ (just download the windows exe file and follow the directions. I believe you have to keep your phone plugged in during installation but I cant remember)
brightivan said:
Hi, I have a rooted Desire 816 currently running unofficial CM12. Before this, it will detect my phone, and thats how I root it and install custom recovery, but now, I tried to go back to stock but I couldn't get adb to work. It kept saying ADB error no device found.
Any help? I've already installed the HTC driver, same. Went to fastboot mode, on the phone it says fastboot USB but nothing happened.
Click to expand...
Click to collapse
How about this. Put a nandroid of stock on your device. Plug it in the PC and create a folder called "clockworkmod" then inside there create one called "backup" now usually you have to move your nandroid to the root of your phone but if you use Philz Recovery, you can change the directory it searches for backups so it will be on your regular internal memory.
Drew recommended a flashing program for recoveries before. It was called Rashr.
Use that to flash Philz recovery.
Then just flash the nandroid and boot up.
Now remove root, flash a stock recovery, then relock your bootloader. Factory restore afterwards and your done.
Also, make sure if you factory restore that your nandroid backup never used titanium backup to remove any system apps as it might make your device act out with force closes. If you have done that either find a full stock with just root backup or use an RUU.
Done.
Sent from my 710C using XDA Free mobile app
macieksoft said:
Try this, its a program that tethers internet from your phone to your pc. It has all the drivers you can possibly need. I use it when I cant find the drivers to my phone online. Friends use this when adb devices dosnt show up with anything. Its worked for me 100% of the time. http://pdanet.co/ (just download the windows exe file and follow the directions. I believe you have to keep your phone plugged in during installation but I cant remember)
Click to expand...
Click to collapse
I have used one very seemed to pdanet and it has given me good result, is called AdbDriverInstaller and is so simple as the telephone connects to pc route usb, to open AdbDriverInstaller and to install the drivers