Related
Ok. I got my nc rooted, and used ROM Manager to install NF internally. Now I want to put gApps on it. So far everything is working wonderfully.
I download the Easy Driver Pack (http://forum.xda-developers.com/archive/index.php/t-910008.html) and follow the instructions. My NC isnt recognized. I went through all the troubleshooting tips there that I could find and my NC still isnt recognized.
Next I download http://legacyschool.us.to/nookdev/nook-usb-installer.rar and follow those instructions thinking that I might be able to fix said problem above. Still a failure. Now I've reached the point that I'm becoming slightly frustrated. Before I rooted my NC was recognized. Before I used ROM Manager to install NF my NC was recognized, and now I cant figure out wtf I'm doing wrong. Can someone help me out please?
UPDATE:
I got ADB to recognize my nook and it says that it's one of the adb devices plugged into my computer. When I go to enter the command prompts to install google apps, the cmd window freezes up after I input the first line (and I'm hoping I read the directions correctly and have my cmd window pointed in the right direction, at the sdk tools folder with the correct google application system file inside it)
So I'm not sure where to go after this because I'm not seeing anywhere that I could go back and fix an error. Maybe someone else will.
Hey guys,
I had a few questions about sideloading off market apps, that i couldn't find answers to. Thanks for your consideration.
If i understand correctly, you can only sideload apps on my unrooted samsung captivate by using a connection to a computer, right?
I know about the sideload wonder machine and i have used it successfully.
I know i could download the android sdk, and use the adb push command.
Is there a way to edit the no_market_app value in the settings db file only using my un-rooted phone?
Or can i use terminal emulator or a combination of both to somehow install an off market app?
I was just trying to think of ways to avoid having to conncect to a computer to install an app. I was on the road with a friend, and i had an off market app i wanted to give him, but he also has att(which blocks sideloading of off market apps), so i didn't even try. But wouldn't it be awesome if i could send the apps to his phone through bluetooth or email, then install it on his phone without rooting his phone? Maybe a temporary root of some sort would work? Isn't that how swc works?
Anyways, once i've played enough with my stock phone, i'll beg for more and i'll eventually root, and i'll probably end up playing with the sdk too. Thanks again guys!
To Root or Not To Root... or Perhaps Just A Temp Root...
There are a few quick fix temp root apps floating around. It really depends on you model and build if they work correctly or not.
You could, as you mentioned, push from a cmd promt in adb, install from the cmd promt in adb to the device - or - pull from the device itself using a shell or terminal.
Unfortunately, I currently don't know of a direct way that you would be able to access, let alone edit the system.db file to make a permanent modification without at least being under a temp root.
Peace-
Hello everybody! I have a lot of android apps on my pc and I want to transfer them to my nook, but I don't know if it is possible. If it is, which folder do I drop them off in? I tried to find where the other apps are installed in my nook that I directly download from the android market, but I can't find their location. Please help me out, I really need some of the apps I have and I can't even find them or can't download them directly. Thank you for your time!
psbear532 said:
Hello everybody! I have a lot of android apps on my pc and I want to transfer them to my nook, but I don't know if it is possible. If it is, which folder do I drop them off in? I tried to find where the other apps are installed in my nook that I directly download from the android market, but I can't find their location. Please help me out, I really need some of the apps I have and I can't even find them or can't download them directly. Thank you for your time!
Click to expand...
Click to collapse
Use adb
Code:
adb install myapp.apk
ros87 said:
Use adb
Code:
adb install myapp.apk
Click to expand...
Click to collapse
Thanks for taking your time to help me I really appreciate it. I've run into a problem though. when I try to set up adb it wont find my device in the cmd prompt. I am following these instructions to set up adb: search in youtube "ANDROID SDK Tools (How-To Install)" first video. I get stuck at the part at 6:23 it just says "list of devices attached" and doesn't list anything. I don't know what am doing wrong .
psbear532,
You can use a file explorer program (astro, es explorer, etc), and choose the apk on sd and install it. Just remember to use nookcolortools and de-select and re-select the non-market app box.
I guess it would be easier - I haven't had luck with adb so far...
psbear532 said:
Thanks for taking your time to help me I really appreciate it. I've run into a problem though. when I try to set up adb it wont find my device in the cmd prompt. I am following these instructions to set up adb: search in youtube "ANDROID SDK Tools (How-To Install)" first video. I get stuck at the part at 6:23 it just says "list of devices attached" and doesn't list anything. I don't know what am doing wrong .
Click to expand...
Click to collapse
Assuming you've successfully rooted your NST:
1: Enable wifi on your NST and make a note of the IP address assigned to it.
2: Tell adb to connect to that IP
Code:
adb connect 10.0.0.2
That's it, if adb was able to connect you can now adb push or adb install all you want
---------- Post added at 01:41 AM ---------- Previous post was at 01:39 AM ----------
apeine said:
psbear532,
I guess it would be easier - I haven't had luck with adb so far...
Click to expand...
Click to collapse
Why?, apart from having to download and install the Android SDK, using adb should be straightforward unless you're trying to get it to connect to the NST trough usb.
Ros87,
Maybe that was my mistake. I've always tried using USB :S
apeine said:
Ros87,
Maybe that was my mistake. I've always tried using USB :S
Click to expand...
Click to collapse
Getting adb to work over USB on the NST is a pain in the a**
Some people have reported getting it to work with the Google drivers, but none of them worked for me in W7. Also I'm unable to try it in Ubuntu as I'm running that trough VMware Player and I cannot redirect the USB port properly.
Thank you both so much! Ros87 I got it to work over wifi which I think is even better since now I don't even have to deal with the wire. apeine I didn't try your method since adb worked, but thanks for your time anyway.
ros87 said:
Getting adb to work over USB on the NST is a pain in the a**
Some people have reported getting it to work with the Google drivers, but none of them worked for me in W7. Also I'm unable to try it in Ubuntu as I'm running that trough VMware Player and I cannot redirect the USB port properly.
Click to expand...
Click to collapse
So why don't you install linux on a separate partition?
How does one do this without an SD card? I will be getting one soon, but for now, can I just create a temporary folder on the home directory and install it from there? Does it automatically install to the apps directory?
Thanks!
EDIT: I just figured out how much you can browse with the computer. So...
The simplest method is to just copy the apps to an SD card, insert the card,browse to the .apk location,tap on the .apk file, you will be prompted with an screen asking if you want to proceed to install or just use the adb over wifi method as explained above
I use and app names Airdroid. It allows you to install apps remotely from your computer via wifi.
I have an "apk" folder in my UbuntuOne account, Dropbox should work too.
then i have the app for the service installed.
it works fine for me
Ouya SuperScript
By TehCrucible
v0.1
INTRODUCTION
So I originally wrote this batch script to simplify and combine some of the most frequently used tweaks on the forums for my own sake, to speed up my tinkering with the Ouya but I've decided to clean it up and upload it in case anyone else wants to use it.
This script is designed as a "one-click" modification tool for a stock Ouya on the latest firmware. Please read this guide carefully.
I ACCEPT NO RESPONSIBILITY FOR ANY DAMAGE OR DATA LOSS. This script is built on the work of many others much smarter than myself and be sure to check the credits.
SO WHAT DOES IT DO?
In a nutshell:
- Install Clockworkmod Recovery
- Root Ouya
- Install Xposed Framework
- Install Google Play Store
WHAT DO I NEED?
- A Windows PC. I have included drivers for both x86 and x64.
- A Micro USB cable.
INSTALLATION OVERVIEW
1. Update your Ouya to latest stock firmware
2. Install ADB drivers
3. Run the script
4. Play some games!
There's a more detailed step-by-step in the included README.txt file.
KNOWN ISSUES
- None
CREDITS & THANKS
WonderEkin
mybook4
elmerohueso
fatesausage
DOWNLOAD
Here
Thanks a lot for this. A lo of people have been asking about an automated method to get the play store running on the OUYA...
Great works. I just think of root my ouya....
A quick update:
It's working. I'm on the latest firmaware which is JZO54L-OUYA, kernel version 3.1.10-g780994a. Completely stock, but I had already rooted my OUYA.
Anyway, I enabled the Wireless ADB which will instantly show you the ip and port, installed the drivers for 64bit. Then open CMD and type: adb connect "iport"
Then I ran the superscript and everything went fine.
Hope this helps. I didn't even have to connect with a wire.
But I guess if you wanna install the CWM recovery you should be connected with a wire...
Hello guys!
I can see the Ouya in Device list in Control panel but I can't connect it in SuperScript. Any ideas?
THX
zmelkoow said:
Hello guys!
I can see the Ouya in Device list in Control panel but I can't connect it in SuperScript. Any ideas?
THX
Click to expand...
Click to collapse
Did you install the drivers right? If yes, then you should open the folder where you extracted your files and right click while holding shift then choose open CMD here. Then write: adb devices
If your device is there, it will give you an output of the IMEI and name of device
From there, you can then tell us what the error is and hopefully we can resolve it...
zmelkoow said:
Hello guys!
I can see the Ouya in Device list in Control panel but I can't connect it in SuperScript. Any ideas?
THX
Click to expand...
Click to collapse
that happened to me yesterday, but I overcame it by have my computer plugged into the Ouya then reboot the ouya and as soon as the computer recognized it started the script and it worked.
but I have an issue too
So I can run the script everything works except getting the recovery installed. the command prompt acts like it successfully installed the recovery then the Ouya proceeds to reboot into recovery mode. When that happens I get this menu? Nothing happens when I push any buttons on my keyboard. This doesn't look like a custom recovery.
I have tried this many times, did a factory reset and started fresh however even after updating the device driver it doesnt recognize the ouya....
unkoil said:
So I can run the script everything works except getting the recovery installed. the command prompt acts like it successfully installed the recovery then the Ouya proceeds to reboot into recovery mode. When that happens I get this menu? Nothing happens when I push any buttons on my keyboard. This doesn't look like a custom recovery.
Click to expand...
Click to collapse
No it doesn't :angel:.
I think I had the recovery installed when I first got the device a long time ago and I used the manual method in this thread, but I'm not sure that it works any more. Also do you have a wired or wireless keyboard? By the way only the Bluetooth keyboard doesn't work. May be if you can install the recovery from that thread, then you can proceed to the next step. One last thing, I don't think you will need the recovery except if you want to install CM or something. Other than that, I never used it before.
TRMB said:
I have tried this many times, did a factory reset and started fresh however even after updating the device driver it doesn't recognize the ouya....
Click to expand...
Click to collapse
Which version of windows are you on? Is it Windows 8 or 8.1? Do you know how to disable driver signature verification?
Also, what does it say when you connect? Just nothing, or not recognized or what? You can try the adb wireless, go into settings/development on the ouya and activate it. Then open CMD from the extracted folder and type adb connect "ip : port" then check by typing "adb devices". Let us know what happens after that.
Which version of windows are you on? Is it Windows 8 or 8.1? Do you know how to disable driver signature verification?
Also, what does it say when you connect? Just nothing, or not recognized or what? You can try the adb wireless, go into settings/development on the ouya and activate it. Then open CMD from the extracted folder and type adb connect "ip : port" then check by typing "adb devices". Let us know what happens after that.[/QUOTE]
I have tried both from my windows 7 computer and 8.1 laptop. It showed up just as you said "missing driver", sent it to the drivers part of SS to get the driver, it said it installed but when i run the SS and hit option "1" it comes up blank...
ahmadshawki said:
No it doesn't :angel:.
I think I had the recovery installed when I first got the device a long time ago and I used the manual method in this thread, but I'm not sure that it works any more. Also do you have a wired or wireless keyboard? By the way only the Bluetooth keyboard doesn't work. May be if you can install the recovery from that thread, then you can proceed to the next step. One last thing, I don't think you will need the recovery except if you want to install CM or something. Other than that, I never used it before.
I am having the same issue but not only with this method, I have also tried to install CWM with oneclicks auto and manual method to no avail.....
any suggestions?
Click to expand...
Click to collapse
always says it installed but will only boot into stock recovery
TRMB said:
always says it installed but will only boot into stock recovery
Click to expand...
Click to collapse
I can see from your posts that you tried everything and I'm so sorry that I'm just a user and not a developer or something. May be you can try sideloading terminal and try CWM manually (if you haven't already) or sideload ROM Toolbox and try the flash recovery option.
That's all I got. But if I were you, I won't bother about the CWM at all. It's useless.
As for the Play store, try the mod that I attached in my reply and let me know if this one works for you...
Unfortunately the link is not working. Is it possible to update it, please?
What I do if my micro usb is broken :/. I only have wireless adb
.. nice .. now my ouya will run again .. thanks
I already tried everything but I can't make this work... I installed every single drive in every single way.
The best screenshot of the whole situation is on attachment. SuperScript simply doesn't recognize OUYA with default drivers, neither provided drivers (or any of its variation like "composite adb" or something like that. The "List of devices attached" always return empty, even when provided drivers installed (signature deactivated and everything else). As readme says, when SuperScript doesn't recognize, it returns "error: device not found" every time that I try something...
This SuperScript seems great to start things on my my untouched and default OUYA... but I'm honestly out of options.
vinirockman said:
I already tried everything but I can't make this work... I installed every single drive in every single way.
The best screenshot of the whole situation is on attachment. SuperScript simply doesn't recognize OUYA with default drivers, neither provided drivers (or any of its variation like "composite adb" or something like that. The "List of devices attached" always return empty, even when provided drivers installed (signature deactivated and everything else). As readme says, when SuperScript doesn't recognize, it returns "error: device not found" every time that I try something...
This SuperScript seems great to start things on my my untouched and default OUYA... but I'm honestly out of options.
Click to expand...
Click to collapse
Problem solved. It is Windows Drivers issue. S-Config did a great job explaining how you should do this HERE. I hope it helps people who got stuck. SuperScript did work, I did installed CWM but I was not able to navigate (neither thru bluetooth usb full keyboard). I'm going to try to figure out what I'm missing later. As I can see, S-Config's website is fully updated... I do highly recommend read there who is going to do anything with ouya.
vinirockman said:
Problem solved. It is Windows Drivers issue. S-Config did a great job explaining how you should do this HERE. I hope it helps people who got stuck. SuperScript did work, I did installed CWM but I was not able to navigate (neither thru bluetooth usb full keyboard). I'm going to try to figure out what I'm missing later. As I can see, S-Config's website is fully updated... I do highly recommend read there who is going to do anything with ouya.
Click to expand...
Click to collapse
.. CWM need wired usb keyboard no navigate .. i don't remember if it can do it via bluetooth
Longtime reader, firsttime caller. I've read as much as I can and searched for a solution, but haven't found one yet.
I have a new Pixel 7 and am trying to install LineageOS following the official instructions. I've successfully worked through the initial steps through flashing custom recovery. However, when I start on installing LineageOS from recovery, I run into a problem that after the factory reset I'm unable to sideload LineageOS because adb doesn't recognize the phone. (I can still see it in fastboot, but not with adb.)
I believe that this is a driver problem, because the phone shows up in Device Manager with a triangle.
I initially installed the drivers from here. After I discovered the problem, I also tried the universal drivers from here. Neither of these has seemed to work.
What would you suggest for what I should try next?
laticola said:
Longtime reader, firsttime caller. I've read as much as I can and searched for a solution, but haven't found one yet.
I have a new Pixel 7 and am trying to install LineageOS following the official instructions. I've successfully worked through the initial steps through flashing custom recovery. However, when I start on installing LineageOS from recovery, I run into a problem that after the factory reset I'm unable to sideload LineageOS because adb doesn't recognize the phone. (I can still see it in fastboot, but not with adb.)
I believe that this is a driver problem, because the phone shows up in Device Manager with a triangle.
I initially installed the drivers from here. After I discovered the problem, I also tried the universal drivers from here. Neither of these has seemed to work.
What would you suggest for what I should try next?
Click to expand...
Click to collapse
You should download the official Google drivers.
elong7681 said:
You should download the official Google drivers.
Click to expand...
Click to collapse
I believe that I did that, but I just tried it again. I downloaded the driver package from here. I then installed them following these instructions. The result is the same: my device shows up in fastboot (if I type 'fastboot devices' I see it, and it shows up in Device Manager), but if I boot into recovery it doesn't show up - 'adb devices' show nothing, and it's not visible in Device Manager.
Is there another driver set that I should try? Or is there something else I can do to make progress with fastboot working?
laticola said:
I believe that I did that, but I just tried it again. I downloaded the driver package from here. I then installed them following these instructions. The result is the same: my device shows up in fastboot (if I type 'fastboot devices' I see it, and it shows up in Device Manager), but if I boot into recovery it doesn't show up - 'adb devices' show nothing, and it's not visible in Device Manager.
Is there another driver set that I should try? Or is there something else I can do to make progress with fastboot working?
Click to expand...
Click to collapse
Which version of platform-tools do you have? You should only be using v33.03. I would also encourage you to use the Pixel Flasher Thread 'PixelFlasher for Google Pixel 7 Support Thread.' https://forum.xda-developers.com/t/pixelflasher-for-google-pixel-7-support-thread.4505289/
laticola said:
I believe that I did that, but I just tried it again. I downloaded the driver package from here. I then installed them following these instructions. The result is the same: my device shows up in fastboot (if I type 'fastboot devices' I see it, and it shows up in Device Manager), but if I boot into recovery it doesn't show up - 'adb devices' show nothing, and it's not visible in Device Manager.
Is there another driver set that I should try? Or is there something else I can do to make progress with fastboot working?
Click to expand...
Click to collapse
I suggest you follow the advice I gave and the other member ended up doing quoted below from another thread (his experience is fairly similar to yours and/or achieving the same things would get to the same end result -- might be worth reading through the whole thing) -- it seemed to work out for him...
simplepinoi177 said:
So, the first thing you need to do is see what is the device being identified as in Device Manager -- it easily could be "Unknown Device" or even identified as something totally different & wrong (Samsung android device, MTP device, etc.). Regardless, it NEEDS to be identified as Android Composite ADB Interface (and Android Bootloader Interface when in Bootloader Mode). When this was happening to many members in the main rooting thread on this forum, it was determined that you can't simply just "Uninstall" it, but you also need to "delete device driver" as well (if option is available)! Most users are able to simply install the driver and sometimes just have to point it to the Google USB Windows Driver folder (that I hope you followed the suggestions of the other members in this thread and got it proper from the source from Google's developer's website), but I suggest going beyond it and pointing the device driver (Update, Browse My computer for drivers, Let me pick from a list, have disk, and choose the .inf file) to the exact .inf file.
Click to expand...
Click to collapse
GodieDan said:
SOLVED! thanks especially to @simplepinoi177 for cracking the case!
In case someone has this same problem in the future, here's the solution:
1. Open device manager and locate the misbehaving driver. If it's not obvious, plug and unplug the USB cable and watch for the appearing and disappearing entry.
2. Right-click the driver > click properties from the drop-down menu > select the driver tab > driver details
3. To be safe, use the snipping tool or something to take a picture of the file directories. Before you change anything in a system file it's always good to keep a record of how things were, but also you'll need to know the directories for the next step.
4. Unplug the device from the computer. As the directory list vanishes, use the screenshot to locate the .dll files.
5. Again to be safe, don't just delete the .dll files; instead just cut and paste into a backup folder somewhere. Also save the screenshot of the directories in the same folder, so you will know where to put them back if you need to. I didn't, and who knows, maybe I could be overcautious, but best practices and whatnot
6. Open device manager and again plug your android in. This time the driver will probably have a different name. Locate it as you did in step 1.
7. Right-click and select "uninstall device." Tick the box and say OK
8. Unplug the phone and reboot the phone and the computer both
9. Plug it back in
I have also determined the cause of my problem: Drive Booster, a program designed to automatically update drivers. It's not an unsafe program, but it is bad at installing the correct driver. I uninstalled it.
Thanks again!
Click to expand...
Click to collapse
laticola said:
I believe that I did that, but I just tried it again. I downloaded the driver package from here. I then installed them following these instructions. The result is the same: my device shows up in fastboot (if I type 'fastboot devices' I see it, and it shows up in Device Manager), but if I boot into recovery it doesn't show up - 'adb devices' show nothing, and it's not visible in Device Manager.
Is there another driver set that I should try? Or is there something else I can do to make progress with fastboot working?
Click to expand...
Click to collapse
Why do you think fastboot and recovery are the same? I haven't been in recovery for a bit but fastboot is available once connected to the computer but is recovery mode supposed to as well? Don't make me go into recovery mode please. But I thought recovery mode was device only.
I'm using platform tools v34.0.1, and I worked through the steps simplepinoi177 suggested for the drivers. I then discovered that my problem was something very basic: I was mistakenly using files for a Pixel 7 Pro instead of a Pixel 7 (my actual device). Once I flashed the correct boot, dbto, and recovery for my device, I was fine.
Apologies for the error, and thanks so much for the help. You all rock! And I will read up on Pixel Flasher.