Hi,
I have been given an old Nook Glowlight that still has 1.2.1 on it.
I have tried NookManager but it won't connect to anything because its still on 1.2.1.
However, I can't update to 1.2.2 because when I connect it to my laptop via USB, nothing shows up in explorer etc.
No idea what to do next!
Does your PC go "bong" when you plug it in?
Do you see anything in Device Manager (devmgmt.msc)?
Is there ADB?
If you can find the old Noogie (for NST) and put it on an SD card you can boot on that.
Renate NST said:
Does your PC go "bong" when you plug it in?
Do you see anything in Device Manager (devmgmt.msc)?
Is there ADB?
If you can find the old Noogie (for NST) and put it on an SD card you can boot on that.
Click to expand...
Click to collapse
Nope, it doesn't do anything. I've tried it in a chomebook too, and that didn't see anything.
I'm very new to this, so not too sure what ADB is.
What is Noogie... sorry.
Moyni said:
I'm very new to this...
Click to expand...
Click to collapse
Ok, well, all this stuff is very old to me and I've forgotten some of it.
ADB is the way we transfer files and get access to a shell for all Android devices.
There are tutorials here somewhere, try searching.
CWM and Noogie are two different recovery images that you can run if you can't get what you want done in the regular system image.
I just dusted off my old NST but it needs charging. I forget which recovery I have on it.
I'm sure that @nmyshkin can get you started with the Nook Manager.
Renate NST said:
Ok, well, all this stuff is very old to me and I've forgotten some of it.
ADB is the way we transfer files and get access to a shell for all Android devices.
There are tutorials here somewhere, try searching.
CWM and Noogie are two different recovery images that you can run if you can't get what you want done in the regular system image.
I just dusted off my old NST but it needs charging. I forget which recovery I have on it.
I'm sure that @nmyshkin can get you started with the Nook Manager.
Click to expand...
Click to collapse
Thanks.
I've looked into ADB, but it assumes I can connect to the device via USB... which I can't.
I wonder if I could SSH into it, but again, I wouldn't know where to start.
Moyni said:
Thanks.
I've looked into ADB, but it assumes I can connect to the device via USB... which I can't.
I wonder if I could SSH into it, but again, I wouldn't know where to start.
Click to expand...
Click to collapse
NookManager has the option to start WiFi and use it to connect via ADB and SSH before doing anything else. You could copy the update over that way.
A perhaps bigger question is the integrity of the port. Can you charge the device? If so then you may just have a driver issue on your PC.
If you want to pursue the ADB angle at least to get started, I recommend the Minimal ADB and Fastboot package. Google that with XDA also and you'll find it.
nmyshkin said:
NookManager has the option to start WiFi and use it to connect via ADB and SSH before doing anything else. You could copy the update over that way.
A perhaps bigger question is the integrity of the port. Can you charge the device? If so then you may just have a driver issue on your PC.
If you want to pursue the ADB angle at least to get started, I recommend the Minimal ADB and Fastboot package. Google that with XDA also and you'll find it.
Click to expand...
Click to collapse
I tried SSH but the password won't work in order to get access, any ideas, "root" didn't work.
Managed to get it connected to my laptop, I tried an old £1 cable and that worked!!
Can't get it to update to 1.2.2 though. I copy the zip file into the device, put it into sleep mode, but nothing happens apart from the device deleting the file!!
So, I'm getting there.
As I'm in the UK, it looks as though the 1.2.2 update from the US site won't work on a UK device.
Before I go though the process of changing the region, does anyone know where I could download the UK version from?
Thanks.
Moyni said:
So, I'm getting there.
As I'm in the UK, it looks as though the 1.2.2 update from the US site won't work on a UK device.
Before I go though the process of changing the region, does anyone know where I could download the UK version from?
Thanks.
Click to expand...
Click to collapse
AFAIK there is no UK update. B&N basically abandoned the non-U.S. firmware devices, suggesting to users that they use them by skipping OOBE. That's a horrible suggestion that leads to decreased battery life and a frantically "busy" system that's always looking for something that's not there. Your best best is the region change followed by the update.
Moyni said:
Can't get it to update to 1.2.2 though. I copy the zip file into the device, put it into sleep mode, but nothing happens apart from the device deleting the file!!
Click to expand...
Click to collapse
You can manually install it. It will have no choice in the matter.
See: https://forum.xda-developers.com/showpost.php?p=83052867&postcount=5
Related
I can't get adb to work with my iconia to save my life... I've tried every driver out there to try to get the device recognized but I can't even get it connected to my computer. I have the mini usb cable and all, and I can copy/paste files into the tablet memory, but whenever I start adb it won't recognize it. How did you guys get yours set up? And I've connected my incredible via adb so I know my sdk kit is legit. Just let me know, thanks-
Oh, and: Iconia is rooted. Also, I've tried to start the device manager (i'm on win7 btw), locate the missing device driver, update driver, and navigate to where I got the acer driver from their website, but to no avail. Could it be my rom? I have a hc 3.1 on there atm. Well, that's about it haha
The ultimate goal is to install native ubuntu on the a500, but I need access to adb first.
officetally said:
I can't get adb to work with my iconia to save my life... I've tried every driver out there to try to get the device recognized but I can't even get it connected to my computer. I have the mini usb cable and all, and I can copy/paste files into the tablet memory, but whenever I start adb it won't recognize it. How did you guys get yours set up? And I've connected my incredible via adb so I know my sdk kit is legit. Just let me know, thanks-
Oh, and: Iconia is rooted. Also, I've tried to start the device manager (i'm on win7 btw), locate the missing device driver, update driver, and navigate to where I got the acer driver from their website, but to no avail. Could it be my rom? I have a hc 3.1 on there atm. Well, that's about it haha
The ultimate goal is to install native ubuntu on the a500, but I need access to adb first.
Click to expand...
Click to collapse
Hmm ... did you install the USB drivers from Acer's support site?
http://support.acer.com/product/default.aspx?modelId=3851
Another option with ADB is to do so via IP. Search the Market for 'adb' and there should be a few apps that will allow you to use ADB over TCP/IP. From your computer, with ADB installed, you'd connect with something like:
adb connect <Tablet's IP address>:<port>
I seem to think port 5555 is the default.
If, after trying this method, you still cannot access/see your tablet (assuming you started ADB services), then you may want to check your SDK.
Best of luck.
officetally said:
I can't get adb to work with my iconia to save my life... I've tried every driver out there to try to get the device recognized but I can't even get it connected to my computer. I have the mini usb cable and all, and I can copy/paste files into the tablet memory, but whenever I start adb it won't recognize it. How did you guys get yours set up? And I've connected my incredible via adb so I know my sdk kit is legit. Just let me know, thanks-
Oh, and: Iconia is rooted. Also, I've tried to start the device manager (i'm on win7 btw), locate the missing device driver, update driver, and navigate to where I got the acer driver from their website, but to no avail. Could it be my rom? I have a hc 3.1 on there atm. Well, that's about it haha
The ultimate goal is to install native ubuntu on the a500, but I need access to adb first.
Click to expand...
Click to collapse
This may sound silly, but have you gone into settings, applications, development, and checked "USB debugging" to on?
kjy2010 said:
This may sound silly, but have you gone into settings, applications, development, and checked "USB debugging" to on?
Click to expand...
Click to collapse
DUDE! Haha, why didn't I think of this?? Thanks a lot man, it worked!
looking335 said:
Hmm ... did you install the USB drivers from Acer's support site?
http://support.acer.com/product/default.aspx?modelId=3851
Another option with ADB is to do so via IP. Search the Market for 'adb' and there should be a few apps that will allow you to use ADB over TCP/IP. From your computer, with ADB installed, you'd connect with something like:
adb connect <Tablet's IP address>:<port>
I seem to think port 5555 is the default.
If, after trying this method, you still cannot access/see your tablet (assuming you started ADB services), then you may want to check your SDK.
Best of luck.
Click to expand...
Click to collapse
And please my op... of course I tried the drivers from acer's site, both of them. And my sdk kit works, just like I said. But thanks!
officetally said:
DUDE! Haha, why didn't I think of this?? Thanks a lot man, it worked!
Click to expand...
Click to collapse
Glad it was something simple!
Sometimes we always overlook the simple things.
But I would not have told on myself.to many other things could blame it on.giggles
Apologies if this is already posted somewhere. just point me to the link and I'll take a look, but everything I have tried so far has failed.
I have been trying to get adb working on my NookColor under Windows 7. I am running a rooted 1.4.2 stock image. I installed the sdk by following the guide at http://nookdevs.com/NookColor_USB_ADB, but when I get to step III.3.1, the device does not show up where the guide tells me it should. I gget a myNOOKcolor device under Portable Devices instead. I tried following the same procedure for this device, but when I get to step III.3.2.3, I get an error message saying "The folder you specified doesn't contain a compatible software driver for your device. If the folder contains a driver, make sure it is designed to work with Windows for x64-based systems."
I was able to follow the same procedure to install the driver for my MyTouch 4g. It looks to me like the problem s that Windows identifies my Nook as a portable storage device, rather than an unidentified device type, like my MyTouch was. I've tried uninstalling the driver, but it just reinstalls itself when I unplug and plug the device back in.
Any suggestions would be greatly appreciated.
marchingknight11 said:
Apologies if this is already posted somewhere. just point me to the link and I'll take a look, but everything I have tried so far has failed.
I have been trying to get adb working on my NookColor under Windows 7. I am running a rooted 1.4.2 stock image. I installed the sdk by following the guide at http://nookdevs.com/NookColor_USB_ADB, but when I get to step III.3.1, the device does not show up where the guide tells me it should. I gget a myNOOKcolor device under Portable Devices instead. I tried following the same procedure for this device, but when I get to step III.3.2.3, I get an error message saying "The folder you specified doesn't contain a compatible software driver for your device. If the folder contains a driver, make sure it is designed to work with Windows for x64-based systems."
I was able to follow the same procedure to install the driver for my MyTouch 4g. It looks to me like the problem s that Windows identifies my Nook as a portable storage device, rather than an unidentified device type, like my MyTouch was. I've tried uninstalling the driver, but it just reinstalls itself when I unplug and plug the device back in.
Any suggestions would be greatly appreciated.
Click to expand...
Click to collapse
I think the problem is the device id. I posted a workaround for CM9. It might be the same for your upgraded stock. See if my post helps. Look here:
http://forum.xda-developers.com/showthread.php?p=21665649
leapinlar said:
I think the problem is the device id. I posted a workaround for CM9. It might be the same for your upgraded stock. See if my post helps. Look here:
http://forum.xda-developers.com/showthread.php?p=21665649
Click to expand...
Click to collapse
Thanks for the post!
I looked at your workaround and it did not help. There is no nook entry under "Other Devices" in the device manager. the only entry for my nook is the "myNOOKcolor" under portable devices. When I right click on that and go to details, there is no device id listed.
Is there any chance that I may need to revert to 1.4.1 in order for this to work?
marchingknight11 said:
Thanks for the post!
I looked at your workaround and it did not help. There is no nook entry under "Other Devices" in the device manager. the only entry for my nook is the "myNOOKcolor" under portable devices. When I right click on that and go to details, there is no device id listed.
Is there any chance that I may need to revert to 1.4.1 in order for this to work?
Click to expand...
Click to collapse
With CM9, you have to be sure to have usb debugging turned on before the device will show up. That guide was written for an earlier version of the stock software. Is there anything like that in your stock software? Do you have to install nook tools to get at the setting? It's been a long time since I played with stock and the software has changed.
Edit: There is an alternate script listed in that referenced page you listed. Did you try that?
leapinlar said:
With CM9, you have to be sure to have usb debugging turned on before the device will show up. That guide was written for an earlier version of the stock software. Is there anything like that in your stock software? Do you have to install nook tools to get at the setting? It's been a long time since I played with stock and the software has changed.
Edit: There is an alternate script listed in that referenced page you listed. Did you try that?
Click to expand...
Click to collapse
I have trtied all the troubleshooting steps in that page, if that's what you mean. Nothing has worked for me so far. I have tried disabling automount and usb debugging, to no avail.
I guess I should ask a new question. If I create a bootable CM7/CM9 sd card, will I be able to copy apk's to /system/app on my nook? That is really the only reason I need adb to work, so I can install non market apps.
marchingknight11 said:
I have trtied all the troubleshooting steps in that page, if that's what you mean. Nothing has worked for me so far. I have tried disabling automount and usb debugging, to no avail.
I guess I should ask a new question. If I create a bootable CM7/CM9 sd card, will I be able to copy apk's to /system/app on my nook? That is really the only reason I need adb to work, so I can install non market apps.
Click to expand...
Click to collapse
Yes, but with difficulty. But you don't really want to install to /system, you want to install to /data (on emmc, which is the difficulty doing it from SD). You can use terminal emulator in CM7 to copy the files to emmc /data/apps. You first have to mount emmc /data. If you want to try that, I can help you.
Sent from my Nook Color running ICS and Tapatalk
leapinlar said:
Yes, but with difficulty. But you don't really want to install to /system, you want to install to /data (on emmc, which is the difficulty doing it from SD). You can use terminal emulator in CM7 to copy the files to emmc /data/apps. You first have to mount emmc /data. If you want to try that, I can help you.
Sent from my Nook Color running ICS and Tapatalk
Click to expand...
Click to collapse
Well something else actually occurred to me. Will I be able to copy apps to my sdcard (not the CM7 bootable, just a regular sd card), then copy them to /data/app using root explorer? If I can do that, there there's really no problem, I'll just have to deal with the fact that adb doesn't work.
If I can't do that, then yes, please help me do it using a bootable sd
marchingknight11 said:
Well something else actually occurred to me. Will I be able to copy apps to my sdcard (not the CM7 bootable, just a regular sd card), then copy them to /data/app using root explorer? If I can do that, there there's really no problem, I'll just have to deal with the fact that adb doesn't work.
If I can't do that, then yes, please help me do it using a bootable sd
Click to expand...
Click to collapse
If you have root explorer working on emmc, yes you can do it that way. You can actually have root explorer just install for you also.
Sent from my Nook Color running ICS and Tapatalk
Please use the Q&A Forum for questions &
Read the Forum Rules Ref Posting
Moving to Q&A
marchingknight11 said:
I have trtied all the troubleshooting steps in that page, if that's what you mean. Nothing has worked for me so far. I have tried disabling automount and usb debugging, to no avail.
I guess I should ask a new question. If I create a bootable CM7/CM9 sd card, will I be able to copy apk's to /system/app on my nook? That is really the only reason I need adb to work, so I can install non market apps.
Click to expand...
Click to collapse
I am using CM10 on my nook color after spending 8+ hours yesterday finally being able to get back to where I started. I can again see my nook and the card but it is now showing up under portable devices. I used to have them listed as drives. this is fine as I have access to the card after I click on the nook in File explorer. I would like it the previous set-up just because Calibre has my card and device flipped and its easy to confuse me. I learned that if I can label my nook f and the card g Calibre will think the first letter is the main drive.
My original reason for this post: I can not find where to disable the automount in CM10 can you tell me where you disabled it? and if anyone can wave their magic wand and get me back to where I can name my nook and card THANKS:fingers-crossed:
Droidatar said:
I am using CM10 on my nook color after spending 8+ hours yesterday finally being able to get back to where I started. I can again see my nook and the card but it is now showing up under portable devices. I used to have them listed as drives. this is fine as I have access to the card after I click on the nook in File explorer. I would like it the previous set-up just because Calibre has my card and device flipped and its easy to confuse me. I learned that if I can label my nook f and the card g Calibre will think the first letter is the main drive.
My original reason for this post: I can not find where to disable the automount in CM10 can you tell me where you disabled it? and if anyone can wave their magic wand and get me back to where I can name my nook and card THANKS:fingers-crossed:
Click to expand...
Click to collapse
You need to activate USB Mass Storage in CM10. It uses MTP by default. Go to settings, storage, menu, USB computer connection and check off Mass Storage rather than MTP. Then they show up as drive letters instead of under portable devices. You may also have to activate in the notification area.
And I think in Windows you can control what the drive letters are. Go to manage computer and select disk management and you can change the drive letters.
Sent from my Nook HD+ Running CM10 on SD
leapinlar said:
You need to activate USB Mass Storage in CM10. It uses MTP by default. Go to settings, storage, menu, USB computer connection and check off Mass Storage rather than MTP. Then they show up as drive letters instead of under portable devices. You may also have to activate in the notification area.
And I think in Windows you can control what the drive letters are. Go to manage computer and select disk management and you can change the drive letters.
Sent from my Nook HD+ Running CM10 on SD
Click to expand...
Click to collapse
THANK YOU, so very much it has been driving me crazy. I knew where that was to change it to mass storage but I just never guessed to hit menu. After I read your post I saw the tiny 3 dots in top right. I really should just wear my glasses
and Yes I have changed the letters in the past as you have noted. However it seems a mute point Calibre just released a new version that lets me correct that problem. However it's nice to have the mass storage issue fixed.
Thanks again
So I have a bit of an issue. Somehow last night, after trying to help my parents with our home theater system, with the device laying on a soft surface, the LCD (not the glass) somehow broke. I am really not sure how this happened, the phone itself didn't fall, it was laying on a bed the entire time. When I went to grab the phone and turn it on, I was pretty surprised. You can see what I mean in the attached file.
Now the problem with this is, while I would normally just walk into the Sprint Store, complain and get a new phone. I am not in the US for another 5 months. In the mean time of trying to figure out what to do, I would like to at the very least, grab any files off my phone, or back up my phones' file structure.
I am able to do a minimal amount of tapping on the phone, only on the upper half of the screen, but I can't see anything, nor does the device respond with any touch data from the bottom half.
I obviously can't access the files if the device is locked, which means I have to bypass the lock screen. I found this guide, but unfrotunately, Method 1 didn't work, and I can't get adb to recognize my phone for Method 2.
I also have tried using CWM (the non-touch version) to backup my data, but I let it sit there for 45 minutes and I couldn't tell if it was finished or not. It didn't appear to actually be doing anything.
Could someone help me navigate around this or provide some assistance in allowing me to just get the files off the phone while I search for a new one?
With that being said, does anyone have some recommendations? I was thinking of getting a Motorola X or Nexus 5.
EDIT: Update:
I have access to terminal via Cerberus shell. I was able to use Method 2 to disable the lock screen (or in this case set it to Swipe). It is still pretty difficult to use the phone but I can at least backup whatever data I still do have on the phone to my laptop.
Would anyone be able to give me some advice as to uninstall applications or XDA xposed modules via shell? Or perform a backup or enable ADB debugging?
You've conntected to your PC at least once so that the ADB has permission, correct? If so, you can get http://forum.xda-developers.com/showthread.php?t=2786395 to get Android Control and view/Control your phone via USB. You need to have Java installed, which most have already. Been controlling my cracked LCD for the past week while waiting for my replacement.
Keep in mind this method is a little slow because of ADB. Hopefully you don't have to type too much.
Darnell0216 said:
You've conntected to your PC at least once so that the ADB has permission, correct? If so, you can get http://forum.xda-developers.com/showthread.php?t=2786395 to get Android Control and view/Control your phone via USB. You need to have Java installed, which most have already. Been controlling my cracked LCD for the past week while waiting for my replacement.
Keep in mind this method is a little slow because of ADB. Hopefully you don't have to type too much.
Click to expand...
Click to collapse
I know I have connected it at least once, but when connecting the phone and the pc together, adb cannot find the phone. I am not sure if this is because of a Cerberus setting (that disables debugging) or something else. I will give it another shot when I get home.
If I can't, is there any way for me to somehow accept the adb permissions on the phone via a command versus touching the screen? Say if I have shell access over Cerberus and adb access from my PC?
slixzen said:
I know I have connected it at least once, but when connecting the phone and the pc together, adb cannot find the phone. I am not sure if this is because of a Cerberus setting (that disables debugging) or something else. I will give it another shot when I get home.
If I can't, is there any way for me to somehow accept the adb permissions on the phone via a command versus touching the screen? Say if I have shell access over Cerberus and adb access from my PC?
Click to expand...
Click to collapse
There's a bit of work to push the ADB acceptance key if you have a spare android phone lying around. Other than that, there probably is but might be more of a headache. I took the ADB key for my desktop from another android and pushed it in through TWRP which accepts ADB commands while in Recovery.
Darnell0216 said:
There's a bit of work to push the ADB acceptance key if you have a spare android phone lying around. Other than that, there probably is but might be more of a headache. I took the ADB key for my desktop from another android and pushed it in through TWRP which accepts ADB commands while in Recovery.
Click to expand...
Click to collapse
I have a sony xperia P that I am using right now until the replacement phone I got arrives. Any idea how I could use that? I have had minimal success with the phone so far in trying to get that phone to flash custom recoveries, to root the device (not sure why, but my laptop just doesn't want to seem to do it, even using automated tools).
Is it better to just wait for the replacement phone to arrive and grab what I need from that and push it? Could you link me to any guide or steps that you used with yours?
Thanks for such quick responses by the way!
EDIT:
Flashing TWRP and booting into recovery with command prompt open and running adb devices / fastboot devices does not show any devices available.
Is there a specific menu setting or other option I need to use to be able to run adb?
When you use TWRP, the phone will be recognized by the PC but the driver doesn't install correctly off the bat. Go to Device Manager and look for your phone. You may need to click the View -> Show Hidden Devices option. Update the driver manually by selecting the one provided by your manufacturer. Some have a dedicated ADB driver for specific functions (bootloader, etc).
The adb key is stored in data/misc/adb/adb.keys -You can pull this file from any other android connected to that PC (or just copy it if you have a root explorer) and push it to the broken one if necessary. This will bypass any ADB authorization issues while the phone is fully booted and let you see the screen.
So i just got my MOJO and was in the process of rooting it but, i can't seem to get windows 7 to recognize the device when i connect it by USB. It always shows up as "unknown device". How do i get Windows 7 to recognize it?
Also i have another problem regarding sound....there isn't any. When i load up a video on the MOJO, or just try to do anything that would have sound, theres nothing. I have the sound at MAX using the CTRL gamepad controls. Still, nothing.
I knew the MOJO was going to be one of those devices you have to fight with in order to get it to do what you want but, this is worse than i expected.
Help?
It really is a terrible experience out of the box. We know who to blame Mad Catz!
For Windows to recognize it, you have to install ADB Drivers, try the ones from teamandroid: www teamandroid .com/download-android-usb-drivers/
You will have to locate the device in the windows device manager and install the drivers manually.
But you can root the mojo without conencting it to the pc. you can root it with towelroot (Version 1). you have to search with google for the apk. the newest version (3) and v2 won't work.
After that you can use Flashify to flash a custom recovery.
For the sound: do you have another hdmi slot at your tv? this sounds like a connection problem.
Pitey said:
For Windows to recognize it, you have to install ADB Drivers, try the ones from teamandroid: www teamandroid .com/download-android-usb-drivers/
You will have to locate the device in the windows device manager and install the drivers manually.
But you can root the mojo without conencting it to the pc. you can root it with towelroot (Version 1). you have to search with google for the apk. the newest version (3) and v2 won't work.
After that you can use Flashify to flash a custom recovery.
For the sound: do you have another hdmi slot at your tv? this sounds like a connection problem.
Click to expand...
Click to collapse
Connecting it to the PC is (supposed)to be the EASY way though. Also....i don't see the mojo listed among the devices on that link you mentioned. Which one should i download??
PSP-Fan said:
Connecting it to the PC is (supposed)to be the EASY way though. Also....i don't see the mojo listed among the devices on that link you mentioned. Which one should i download??
Click to expand...
Click to collapse
Try the driver from Samsung.
If they don't work, use the universal adb drivers: github.com/koush/UniversalAdbDriver
Towelroot would be much easier, you just install the App and klick one button (but only v1 works with mojo)
Pitey said:
Try the driver from Samsung.
If they don't work, use the universal adb drivers: github.com/koush/UniversalAdbDriver
Towelroot would be much easier, you just install the App and klick one button (but only v1 works with mojo)
Click to expand...
Click to collapse
Thanks for the reply but i've tried all towelroot 1.0 as well as 3.0 and it did NOT work. I got an error saying, "This phone isn't currently supported". No matter which version i try.
Edit: Ok got it working! Turns out i was attempting the V2.0 & V3.0 versions. There are plenty of sites out there that would claim to have v1.0. However, once i downloaded and installed it, i'd see a "v2" or "v3" at the top of the screen.
In the end, I had to do a google search for a towelroot spefically for MOJO. Only then did i finally come across a site that had a legit v1.0.
PSP-Fan said:
Thanks for the reply but i've tried all towelroot 1.0 as well as 3.0 and it did NOT work. I got an error saying, "This phone isn't currently supported". No matter which version i try.
Edit: Ok got it working! Turns out i was attempting the V2.0 & V3.0 versions. There are plenty of sites out there that would claim to have v1.0. However, once i downloaded and installed it, i'd see a "v2" or "v3" at the top of the screen.
In the end, I had to do a google search for a towelroot spefically for MOJO. Only then did i finally come across a site that had a legit v1.0.
Click to expand...
Click to collapse
Good job! I'm glad it worked in the end.
I also had to search a long time to find the correct tr version. But you will never need it again, once it's rooted. if you want to go back to stock, you can flash the original firmware with twrp, too!
Pitey said:
Good job! I'm glad it worked in the end.
I also had to search a long time to find the correct tr version. But you will never need it again, once it's rooted. if you want to go back to stock, you can flash the original firmware with twrp, too!
Click to expand...
Click to collapse
Here was the thread it was in:
http://forum.xda-developers.com/mad-catz-mojo/development/root-mojo-towelroot-one-click-t2799712
And the link for V1.0 in case anyone wants it. It was tough to find:
http://www.mediafire.com/download/oxrryya4ffs4w6u/tr-1.apk
Ok so after a few hard weeks messing with this device, i've figured out ways to fix all its quirks, except for one: Not being able to connect to Pc. Thats annoying. I don't like having to remove my Micro SD card everytime i want to add more files.
Especially since this device was deigned in such a way that, its virtually impossible to remove without first removing the HDMI cable first. As they are sooooo CLOSE together.
Any suggestions for drivers? I just need it to function like a plain USB mass storage device, so i can access my Micro SD card on the Pc.
Yeah, the microSD is a pain to remove.. but I never need to touch it.
I don't understand why you want to access the SD via PC as a USB device?
To access the sdcard over wifi I use a SambaDroid server on the mojo pointed to the sdcard.. it works.
gwaldo said:
Yeah, the microSD is a pain to remove.. but I never need to touch it.
I don't understand why you want to access the SD via PC as a USB device?
To access the sdcard over wifi I use a SambaDroid server on the mojo pointed to the sdcard.. it works.
Click to expand...
Click to collapse
I want to be able to freely connect my MOJO by USB and drag & drop files at will to the Micro SD, without having to physically remove the Micro SD card each time (which also means unplugging the HDMI every time!!).
So far i'm enjoying the MOJO console as i've found fixes for every other problem i've run into. This is the only one that continues to elude me. I had not thought about the possibility of my Pc being able to connect remotely though wi-fi, to access the MOJO storage. This might be yet another out-of-the-box fix for me. Can you explain more about how this is done??
PSP-Fan said:
I had not thought about the possibility of my Pc being able to connect remotely though wi-fi, to access the MOJO storage. This might be yet another out-of-the-box fix for me. Can you explain more about how this is done??
Click to expand...
Click to collapse
Not sure why you want to have a USB on the MOJO that way... the idea of MOJO(or any other topset box) is to keep it online next to your TV, I used to plug USB thumb drives into it.. but you never want to change microSD cards.. same like on a phone or tablet really.
Just install this on mojo:
https://play.google.com/store/apps/details?id=berserker.android.apps.sambadroid&hl=en
You can configure it so it shares a folder (google how to share folders on windows or youtube sambadroid).
You can use just the microSD (i think it's /mnt/card1) or the internal storage(i think /storage) or both using just /
I wouldn't do just / though.
It's pretty easy, just replicates windows file sharing and works well.
I'll be darned if I can find an answer on this, which is weird, because I was able to 'fix' this on three prior phones.
When you connect (to Windows 7 PC in my case) via USB, the system detects and mounts a new USB drive (as a drive letter device) and pops up an Autoplay window. If allowed, it will install the drivers. Handy? The first time, yes. Many times later? Lightly annoying. *shrug*
Who's got the skinny on a solution for this "issue". LOL
lordbear said:
I'll be darned if I can find an answer on this, which is weird, because I was able to 'fix' this on three prior phones.
When you connect (to Windows 7 PC in my case) via USB, the system detects and mounts a new USB drive (as a drive letter device) and pops up an Autoplay window. If allowed, it will install the drivers. Handy? The first time, yes. Many times later? Lightly annoying. *shrug*
Who's got the skinny on a solution for this "issue". LOL
Click to expand...
Click to collapse
Me! You'll need to have root access though. All you need to do is delete the /system/etc/usb_drivers.iso file and you're done.
shadowstep said:
Me! You'll need to have root access though. All you need to do is delete the /system/etc/usb_drivers.iso file and you're done.
Click to expand...
Click to collapse
Thanks!
It's even an ISO image file... makes perfect sense if I had gone spelunking.
lordbear said:
Thanks!
It's even an ISO image file... makes perfect sense if I had gone spelunking.
Click to expand...
Click to collapse
Do copy before. If you lose those drivers you need to look for them on internet, there is no official drivers or I couldn't find them. What about disable autoplay from usb on Windows.
Gizmundo said:
Do copy before. If you lose those drivers you need to look for them on internet, there is no official drivers or I couldn't find them. What about disable autoplay from usb on Windows.
Click to expand...
Click to collapse
I renamed, adding .bak to the filename. Seems to have worked. (After I otherwise solved my problem with access to root files that ES File Manager couldn't grant access to, that is. Solid Explorer FTW)
I looked at Windows-side options, but I needed to solve the root access problem anyway, so... Also, I wanted to disable it for just this volume and it was unclear how feasible it would be for a single volume. I think I saw something about it being able to be on a per-volume (using unique ID) but didn't dig very far.
Gizmundo said:
Do copy before. If you lose those drivers you need to look for them on internet, there is no official drivers or I couldn't find them. What about disable autoplay from usb on Windows.
Click to expand...
Click to collapse
If ever needed, you can download them from here, or let me know if this link expires sometime. I'll upload them for you.
shadowstep said:
If ever needed, you can download them from here, or let me know if this link expires sometime. I'll upload them for you.
Click to expand...
Click to collapse
Thanks man.. I'll have a look at it when I come home if there's" no signature" message like on the others I found before. :good: