Develop Bugs

Device not recognized

I have a pretty big problem and need some guided help. My stock samsung usb charger sometimes charges the phone and sometimes does not. Tried multiple different chords and got the same results, sometimes works sometimes does not. So now I am assuming this is an internal hardware problem soo I decided I should flash stock images, unroot and relock the bootloader and here comes the worst problem.... My device is NOT recognized when I connect it to my PC... therefor I can't access adb connection to flash stock images so I can return it to VZW....
Not sure what to do next.. any suggestions would be great...

It sounds like you just don't have the drivers installed. Just install the Samsung drivers here.

mwalt2 said:
It sounds like you just don't have the drivers installed. Just install the Samsung drivers here.
Click to expand...
Click to collapse
I tried that. uninstalled the old ones (that worked for 3 months) reinstalled them again and still no luck..

Do you have any other Android processes running on your cpu? Droid Explorer or alike? Droid Ex **** blocks adb; I had a frustrating few minutes once when adb wouldn't connect to my device until I realized DE was running in the background.
Long shot, but just a thought.

This is actually a common hardware error. See http://code.google.com/p/android/is...ary Stars&groupby=&sort=&id=23789#makechanges and http://forum.xda-developers.com/showthread.php?t=1427539
Basicly you need to buy a new USB charging board.

chuckdz3 said:
and here comes the worst problem.... My device is NOT recognized when I connect it to my PC... therefor I can't access adb connection to flash
Click to expand...
Click to collapse
You mean fastboot

Melhouse said:
This is actually a common hardware error. See http://code.google.com/p/android/is...ary Stars&groupby=&sort=&id=23789#makechanges and http://forum.xda-developers.com/showthread.php?t=1427539
Basicly you need to buy a new USB charging board.
Click to expand...
Click to collapse
Yeah I believe that is what I am going to do, I just have to find the sch-i515 CDMA version because I am finding a lot of GSM versions out there right now.
bk201doesntexist said:
You mean fastboot
Click to expand...
Click to collapse
Sure. My adb command prompt does not recognize my device therefor I cannot execute any commands ei fastboot.

chuckdz3 said:
Sure. My adb command prompt does not recognize my device therefor I cannot execute any commands ei fastboot.
Click to expand...
Click to collapse
fastboot doesnt have anything to do with adb; boot your device into bootloader
'fastboot devices'
do you see your device?

bk201doesntexist said:
fastboot doesnt have anything to do with adb; boot your device into bootloader
'fastboot devices'
do you see your device?
Click to expand...
Click to collapse
I am in the bootloader and don't see 'fastboot devices' or do I see my device. I see the product name, variant, bootloader version, baseband version, etc. Would that be considered 'my device' being recognized and I could actually flash the stock images?

