[Q] Unable to connect to Mac w/ Remote Storages via File app - Motorola Droid Bionic

Hi everyone,
I appreciate any help you can give "the newbie" here.
I swear I'm not a total moron, but I can't get this to work. I've tried searching the forums and google, and I've found posts with similar problems, but no solutions. Until I can get another computer to test this on, I don't know if the problem is with my Droid Bionic (unrooted, running JB stock 4.1.2), or my computer (Mac OSX 10.8.3) or my modem.
I would LOVE to root my phone, but I can't even get the darned thing to connect to my computer through the file app!
The phone is on the same wifi network as my computer. Both have no trouble accessing the internet. Both can ping each other (packets sent and received fine). But I can't connect one to the other.
I turn on file sharing on my computer with SMB only
select a folder on my computer to share
Assign a user and password permission to access that folder
make sure permissions for that folder are set to read and write
then go to my phone, open the stock file app
Select "Remote Storages" and "add storage"
Then I enter the IP address for the computer
WORKGROUP for the domain name
The name of the shared folder
The user name and password
then I try to connect.
And I get an alert box on the phone that says
"Network Error
There is a problem in your network connection with remote host. Please repair your network connection and try again."
I'm doing everything that's obvious to do, so I'm guessing there's something "not obvious" that I'm missing. - Anyone here had a similar problem and solved it?
Some things I've tried:
Moving the shared folder to different directories including root, desktop, and "public folder" (each time I moved it, I removed it from the shared list and re-added it)
Creating a guest account and allowing it access to the shared folder - no password needed
Creating a 2nd admin account and allowing it access to shared folders (password)
Turning off computer's firewall
Seeing if I could connect through the computer and phone's browsers (no go!)
Lots of turning things on and off (sharing, users, permissions, wireless...etc.)
Gone into recovery mode on the phone and done a factory reset and wiped the cache partition.
When I check my modem's admin page, I can see both the computer and phone listed there as connected devices. The modem sees them both, and they can ping each other. Why the heck can't I connect them to each other?
Oh, and though I don't think this is relevant, when I connect via cable in USB Storage mode, I can see the internal and external cards on my Mac just fine. They both mount as drives and I can drag stuff back and forth. - Wish I could find instructions to root THAT way!
I finally get the nerve to try to root this and get it on TMobile, and I can't get past the part that should be a no-brainer!
Any help would be appreciated.
BB01
-------------
Editing on 1/8/14 to add that the problem may be related to a Samba issue in OSX Mountain Lion. I'm also wondering if it could be an issue with my modem, which is several years old. I'm going away for about a week so I may try this on a friend's computer. I'll report back WHEN I am successful with this (because I will be!)

