Hope this isn't a post that will really piss everyone off, but I'm not sure really where to go from here. Tried about 20 times. I run the loop command, it shows up for about 1 line and goes away.
I am still getting an Android 1.0 error of some sort. I've been reading about how to get this driver installed correctly. I uninstalled everything and started over (USBDeview, HTC Sync...The one for the Slide, SDK, Updated it with SDK Updater)
Windows 7 x64
Just went to Computer> right click> Manage> ABD Testing Interface....
I have a little yellow exclamation point next to this... Tried updating the driver. Not really sure though what driver I need or where it's at or the place I need to download it.
You ever feel like you've surfed cyberspace to the end of the megacluster? Yeah that's pretty much where I'm at frustrated, broken hearted, and wanting a one-click root procedure like the g1/mytouch.
Is it rude to wave money in developers faces for help? Does this make you feel like a stripper?
Ahhhh I'm just stuck.... Help would be so awesome.
I'm not a dev but I do feel like a stripper, but for unrelated reasons... Anyways. On my win7 64 I had to use pdanet and actually have the program running. For whatever reason when I tried closing pdanet it wouldn't work, so give that a shot. It also stopped the android 1.0 driver issues. I also gather from wes garners' twitter page he's working on a method of rooting that runs the adb scripts and **** for you. Maybe just wait it out.
Sent from my T-Mobile myTouch 3G Slide using Tapatalk
DaemionIX said:
Fermunky, I've been following your problem because I was having it too. What finally got it for me was, I formated a different sd card, put it in the phone, removed all software ( htc sync, pdanet) and removed all drivers I could find using usbdeview. Then rebooted with phone unplugged, installed pdanet following all their instructions, then the loop worked perfect. Good luck
Tl;dr version, i tried it all at the same time and it worked
Click to expand...
Click to collapse
That was on a win x64 system. Honestly I think it was the sd card, as weird as that sounds, because I tried all the usb stuff for about 4 hours to no avail, swapped out the sd card, rooted the first try.
I'll give all this a try. Do you use PDANet with or without HTC Sync? I was pretty tired last night when I tried and eventually gave up.
Hence all the stripper references.
I have an extra SD Card from my original Mytouch. I'll give it a try and let you know how it goes.
2Noob4U said:
I'll give all this a try. Do you use PDANet with or without HTC Sync? I was pretty tired last night when I tried and eventually gave up.
Hence all the stripper references.
I have an extra SD Card from my original Mytouch. I'll give it a try and let you know how it goes.
Click to expand...
Click to collapse
Just pdanet
Alright I'll give it a whirl. I'll let you know how it goes.
-------------------------------------
Sent via the XDA Tapatalk App
Took me a day to figure this out too. Uninstall all the drivers then install pda net and reboot .. you must reboot .. then try the process . I wasn't rebooting after removing drivers and it wouldn't work until I did ..
-------------------------------------
Sent via the XDA Tapatalk App
You should really have looked at the other thread on this already. Any driver will work, as long as you can get "adb devices" to show your phone when the phone is booted normally. Whats worked for many others, especially myself after 4 days of trying, was using a different, freshly formatted SD card. Good luck.
To no avail!
Just tried again. Tried without rebooting the computer the first time and "offline" would hang for a little longer than before. Still wouldn't stay. Should I have tried recovery a few more times? (I did try about three times.)
Uninstalled and reinstalled everything. Then tried "loop". "offline" doesn't even show up. Tried an old SD card too after I reformatted it. Does it matter the size of the SD card?
fermunky- I've been following your posts pretty regularly and I think I'm having the same problem. Yes I do have ADB devices showing up if the phone is on normally and running through the SDK. Had a problem for a while where it wouldn't recognize the device, but it does now.
C:\>cd android\tools
C:\Android\tools>adb devices
List of devices attached
HT05PPS07559 device
If I do figure this out I want to post up a step-by-step in this thread of what exactly I did to make it easier on people like myself.
It goes like this
C:\Android\tools>adb devices
List of devices attached
C:\Android\tools>GOTO TOP
C:\Android\tools>adb devices
List of devices attached
C:\Android\tools>GOTO TOP
C:\Android\tools>adb devices
List of devices attached
HT05PPS07559 offline
C:\Android\tools>GOTO TOP
C:\Android\tools>adb devices
List of devices attached
HT05PPS07559 offline
C:\Android\tools>GOTO TOP
C:\Android\tools>adb devices
List of devices attached
HT05PPS07559 offline
C:\Android\tools>GOTO TOP
C:\Android\tools>adb devices
List of devices attached
HT05PPS07559 offline
C:\Android\tools>GOTO TOP
C:\Android\tools>adb devices
List of devices attached
HT05PPS07559 offline
C:\Android\tools>GOTO TOP
C:\Android\tools>adb devices
List of devices attached
HT05PPS07559 offline
C:\Android\tools>GOTO TOP
C:\Android\tools>adb devices
List of devices attached
C:\Android\tools>GOTO TOP
C:\Android\tools>adb devices
List of devices attached
Is there a way to catch it offline?
It is a hit or miss deal. Some times it works, some times it doesn't. I ran into the issue while rooting mine and just kept at it till I succeeded. One plus is that after you root you never have to worry about it not detecting the device properly.
sk8rbebop said:
It is a hit or miss deal. Some times it works, some times it doesn't. I ran into the issue while rooting mine and just kept at it till I succeeded. One plus is that after you root you never have to worry about it not detecting the device properly.
Click to expand...
Click to collapse
Am I doing it right overall though.
1. Switch out SD card right before getting into recovery so there is absolutely nothing on the SD Card. (I've noticed if you let it boot it puts a LOS.DIR file or something of that sort.
fermunky had a similar problem and said once he installed everything a certain way he got it "offline" right away.
Is there a step-by-step I should be trying? Maybe another post I haven't read yet?
I'll keep trying, but it's kind of seeming like a lost cause. I've only been trying 2 days (Ha ha) After I surpass 4 days or so I'll give up and wait for Wes for the hook up.
Money for him!
Ultimate fix for device detection!!!
Uninstall EVERY driver (USBdeview) for anything android, i mean everything.
Installl HTC SYNC for espresso(any other software, PDAnet, Android Explorer.... needs to go). Dont let any drivers install while the phone is on!
Power off the phone and then plug your usb into it (phone needs to be usb debugg on and in sync mode).
Boot phone into the bootloader and the only driver it will install is the ADB driver which , without loop or multiple recovery boots or anything the phone will be detected.
I tried EVERY method in these forums and this worked perfect , went straight to pushing files, and only took 20 minutes to get it all the way to slidemeroot2. works great and everytime i need clockwork i can push the update without the problem of the device not being detected even after all the other drivers installed when i rebooted the phone. It seems that the other drivers were killing the adb function???? dunno, but i no longer have an undetected device, ever!
Also, i suggest if you want to get back into clockwork easily, plug in the phone while in normal operation mode and the adb reboot recovery that joker.
Hope this helps some, and thanks to all that have gotten us this far.
Thanks
mtjnkee said:
Uninstall EVERY driver (USBdeview) for anything android, i mean everything.
Installl HTC SYNC for espresso(any other software, PDAnet, Android Explorer.... needs to go). Dont let any drivers install while the phone is on!
Power off the phone and then plug your usb into it (phone needs to be usb debugg on and in sync mode).
Boot phone into the bootloader and the only driver it will install is the ADB driver which , without loop or multiple recovery boots or anything the phone will be detected.
I tried EVERY method in these forums and this worked perfect , went straight to pushing files, and only took 20 minutes to get it all the way to slidemeroot2. works great and everytime i need clockwork i can push the update without the problem of the device not being detected even after all the other drivers installed when i rebooted the phone. It seems that the other drivers were killing the adb function???? dunno, but i no longer have an undetected device, ever!
Also, i suggest if you want to get back into clockwork easily, plug in the phone while in normal operation mode and the adb reboot recovery that joker.
Hope this helps some, and thanks to all that have gotten us this far.
Click to expand...
Click to collapse
Haven't tried this yet.
Do it in a few hours. I've been at this all day and need some food and beer! Beer always makes computer/smartphone problems disappear.
sorry to be "that guy" but there are already 5 threads about this issue also, there is a questions and answers thread that this should have been posted in instead.
Straight to "recovery" not "offline"!
Ok is this good or bad? It's not what the video nor website says, but it's different and different is good!
Just lists the HT........ recovery over and over??? Can I start everything from here?
Dude if this works I'll buy you a beer!
I'd be glad to move it.
HighRidas said:
sorry to be "that guy" but there are already 5 threads about this issue also, there is a questions and answers thread that this should have been posted in instead.
Click to expand...
Click to collapse
No biggie man. Just wanna figure it out and you can move this at will if you like.
If you have it in recovery, hit volume up and power. It should display the recovery menu. Try pushing the update file over.
-------------------------------------
Sent via the XDA Tapatalk App
sk8rbebop said:
If you have it in recovery, hit volume up and power. It should display the recovery menu. Try pushing the update file over.
-------------------------------------
Sent via the XDA Tapatalk App
Click to expand...
Click to collapse
Tried... It wouldn't push said failed
Then it is an issue with your PC. Do what mtjnkee said and uninstall everything Android. Then use HTC Sync's drivers.
Related
Hey guys I an having the darnest time root this guy should be easy with these one clickers programs.
Pretty sure its a driver thing, note I can see the device when in cmd and doing the adb devices that shows up. just gets hung up at the end there.
attached a pic of what the cmd line looks like
anybody have the current drivers, googling for them just yields me to forum posts asking where the drivers are
thirty views and nothing
ok its not a driver issue if your loading root.sh (the big block of text) the issue is that the adb server isnt starting back up in time in order for your device to be recognized. solution? open up the bat file and copy and paste the commands one at a time; or if you have a linux/osx computer try doing it there with my scripts in my sig
couple ideas..
1.open up the run.bat file in notepad or similar and go through all the commands manually, that way you have control on speed of commands and allow enough time for adb to startup again.
2. open up the run.bat file and increase the wait time in the script.. -w 3000 or something like that..
i would suggest you do commands manually. The one-click root did not work for me but doing things manually worked right away.
How to do it
Hey man this is how I got it to work. I was having all the problems device not found etc etc. Have been trying since Sunday. What I finally did after installing the drivers was restart the computer and Phone. After that i tried to run the program it failed with device not found again so i unplugged the usb cable from the phone and closed the cmd window. And also brought up Task manager and killed the adb.exe process. then i reran the run.bat file and this time when it gets to the adb restart relogin apart i killed the SMALLEST ADB.EXE IN THE PROCESS TAB OF TASK MANAGER and that is when it finally got it to work. Had to do the same when I tested it with the uninstaller. So that seems to work. If anyone has any questions feel free to pm me.
But thank god it finally worked.
David
other people have done this and it worked for them also.
I tried all kinds of stuff ultimately I ended up using an xp machine. I later remembered the whole xp mode in windows 7 but didn't actually try it ... win7 just gave me a hard time although the post about changing the amount of time to restart adb makes sense
Sent from my SPH-D700 using XDA App
will try all of that thankyou gents
Ok I've researched this to death and tried in on both Windows 7 and osx 10.6.6 to attach using adb and install a couple of .apk's and the same thing happens on both platforms - NOTHING :-(.
You would think this would be pretty basic, but I am missing something somewhere.
Summary:
1. Am running the stock rooted b&n rom.
2. Can access both the internal and SD cards on the nook on both windoze and
osx. Eliminates cables, drivers etc...
3. Debug is selected in the nookstools settings
On both OSX and Win 7 installed the latest version of the Android SDK - both installs provided me with the platform-tools directory from which I will initiate all adb commands. So far so good...
on mac: ./adb devices returns:
$ ./adb kill-server
$ ./adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
$
As you can see I never get any device information returned, does not matter if Im on Windows or mac - same response.
Just for grins I downloaded the wireless app and tried to connect adb that way...no luck...
I could go into everything that i have tried over the last 24 hours...but that would also be pointless.
Bottom line...assuming this is something simpleI am just missing. Assuming since the symptoms are the same on both platforms that the issue lies on the nook but for the life of me I cannot find it.
Assuming if I cannot figure this out I will slowly go insane..my next step is to flash either froyo or honeycomb rom and see if this helps with the problems. Of course I MUST have the market available to me or I will not b able to load any .apk's.
Hpe Im in the right place. Any guidance is GREATLY appreciated.
Love this little Nook....BG
I know this will sound stupid, but I had this same problem and the only way I found to fix it is to adb while I have the superuser app running.
YMMV, but it solved that issue fo me.
Who Swami - It Worked
Swami,
I fall to my knees and bask in your knowledge: It WORKED!
I knew it was something simple, there is not a post on the entire Internet in any forum I have ever found (and I may have searched them all!) that mentions superuser needs to be running for adb to be able to communicate with the device. I wonder if this is a nook issue only. Will test on my wife's Epic this evening and post the results tonight.
My sanity now restored I bid you all a hearty SEE-Ya!
-BG
Omg I actually helped someone!
Glad it worked for ya I'm sure you felt the same relief I did when I finally stumbled across that fix.. I was pulling my hair out for hours LOL
Thanks Once More
As was I such a simple fix you would think I would have thought about permissions on the client side , such is life and tech thats why we all hang together.
Must say I was going to purchase the iPad 2 when it came out (NEVER buy 1st gen Apple) but now I'm not so sure...LOVING my Nook.
themirthfulswami said:
I know this will sound stupid, but I had this same problem and the only way I found to fix it is to adb while I have the superuser app running.
Click to expand...
Click to collapse
I'm not sure if this is related but I *think* that what made it work for me was to freshly enable the Debugging USB mode immediately before connecting the USB cable. Maybe that also triggered the Superuser app??? It's always the small things in life that make us smile
my problem is a little different.... I have sd cards with honeycomb (no market) and froyo (market and other apps). I can see the NC in adb with both, but honeycomb shows the device offline... and adb cannot talk to it. froyo show the device online and I can use adb. Both honeycomb and froyo show up in windows too.
I can't find anything that talks about getting the NC to show online to adb.
Same Problem
I have the same problem of trying to get my nook recognized. The only thing I can see different between my setup and the instructions on NookDevs was that they said I should see Android ADB Composite Interface on my Device Manager. Mine reads Android ADB Interface.
Tried the Superuser and the USB Debugging with no luck. Just really trying to get this set up so in case I need to factory reset. Because the 8x method manually is way too hard.
Have you guys read though this thread?
http://forum.xda-developers.com/showthread.php?t=910008&highlight=ADB
it worked for me like a charm.
that thread didnt work for me..
i tried lots more ways. just not able to get my nook (running honeycomb) online.
adb devices
just shows a serial code and says offline.
what do i do?
i want to install the G-apps.
I had intermittent ADB success with my Mac. After installing the ADB Wireless app there have been no problems.
Seaweedbrain said:
that thread didnt work for me..
i tried lots more ways. just not able to get my nook (running honeycomb) online.
adb devices
just shows a serial code and says offline.
what do i do?
i want to install the G-apps.
Click to expand...
Click to collapse
nvm
i connected my nook to the back of the cpu.
for some reason, it seemed to work fine.
it read the device as online.
got the g-apps
Ok... first off im a noob to this forum but I know this is a legitimate issue not user error and ive spent the last 4 days scouring to get SOME information on this and the only thing ive found is remove battery and reset phone... HELLO!!!! thats step one on the list... sorry venting done...
Device: mytouch 4g
OS: Windows 7
When I got this phone i plugged it in and ran with no issues until i tried to root it without success... and when i tried the ADB method i found that the phone would no longer mount into windows 7 i have tried multiple computers and multiple cables so it's a device issue.
When I plug my phone into a computer it comes up with "searching for drivers" and fails... look in device manager and it says "Windows has stopped this device because it has reported problems. (Code 43)"
Tried manually finding drivers and can't...
Tried "repairing" the install of HTC drivers that came off the HTC website and didn't work...
Tried installing PDA net to get different drivers... didnt work
uninstalled devices and get the same issue...
deleted upper and lower filters from registry
Tried every combination of fastboot/USB debug
even tried desperatly deleting cookies/cache/web history(found on another forum)
AND NOTHING WORKS...
if you can think of anything I haven't tried it would be nice
Currently installed Apps that may be involved
Visionary
Super User
Terminal Emulator
I would like to help you out but need to what rom is on your device and what exactly your trying to do on windows
Sent from my HTC Glacier using XDA Premium App
It's running the complete stock rom... i believe it's called espresso... and all im trying to do with it right now is get it to show up in windows as a hard drive...
usually I would assume a driver issue (thats what windows thinks it is) but I've reinstalled the drivers around 10 times desperately and restored my computer to no avail so i think when i tried to root it the first time it flashed the usb firmware... if thats complete bs then just let me know... new to android... not new to computers...
sky2k-y2k said:
It's running the complete stock rom... i believe it's called espresso... and all im trying to do with it right now is get it to show up in windows as a hard drive...
usually I would assume a driver issue (thats what windows thinks it is) but I've reinstalled the drivers around 10 times desperately and restored my computer to no avail so i think when i tried to root it the first time it flashed the usb firmware... if thats complete bs then just let me know... new to android... not new to computers...
Click to expand...
Click to collapse
For a Hard Drive
1lug your phone into the computer
2:On your phone, drag the top slider bar down to the bottom
3:There should be a notification that says charge only. Click on that and select Disk Drive, Mount as disk drive. Click that
Try that and let us know what happens.
Edit: If you are trying to use ADB you want to be on charge only and have USB debugging on . To get to debugging
Menu-settings-applications-development-USB debugging
yeah that was one of the first things I tried(i actually have that as default)... The problem is that my computer thinks its an unknown device when plugged in and I can't point it to the correct driver...
USB Debugging is enabled, correct?
Seems strange... have you even tried installing the driver on another computer?
I've tried debugging on and off...
And yes I've tried a different computer that was one of the second things I tried
Sent from my HTC Glacier using XDA App
sky2k-y2k said:
Ok... first off im a noob to this forum but I know this is a legitimate issue not user error and ive spent the last 4 days scouring to get SOME information on this and the only thing ive found is remove battery and reset phone... HELLO!!!! thats step one on the list... sorry venting done...
Device: mytouch 4g
OS: Windows 7
When I got this phone i plugged it in and ran with no issues until i tried to root it without success... and when i tried the ADB method i found that the phone would no longer mount into windows 7 i have tried multiple computers and multiple cables so it's a device issue.
When I plug my phone into a computer it comes up with "searching for drivers" and fails... look in device manager and it says "Windows has stopped this device because it has reported problems. (Code 43)"
Tried manually finding drivers and can't...
Tried "repairing" the install of HTC drivers that came off the HTC website and didn't work...
Tried installing PDA net to get different drivers... didnt work
uninstalled devices and get the same issue...
deleted upper and lower filters from registry
Tried every combination of fastboot/USB debug
even tried desperatly deleting cookies/cache/web history(found on another forum)
AND NOTHING WORKS...
if you can think of anything I haven't tried it would be nice
Currently installed Apps that may be involved
Visionary
Super User
Terminal Emulator
Click to expand...
Click to collapse
sounds like a driver issue... i am not a 100% but thats what i sounds like.. download and install this program.. it uses the correct drivers.. just make sure u select "HTC" when prompted.. http://junefabrics.com/android/download.php goodluck report back
i tried that already and after trying again (just now) it failed again... i wish this was a simple driver issue...
I might be totally off but try changing your sd card and see whether your computer accepts it.
Also when installing drivers make sure your device is not connected to the computer.
Or try different USB port, or a factory reset.
Sent from my HTC Glacier using XDA Premium App
nope... different sd card/different usb port/factory reset didn't do it...
sky2k, I had some driver issues with my mt4g too.
Try this:
Download USBDeview - http://www.nirsoft.net/utils/usb_devices_view.html
Download the drivers for your phone from HTC - http://www.htc.com/us/support/t-mobile-mytouch-4g/downloads/
Run USBDeview AS ADMINISTRATOR. List all drivers in alphabetical order. Remove any and all associated with your mytouch 4g.
Reinstall drivers via HTC Sync software. Please let me know how this works for you.
Try to connect the phone with both the SD and SIM cards removed.
well guys im still having issues connecting via USB... but...
I found something to let me connect to ADB via WIFI so using it I got everything pushed and I am now S-off... so I am extremely pleased... that said i would "like" to be able to plug in and mount the sdcard/run adb but if I cant i can deal with my work arounds...
Hey guys ive been pretty stoked to root and rom my g2 now that im bored of LG's UI haha i have been trying to use the IOroot method but something about the drivers is giving me such a hard time! i installed them but every time i open a command window and type in "adb devices" nothing is coming up so obviously its not being able to read my device which isnt alowing me to root my phone any help would be greatly appriciated! thanks in advance
I was having trouble, finally went to LG site to download drivers
Sent from my VS980 4G using XDA Premium 4 mobile app
adb is a special android thing. You need to install it to just use it anywhere. Do this:
1. Create a folder on your desktop (you can call it root or whatever you want).
2. Extract IORoot into folder created in step one.
3. SHIFT RIGHT CLICK and do "open command window here" (This is the most important).
4. type
Code:
adb devices
5. if you devices shows run the root.bat file to root your device.
Look at this for a little more help.
http://forum.xda-developers.com/showthread.php?t=2515978
djraimondi said:
adb is a special android thing. You need to install it to just use it anywhere. Do this:
1. Create a folder on your desktop (you can call it root or whatever you want).
2. Extract IORoot into folder created in step one.
3. SHIFT RIGHT CLICK and do "open command window here" (This is the most important).
4. type
Code:
adb devices
5. if you devices shows run the root.bat file to root your device.
Look at this for a little more help.
http://forum.xda-developers.com/showthread.php?t=2515978
Click to expand...
Click to collapse
IVe done this so many times haha... the problem is when i type that into the command window nothing comes up under listed devices and ive downloaded and installed the drivers from several different locations including the LG website... could it be the ethernet thing that im missing? because thats the only thing i dont believe ive done cause this is a hastle xD ive had no problems rooting in the past
Cyko.Tech67 said:
IVe done this so many times haha... the problem is when i type that into the command window nothing comes up under listed devices and ive downloaded and installed the drivers from several different locations including the LG website... could it be the ethernet thing that im missing? because thats the only thing i dont believe ive done cause this is a hastle xD ive had no problems rooting in the past
Click to expand...
Click to collapse
Do you have the phone listed correctly for what mode to be in when you plug in the USB cord???
hd-renegade said:
Do you have the phone listed correctly for what mode to be in when you plug in the USB cord???
Click to expand...
Click to collapse
i have tried both with Charge only mode and MTP
Cyko.Tech67 said:
i have tried both with Charge only mode and MTP
Click to expand...
Click to collapse
This is just a thought, but maybe, power the phone off, power the PC off. Turn them both back on, re-read the instructions on how to root the phone. It sort of sounds like you could be missing just a little thing on the instructions. You may also try a different USB port on your PC too. I rooted mine back on iRoot 6 so I would have to think that iRoot 10 should be better then what I used.
hd-renegade said:
This is just a thought, but maybe, power the phone off, power the PC off. Turn them both back on, re-read the instructions on how to root the phone. It sort of sounds like you could be missing just a little thing on the instructions. You may also try a different USB port on your PC too. I rooted mine back on iRoot 6 so I would have to think that iRoot 10 should be better then what I used.
Click to expand...
Click to collapse
I just dont think im installing the drivers right because ive tried everyone and their mothers usb ports and ive tired it on 4-5 computers there has to be something im missing with the drivers because the process just wont start Daemon will succsesfully start running than nothing...
Cyko.Tech67 said:
I just dont think im installing the drivers right because ive tried everyone and their mothers usb ports and ive tired it on 4-5 computers there has to be something im missing with the drivers because the process just wont start Daemon will succsesfully start running than nothing...
Click to expand...
Click to collapse
It has been a while sense I rooted mine, but I think the fix for me was getting the drivers from the LG Site and using the LG Flash tool.
hd-renegade said:
It has been a while sense I rooted mine, but I think the fix for me was getting the drivers from the LG Site and using the LG Flash tool.
Click to expand...
Click to collapse
whats the flash tool for?
I think I ended up flashing back to LG stock. Sorry it has been a while sense I played with that stuff.
Sent from my VS980 4G using Tapatalk HD
I had the same issue. I installed these lg drivers, not sure if they had anything to do with it because it still didn't work. What finally worked was when I turned off debug and may have been in mtp connection. Obviously after you have to put back in debug and ethernet connection to follow the ioroot method.
dp917 said:
I had the same issue. I installed these lg drivers, not sure if they had anything to do with it because it still didn't work. What finally worked was when I turned off debug and may have been in mtp connection. Obviously after you have to put back in debug and ethernet connection to follow the ioroot method.
Click to expand...
Click to collapse
alright one more question and thanks for the fast replies guys! i appriciate it but im not to nifty with computer tech as i am Smartphone xD laptops still have an ethernet mode correct? and if so where do i go to enable it?
Cyko.Tech67 said:
alright one more question and thanks for the fast replies guys! i appriciate it but im not to nifty with computer tech as i am Smartphone xD laptops still have an ethernet mode correct? and if so where do i go to enable it?
Click to expand...
Click to collapse
Ethernet mode is in enabled in your phone. Settings > scroll to bottom "pc connection."
dp917 said:
Ethernet mode is in enabled in your phone. Settings > scroll to bottom "pc connection."
Click to expand...
Click to collapse
awesome thanks so much guys a thanks to both of you ill try it when i get home and let ya know how it went
Cyko.Tech67 said:
awesome thanks so much guys a thanks to both of you ill try it when i get home and let ya know how it went
Click to expand...
Click to collapse
Let the folks here know how you make out.
hd-renegade said:
Let the folks here know how you make out.
Click to expand...
Click to collapse
unfortunatly with ethernet on i am still getting the same results... its just not recognizing my device? at least now in the notification bar i get the notification that USB debugging is on so i guess im making progress? uggh this is getting pretty annoying any thoughts guys?
Run it directly from local drive root. IE C:/ Windows 7? Control alt delete. End the stale adb process, you should see two, one not performing sitting around 2000 kb ram and the other using ram. End that and it should force adb to kick in. I had to do this on win 7 multiple times with dif phones. It's like it locks up when finding the com port or whatever the hell it's doing. I take no blame if you screw up your device this way. I have resorted to a virtual xp for all my phone needs as not everything works in Linux.
Here's how rooted my phone with IORoot:
Unzipped IORoot to root of my hard drive
Plugged in phone with usb (make sure debug mode is enabled). When prompted to choose connection, choose modem. You should see debug icon appear in status bar. If not, choose Ethernet.
Opened IORoot folder. Hold down shift and right click an empty area and choose 'open command window'
Type adb devices. If device shows up, proceed. With normal root procedure.
Steamer86 said:
Run it directly from local drive root. IE C:/ Windows 7? Control alt delete. End the stale adb process, you should see two, one not performing sitting around 2000 kb ram and the other using ram. End that and it should force adb to kick in. I had to do this on win 7 multiple times with dif phones. It's like it locks up when finding the com port or whatever the hell it's doing. I take no blame if you screw up your device this way. I have resorted to a virtual xp for all my phone needs as not everything works in Linux.
Click to expand...
Click to collapse
simon_lefisch said:
Here's how rooted my phone with IORoot:
Unzipped IORoot to root of my hard drive
Plugged in phone with usb (make sure debug mode is enabled). When prompted to choose connection, choose modem. You should see debug icon appear in status bar. If not, choose Ethernet.
Opened IORoot folder. Hold down shift and right click an empty area and choose 'open command window'
Type adb devices. If device shows up, proceed. With normal root procedure.
Click to expand...
Click to collapse
Not sure if it matters but I am running 64 bit Windows 8
- In the instructions didn't you have to change a setting for the Com Port to get it to see the phone??
- Did you ever get the prompt on your phone to accept the Connection. I can not remember what it was, but it only comes up once, and I am not referring to the USB connection IE Ethernet??
- Are you sure you have Developer Options turned on?? The step where you keep tapping on the Developer thing and then the phone finally gives you the Developer Options??
I can't believe I did it, must of accidentally deleted photo album. Stayed up for hours last night and all of this morning trying to find a way to recover the album. I have a bunch of my daughter's pics in that album and I really need them back.
I have a Nexus 4 with 4.4.2 loaded on it and the phone is not rooted. I have been trying to find a way to root the phone without wiping the data so I can try to use diskdigger to recover what I can. I don't know if there is a way with this version, but if there is and you know, please post. If you can show me a way and it is successful you will have some paypal money coming your way. Thanks in advance!
rboklewski said:
I can't believe I did it, must of accidentally deleted photo album. Stayed up for hours last night and all of this morning trying to find a way to recover the album. I have a bunch of my daughter's pics in that album and I really need them back.
I have a Nexus 4 with 4.4.2 loaded on it and the phone is not rooted. I have been trying to find a way to root the phone without wiping the data so I can try to use diskdigger to recover what I can. I don't know if there is a way with this version, but if there is and you know, please post. If you can show me a way and it is successful you will have some paypal money coming your way. Thanks in advance!
Click to expand...
Click to collapse
Perhaps the photos were somehow uploaded to your Google+ account?
A
scream4cheese said:
Perhaps the photos were somehow uploaded to your Google+ account?
Click to expand...
Click to collapse
They were to a point, but not like the last year
rboklewski said:
I can't believe I did it, must of accidentally deleted photo album. Stayed up for hours last night and all of this morning trying to find a way to recover the album. I have a bunch of my daughter's pics in that album and I really need them back.
I have a Nexus 4 with 4.4.2 loaded on it and the phone is not rooted. I have been trying to find a way to root the phone without wiping the data so I can try to use diskdigger to recover what I can. I don't know if there is a way with this version, but if there is and you know, please post. If you can show me a way and it is successful you will have some paypal money coming your way. Thanks in advance!
Click to expand...
Click to collapse
My first response would be to use disk digger like you said, but as much as rooting is a wonderful thing, I don't think it is needed in this case.
Disk digger is actually derived from a desktop app of the same name, that does the same thing with desktop and laptop hard drives.
Web page here
http://diskdigger.org/
If you connect your phone to your computer as external storage then you should be able to run the program on the computer but targeted at your phone, hence recovering your lost files.
Note: if this works then LOTS of files will be found, (including ones you never knew were even on your phone) so be prepared to search through them all.
I really hope this helps, I know what it is like to loose precious files, safe to say you should backup everything valuable from hereon
Let me know what happens either way and I will try and help if it does not work
Sent from my Nexus 4 using Tapatalk
captaindyson said:
My first response would be to use disk digger like you said, but as much as rooting is a wonderful thing, I don't think it is needed in this case.
Disk digger is actually derived from a desktop app of the same name, that does the same thing with desktop and laptop hard drives.
Web page here
http://diskdigger.org/
If you connect your phone to your computer as external storage then you should be able to run the program on the computer but targeted at your phone, hence recovering your lost files.
Note: if this works then LOTS of files will be found, (including ones you never knew were even on your phone) so be prepared to search through them all.
I really hope this helps, I know what it is like to loose precious files, safe to say you should backup everything valuable from hereon
Let me know what happens either way and I will try and help if it does not work
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
yeah, just tried the pc software for diskdigger, phone doesn't show in list. Has a advanced tab, but only lets you choose .vhd files it looks like. If only you could get the phone into a vhd.
OK, so the first question is if the phone is mounted correctly, does it show in 'my computer' and when double clicked on can you see files?
Next question is if you are using the .exe correctly, take a look at this tutorial: http://diskdigger.org/node/1025
I'm sorry if this sounds condescending, but I don't know your experience with computers
Sent from my Nexus 4 using Tapatalk
captaindyson said:
OK, so the first question is if the phone is mounted correctly, does it show in 'my computer' and when double clicked on can you see files?
Next question is if you are using the .exe correctly, take a look at this tutorial: http://diskdigger.org/node/1025
I'm sorry if this sounds condescending, but I don't know your experience with computers
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
LOL...no problem. Been a systems admin for about 10 years. Anywho, yeah, this is the nexus 4 so it only has internal memory, no sd card. I can see the phone in my computer, but there is no drive letter assigned, apparently that changed in 4.3 up through 4.4.2, which I am on. So what that means is no mass storage option where drive letter gets assigned, so routine recovery software can't read it as an attached drive.
rboklewski said:
LOL...no problem. Been a systems admin for about 10 years. Anywho, yeah, this is the nexus 4 so it only has internal memory, no sd card. I can see the phone in my computer, but there is no drive letter assigned, apparently that changed in 4.3 up through 4.4.2, which I am on. So what that means is no mass storage option where drive letter gets assigned, so routine recovery software can't read it as an attached drive.
Click to expand...
Click to collapse
Hmmm, you should still be able to mount as external storage, I have done so before on that android version.
First thing then is if USB debugging is enabled, this will be in your settings under developer options and should not require root.
Then it is a question of whether your computers drivers are correct, android has a tendency of not liking to do drivers correctly, I used PDAnet to install the correct USB drivers (note these are different to the ADB drivers which you don't need)
Get back to me with the results of those 2 points
Sent from my Nexus 4 using Tapatalk
captaindyson said:
Hmmm, you should still be able to mount as external storage, I have done so before on that android version.
First thing then is if USB debugging is enabled, this will be in your settings under developer options and should not require root.
Then it is a question of whether your computers drivers are correct, android has a tendency of not liking to do drivers correctly, I used PDAnet to install the correct USB drivers (note these are different to the ADB drivers which you don't need)
Get back to me with the results of those 2 points
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
Yeah, I had developer options enabled and USB Debugging mode on, maybe it could be a driver issue. I tried PDAnet and that didn't seem to update the drivers for the phone. The device shows okay in device manager, no exclamation point, shows as Nexus 4 as well and the driver seems to be a Microsoft driver. Are you sure you had the same android version? Everywhere I look any version after 4.2.2 cannot be used as a mass storage device because of the MTP-PTP change in 4.3 and 4.4.
rboklewski said:
Yeah, I had developer options enabled and USB Debugging mode on, maybe it could be a driver issue. I tried PDAnet and that didn't seem to update the drivers for the phone. The device shows okay in device manager, no exclamation point, shows as Nexus 4 as well and the driver seems to be a Microsoft driver. Are you sure you had the same android version? Everywhere I look any version after 4.2.2 cannot be used as a mass storage device because of the MTP-PTP change in 4.3 and 4.4.
Click to expand...
Click to collapse
I am on 4.4.3 now, and have the phone connected fine right now, have you tried switching between MTP and PTP?
Note: I am on MTP and it is working.
I am sure there is a problem with something to do with connecting your nexus to the computer, as mine is doing so right now. If we can resolve that issue and access the internal storage then you should be able to then recover the files with disk digger.
My best guess would be a driver issue as android has never really played well when trying to set up drivers. But like you said the computer is recognising it correctly. I think perhaps testing the drivers connection my be the next step, use ADB with the command 'adb devices' (without quotes) to see the devices connected to the adb server. If nothing comes up then we may be able to start troubleshooting :good:
Perhaps ADB is the difference, i have it installed and sorted, do you?
If you have never used ADB before, here is a good place to get started and here is another mention of the drivers, perhaps another attempt may be worth a try, with a clean intall
Safe to say in my drivers list it is connected under android device > android composite ADB interface.
Actually yes, thinking about what i have just written i am confident it is ADB and drivers, you should not be connected with Microsoft drivers, they are the automatically installed ones and never work. Follow the guides above (and perhaps some googling) to get the proper drivers and ADB set up, once you think you have test it with the 'adb devises' command, once you get it returning a serial number for your phone then take a look in 'My Computer' again and see if the storage is visible.
nexus 4 only support MTP, not USB Mass Storage, so can't be mounted with a drive letter and can't be used with undelete software . If you know any working solution without root - please tell us, but test first yourself before writing please
P.S. you are on 4.4.3 ?
RolF2 said:
nexus 4 only support MTP, not USB Mass Storage, so can't be mounted with a drive letter and can't be used with undelete software . If you know any working solution without root - please tell us, but test first yourself before writing please
P.S. you are on 4.4.3 ?
Click to expand...
Click to collapse
My most sincere apologies, i was mistaking the mounted MTP device for the mounted drive, i now see what you mean.
In this case rooting is your only option, you need to run the file recovery natively.
I had hoped that this would not be necessary as unfortunately the rooting process will perform a lot of write operations so you must be prepared for some of your images to become corrupted or incomplete, (hence why i wanted to attempt other options) this is just the risk that you will have to face. How many will be damaged is difficult to say.
So use one of the many tool-kits or root manually, install the disk digger APK and you are good to go.
to root you will need to unlock phone bootloader and that will wipe all your device ...