chuckdz3 said:
I am in the bootloader and don't see 'fastboot devices' or do I see my device. I see the product name, variant, bootloader version, baseband version, etc. Would that be considered 'my device' being recognized and I could actually flash the stock images?
Click to expand...
Click to collapse
fastboot is like adb. You need to run it from a command line. You should have had to use it when you installed a custom recovery ('fastboot flash recovery customrecovery.img') or unlocked your phone (ie 'fastboot oem unlock'). fastboot is part of the android sdk (think it's in tools folder, but I moved mine so am not sure).

mwalt2 said:
fastboot is like adb. You need to run it from a command line. You should have had to use it when you installed a custom recovery ('fastboot flash recovery customrecovery.img') or unlocked your phone (ie 'fastboot oem unlock'). fastboot is part of the android sdk (think it's in tools folder, but I moved mine so am not sure).
Click to expand...
Click to collapse
That's what my understanding of what it was too. I'm in the bootloader running a command prompt through windows and for the first time I think it recognized my devices. I ran 'fastboot devices' and a bunch of numbers on one line came up followed by fastboot. So I think my device is recognized and I can flash stock images?

chuckdz3 said:
That's what my understanding of what it was too. I'm in the bootloader running a command prompt through windows and for the first time I think it recognized my devices. I ran 'fastboot devices' and a bunch of numbers on one line came up followed by fastboot. So I think my device is recognized and I can flash stock images?
Click to expand...
Click to collapse
yes, you can download the images for your device from google and flash them to your phone using fastboot if you want. I'm pretty sure that would put you back at stock with an unlocked bootloader.

@op, next time read how to flash/get back to stock before flashing anything. there must be like a dozen of topics in xda about this ****.

bk201doesntexist said:
@op, next time read how to flash/get back to stock before flashing anything. there must be like a dozen of topics in xda about this ****.
Click to expand...
Click to collapse
I know how to. It was just your demeanor and wording/phrasing that had me confused.

I have the same problem, fastboot was working this morning, now after flashing Revolution HD, typing "fastboot devices" in CMD doesnt return anything anything, neither does adb push command which replies failed to copy .... As if the phone doesnt exist or its not attached. Does the phone need to be in clockwork mod? or just boot the phone normally?
Edit: This should do the trick, open CMD in Windows, navigate to your c:\android where you have fastboot and adb stored and type:
:cd %:h
adb kill-server
adb reboot bootloader

brooklynite said:
I have the same problem, fastboot was working this morning, now after flashing Revolution HD, typing "fastboot devices" in CMD doesnt return anything anything, neither does adb push command which replies failed to copy .... As if the phone doesnt exist or its not attached. Does the phone need to be in clockwork mod? or just boot the phone normally?
Edit: This should do the trick, open CMD in Windows, navigate to your c:\android where you have fastboot and adb stored and type:
:cd %:h
adb kill-server
adb reboot bootloader
Click to expand...
Click to collapse
*facepalm*

Make sure USB debugging is turned on.
Sent from my Galaxy Nexus

mentose457 said:
Make sure USB debugging is turned on.
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
*facepalm*

Melhouse said:
*facepalm*
Click to expand...
Click to collapse
Did I say something stupid?

mentose457 said:
Did I say something stupid?
Click to expand...
Click to collapse
debugging has nothing to do with it.
Windows XP absolutely HATES the samsung galaxy nexus.
The don't play along and it's almost impossible to get the drivers (especially MTP) installed correct.
Fortunately I have a W7 BEAST rig at home.. But the work XP pc can't handle the Nexus

[Q] Semi-bricked Nexus and not sure what to do

So I made a mistake and I tried to flash the newest aokp build 3 without a backup. I got my new phone a while back and never made a backup.
I flashed build 3 and (accidentally) some old gapps and I kept getting stuck on the Google screen.
Next I tried pushing files through the Gnex tool kit and manually through fastboot. I keep getting errors that there is no insecure boot or that the device is not connected. attempts at a temporary insecure boot on the tool kit fail.
Next I tried a wipe and then just installing build 3 without google apps so I could add the correct one after boot, but it is again stuck.
So now I'm really not sure what to do. Any suggestions?

Rule number 1 : STOP using toolkits!!
now, can you get into cwm recovery?

Yes, I can gt into twrp everything I did except for trying to push the last files was through twrp
by the way, I have a Verizon Nexus
And as a side comment: The tool kit was used as a last ditch effort. The toolkit had nothing to do with bricking the device. The toolkit has been extremely useful for unlocking and rooting multiple devices quickly.

You could eithther try to flash back to stock or you could boot into TWRP & adb push a different ROM. (You did try Wipe Data / Factory Reset right?)

MK17 said:
Yes, I can gt into twrp everything I did except for trying to push the last files was through twrp
by the way, I have a Verizon Nexus
And as a side comment: The tool kit was used as a last ditch effort. The toolkit had nothing to do with bricking the device. The toolkit has been extremely useful for unlocking and rooting multiple devices quickly.
Click to expand...
Click to collapse
I think what thegtfusion was trying to say was: if you wouldn't have used a toolkit in the past, you would have known how to fix your bootloop.
Buy anyway:
1) Boot into recovery and plug into your PC
2) Open a command prompt (in the folder where you have adb.exe and fastboot.exe)
3) Push the ROM (and kernel if it doesn't come with it) you want to flash to your device: adb push /path/to/ROM.zip /sdcard/
4) Reboot into fastboot mode
5) Erase your old ROM: fastboot erase system
6) Erase your old kernel: fastboot erase boot
7) Reboot into recovery
8) Wipe /data and /cache
9) Flash your ROM & kernel in recovery
10) Reboot. Done.
EDIT: Ninja'd by 3rdstring!