Can't root through Mac Mountain Lion. Use Easy Root in VB
Replying to my own post, to follow up. I was unable to connect through samba on my mac running Mountain Lion, while at a friend's house. So the problem was not the modem, but my OS itself.
I'd read that Easy Root ( http://forum.xda-developers.com/showthread.php?t=2256439 ) using Virtual Box hadn't worked on a Mac, but I decided to try it anyway. I had to change one setting in Virtual Box from NVidia to "en1: Wi-Fi (AirPort)", and then the Easy Root worked flawlessly. When it got to the part about connecting the Bionic to the Remote Storage folder, I thought "Here we go... this is the part that won't work!" but with Easy Root running in Virtual Box, the bionic connected to the shared folder perfectly.
Mac users with Mountain Lion or above, use Easy Root in Virtual Box to root your Droid Bionic running Jellybean 4.1.2 (here's the link again: http://forum.xda-developers.com/showthread.php?t=2256439 ). I know there are posts by people who were able to root their droids through the Mac terminal, but I'm guessing they were on an older OS where smb still worked correctly.

Related

[Q] Nook, ADB problems

For some reason my nook won't show up in windows 7 device manager as anything but a storage device (both the nook and sdcard). It doesn't show up under "other hardware" like all the tutorials show. I am at a loss?
Should I reset my device (unroot, wipe clean, etc)? And try again or am I missing something.
I am looking to get ad hoc working and am stuck in the mud
Depending on what ROM you're running... you may need to go into nook color tools and toggle usb debugging mode... it is a known issue in some ROMs....
You may also need to edit %userprofile$\.android\adb_usb.ini so the only line in it is:
0x2080
anyone have problems in ubuntu 10.04 can't get it :'(
I figuered it might be that I had tried some different kerenels recently. I did eventually return to stock. I have toggled debugging mode to no avail.
I will follow the other instructions you provided and if all else fails wipe her clean and try that.
Thanks.
Sent from my rooted nook color using Tapatalk
I have the same problem and am using the stock kernal. I have even tried two different computers (one with Win 7 and the other with XP) and get the same result. The first time it I tried with XP it showed "NookColor" under Other Devices with a ? mark. In just a second, it reloaded Device Manager and would never showed up again. I have tried all suggestions including the USB Debugging toggle with no positive results. By the way, I rooted using auto-nooter 3.0 for Nook Version 1.1. Everything seems to work well and I am using ADW Laucher EX. I am familiar with ADB as I used it root my Motorola Droid. In that case, I had no problems with it seeing my Droid.
Any suggestions would be helpful. I also have Ubuntu on a test computer that I may try if no solutions are found.
[email protected] said:
anyone have problems in ubuntu 10.04 can't get it :'(
Click to expand...
Click to collapse
I had the same issue in Ubuntu 10.04. My Evo would show up fine. My NookColor I could not get to show up though. No matter what I tried (I tried all the walk throughs on forums, Nookdevs.com, etc).
I finally just gave up. I've just been moving APK's from my Evo to my Nook to install them. There are many other things I'd wish to do through ADB other then install apps though so I may give it another shot sometime soon.
If it worked in some ROM versions and not in others... you need to check the device ID in windows device manager... get the PID for the device listed.... then you will need to add the device PID to the .inf file for the drivers so it will know to use the drivers that work for the "new" device (not really new.. just HWID change in some new kernels/ROMs
I had a world of trouble getting getting my computer to recognize the nook so that ADB would recognize the device. I mean HOURS of debugging.
However.. good news!... The answer that can help you is...: screw it and just download adbwireless app. All you do is run the app while connected to your home network and then on your computer run the the command "adb connect 192.168.1.xxx:5555" and you are connected and can run adb just like you were USB'd up
I hope this helps
Recommend installing the easy ADB install for Windows from the developers forum.
On Win7, sometimes you need to force the driver to use "USB Composite device" or "Android composite USB device", even after doing the easy ADB installer above.
Managed to get ADB working after Autonooker 3.0, Nook 1.1
Hi, All,
I had similar problems. I managed after a bit of fuss on my mac to get ADB up and running.
The main problem seemed to be getting USB debugging working. I went into nook color tools, from ADW launcher. I went to All Settings : Development, and saw that USB debugging was checked, but I didn't believe it was running.
So, I unchecked both Auto Mount (to simplify what the heck was going on over USB) and USB debugging, and hit back, to save the settings. Then I went back into debugging, and re-checked USB debugging.
Then, I made sure that ~/.android/adb_usb.ini contained the line:
0x2080
I killed the adb server and restarted it, and voila, ADB.
Hope this helps some folks.
Dave
I am in the same boat, adb works fine on my other android device, but won't see my nook for anything.
I have tried every permutation I have seen of the rules file, still nothing.

Honeycomb adb not recognizing my nook

installed easyadb, drivers seem fine but when I type "adb devices" I get nothing under devices listed. I've read a bunch and tried several different things concerning usb debugging and different drivers, nothing seems to be working.
Thanks.
EDIT - It finally connected but I have no idea why. Is there anything I can do to make this less of a PITA?
here is what worked for me
Had the same issue on windows 7.
Took days for me to figure this out.
Clue was one time when i connected the nook, the add hardware popup reported an error. I looked at the details, which by the way, showed up behind my other windows. It stated that B & N Nook Color..., USB Mass... and USB Composite... installed correctly, but a device named NookColor did not.
So the fix i figured out was to open the android_winusb.inf file in the C:\android-sdk-windows\usb_driver folder and add
;
;NookColor
%SingleAdbInterface% = USB_Install, USB\VID_2080&PID_0002
%CompositeAdbInterface% = USB_Install, USB\VID_2080&PID_0002&MI_01
;
under the [Google.NTx86] and [Google.NTamd64] sections.
Note: I don't believe that the lines with the single ; mean anything other then to make the file more readible. you should make every effort to keep the file neat, orderly and easy to read though. You should be able to figure out the simple patern in the ini file.
Make sure that you have the .android folder and adb_usb.ini file with the 0x2080 contents in your user directory. (easily found in windows explorer and adding it is detailed in almost all instructions to get ADB set up)
Next step was to connect the nook via usb if not connected. Delete all of the devices with HW id which have the first value of USB\VID_2030&PID_002&REV_0216&MI_00. There could be 1 to 3 listed as USB Composite Device, USB Mass Storage Device under Universal Serial Bus Controllers, and Android Coposit ADB Interface under Adroid Phone.
I ran adb kill-server from the cmd line at this point. this is a good trick if at any point your having a problem replacing or editing anything in the .android folder.
Unplug the nook usb and (i like to wait a few seconds) plug it back in. windows should start to reconize and add the device.
when windows is finished being windows, you can check if this succeded by runing adb devices from the cmd line. If it is successful your device serial number should be listed.
If not successful delete all of the devices mentioned above from device manager. unplug the nook and reboot. When windows finishes booting up, try to plug in the nook again.
If that doesn't work I suggest deleting the any of the 3 devices from device manager again, check that the .android folder is there and contents are correct, make sure the android_winusb.inf has the changes recommended above, disconnect nook, reboot and plug in nook again. As this is windows, rebooting often isn't a bad idea either.
Hope this helps the weary Nook HC nobe as i am one. Keep pluging away.
Also if you get this working check out the root forum. I'm still trying to figure the fax speak out myself but it looks like the next step.
http://forum.xda-developers.com/showthread.php?t=953110
Edit: above instructions worked for me. my faxspeak is getting better. errrermmmmmeerrebeeep.
Do the nebe group a favor as well and if you figure something out post it to the general forum.
After you make all those device edits, do you always get adb or can you turn off debugging in nook color tools and get the usb mode for regular transfers?
Just Tested
doncaruana said:
After you make all those device edits, do you always get adb or can you turn off debugging in nook color tools and get the usb mode for regular transfers?
Click to expand...
Click to collapse
I think your asking can you browse the nook HC folders from a PC the same way you can browse BN media folder when you connect the usb, so for instance you can drag and drop files onto your nook HC. i'm assuming your dual booting eggclair and HC.
My goal for getting adb working was to get su, which i got here http://forum.xda-developers.com/showthread.php?t=953110 with a bit of trouble but seems to work, so that i could drag items from my pc onto HC. I'm using http://forum.xda-developers.com/showthread.php?t=952456 to mount the media directory. I now seem to have su installed and the USM app is working. i only see my BN media directory from my pc now (yay) but i can't browse that directory from my nook HC (boo). So i can't share files between eggclair and HC. I'm a noob to nook and newbe to linux, so i'm assuming it is a permissions issue but don't have enough knowledge on how to change them yet.
I did just test if i could use the same drivers to connect the rooted BN eclair and still access the drive from my pc and was successful. remember you have to unlock the BN eclair to access the drives.
ADB doesn't block access to the drives. you don't need to turn it off. HC v4 just doesn't have the right stuff yet to allow the mount. my guess is that it is mostly a linux filesystem, i'm guessing the media directory is a fat or windows filesystem and that is why you can mount and use from a PC.
i assume that if you just have rooted eggclair this ADB settup method should work, and it should still allow access to the BN media directory from your PC.
If that still doesn't work for you, I got mine to work under Win7x64 by removing everything with that VID in device manager and using the USB cable from my Evo. The Nook one had serious issues getting the composite ADB device.
Anyone found a solution for the Mac?
EDIT: Never mind. Found a solution here: http://nookdevs.com/NookColor_USB_ADB
Love the internet
My experiences with Adb has been a hit and miss kind of thing. Stopped trying to use it since there was not point in it.
I've been using the wireless adb app from the market without any issues.
I was having trouble setting up ADB but then just gave up via usb *being lazy that is all* and used the adbwireless app and had no problems at all

Help needed.... My Nook HD+ shows error during registration.

Hi friends, I got my Nook HD+ today(India). The first time I turn it on, it prompted to install a critical update. I connected it to my wifi network and it downloaded and updated fine. After updating, at the registration process it again checked for critical updates and from this time onwards it keep saying that
" Network Problem: A network-related error occurred. You may have lost connectivity to the local wireless network. Press continue and we'll try to test your connection"
When I press continue it shows " Checking connection" and then detect my wifi fine (Signal strength shows excellent). Then again when I click "continue with setup", this whole procedure is repeating. My Galaxy tab 2 and Laptop are working fine with the same wifi network.
Please, some experts help me about what to do. I'm clueless about what to do next.
There is a known issue with the latest stock Nook firmware moaning about loss of wireless.
Are you able to skip these steps for the time being?
Otherwise I would suggest just flashing one of the Cyanogenmod firmwares instead.
Thanks for the reply artesea. No, I can't skip those steps. All it does is booting to the same procedure again and there is no option to skip. Is it worth waiting for this problem to get fixed by B&N? I really wanna experience the stock OS.
From what others are saying it looks like B&N might have a server down, once it's back up it should just start to work. However if the latest firmware is pointing in the completely wrong direction (IP or domain they don't own) then it might require a firmware patch. Not sure if the device will update if you aren't getting past the reg screens. But a flashable file should be available either direct from them, or someone on these forums.
Keep an eye on this thread where it was first reported
http://forum.xda-developers.com/showthread.php?t=2431280
Thanks artesea. One more question. Does doing the factory reset and turning off the wifi will allow me to use the device without registering?
mashac said:
Thanks artesea. One more question. Does doing the factory reset and turning off the wifi will allow me to use the device without registering?
Click to expand...
Click to collapse
There is a way to skip registration. Look at my HD/HD+ Tips thread linked in my signature and look for the item about skipping OOBE.
Sent from my Nook HD+ running CM10.1 on emmc.
Thanks artesea and leapinlar for the help. My Nook HD+ detected my wifi again out of nowhere and after another update I successfully registered my device. Thanks again guys.
Mine is doing the same thing on February 13, 2018. Really making me mad. Any help is appreciated.
Mine is doing the same thing and it was working fine until then I thought I had to do something with the nook itself so I factory reset it. Now it will not connect to my wifi at all I have even tried my hotspot on my phone but it didn't work. My nook has worked fine up until this point and I have had it for over 5 years. I know it has nothing to do with my battery because I just replaced it at the beginning of this year. It just makes me mad that it will not connect to my wifi.
Can't get past the 'Network Problem' error
I seem to have the same problem as the OP of this thread. I cannot get past a prompt on the stock ROM setup of my Nook HD+ where it says a network-related error has occurred. I'm connected to my home wi-fi just fine but setup will not go past this error. From what I've read it's caused by a security patch needing to be installed on the Nook. In the past, it updated automatically from an OTA update released by B&N but that is not happening any more. Have had it plugged in for days with no update occurring.
Have downloaded the patch file from B&N's website but I can't manually install it because Windows cannot recognize the Nook as a USB device. Have tried updating drivers, uninstalling/reinstalling the device in Windows but nothing works. If I could get that to work, apparently I can just drag & drop the file onto the Nook in Windows and it will install and update the Nook.
So, if anyone can offer a solution to my problem, it would be GREATLY appreciated. I went back to stock ROM because after trying Cyanogen & Lineage the Nook was just too slow to run either one successfully.
Solved: Right after I posted this, I found what is apparently a newer version of the stock ROM than I had previously installed. In case anyone needs this stock ROM it's in the [Stock][Android 4.0.4 ICS] Nook HD/Nook HD+ [Hummingbird/Ovation] 2.2.1 [2018 Update] thread. After installing it, setup went flawlessly and I'm back to full stock ROM. Thanks to secretwolf98 for posting this!
techfandan said:
I seem to have the same problem as the OP of this thread. I cannot get past a prompt on the stock ROM setup of my Nook HD+ where it says a network-related error has occurred. I'm connected to my home wi-fi just fine but setup will not go past this error. From what I've read it's caused by a security patch needing to be installed on the Nook.
Solved: Right after I posted this, I found what is apparently a newer version of the stock ROM than I had previously installed. In case anyone needs this stock ROM it's in the [Stock][Android 4.0.4 ICS] Nook HD/Nook HD+ [Hummingbird/Ovation] 2.2.1 [2018 Update] thread. After installing it, setup went flawlessly and I'm back to full stock ROM. Thanks to secretwolf98 for posting this!
Click to expand...
Click to collapse
I just got a secondhand Nook tablet 7" HD BNTV400 that the vendor has factory reset, and I'm stuck in the same loop:
"Select network/continue with setup/a network error has occurred/we'll test your connection/continue with setup/a network error has occurred" etc etc.
Can anyone point to the security patch that needs installing, based on the previous post and its solution? This tablet is factory reset, so no funky ROMs needed or anything. Thanks for any help or suggestions.
link to update barnes&nobles site
sumbodyelse said:
I just got a secondhand Nook tablet 7" HD BNTV400 that the vendor has factory reset, and I'm stuck in the same loop:
"Select network/continue with setup/a network error has occurred/we'll test your connection/continue with setup/a network error has occurred" etc etc.
Can anyone point to the security patch that needs installing, based on the previous post and its solution? This tablet is factory reset, so no funky ROMs needed or anything. Thanks for any help or suggestions.
Click to expand...
Click to collapse
http s: // help.barnesandnoble.com/app/answers/detail/a_id/1139/~/nook-hd%2Fhd%2B---software-version-2.2.1
(you'll need to put that url back together I don't have sufficient number of posts to insert links....)
the current download is 2.2.1 - you'll need to download to a computer I use an old windows xp laptop,cause it doesn't have problems recognizing
the usb connection when the nook is plugged into the computer. after the file is downladed from barnes&nobles,
you'll need to hookup to computer with your charging (usb) cable and copy the file
over to the root directory of the nook
as the instructions state, don't rename the file... it won't work..
NOOK HD/HD+ version 2.2.1 update is available as an automatic download to registered NOOK HD/NOOK HD+ devices connected to Wi-Fi (Wi-Fi should be turned ON and connected to a hotspot, and the device should be left in sleep mode).
To get the software update right now, be sure you are connected to a Wi-Fi hotspot, tap the Settings icon in the Status bar at the top of your screen, tap on All Settings, then tap on Device Information, and check to see that your Software version matches the number at the top of this page. If it does not, tap on Software version and then tap on the Check for updates button. Follow any on-screen instructions. Do not turn off your device while it is downloading or installing a software update.
To get the update manually, you can download the software update to your computer at any time and then copy it onto your NOOK HD. Simply follow the steps below.
The process will take about 15 minutes for a manual download (depending on the Internet connection for your computer). You should NOT turn your NOOK off while the new software is being downloaded.
Manual Download Instructions
1. From your computer, click here for the software update file. Select Save and select Desktop as the location.
Do NOT modify or change the downloaded file's name in any way. Do NOT try to open the file.
2. Tap the Settings icon in the Status bar at the top of your screen. Tap on All Settings, then tap on Device Information and make sure your NOOK battery charge is at 20% or more.
3. a) For Windows users: Connect your NOOK to your computer using the USB cable that came with your device. A new drive, named MyNOOK or BNTV400, should show up in My Computer. Open this drive and then open the Internal Storage folder within the drive.
From your computer, drag and drop the downloaded file onto the main directory of the Internal Storage folder. Do NOT open or unzip the file. You should not create a new folder on the NOOK drive or add the file to any other existing folder within Internal Storage.
b) For Mac users: Connect your NOOK to your computer using the USB cable that came with your device. A new, removable drive, named MyNOOK should appear on the desktop or in devices. Open the drive MyNOOK.
From your computer, drag and drop the downloaded file onto the top level of the MyNOOK drive. Do NOT open or unzip the file. You should not create a new folder on the MyNOOK drive or add the file to any other existing folder within the MyNOOK drive.
4. Eject or Safely Remove the NOOK drive after the file transfer is complete, and then disconnect your NOOK from your computer.
5. Your NOOK will automatically recognize the file after a few minutes when it goes into sleep mode, and proceed to install the updates.
6. Please do not turn off your NOOK during the installation process.
7. Once the installation is completed, your NOOK will automatically restart and go to the unlock screen.
8. Tap on the small "n" NOOK symbol that appears in the Status bar for additional information. The software has been successfully updated.
Your NOOK must remain turned on while the update is being installed. Once the software is installed, your NOOK will automatically restart. To verify you have the latest update, tap the Settings icon in the Status bar at the top of your screen, tap on All Settings, then tap on Device Information, and check to see that your Software version number matches the number at the top of this page.
Once the software update is completed, your NOOK will automatically restart. The software update will preserve your personal settings, including your registered account information, content, display settings, and Wi-Fi settings.
worked for me anyhow.....
sumbodyelse said:
I'm stuck in the same loop:
"Select network/continue with setup/a network error has occurred/we'll test your connection/continue with setup/a network error has occurred" etc..
Click to expand...
Click to collapse
I have the same issue but a slightly different end result. I'm in the same setup loop. The B&N help page says it needs the updated TLS info for security online. I can successfully download the proper file for my nook HD, but the help page says that it should connect as MyNOOK and that you only copy the file to that directory. My nook connects as BNTV400 and then shows a sub-directory of 'internal storage' like a camera would show up. Nowhere in the sub-directories is there a file or folder I can find called MyNOOK and that's not the name of the device when connected to my Win7 desktop or laptop. I spent a couple of hours exchanging messages with B&N via text chat last night and they finally gave up. I can't believe that mine is the only unit doing this.
So, in short, my nook successfully syncs with my computer(s) and I have successfully downloaded the needed TLS update file, I just don't know where to put it without potentially bricking the unit. Thanks in advance for any thoughts.
------- Edited to add -------
After posting the above message, I checked a few more places and ran across someone with the exact problem I had - the nook was recognized but showed the name as BNTV400, not MyNOOK. He just copied the file over anyway and it worked, so I decided to try that too. In Windows Explorer, I copied the "sideload_2_2_update.npk" file over to the top directory, shown as internal storage. I set the nook aside and, a few minutes later, I noticed it was rebooting. It then went though several onscreen updates to apps then let me move beyond the place where it was previously stuck and I was able to connect to the internet and complete setup. I wanted to post this for future searchers...
The Barnes and Noble Nook first generation e-reader is officially discontinued today. Customers are now unable to purchase new content, register with a BN.com account, or sign in using a NOOK account. Users will still have access to their purchased content and are able to continue sideloading ebooks. If you log out of your B&N account or perform a factory reset, you will lose everything.
Barnes and Noble decided to discontinue this device for two reasons. Firstly the original Nook came out in 2009 and many users have switched to a different e-reader. The second is primarily due to B&N implementing new security standards, known as Transport Layer Security (TLS). TLS Versions below 1.2 are being phased out, and devices accessing the Internet that are not updated to utilize the required TLS Version will not be able to perform many functions related to Internet connectivity. This is why the bookseller issued a new firmware update for all of their e-readers and tablets.

Solved [Q] How to copy files to my phone

Hi all,
the question seems simple, but I am unable to solve it, would be very grateful for somebody helping me out.
I have an unlocked HTC One
Bootloader is working, OS is upgraded to 2.24.401.1
Recovery is installed and working TWRP 2.6.1.0
When starting the phone, the system asks to connect to WiFi but does not find a network in the air, hence I am not able to continue that route.
When connecting it to a Windows PC, it is recognized, the usual "drives"are mounted as the drivers are installed.
I see the HTC One but it is read-only and a file cannot be copied to it.
I tried to use the adb push xxxx /storage command but this also says the system is read-only.
I just lack the knowledge on how to continue, I cannot flash a rom as it is not copied to the device.
Please be so kind to guide me in the right direction.
Ruud
When you connect the phone to the PC - the phone will show its connected on the top (notification bar) pull that down and select /USB connected then choose
HTC Sync Manager
Now connect the phone to the pc and it will be seen as a media devise open it and in root copy the rom and anything else you need
leave the phone with that setting then when you need to move photo, music, docs or whatever its is just a matter of finding the correct file and copy/paste
L0rdNels0n said:
When you connect the phone to the PC - the phone will show its connected on the top (notification bar) pull that down and select /USB connected then choose
HTC Sync Manager
Now connect the phone to the pc and it will be seen as a media devise open it and in root copy the rom and anything else you need
leave the phone with that setting then when you need to move photo, music, docs or whatever its is just a matter of finding the correct file and copy/paste
Click to expand...
Click to collapse
Thanks, but your explanation is for normal usage, as said, I had a read-only system, this did not work for me.
I understand that the command adb remount did the trick, after that at least adb was able to do its task.
Sent from my ASUS Transformer Pad TF700T using Tapatalk 4
Ruud Westerhout said:
Hi all,
the question seems simple, but I am unable to solve it, would be very grateful for somebody helping me out.
I have an unlocked HTC One
Bootloader is working, OS is upgraded to 2.24.401.1
Recovery is installed and working TWRP 2.6.1.0
When starting the phone, the system asks to connect to WiFi but does not find a network in the air, hence I am not able to continue that route.
When connecting it to a Windows PC, it is recognized, the usual "drives"are mounted as the drivers are installed.
I see the HTC One but it is read-only and a file cannot be copied to it.
I tried to use the adb push xxxx /storage command but this also says the system is read-only.
I just lack the knowledge on how to continue, I cannot flash a rom as it is not copied to the device.
Please be so kind to guide me in the right direction.
Ruud
Click to expand...
Click to collapse
Do you have USB debugging mode activated when you connect to a PC?
Also you can adb sideload a rom when you are in recovery.
Thanks farang4u,
As I said, Matt helped me out and the last Wipe Data which I did this morning was also the trick, so now all seem fine with my phone again.
Thanks all.

[Q] Can someone please help with USB connection?

Had another thread going about getting my Moto X from Sprint Rooted. I did get the bootloader unlocked, but the problem I have now is that when I plug in the device via usb, it only connects as a camera. I can't find the setting that makes the device look like a disk drive so I can push adb files and stuff to it.
I can't get the thing rooted to save my skin. I'm pretty sure I have the camera update, and I have rooted other devices. It used to be with the EVO 4g that when connected via usb, the device would give you options. I do have usb debugging enabled.
Is there a setting I'm missing?
Kidjoe, sorry for starting another thread but I think the inability to copy files to my device is the source of the problem. Was going to try PwnmyMoto first per the instructions, but all I get is that it shows up as a camera, not as a usb device.
Where's the setting I'm missing?
bullpen7979 said:
Had another thread going about getting my Moto X from Sprint Rooted. I did get the bootloader unlocked, but the problem I have now is that when I plug in the device via usb, it only connects as a camera. I can't find the setting that makes the device look like a disk drive so I can push adb files and stuff to it.
I can't get the thing rooted to save my skin. I'm pretty sure I have the camera update, and I have rooted other devices. It used to be with the EVO 4g that when connected via usb, the device would give you options. I do have usb debugging enabled.
Is there a setting I'm missing?
Kidjoe, sorry for starting another thread but I think the inability to copy files to my device is the source of the problem. Was going to try PwnmyMoto first per the instructions, but all I get is that it shows up as a camera, not as a usb device.
Where's the setting I'm missing?
Click to expand...
Click to collapse
you can push adb when the phone is connected as a camera. To connect it via ptp, you just scroll down your notifications bar and click on the usb notification, you can switch to ptp there. But like i said, adb works when connected as a camera device, so you are doing something incorrectly with adb. Possibly the commands you are running. The OS for your computer might be causing the problem (but that would mean oyu have the wrong stuff downloaded to adb with the computer set up you are using). You don't have the correct drivers. You are using a faulty data cable. you are using a usb 3.0 port that isn't compatible. it is an endless list. Also, you can copy stuff to your device in camera mode as well.
also would like to note that whether you phone is rooted or not has nothing to do with your ability to use adb or push files to your phone.
finally, this is a question which should go under q&a not the general discussion subforum.
I am able to plug phone in and get this:
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\xxxxxxxx>adb devices
List of devices attached
T063202TFL device
C:\Documents and Settings\xxxxxxxxx>
Right click on computer/manage and I see android phone in list of devices there.
I was able to use this same data cable to unlock the bootloader. If it were faulty, I don't think I could have done that.
I have tried both usb ports on front and back of the desktop unit, as well as those on a netbook I have in tow. Same result everywhere.
I don't know what to do next.
The thing that sucks is it has to be something simple.....
Seriously. I'd paypal someone to help me out here. I just can't imagine what's going wrong.
bullpen7979 said:
I am able to plug phone in and get this:
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\xxxxxxxx>adb devices
List of devices attached
T063202TFL device
C:\Documents and Settings\xxxxxxxxx>
Right click on computer/manage and I see android phone in list of devices there.
I was able to use this same data cable to unlock the bootloader. If it were faulty, I don't think I could have done that.
I have tried both usb ports on front and back of the desktop unit, as well as those on a netbook I have in tow. Same result everywhere.
I don't know what to do next.
The thing that sucks is it has to be something simple.....
Seriously. I'd paypal someone to help me out here. I just can't imagine what's going wrong.
Click to expand...
Click to collapse
so whats the problem. you have adb working. What do you mean you can't copy things to the phone. What error do you get when you try to push a file to the sdcard on the phone? You see your phone in the list of devices so you can put files on it that way too. Really confused at your dilemma.
you trying to root? you trying to push files to the phone? IDK, but you clearly should be able to push them if you have adb running. Perhaps you aren't running the right commands to push files to your phone.
Don't you have to have USB debugging on?
Sent from my XT1060 using Tapatalk
bullpen7979 said:
I am able to plug phone in and get this:
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\xxxxxxxx>adb devices
List of devices attached
T063202TFL device
C:\Documents and Settings\xxxxxxxxx>
Click to expand...
Click to collapse
Unless you have another android device connected to your computer, your X has USB Debugging mode turned on, and Windows & ADB properly sees your phone.
As jayboyyyy posted, in this state you can use ADB to push files from the PC to phone, or pull files from the phone onto the PC, assuming you are using the right commands. But if all you are looking to do is copy files back and forth, this is overkill as you can do it with windows. ADB is usually only need for hacking and flashing your phone.
As I said in the other thread... Please include what you were doing and what the results are. You haven't given us a complete enough of a picture to understand 1. what you are trying to do. 2. Any/all steps you have taken. 3. EXACT error message you are receiving.
From your first sentence in the original post in this thread you say you are rooted and have unlocked your boot loader. But your second paragraph starts saying you can't get the thing rooted to save you life.. So which is it? Are you rooted or trying to root? If you are trying to root, what process are you trying to follow? What step in that process are you stuck at? What did you type and what did you get back?
I know you are probably frustrated, but its just as frustrating on this side when you don't give a complete picture that allows us to help you. Look, rooting and hacking isn't easy. It can even result in turning your phone into a paper weight. So these details are important so we don't screw things up and add to the headaches and frustrations.
bullpen7979 said:
Right click on computer/manage and I see android phone in list of devices there.
I was able to use this same data cable to unlock the bootloader. If it were faulty, I don't think I could have done that.
I have tried both usb ports on front and back of the desktop unit, as well as those on a netbook I have in tow. Same result everywhere.
I don't know what to do next.
The thing that sucks is it has to be something simple.....
Seriously. I'd paypal someone to help me out here. I just can't imagine what's going wrong.
Click to expand...
Click to collapse
I'm not sure what you are doing, or trying to do, as you said in the first post that you unlocked the boot loader and rooted.
The Moto X wont show as a drive letter in "My Computer." Even if USB Debugging is on, it should show up as a "Media" device, or Player type device with an icon in a separate section from your hard drives, DVD drive, mapped network drives, or even USB memory sticks/flash drives. It does this because the X supports/uses MTP/PTP, and NOT USB MASS STORAGE MODE.
MTP/PTP wont show a drive letter in My Computer. This is by design. You don't have to "stop" or "eject" the phone from windows when you are done. This mode also allows the phone to access the "storage" or emulated "SD" partition at the same time a connected Computer can.
USB Mass Storage mode will give you a drive letter in My Computer, IF the phone supported it. However the X doesn't, at least not out of the box, and I'm unaware of any app or hack to enable this. In USB Mass Storage mode, the PHONE looses access its storage partition or emulated internal SD card while the PC is connected. You'd need to "stop" or "eject" the device when you want to disconnect form the PC in order to prevent data corruption of the "emulated SD"
So again, its important for us to know exactly what you are trying to do.
From your first sentence in the original post in this thread you say you are rooted and have unlocked your boot loader.
Im sorry I was unclear. Bootloader is unlocked, but I am not rooted. What I said was that I had another thread about getting it rooted.
I'm sorry for the mis-speak. And I'm sorry I'm being such a pain, but others in the thread I'm referencing are clearly having the same issue I am. I just need to know what to do to obtain root access if my bootloader is already unlocked. To be clear, I do NOT have root access.
This is my procedure.
Start with this link:
http://forum.xda-developers.com/showthread.php?t=2509676
Download Cydia Impactor. Check.
Download RockMyMoto.zip attachement. Unzip two files to directory x. Check.
Download PuTTYtel file "puttytel.exe" Check.
Step one. I have my ip address. At bottom of wireless config on phone, it is 10.59.1.6. So far so good.
I run adb shell getprop dhcp.wlan0.ipaddress just to be sure. same ip addy. Good.
I start command window. push the two files to the phone. all is well.
Step two i open the puttytel window and proceed to run the exploit
dalvikvm -cp /sdcard/RockMyMoto.jar RockMyMoto
and I can't run the damn thing because i get PuTTytel Fatal Error
Network Error: connection timed out.
exactly like this dude: http://dl.xda-developers.com/attach...f04a/5290120c/2/3/8/1/6/0/9/1384014224630.jpg
The end. I read the rest of the thread, and post #22 is the first of about five other posts that mentions the same time out problem, a solution for which is NEVER ADDRESSED, except indirectly as a possibility that the the two devices are not on the same network. My wireless card is on dhcp and the phone is the IP address above.
that's where it stops. I can't run the exploit because i can't type the command fast enough. Several people mention this problem, but I read all SIX pages of the thread and this defect is experienced my many and adressed by nobody.
This is driving me stark raving Bat S#!+ crazy.
And yes I have USB debugging on.
If your boot loader is already unlocked, there is another process.
https://plus.google.com/110773150384694258853/posts/VhtJtg92sTP
Is the process and while I think that twrp version should work, you might need the older version. Had to take my mom to the hospital so not in a good position to find older if newer doesn't work.
EDIT: this thread -> http://forum.xda-developers.com/showthread.php?t=2536200 has some discussion too

Categories

Resources