Related
My friend has HTC One. He wiped all the data on SD including the ROM files and One is not booting right now. It's rooted and has Trickdroid's 4.2.2 based ROM.
We tried lots of things so far;
- Pushing files via ADB
Trying ADB, it says device not found, no matter we did we couldn't manage the pc to recognize the phone.
- Mounting SD via CWM
I have HOX, when I enter CWM I can see the option to mount the SD but on One there's no line like this.
- Activating Sideload on TWRP
We also flashed TWRP and tried to use Sideload feature but when we tried to activate it, it says something like "unable to mount .."
- Flashing the RUU
And lastly we tried to flash the RUU, we checked the CID and it says o2___001 and there's no RUU for it.
I just saw that One could be S-OFF and got Super-CID, but to do that again, I have to pull and push some files via ADB so we stuck here.
Could you plese help me on this?
Try cwm recovery it has sideload feature I was in a similar situation once before and it worked using cwm recovery
Also. If you want to try use adb again, try to plug in your device and then wait for few seconds before running a push command. It worth mentioning that once adb fail one time, it is not going to work again by repeating the same push command. Once it fails run this command: adb kill-server
This command will stop the previous failed process after killing the server then try to push again
NiMH_999 said:
Try cwm recovery it has sideload feature I was in a similar situation once before and it worked using cwm recovery
Also. If you want to try use adb again, try to plug in your device and then wait for few seconds before running a push command. It worth mentioning that once adb fail one time, it is not going to work again by repeating the same push command. Once it fails run this command: adb kill-server
This command will stop the previous failed process after killing the server then try to push again
Click to expand...
Click to collapse
We tried a different computer and solved the ADB problem, then I did just like you told and it's OK now.
Thank you.
You're welcome. glad it's all all OK for you
Boot TWRP, then select “Mount”, then select only “Data” and connect your HTC One to your computer.
Considering you have adb.exe (Windows, part of fastboot.zip) or on Linux:
cd Downloads\ROM.zip
adb push ROM.zip /sdcard/
Replace ROM.zip with the ROM filename you copied earlier to Downloads (or any other) folder, then install the ROM.
It should be nearly same running CWM recovery. Hope that helps.
Same problem as you --> fixed
I was able to recognize my device in device manager when using fastboot, but wasnt able to recognize the device as soon as I switched to recovery mode.
I found this universal driver which would recognize both: download.clockworkmod.[com]/test/UniversalAdbDriverSetup6.msi
(remove brackets from [.com] above)
I was now able to use adb sideload to transfer the .zip to my sd card and flash my new rom.
Hope this helps anyone else.
If you found that adb worked from a different machine, you might check whether you had any tethering drivers installed (eg EasyTether) on the machine that was not able to see the phone via adb. I found that they interfered with adb's operation on my Macbook previously; it was maddening.
woraz said:
My friend has HTC One. He wiped all the data on SD including the ROM files and One is not booting right now. It's rooted and has Trickdroid's 4.2.2 based ROM.
We tried lots of things so far;
- Pushing files via ADB
Trying ADB, it says device not found, no matter we did we couldn't manage the pc to recognize the phone.
- Mounting SD via CWM
I have HOX, when I enter CWM I can see the option to mount the SD but on One there's no line like this.
- Activating Sideload on TWRP
We also flashed TWRP and tried to use Sideload feature but when we tried to activate it, it says something like "unable to mount .."
- Flashing the RUU
And lastly we tried to flash the RUU, we checked the CID and it says o2___001 and there's no RUU for it.
I just saw that One could be S-OFF and got Super-CID, but to do that again, I have to pull and push some files via ADB so we stuck here.
Could you plese help me on this?
Click to expand...
Click to collapse
if you have problems always use Hasoon All-In-One_Kit for HTC
Am having the same issues, have tried everything I can think off and everything google has suggested. I'm beyond stuck any and all help would be greatly appreciated
my bad exp
I don't know if that help anyone but I had the problem "device not found" when I was trying to side load with HTC AIO KIT.
I removed all my drivers for htc from the control panel and installed only the htc driver (binary100100.googlecode.[com]/files/HTCDriver3.0.0.007.exe). Then the adb started to work. (after the htc drivers install you need to restart your OS)
When I installed new ROM and reboot the device it showed me the screen with the developer's rom. I thought that I failed and flashed new rom then suddenly the new ROM after one minute started to work. So looks like that I should wait long enough for the first and may be it would also starts to work.
Was he by chance having issues charging his phone before he wiped it?
Myself and my brother both a had issues with the USB port going. Couldn't charge while phone was on. PC wouldn't pick it up so no adb. However was able to pickup fastboot and charge while in fastboot mode.
If that's the case you could try running a zip in oemRUU mode just to get an os on there.
Is he soff?
Sent from my HTC One using xda premium
makkasi said:
I don't know if that help anyone but I had the problem "device not found" when I was trying to side load with HTC AIO KIT.
I removed all my drivers for htc from the control panel and installed only the htc driver (binary100100.googlecode.[com]/files/HTCDriver3.0.0.007.exe). Then the adb started to work. (after the htc drivers install you need to restart your OS)
When I installed new ROM and reboot the device it showed me the screen with the developer's rom. I thought that I failed and flashed new rom then suddenly the new ROM after one minute started to work. So looks like that I should wait long enough for the first and may be it would also starts to work.
Click to expand...
Click to collapse
This worked for me. Thanks!!
Once I removed all the extra crap from control panel and used the latest I was able to do adb devices successfully from bootloader / recovery.
I was just having the same problem on the new LG G2 (D803). It was perplexing because the computer *bleeped* every time it attached so I knew that it saw something. Based on the tips here I went to the Device Manager and sure enough there it was... I reinstalled the drivers inside device manager and then I got an easy adb hit on the phone... hmmm :fingers-crossed:
EazyVG said:
Boot TWRP, then select “Mount”, then select only “Data” and connect your HTC One to your computer.
Considering you have adb.exe (Windows, part of fastboot.zip) or on Linux:
cd Downloads\ROM.zip
adb push ROM.zip /sdcard/
Replace ROM.zip with the ROM filename you copied earlier to Downloads (or any other) folder, then install the ROM.
It should be nearly same running CWM recovery. Hope that helps.
Click to expand...
Click to collapse
flsurf7 said:
I was able to recognize my device in device manager when using fastboot, but wasnt able to recognize the device as soon as I switched to recovery mode.
I found this universal driver which would recognize both: download.clockworkmod.[com]/test/UniversalAdbDriverSetup6.msi
(remove brackets from [.com] above)
I was now able to use adb sideload to transfer the .zip to my sd card and flash my new rom.
Hope this helps anyone else.
Click to expand...
Click to collapse
This worked for my Nexus 4 and TWRP installed. Running the ADB sideload commad from TWRP did not, and just trying to push or sideload from command prompt on PC (Win 8) did not. I had drivers for Nexus 4 recognition installed previously from Nexus Root Toolkit which worked when the Nexus 4 was booted into system, but did not recognize it when wiped and/or in recovery mode. Loading these drivers the Nexus 4 was recognized in recovery mode, and I was able to push the ROM and install using TWRP.
Thanks much!
:good:
timekills said:
This worked for my Nexus 4 and TWRP installed. Running the ADB sideload commad from TWRP did not, and just trying to push or sideload from command prompt on PC (Win 8) did not. I had drivers for Nexus 4 recognition installed previously from Nexus Root Toolkit which worked when the Nexus 4 was booted into system, but did not recognize it when wiped and/or in recovery mode. Loading these drivers the Nexus 4 was recognized in recovery mode, and I was able to push the ROM and install using TWRP.
Thanks much!
:good:
Click to expand...
Click to collapse
Man, I just wanted to say thank you. I've been stuck on this for hours and this did the trick!
Worked
flsurf7 said:
I was able to recognize my device in device manager when using fastboot, but wasnt able to recognize the device as soon as I switched to recovery mode.
I found this universal driver which would recognize both: download.clockworkmod.[com]/test/UniversalAdbDriverSetup6.msi
(remove brackets from [.com] above)
I was now able to use adb sideload to transfer the .zip to my sd card and flash my new rom.
Hope this helps anyone else.
Click to expand...
Click to collapse
the drivers mentioned here worked for me.
Device : HTC One M7
Recovery : TWRP
Thanks
Thank you so much! This universal driver worked for me! (HTC One Mini with TWRP, soft-bricked)
NiMH_999 said:
Try cwm recovery it has sideload feature I was in a similar situation once before and it worked using cwm recovery
Also. If you want to try use adb again, try to plug in your device and then wait for few seconds before running a push command. It worth mentioning that once adb fail one time, it is not going to work again by repeating the same push command. Once it fails run this command: adb kill-server
This command will stop the previous failed process after killing the server then try to push again
Click to expand...
Click to collapse
Years later, thank you sir, for helping a noob with "adb kill-server"
I was so freaked as to why TWRP wasn't sideloading but PhilZ was.
flsurf7 said:
I was able to recognize my device in device manager when using fastboot, but wasnt able to recognize the device as soon as I switched to recovery mode.
I found this universal driver which would recognize both: download.clockworkmod.[com]/test/UniversalAdbDriverSetup6.msi
(remove brackets from [.com] above)
I was now able to use adb sideload to transfer the .zip to my sd card and flash my new rom.
Hope this helps anyone else.
Click to expand...
Click to collapse
ADB didn't recognize my Xperia SP in Clockworkmod. That driver worked like a charm Thank you!
This worked for me...
flsurf7 said:
I was able to recognize my device in device manager when using fastboot, but wasnt able to recognize the device as soon as I switched to recovery mode.
I found this universal driver which would recognize both: download.clockworkmod.[com]/test/UniversalAdbDriverSetup6.msi
(remove brackets from [.com] above)
I was now able to use adb sideload to transfer the .zip to my sd card and flash my new rom.
Hope this helps anyone else.
Click to expand...
Click to collapse
Thank you so much for this. This really helped me out.
Last night, on TWRP I formated data on the SD card, which is why I have no OS. Now looking for how to fix this on xda/google, I get into the bootloader, have fastboot usb and try to adb shell but I keep getting the "error no device found". I already installed latest drivers from HTC on to my laptop and still nothing. Any other idea?
windows 8?
First off, make sure you have HTC Sync Manager installed because that will give you the proper drivers in order to be able to use ADB commands.
Afterwards, make sure you install Java JDK and Android SDK.
Just follow this tutorial here: http://www.howtogeek.com/125769/how-to-install-and-use-abd-the-android-debug-bridge-utility/
Follow it word for word and make sure you install JDK X86 even if you have a X64 computer. And then download SDK Manager, put it in C:/ drive, open SDK Manager, and download the necessary tools (also all in the tutorial).
I was in the same position as you just before yesterday and I followed this tutorial with success.
skinsfanbdh said:
windows 8?
Click to expand...
Click to collapse
Windows 7, and mac.
Evolancer13 said:
Windows 7, and mac.
Click to expand...
Click to collapse
try downloading all in one toolkit and try that. just make sure to read the onscreen instructions as you go through the process
TarekElsakka said:
First off, make sure you have HTC Sync Manager installed because that will give you the proper drivers in order to be able to use ADB commands.
Afterwards, make sure you install Java JDK and Android SDK.
Just follow this tutorial here: http://www.howtogeek.com/125769/how-to-install-and-use-abd-the-android-debug-bridge-utility/
Follow it word for word and make sure you install JDK X86 even if you have a X64 computer. And then download SDK Manager, put it in C:/ drive, open SDK Manager, and download the necessary tools (also all in the tutorial).
I was in the same position as you just before yesterday and I followed this tutorial with success.
Click to expand...
Click to collapse
skinsfanbdh said:
try downloading all in one toolkit and try that. just make sure to read the onscreen instructions as you go through the process
Click to expand...
Click to collapse
I'll look into both things, thanks.
EDIT: even on my mac adb does not see any devices, before when I entered ./adb devices it would show "list of devices:" and it would be blank.
Good luck, man. It's fairly easy once you read the tutorial carefully and follow all the steps to the word. After it's all done and the command prompt says Sideload 100%, boot into TWRP, tap INSTALL and then scroll down to sideload.zip and that's your ROM. Also after copying the desired ROM to platform-tools in the SDK folder, rename it to rom.zip, it seems to work 100% that way while it struggles a bit with long names.
TarekElsakka said:
Good luck, man. It's fairly easy once you read the tutorial carefully and follow all the steps to the word. After it's all done and the command prompt says Sideload 100%, boot into TWRP, tap INSTALL and then scroll down to sideload.zip and that's your ROM. Also after copying the desired ROM to platform-tools in the SDK folder, rename it to rom.zip, it seems to work 100% that way while it struggles a bit with long names.
Click to expand...
Click to collapse
Still getting the error: device not found.
I even ran the all in one tool kit and attempted the "ADB sideload a ROM" follow the steps but get an error on CMD "C:\users\(username) is not recognized as an internal or external command, operable program or batch file"
I really do not understand why adb is not working, I did s-off and supercid myself maybe less than a week ago.
Are you sure you followed all the steps in the tutorial including installing JDK, using SDK Manager to download some tools and such? And are you sure you have the proper drivers installed (e.g HTC Sync Manager)? I used to get that error before I installed it. Go to Device Manager while in ADB mode in TWRP and see if the device is recognized or if there's a yellow sign beside it indicating that there are no drivers for it.
TarekElsakka said:
Are you sure you followed all the steps in the tutorial including installing JDK, using SDK Manager to download some tools and such? And are you sure you have the proper drivers installed (e.g HTC Sync Manager)? I used to get that error before I installed it. Go to Device Manager while in ADB mode in TWRP and see if the device is recognized or if there's a yellow sign beside it indicating that there are no drivers for it.
Click to expand...
Click to collapse
It came up under Android USB Devices as My HTC. When I was following the steps on the link you provided, when I tried to update the drivers with the google usb driver wouldnt work, it would say "windows had determined the driver software for your device is up to date". When I go into My HTC properties says the driver version is 2.0.7.18.
The Google USB drivers did not work for me either, only the ones provided by HTC Sync Manager did. I have not experienced that problem, mate, so I do not know what to do at this point, I am very sorry. If you are not able to fix this, I suggest getting an OTG cable and directly loading the ROM from the PC to your SD card. I ordered one a couple of days ago and it is coming tomorrow, it's very helpful
TarekElsakka said:
The Google USB drivers did not work for me either, only the ones provided by HTC Sync Manager did. I have not experienced that problem, mate, so I do not know what to do at this point, I am very sorry. If you are not able to fix this, I suggest getting an OTG cable and directly loading the ROM from the PC to your SD card. I ordered one a couple of days ago and it is coming tomorrow, it's very helpful
Click to expand...
Click to collapse
Crap, I appreciate your help though.
EDIT: nevermind googled it, gonna pick one up. Phoneless till wednesday
I am sorry to hear that, but I suppose that's the only thing you can do at the moment. Even if somehow get ADB working, do not cancel your order because OTG cables aren't only used for mounting the device, but also for things like connecting gamepads and controllers to play games on your device.
USB 3
If you have USB3 port adb.exe wan't recognize your device.
I triend first on USB3 and after on other older computer on USB2 all was fine
Evolancer13 said:
Last night, on TWRP I formated data on the SD card, which is why I have no OS. Now looking for how to fix this on xda/google, I get into the bootloader, have fastboot usb and try to adb shell but I keep getting the "error no device found". I already installed latest drivers from HTC on to my laptop and still nothing. Any other idea?
Click to expand...
Click to collapse
You can't acces to "adb shell" without OS, there is special mode in adb named "adb sideload" , not shell !
1) Check version adb by "adb version" you need version 1.0.29 or higher
2) Check TWRP version (2.3 or higher) Go to TWRP recovery -> adb sideload
3) Connect PC to phone , at PC in device manager must be MY HTC device.
4) Type jn PC adb sideload /yourpath/yourrom.zip
tash2013 said:
You can't acces to "adb shell" without OS, there is special mode in adb named "adb sideload" , not shell !
1) Check version adb by "adb version" you need version 1.0.29 or higher
2) Check TWRP version (2.3 or higher) Go to TWRP recovery -> adb sideload
3) Connect PC to phone , at PC in device manager must be MY HTC device.
4) Type jn PC adb sideload /yourpath/yourrom.zip
Click to expand...
Click to collapse
check first with "adb devices" to see does your PC recognize your HTC
tash2013 said:
You can't acces to "adb shell" without OS, there is special mode in adb named "adb sideload" , not shell !
1) Check version adb by "adb version" you need version 1.0.29 or higher
2) Check TWRP version (2.3 or higher) Go to TWRP recovery -> adb sideload
3) Connect PC to phone , at PC in device manager must be MY HTC device.
4) Type jn PC adb sideload /yourpath/yourrom.zip
Click to expand...
Click to collapse
Tash2013 YOU ARE AMAZING! Got my One back up running!
Oh man I'm so glad it's working. I thought you already knew that it is sideload not shell lol.
Sent from my HTC One using Tapatalk 4 Beta
TarekElsakka said:
Oh man I'm so glad it's working. I thought you already knew that it is sideload not shell lol.
Sent from my HTC One using Tapatalk 4 Beta
Click to expand...
Click to collapse
If I knew I would have tried lol, and it no one said anything about sideload but oh well.
Haha! Damn. I am glad it worked out, though.
Hello, This is my first ever post on this site. I'm a beginner so take it easy,"if you can"
i have searched all the post i could find both google and xda. i seem to be stuck in twrp mode every time it boots it goes directly to the
twrp menu. i found i have no os installed and no files at all even the twrp.zip file which i had it saved on the /sdcard/downloads. im not to familiar with fastboot but i think i can get it into it by using the factory cable but i can see it on my comp as kindle but missing drivers. i tried installing drivers but to no avail. what can i do... please help if you can and ask for more info if you need it. Thank you
You shouldn't nessasrily need fastboot to fix this, I'm assuming the drivers you don't have installed for twrp is the adb device, so try updating Ur drivers with this version of the drivers: http://forum.xda-developers.com/showthread.php?p=44446906
Once the adb driver work you should be able to go I to twrp, hit advanced, then hit side load, and swipe to start side load, and with it plugged I to your PC put either a cm ROM or the stock rooted amazon ROM from android development into the same folder as your adb command, and run a line with this syntax in a command prompt: adb sideload myrom.zip
If that doesn't work you might be able to use adb push when not in side load mode but I haven't tinkered to much with twrp. If you must resort to using fastboot you shouldn't even need a factory cable in this case, as u can just go into twrp and hit reboot and tap bootloader, that should put you in fastboot. Hope this helps.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Code:
adb shell idme bootmode 1
Solution
Am3nd said:
Hello, This is my first ever post on this site. I'm a beginner so take it easy,"if you can"
i have searched all the post i could find both google and xda. i seem to be stuck in twrp mode every time it boots it goes directly to the
twrp menu. i found i have no os installed and no files at all even the twrp.zip file which i had it saved on the /sdcard/downloads. im not to familiar with fastboot but i think i can get it into it by using the factory cable but i can see it on my comp as kindle but missing drivers. i tried installing drivers but to no avail. what can i do... please help if you can and ask for more info if you need it. Thank you
Click to expand...
Click to collapse
Ok guys thanks a lot to stunts513 i have got it fixed. i will explain it to all the noobs out there what i did.
Like stunts513 said download the drivers from the link he provided, ok once you download it you will see a whole bunch of files but no exe files
like i said i was a noob and i was stuck on how to install the drivers, what you do, is you go to the device manager and click update drivers on the unknown or kindle with the yellow sign (assuming you have one) the click "let me pick from a list....." next if you see "have a disk" click that if you dont see it, hit next you will see it then. now point it toward the "usb drivers file" you just downloaded there should be a .inf file there click it and say open (next-next-next) your done on that part then follow his instructions
when you reach the part of the adb command this is what i did, i moved the file to where my adb was right next to adb.exe. i named it com10.zip to make it short and easy to type. you then start the adb by typing cd (wherever you placed your adb setup, mine was in C:\Users\MN\Desktop\adt-bundle-windows-x86-20130717\sdk\platform-tools) then type adb devices to see if your kindle is under there it should, mine at the time said something like "12312if8923823f recovery" before you type adb sideload make sure you are in the twrp menu and your in the sideload option. you then type adb sideload yourfilename.zip ....... "yourfilename meaning the file you wanted to transfer which should be in the adb tool section" it will start to transfer, when it was finished go and flash it your done.
One other thing that i had a problem with was, i couldn't get the kindle to connect to my computer, what you do is while it is connected uninstall the driver first in the devicemanager, then go to program files and the amazon folder keep going until you get to a folder with a uninstall .exe click it and uninstall it, then disconnect and then install the kindle drivers the reconnect there you go.
I hope i helped anyone had a similar problem cause i was up since 3 am in the morning working on this lol " i had hard bricked a kindle before, i was determined not to let it happen again"
~second post~
Am3nd said:
Ok guys thanks a lot to stunts513 i have got it fixed. i will explain it to all the noobs out there what i did.
Like stunts513 said download the drivers from the link he provided, ok once you download it you will see a whole bunch of files but no exe files
like i said i was a noob and i was stuck on how to install the drivers, what you do, is you go to the device manager and click update drivers on the unknown or kindle with the yellow sign (assuming you have one) the click "let me pick from a list....." next if you see "have a disk" click that if you dont see it, hit next you will see it then. now point it toward the "usb drivers file" you just downloaded there should be a .inf file there click it and say open (next-next-next) your done on that part then follow his instructions
when you reach the part of the adb command this is what i did, i moved the file to where my adb was right next to adb.exe. i named it com10.zip to make it short and easy to type. you then start the adb by typing cd (wherever you placed your adb setup, mine was in C:\Users\MN\Desktop\adt-bundle-windows-x86-20130717\sdk\platform-tools) then type adb devices to see if your kindle is under there it should, mine at the time said something like "12312if8923823f recovery" before you type adb sideload make sure you are in the twrp menu and your in the sideload option. you then type adb sideload yourfilename.zip ....... "yourfilename meaning the file you wanted to transfer which should be in the adb tool section" it will start to transfer, when it was finished go and flash it your done.
One other thing that i had a problem with was, i couldn't get the kindle to connect to my computer, what you do is while it is connected uninstall the driver first in the devicemanager, then go to program files and the amazon folder keep going until you get to a folder with a uninstall .exe click it and uninstall it, then disconnect and then install the kindle drivers the reconnect there you go.
I hope i helped anyone had a similar problem cause i was up since 3 am in the morning working on this lol " i had hard bricked a kindle before, i was determined not to let it happen again"
~second post~
Click to expand...
Click to collapse
Thanks, this helped.
Another noob here, first post. Firstly, thanks very much, this was also a great help to me. Just wanted to say i had a little trouble with the sideload command. Kept returning the error * cannot read 'com10.zip' *. Despite being in the same directory as the adb, to fix you must give the directory in the command like so:
adb sideload C:\pathToAdb\com10.zip
Just in case anyone is having the same issue. Cheers again
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
HI..I'm a complete noob when it comes to this. Somebody helped me install an older ROM 4.1.2, sense 5, 1.31.651.2 to use on another network and I want to install a newer ROM with better firmware...mostly because 3g is really slow here, sometimes doesnt even register and I think the radio can be better.
Can i use TWRP thats on my phone to flash a newer firmware before I flash the ROM? If so, do i have to wipe before I do that? How else may I update the firmware?
Thanks for your help.
You should always wipe before flashing a new ROM, but you only need to wipe system, data and cache (dalvik cache as wll if you have that option) - NEVER wipe internal storage or you will lose the rom file and likely have to RUU.
Here http://forum.xda-developers.com/showthread.php?t=2795856 is a link to the most recent firmware which comes with a brief tutorial as to how to flash the firmware using fastboot. If you are a noob, you will want the one that says "modified firmware with hboot and recovery removed" since you want to keep TWRP.
You will need to connect your phone to your pc while it is in the bootloader. You can get into the bootloader by turning your phone off, then holding volume down and the power key until a while screen comes up that says "Hboot" near the top. If you don't have ADB and/or the android sdk on your computer, you will need to get that first and then you will need to open a command prompt in the same folder where "fastboot.exe" is after installing the android sdk.
So again, you will download the extracted firmware, and also download the android sdk. Once android sdk is installed, navigate to the folder on your computer called "adb" and ensure that you can find "fastboot.exe". Once you have found this folder, copy the firmware file into the adb folder and rename it "firmware". Then hold shift and right click in the folder and select "open a command prompt here". After that, reboot your phone to the bootloader and plug in your phone to your computer. Then follow the instructions for flashing firmware at the link I posted.
You do not need to wipe prior to installing firmware. You should flash the new firmware before you flash a new rom since the firmware will work with any rom but the new roms only work with the new firmware. Wouldn't want to install a new rom only to find out you can't figure out how to install firmware.
Thank you very much for your reply The_mamba. I appreciate the time you took to write that all out. Can't wait to give it a shot.
[email protected] said:
Thank you very much for your reply The_mamba. I appreciate the time you took to write that all out. Can't wait to give it a shot.
Click to expand...
Click to collapse
No problem, I wouldn't know what I know if not for people taking the time to explain it. Let me know if you run into any problems or you need me to elaborate on any instructions.
The_mamba said:
No problem, I wouldn't know what I know if not for people taking the time to explain it. Let me know if you run into any problems or you need me to elaborate on any instructions.
Click to expand...
Click to collapse
So I downloaded adb, found fastboot.exe and tried following the directions but once I typed the command it just said "waiting on device". I extracted and renamed the folder and even tried it compressed...reason being the directions said to rename it firmware.zip but after it was extracted it's not a zip file anymore. I don't even know if that's the issue just something I wanted to bring up.
I also made sure my device said fastboot usb as well.
Other notes
I didn't download sdk, just an abbreviated adb. My computer says it doesn't recognize the device as soon as I get to fastboot usb. Under file name it says compressed file then .zip...can the command be wrong? Lastly, I hold shift and open a command within the folder that houses fastboot.exe and firmware among a few other files correct?
[email protected] said:
So I downloaded adb, found fastboot.exe and tried following the directions but once I typed the command it just said "waiting on device". I extracted and renamed the folder and even tried it compressed...reason being the directions said to rename it firmware.zip but after it was extracted it's not a zip file anymore. I don't even know if that's the issue just something I wanted to bring up.
I also made sure my device said fastboot usb as well.
Other notes
I didn't download sdk, just an abbreviated adb. My computer says it doesn't recognize the device as soon as I get to fastboot usb. Under file name it says compressed file then .zip...can the command be wrong? Lastly, I hold shift and open a command within the folder that houses fastboot.exe and firmware among a few other files correct?
Click to expand...
Click to collapse
Couple things: The abridged adb should be fine, it sounds like your computer is not recognizing the phone. Things to try for that is use a different USB port (sounds stupid but this often works) and make sure you have the most updated HTC drivers for the phone installed on your computer. You may want to ensure that your abridged ADB came with the adb and fastboot drivers as well. Also, you do not need to extract the firmware zip file that you download, just rename it. Literally just copy the downloaded firmware to the adb folder, rename it, and flash. You are correct about the command prompt window, you just want to open the command prompt from that folder so you don't have to navigate to the adb folder once in command prompt. As long as you open the command prompt from the folder it should say something like "C:\adb>" with a blinking underscore. Obviously if you didn't install adb to the root of your C:/ drive then it will say wherever you installed it.
Commands in order (once phone is in fastboot mode and recognized) should be:
fastboot oem rebootRUU (this will reboot the phone to a black screen with silver htc logo)
fastboot flash zip firmware.zip
(then it will run several lines of code and hopefully say "Success!")
fastboot reboot
Be cognizant of spaces and such.
Let me know if you still can't get it to work.
The_mamba said:
Couple things: The abridged adb should be fine, it sounds like your computer is not recognizing the phone. Things to try for that is use a different USB port (sounds stupid but this often works) and make sure you have the most updated HTC drivers for the phone installed on your computer. You may want to ensure that your abridged ADB came with the adb and fastboot drivers as well. Also, you do not need to extract the firmware zip file that you download, just rename it. Literally just copy the downloaded firmware to the adb folder, rename it, and flash. You are correct about the command prompt window, you just want to open the command prompt from that folder so you don't have to navigate to the adb folder once in command prompt. As long as you open the command prompt from the folder it should say something like "C:\adb>" with a blinking underscore. Obviously if you didn't install adb to the root of your C:/ drive then it will say wherever you installed it.
Commands in order (once phone is in fastboot mode and recognized) should be:
fastboot oem rebootRUU (this will reboot the phone to a black screen with silver htc logo)
fastboot flash zip firmware.zip
(then it will run several lines of code and hopefully say "Success!")
fastboot reboot
Be cognizant of spaces and such.
Let me know if you still can't get it to work.
Click to expand...
Click to collapse
Hey. Thanks for the last reply. I did everything you recommended but it still didn't work. I used two different usb cables, 3 different ports, and I keep getting the message I attached. However, htc sync worked albeit it gave me a warning message and said I needed a different driver and it downloaded it before it registered. Do you think my version is too outdated to be supported? I tried this HTC-Mobile-Driver_v4.16.0.001.exe and HTC-Mobile-Driver-v4.17.0.001 (1).zip and a website recommended this HTC_BMP_USB_Driver_x64_1.0.5375.msi but none helped.
I do get a noise every time I plug in and unplug the usb, so that seems to be working. USB debugging should be enabled correct?
Lastly and hopefully this is the main problem: when I turn off the phone and plug it in to the computer, I receive a message that say "The connected charger will take longer to charge. To charge faster, use the original charger and cable that were provided with this phone." I'm not sure if that's because its low voltage being delivered from the usb or the cable is actually not adequate, I will google that.
Also failed to mention my computer is running on Windows 10
[email protected] said:
Hey. Thanks for the last reply. I did everything you recommended but it still didn't work. I used two different usb cables, 3 different ports, and I keep getting the message I attached. However, htc sync worked albeit it gave me a warning message and said I needed a different driver and it downloaded it before it registered. Do you think my version is too outdated to be supported? I tried this HTC-Mobile-Driver_v4.16.0.001.exe and HTC-Mobile-Driver-v4.17.0.001 (1).zip and a website recommended this HTC_BMP_USB_Driver_x64_1.0.5375.msi but none helped.
I do get a noise every time I plug in and unplug the usb, so that seems to be working. USB debugging should be enabled correct?
Lastly and hopefully this is the main problem: when I turn off the phone and plug it in to the computer, I receive a message that say "The connected charger will take longer to charge. To charge faster, use the original charger and cable that were provided with this phone." I'm not sure if that's because its low voltage being delivered from the usb or the cable is actually not adequate, I will google that.
Click to expand...
Click to collapse
Hmmmm, interesting. Are you using usb ports on the front of the computer or the back? Sometimes the ones on the front aren't as good as the ones directly on the mainboard so if you haven't already then you could try the back ones. Also, despite using two cables, I guess there is still a chance that your cables are to blame. It concerns me that you are still getting driver errors even after updating sync so you may want to keep trying to solve the driver aspect. Here is an excerpt from a post on another forum I found that may be relevant:
"If you have the full AndroidSDK installed, check your device manager for an unknown device. If you find one that's supposed to be your phone, update the driver and use the driver in SDK directory\extras\google\usb_driver . If that still doesn't work, make sure you don't have HTC Sync running on your computer. It will hose the entire deal."
So try checking out your device manager regarding the driver and also be sure to close HTC sync completely (including the system tray icon if applicable) before plugging your phone in with bootloader up.
Check out the whole tread in general for some good tips: http://forums.androidcentral.com/rezound-rooting-roms-hacks/209934-stuck-waiting-device-after-fastboot-command.html
Keep me posted, I'm invested now, haha.