Screwing up is part of the learning process. It's actually a great way to learn how your phone really works.

Thanks for the reply. For some reason I can't get my device to be recognized on my new computer. I downloaded drivers, adb and fastboot and rebooted everything but it didn't work. I'll have to retry again on my other computer tomorrow.

MK17 said:
Thanks for the reply. For some reason I can't get my device to be recognized on my new computer. I downloaded drivers, adb and fastboot and rebooted everything but it didn't work. I'll have to retry again on my other computer tomorrow.
Click to expand...
Click to collapse
Try uninstalling all drivers and reinstalling them.
Sent from my Galaxy Nexus using xda premium

Drivers

Thanks for the drivers. I uninstalled all of the drivers and used the universal one. Everything seems to work until I run 'adb devices' and my Galaxy Nexus is not listed.
I feel that my device is not getting seen because of something I have wrong, but after adb, fastboot, and the correct drivers I'm not sure.
PS - Even with the universal driver I still have to run adb and fastboot from the original directory that I installed them correct? I don't run them from the driver in anyway correct?

MK17 said:
Thanks for the drivers. I uninstalled all of the drivers and used the universal one. Everything seems to work until I run 'adb devices' and my Galaxy Nexus is not listed.
I feel that my device is not getting seen because of something I have wrong, but after adb, fastboot, and the correct drivers I'm not sure.
PS - Even with the universal driver I still have to run adb and fastboot from the original directory that I installed them correct? I don't run them from the driver in anyway correct?
Click to expand...
Click to collapse
did you install android-sdk (and added adb/fastboot to your $PATH) or are you using binary versions of adb and fastboot downloaded elsewhere?
if it's the latter, commands should be run from the directory where you extracted them.
about the drivers, i think you need to go to device manager and update drivers manually to the ones you installed (refered here in the post before mine), assuming you're on windows.
sent from my i9250

You're booted into TWRP when trying adb?

Fixed! I ended up booting into recovery and the device was recognized in adb there. I was able to push fresh copies of aokp build 3 and gapps (my original build 3 download started failing) and now I just got done initiating swagger!

MK17 said:
Fixed! I ended up booting into recovery and the device was recognized in adb there. I was able to push fresh copies of aokp build 3 and gapps (my original build 3 download started failing) and now I just got done initiating swagger!
Click to expand...
Click to collapse
he didnt have usb debugging on.
sent from my i9250

Just for understanding, USB debugging is only activated through recovery?

It's also under settings >> developer options so you can use adb while the android is running.

3rdstring said:
It's also under settings >> developer options so you can use adb while the android is running.
Click to expand...
Click to collapse
Of course,but that is hard to get to when your phone doesn't boot

MK17 said:
Of course,but that is hard to get to when your phone doesn't boot
Click to expand...
Click to collapse
USB Debugging needs to be enabled in Android for ADB to work in Android.
CWM and TWRP have USB Debugging enabled by default, so ADB will work fine in recovery with no other action from the user.

[Soft Brick] No OS Installed

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

Problems rooting, adb etc.

Hello, I've tried rooting my Nexus 7 (2013) with LTE for like 5 hours now...
I've done every single thing in every single thread, and I still can't do ****.
I've tried the WugFresh root toolkit, but that did not work at all for me, I uninstalled and remove what they told me to do... But nothing worked, when I followed the WugFresh toolkit I lost usb mass storage... N7 did not appear at all on my computer, which it did, before I tried to screw with it...
I've tried doing it the manual way too, downloading all the drivers, uninstalling the other onces first.. But nothing... I could not even get the device listed in adb! I tried the full driver installation thing + automatic check if everything worked out, but the tablet would NOT run the script to reboot it into fastboot, and when I tried to restart the tablet into fastboot, and then continue to run the toolkit, it would start TWRP, the popup on my computer told me to flash something "!flashready", but I could not find it in the sdcard...
I unlocked the n7 manually, holding the volume button and power button down.
I know that was very bad written, but I'm a bit in a hurry. Anything I could do?

Potetsjokolade said:
Hello, I've tried rooting my Nexus 7 (2013) with LTE for like 5 hours now...
I've done every single thing in every single thread, and I still can't do ****.
I've tried the WugFresh root toolkit, but that did not work at all for me, I uninstalled and remove what they told me to do... But nothing worked, when I followed the WugFresh toolkit I lost usb mass storage... N7 did not appear at all on my computer, which it did, before I tried to screw with it...
I've tried doing it the manual way too, downloading all the drivers, uninstalling the other onces first.. But nothing... I could not even get the device listed in adb! I tried the full driver installation thing + automatic check if everything worked out, but the tablet would NOT run the script to reboot it into fastboot, and when I tried to restart the tablet into fastboot, and then continue to run the toolkit, it would start TWRP, the popup on my computer told me to flash something "!flashready", but I could not find it in the sdcard...
I unlocked the n7 manually, holding the volume button and power button down.
I know that was very bad written, but I'm a bit in a hurry. Anything I could do?
Click to expand...
Click to collapse
So the current condition of your device is that ADB is nonfunctional but you are able to temporarily boot into TWRP with fastboot - is this correct?

Username invalid said:
So the current condition of your device is that ADB is nonfunctional but you are able to temporarily boot into TWRP with fastboot - is this correct?
Click to expand...
Click to collapse
Yes, that is correct, temporarily, with the toolkit I mentioned. But I do not find the files that the toolkit tells me to flash

Potetsjokolade said:
I've tried doing it the manual way too, downloading all the drivers, uninstalling the other onces first.. But nothing... I could not even get the device listed in adb! I tried the full driver installation thing + automatic check if everything worked out, but the tablet would NOT run the script to reboot it into fastboot, and when I tried to restart the tablet into fastboot, and then continue to run the toolkit, it would start TWRP, the popup on my computer told me to flash something "!flashready", but I could not find it in the sdcard...
I unlocked the n7 manually, holding the volume button and power button down.
Click to expand...
Click to collapse
I'm not sure what this means. If you're using a toolkit, you're not doing it manually. Have you tried ADB and fastboot alone, without a toolkit? Is TWRP on your phone now? If so, you're done; just flash from recovery 1) a ROM for a custom ROM or 2) SuperSU.zip for just root.
If you don't have TWRP, does your Google boot screen has a locked icon at the bottom? If so: for ADB to work you need to have debugging turned on in your phone's developer settings. You don't need ADB though; just reboot into the bootloader by holding power and volume-down. Then type "fastboot devices" and see if anything shows up.
If it's an unlocked icon, just flash a recovery.img from fastboot.

bananagranola said:
I'm not sure what this means. If you're using a toolkit, you're not doing it manually. Have you tried ADB and fastboot alone, without a toolkit? Is TWRP on your phone now? If so, you're done; just flash from recovery 1) a ROM for a custom ROM or 2) SuperSU.zip for just root.
If you don't have TWRP, does your Google boot screen has a locked icon at the bottom? If so: for ADB to work you need to have debugging turned on in your phone's developer settings. You don't need ADB though; just reboot into the bootloader by holding power and volume-down. Then type "fastboot devices" and see if anything shows up.
If it's an unlocked icon, just flash a recovery.img from fastboot.
Click to expand...
Click to collapse
Tried both manually with adb, and with WugFresh toolkit. I got WugFresh to run TWRP temporarily.

Potetsjokolade said:
Yes, that is correct, temporarily, with the toolkit I mentioned. But I do not find the files that the toolkit tells me to flash
Click to expand...
Click to collapse
The toolkit is using the command
Code:
fastboot boot openrecovery-twrp-2.6.3.0-deb.img
to temporarily boot it over the stock recovery. Since you unlocked your bootloader manually, you can replace the stock recovery manually too using
Code:
fastboot flash recovery openrecovery-twrp-2.6.3.0-deb.img

Username invalid said:
The toolkit is using the command
Code:
fastboot boot openrecovery-twrp-2.6.3.0-deb.img
to temporarily boot it over the stock recovery. Since you unlocked your bootloader manually, you can replace the stock recovery manually too using
Code:
fastboot flash recovery openrecovery-twrp-2.6.3.0-deb.img
Click to expand...
Click to collapse
How can I do that when my N7 does not show up on
adb devices
Click to expand...
Click to collapse
Getting "waiting for device"

Potetsjokolade said:
How can I do that when my N7 does not show up on
Click to expand...
Click to collapse
Fastboot is separate from ADB. Your fastboot is working if the toolkit is able to boot TWRP.
Code:
fastboot devices
is what you use while your device is in the bootloader.

Username invalid said:
Fastboot is separate from ADB. Your fastboot is working if the toolkit is able to boot TWRP.
Code:
fastboot devices
is what you use while your device is in the bootloader.
Click to expand...
Click to collapse
Great! I'll try that, just upoading openrecovery-twrp-2.6.3.0-flo.img to dropbox, just in case I'm able to flash it from download/

Potetsjokolade said:
Great! I'll try that, just upoading openrecovery-twrp-2.6.3.0-flo.img to dropbox, just in case I'm able to flash it from download/
Click to expand...
Click to collapse
openrecovery-twrp-2.6.3.0-flo.img is for the WiFi model. TWRP for the LTE model is openrecovery-twrp-2.6.3.0-deb.img.

Username invalid said:
The toolkit is using the command
Code:
fastboot boot openrecovery-twrp-2.6.3.0-deb.img
to temporarily boot it over the stock recovery. Since you unlocked your bootloader manually, you can replace the stock recovery manually too using
Code:
fastboot flash recovery openrecovery-twrp-2.6.3.0-deb.img
Click to expand...
Click to collapse
Where in windows should I paste openrecovery-twrp-2.6.3.0-deb.img, so I can then flash it? It showed up in fastboot devices
EDIT: Nevermind that stupid question

Potetsjokolade said:
Where in windows should I paste openrecovery-twrp-2.6.3.0-deb.img, so I can then flash it? It showed up in fastboot devices
Click to expand...
Click to collapse
C:\Program Files\WugFresh Development
Then in toolkit > Advanced Utilities > Launch CMD Prompt > "fastboot flash recovery openrecovery-twrp-2.6.3.0-deb.img"

Username invalid said:
C:\Program Files\WugFresh Development
Then in toolkit > Advanced Utilities > Launch CMD Prompt > "fastboot flash recovery openrecovery-twrp-2.6.3.0-deb.img"
Click to expand...
Click to collapse
Flashed custom recovery + superSU
Thanks guys... Could you help me solve the problem where Nexus 7 wont show up on "my computer"? :laugh:

Potetsjokolade said:
Flashed custom recovery + superSU
Thanks guys... Could you help me solve the problem where Nexus 7 wont show up on "my computer"? :laugh:
Click to expand...
Click to collapse
What do you see if your computer Device Manager with USB Debugging on?

Username invalid said:
What do you see if your computer Device Manager with USB Debugging on?
Click to expand...
Click to collapse
It's connected as MTP, USB Debugging is on, and it does not show up on My Computer as Nexus 7
However, if I connect it as as PTP, it will show up.

Potetsjokolade said:
It's connected as MTP, USB Debugging is on, and it does not show up on My Computer as Nexus 7
However, if I connect it as as PTP, it will show up.
Click to expand...
Click to collapse
I've never had that problem so I can't speak from experience.
http://forum.xda-developers.com/showthread.php?t=2428061&highlight=mtp
http://forum.xda-developers.com/showthread.php?p=44219641#post44219641

ultra fail... root process

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