[RECOVERY] Ouya CWM Recovery - Ouya Android Development

Unofficial CWM Recovery for Ouya
One-Click Style Method
To help people get up and going quickly, I've turned the steps below into an automated script package.
The attached OneClickOuyaRecovery.zip archive contains automated scripts to install CWM Recovery.
Whether you use Linux, Mac OSX, or Windows 7, all are invited to join in the fun!
Before you begin, you need to have your Ouya hooked up to a TV and powered on.
You also need to have a micro usb cable handy.
1) Download the OneClickOuyaRecovery.zip file and extract it (a folder on your desktop is fine).
2) Open the folder and you'll see a folder for each operating system. Open the folder for the OS of your choice.
3a) For Linux and Mac OSX users, run InstallOuyaCWMRecovery.sh in terminal by navigating the folder and running "./InstallOuyaCWMRecovery.sh" (you might just be able to run it by double clicking it. It depends on your setup).
3b) For Windows 7 users, double click the batch file InstallOuyaCWMRecovery.bat
4) Follow the on screen instructions. If you get an error saying there was no device found, run the script again (sometimes adb is finicky).
5) If all went well, you should be brought to CWM recovery.
If you have any trouble, seeking help is more efficient if you post the script's output to a pastebin (http://pastebin.com/) and post a link to it (I/others can see what happened).
Link to OneClickOuyaRecovery.zip - http://invisiblek.org/ouya/OneClickOuyaRecovery.zip
P.S. If anyone has proper hosting and would like to host OneClickOuyaRecovery.zip, please let me know and I'll change the link.
Thanks to invisiblek we have some more permanent hosting than a Dropbox account. Hosting costs money guys, so be sure to drop invisiblek a few coins if you can spare it.
Manual Method
Steps to install CWM on Ouya:
1) Perform the SDK Setup portion of thread http://forum.xda-developers.com/showthread.php?t=2272266 and install su, busybox, and superuser from this thread http://forum.xda-developers.com/showthread.php?t=2270589. This is done so we can get adb access and the necessary tools on the Ouya
2) Download the OuyaCWMrecovery6.0.3.2.img file and the OuyaCWMrecovery6.0.3.2flashable.zip.
3) Transfer the OuyaCWMrecovery6.0.3.2flashable.zip to your Ouya's internal sdcard (you can do this with "adb push /path/to/OuyaCWMrecovery6.0.3.2flashable.zip /sdcard/OuyaCWMrecovery6.0.3.2flashable.zip"). Leave the OuyaCWMrecovery6.0.3.2.img on your computer.
4) Connect your computer to the Ouya's micro-usb port (if it isn't already), connect a USB keyboard to the Ouya (bluetooth won't work), and run "adb reboot bootloader"
5) Wait 30 seconds (seriously)
6) Use fastboot to boot CWM by running "fastboot boot /path/to/OuyaCWMrecovery6.0.3.2.img". This boots from our CWM recovery without writing to any partitions.
7) Using your USB keyboard's arrow and enter keys, select "install zip from sdcard", "choose zip from sdcard", and "OuyaCWMrecovery6.0.3.2flashable.zip". This flashable zip writes CWM to the recovery partition and renames a pesky file that causes the stock recovery to be written on reboot.
8) Select "go back", and "reboot system now" to return to Andriod (CWM will ask "ROM may flash stock recovery on boot. FIX?". Make sure you select "NO")
9) Since we don't have any volume or home keys on the Ouya, to get back into recovery, you need to run "adb reboot recovery". Go ahead and try it once the Ouya has been sitting in Android for a minute or so. If all went well, you should reboot into CWM recovery!
This method was generated from the work done in http://forum.xda-developers.com/showthread.php?t=2292556. If you feel like pressing the thanks button, don't just thank me. Also thank professorpoptart, sonofskywalker3, and rayman. And obviously this is possible because of the fine folks behind CWM and Cyanogenmod.

Followed all your instructions, worked fantastically (aside from some strange windows 8 driver issues of course). Great job guys!

FrostyWolf said:
Need to fix your two forum links.
Click to expand...
Click to collapse
Thanks. All fixed.
Sent from my SCH-I535 using xda premium

Excellent work to everyone involved.

So, you are saying that no bluetooth KB work or just the one you tried? Did it have it's owen receiver or did you try to pair with Ouya's bluetooth? I am very interested in this because I have a Asus bluetooth KB/Mouse with their own receiver that I was hoping to use with the Ouya.

lartomar2002 said:
So, you are saying that no bluetooth KB work or just the one you tried? Did it have it's owen receiver or did you try to pair with Ouya's bluetooth? I am very interested in this because I have a Asus bluetooth KB/Mouse with their own receiver that I was hoping to use with the Ouya.
Click to expand...
Click to collapse
I believe what he meant was simply that it won't work in recovery.

tcollum said:
I believe what he meant was simply that it won't work in recovery.
Click to expand...
Click to collapse
That is correct. BT keyboards work fine on the OUYA normally.

Thoughts, when I fastboot the recovery.img I get no video to navigate to the correct option to install the zip. I know the recovery.img I fastbooted booted because it shows listed as "recovery" under adb devices.
I had this issue with the stock recovery and a mix of hooking it up to another monitor and pushing a Generic.kl with an edited home button seemed to fix it. I have reboot and went back into stock recovery and video works fine there, just not when I fastboot the CWM one.
I could use the adb shell in recovery to "--install_package=xxxxxx.zip" but it wont be too much help if I cant navigate the CWM menu...

professorpoptart said:
Thoughts, when I fastboot the recovery.img I get no video to navigate to the correct option to install the zip. I know the recovery.img I fastbooted booted because it shows listed as "recovery" under adb devices.
I had this issue with the stock recovery and a mix of hooking it up to another monitor and pushing a Generic.kl with an edited home button seemed to fix it. I have reboot and went back into stock recovery and video works fine there, just not when I fastboot the CWM one.
I could use the adb shell in recovery to "--install_package=xxxxxx.zip" but it wont be too much help if I cant navigate the CWM menu...
Click to expand...
Click to collapse
Hmmm. That's weird. It worked fine on my TV without pressing a key before hand. Maybe it's the keyboard or TV?
Sent from my Nexus 7 using xda premium

Tried 2 tv's stock recovery works on both.
edit: Tried it on a third TV works!? whatever... At least we know anyone has issue in the future just keep trying more displays until one works...
edit: don't know if it matters but just fyi, but I tried 2 1080P displays and got nothing, tried it on an old 1080i and it worked...
edit: Hooked it back up to the main TV and recovery video still works... whatever...
Sent from my SAMSUNG-SGH-I337 using xda app-developers app

professorpoptart said:
Tried 2 tv's stock recovery works on both.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
Probably not the issue, but wanted to rule it out anyway. What's the md5 hash of the .img. I got c6b37906f280b16cd200503c3cde6dfb
Sent from my Nexus 7 using xda premium

mybook4 said:
Probably not the issue, but wanted to rule it out anyway. What's the md5 hash of the .img. I got c6b37906f280b16cd200503c3cde6dfb
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
got it working, edited my previous post... basically tried a third, lol

Crazy driver / edid issues maybe? Who knows. I'm glad you got it working though.
Sent from my Nexus 7 using xda premium

mybook4 said:
Crazy driver / edid issues maybe? Who knows. I'm glad you got it working though.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
I was also unable to get video after running fastboot unless I had the HDMI plugged in prior to issuing the command.

FrostyWolf said:
I was also unable to get video after running fastboot unless I had the HDMI plugged in prior to issuing the command.
Click to expand...
Click to collapse
Ohhhhhh. I keep HDMI plugged in the entire time. Maybe that's the issue. Professorpoptarts, we're you plugged into HDMI at all times?
Sent from my SCH-I535 using xda premium

When it wasnt working yes, had everything connected, then powered up, then fastbooted. Even tried unplugging and plughing back in the hdmi a few times to try and get it to come on. However since I got it working I have not gad the issue (knock on wood)
Sent from my SAMSUNG-SGH-I337 using xda app-developers app

professorpoptart said:
When it wasnt working yes, had everything connected, then powered up, then fastbooted. Even tried unplugging and plughing back in the hdmi a few times to try and get it to come on. However since I got it working I have not gad the issue (knock on wood)
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
is there a custom kernel up for this device yet? I havent seen one.

Kernel source was released 4 days ago, it may take some time.
However, I'm currently working on porting Cyanogenmod 10 from source, professorpoptart is working on porting an aosp rom from the HTC One X+, and I'm probably going to release a "Custom ROM" tonight that's just an easy flash to add a bunch of extra functionality. So no kernels yet, but Roms should start popping up soon.

I love you all!

FrostyF7 said:
I love you all!
Click to expand...
Click to collapse
Hooray! I'm taking my ouya off craigslist! I was beginning to think nobody was going to develop for this box! I can't wait to start sending donations! (soon, life is expensive these days....).

Related

Retrieving data from phone memory of a screen-broken handset

Hi,
I should update my question:
Is it possible to access a Galaxy S i9000's internal sd (e.g. with ADB or an Android manager) without debugging enabled?
My screen is broken (can't see anything, not responding to touch I think, I can hear texts coming through but can't access them) and debugging is disabled but I need to get the data out.
'
Apparently ADB works straight up if the phone is in recovery mode. I've tried a lot of "blind" recovery mode attempts, but no go. ADB still doesn't recognise the device.
Other users have had this problem but they either a) had debugging enabled, or b) their touch works or can see a portion of the screen. Mine is neither.
adb?
Sent from my GT-I9300 using xda premium
slaphead20 said:
adb?
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
Tried adb using Droidzone's tutorial, but I can't enable usb debugging on my phone cause the screen is completely out of action.
It doesn't explicitly state this in the tutorial, but I gather debugging has to be on for adb to work, no?
is my handset a paperweight?
Sure not,acces the recovery(everything with blind mode on and mount your sd card and internal sd card. It can be done,recovery doesnt need any touch to work. I cant give you direct instructions right now but maybe some others can help you with those clicky things. What recovery you got?
Sent from my GT-I9000 using XDA
droidoidoid said:
is my handset a paperweight?
Click to expand...
Click to collapse
download this tool and give it a go http://forum.xda-developers.com/showthread.php?t=1761556
frogger5 said:
Sure not,acces the recovery(everything with blind mode on and mount your sd card and internal sd card. It can be done,recovery doesnt need any touch to work. I cant give you direct instructions right now but maybe some others can help you with those clicky things. What recovery you got?
Sent from my GT-I9000 using XDA
Click to expand...
Click to collapse
Man, I'm not sure what recovery I got. I flashed Darky ROM into my phone a while ago so I believe I have CWM. When I say blind I just mean trying to get into recovery without looking at the screen. It doesn't help that for my handset, some people say volume up and others say volume down. It's a big pain. I've done it before but I can't remember the key combo.
The only other thing I'm not sure about is the environment variable for ADB. I got it as PATH under User Variables and as Path under System Variables just to make sure. I think that's right.
xsenman said:
download this tool and give it a go http://forum.xda-developers.com/showthread.php?t=1761556
Click to expand...
Click to collapse
Getting 'error: device not found' on that one buddy.
Added the environment variable > Plugged the phone in (turned on) > started AndroPlatina > 5. Recovery Tools > 4. Reboot to Recovery > device not found
Will keep at it.
Ok if any methods above didnt work the blind recovery may be the last one. I just need the version of your recovery or just a version of darky rom so i can check the CWM. Trust me it can work sorry for my bad english im from east europe.
The COMBO for recovery is vol UP+home+power for a few seconds(maybe 3 or 4)
Sent from my GT-I9000 using XDA
frogger5 said:
Ok if any methods above didnt work the blind recovery may be the last one. I just need the version of your recovery or just a version of darky rom so i can check the CWM. Trust me it can work sorry for my bad english im from east europe.
The COMBO for recovery is vol UP+home+power for a few seconds(maybe 3 or 4)
Sent from my GT-I9000 using XDA
Click to expand...
Click to collapse
I believe it's Darky ROM 10.4.2
Need more info. Do you have stock recovery? CWM? TWRP?
What version of android? Gingerbread? ICS?
Sent from my Nexus 7 using Tapatalk 2
Kagadar said:
Need more info. Do you have stock recovery? CWM? TWRP?
What version of android? Gingerbread? ICS?
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
CWM
Gingerbread
If recovery mode auto-enables debugging then theoretically I should be able to view everything on my phone (texts, contacts, data etc) with an Android manager cause all an Android manager requires is that the phone be in debugging mode.
CWM has adb enabled. Try using Nexus S drivers straight from Google. Have you got a plan for how to extract the data once you adb in? Data isn't mounted in recovery by default. You can use the mount command, if you need details I'll add them in another post.
Sent from my GT-I9000 using Tapatalk 2
Kagadar said:
CWM has adb enabled. Try using Nexus S drivers straight from Google. Have you got a plan for how to extract the data once you adb in? Data isn't mounted in recovery by default. You can use the mount command, if you need details I'll add them in another post.
Sent from my GT-I9000 using Tapatalk 2
Click to expand...
Click to collapse
adb pull
What will the Nexus S drivers do?
So as long as adb isn't finding my device, I can rightly assume that I'm simply not in recovery mode. Maybe I am in recovery mode and something else is at fault, like with the adb installation. Could the environment variables be causing anything?
The ideal outcome would be to turn debugging on with adb so I can view the phone's contents using an Android manager. That way, I can get out the data, as well as read the texts that have been coming through. Don't know if this is possible though.
This is still the best I can get. I'm sick of seeing it.
--------------------------------------------
C:\>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
C:\>
--------------------------------------------
Update: adb works fine on my GS3 in recovery mode (with debugging turned off in settings) but not on my GS for some reason.
Check device manager on the computer. Is your phone showing up there at all? What about if you reboot into download mode?
Sent from my GT-I9000 using Tapatalk 2
^ Not showing up in device manager (GS3 shows up fine). Download mode same thing - I can attempt it blind but since I can't see the screen I don't know if I'm download mode - regardless, still nothing in device manager or adb.
I can manage to boot it up (I hear the intro). I can also hear the usb sound on my pc when I plug it in. But then I have to do 2 things with no screen a) do my security pattern, and b) tap 'mass storage mode'. Sounds easy but I've tried it many times and can't nail it.

Im a knucklehead - Formatted entire SD card

all my Rom zips and backups are gone. How can I access my internal SD card to copy a ROM over to it then flash?
I have no OS installed so it wont boot into anything except TWRP recovery
step by step instructions greatly appreciated
--------------------------------------------------------------------------------------------
EDIT: This is how I fixed my phone
I used the AIO toolkit to "Flash My Own Recovery" after I downloaded CWM Touch
http://goo.im/devs/Flyhalf205/M7WLS/Recovery/recovery-clockwork-touch-6.0.3.1-m7wls.img
I flashed CWM then booted into recovery and selected sideload
I used the AIO tool kit to select my ROM of choice and it installed perfectly
I am now in my phone and able to access my internal storage
Connect to PC, the copy over to storage on phone. Boot into recovery and install.
Chris9971 said:
Connect to PC, the copy over to storage on phone. Boot into recovery and install.
Click to expand...
Click to collapse
PC doesn't connect to internal storage unless completely booted into a ROM. I have no ROM installed. Just plugging my phone in to my PC doesn't open up my storage
Did you plug the phone in and let it install drivers? i'm assuming you're running Windows 7/8.
EDIT: Did you try ADB to see if computer recognizes phone? You could flash rom this way if it does.
Barman49 said:
Did you plug the phone in and let it install drivers? i'm assuming you're running Windows 7/8.
Click to expand...
Click to collapse
Ive had the phone plugged in many times and all drivers installed. When I plug it in now, my PC makes that noise that something is connected, but I don't get any prompts to install drivers or notifications that a device is connected.
If I try to boot, it just stays on the "HTC quietly brilliant" screen and goes no further
Barman49 said:
EDIT: Did you try ADB to see if computer recognizes phone? You could flash rom this way if it does.
Click to expand...
Click to collapse
no I haven't. What is ADB?
Are you trying to get into recovery (Power/vol down)?? If you can't get into that you need to use fastboot (ADB) to reflash recovery so you can access your internal. I'm guessing you know how to do this since you already had it. If not, lemme know. I can try and give step by step to get it back.
Barman49 said:
Are you trying to get into recovery (Power/vol down)?? If you can't get into that you need to use fastboot (ADB) to reflash recovery so you can access your internal. I'm guessing you know how to do this since you already had it. If not, lemme know. I can try and give step by step to get it back.
Click to expand...
Click to collapse
I can get into recovery no problem. I can even view whats currently on my internal storage (which is nothing lol) but I just need to connect to it to copy a ROM over
magnumtripod said:
I can get into recovery no problem. I can even view whats currently on my internal storage (which is nothing lol) but I just need to connect to it to copy a ROM over
Click to expand...
Click to collapse
Ok, I gotcha now. Sounds like the drivers aren't working between the phone & PC.
Goto HTC and download HTC Sync, sorry can't cause I don't have enough posts to show link.
Leave phone disconnected and let it install. Then try again. Report back.
Kinda a novice here but you did say you formatted the SD so I would ask how? But more importantly to what file format? fat32?
Not even sure what it is supposed to be but in trouble shooting this I would make sure the SD is formatted correctly. Just saying...and sorry for butting in here.
Barman49 said:
Ok, I gotcha now. Sounds like the drivers aren't working between the phone & PC.
Goto HTC and download HTC Sync, sorry can't cause I don't have enough posts to show link.
Leave phone disconnected and let it install. Then try again. Report back.
Click to expand...
Click to collapse
sweet will do
brb
HTC Sync doesn't recognize the phone
Everyone replying to this post has no clue what they are talking about. Head on over to the RUU thread by O.M.J. and follow my step by step to RUU back to stock and start from scratch bub.
Sent from my HTCONE using xda app-developers app
budroux said:
Kinda a novice here but you did say you formatted the SD so I would ask how? But more importantly to what file format? fat32?
Not even sure what it is supposed to be but in trouble shooting this I would make sure the SD is formatted correctly. Just saying...and sorry for butting in here.
Click to expand...
Click to collapse
There is a format option through TWRP (wipe/format data) that formats EVERYTHING. So whatever TWRP formats it as is what it is.
youkosnake said:
Everyone replying to this post has no clue what they are talking about. Head on over to the RUU thread by O.M.J. and follow my step by step to RUU (of 3 of that thread I believe)back to stock and start from scratch bub.
Sent from my HTCONE using xda app-developers app
Click to expand...
Click to collapse
Didn't mean to quote. My bad. Stupid app
Sent from my HTCONE using xda app-developers app
youkosnake said:
Everyone replying to this post has no clue what they are talking about. Head on over to the RUU thread by O.M.J. and follow my step by step to RUU back to stock and start from scratch bub.
Sent from my HTCONE using xda app-developers app
Click to expand...
Click to collapse
will check it out
Everyone responding seems to think you can get into your Rom. Just follow my step by step and start from scratch.
Sent from my HTCONE using xda app-developers app
Downloading the required files now
will this uninstall my recovery and unroot me? Is this a complete stock flash?
so I got these commands to work
fastboot oem lock
fastboot oem rebootRUU
but when i try to run the last command
fastboot flash zip c:/lol.zip
it just says
cannot load c:/lol.zip
and it has been renamed to lol.zip and is at the root of my C drive
my phone is currently on the black HTC screen
Try it without the c:/
Sent from my HTCONE using Tapatalk 2
Barman49 said:
Try it without the c:/
Sent from my HTCONE using Tapatalk 2
Click to expand...
Click to collapse
I tried every combination

[Q] HELP! I rooted my HTC ONE 801n everything was fine until...

Hey you guys what's up!
I unlocked the bootloader on my HTC One via HTC Devs and flashed a custom recovery (CWM) and then flashed Cyanogenmod 10.1 and everything was AMAZING and great I was updating the nighties almost daily and I was having a blast! Then my Google Apps stopped working. They would have a server error repeatedly and I couldnt update my apps on Play store or use G+ or sync my email none of my Gapps were working. So i figured i'd relfash my GAPPS and thats exactly what i did still nothing changed. So I wiped the device and reinstalled Cyanogenmod. In the welcome screen when i sign to Gmail, it gave me the same server error. So I wiped the sd card by accident and now i'm on Recovery but NO ROMS to flash! And because the phone doesn't support an external SD Card, I cannot add the rom again to flash it via recovery! I tried to adb sideload but it wont work the adb installer keeps telling my windows 8 64bit error! Also, I tried to mount the sdcard to copy the rom again and flash it in recovery but it wont mount my computer wont read the phone. It gives me the alert that the phone is connected but i do not get to access the memory to copy a rom to it.
Now I'm stuck with a HTC One that has CWM recovery and no roms to boot. Please please help!
Thanks
This happened to me. With cwm you'll just have to side load a new zip. Use adb sideload ROM.zip this should get you back in business.
Sent from my One using xda app-developers app
jalati said:
This happened to me. With cwm you'll just have to side load a new zip. Use adb sideload ROM.zip this should get you back in business.
Sent from my One using xda app-developers app
Click to expand...
Click to collapse
Thats what i initially tried to do, when i go to sideload adb the command screen i type in the command but nothing happens on the phone
If you have an OTG cable it will come in handy here. Try uninstalling the drivers and reinstall them
Sent from my HTC One using Tapatalk 4 Beta
just curious
altimax98 said:
If you have an OTG cable it will come in handy here. Try uninstalling the drivers and reinstall them
Sent from my HTC One using Tapatalk 4 Beta
Click to expand...
Click to collapse
Why would an OTG cable come in handy? I have one but haven't really found any practical uses for it beside hooking up a mouse, keyboard, or sd reader.
---------- Post added at 04:37 AM ---------- Previous post was at 04:35 AM ----------
adezd00 said:
Why would an OTG cable come in handy? I have one but haven't really found any practical uses for it beside hooking up a mouse, keyboard, or sd reader.
Click to expand...
Click to collapse
after reading my own post, im guessing to to put zip files on an sd card when you cant use adb?
I'm having a similar problem, I can't access the sdcard (or /data directory) and don't have an OTG cable. Any way I can access the /data directory? recoveries keep showing it as 0MB. :/
---
EDIT: Got it fixed. Sideload didn't work on TWRP. I tried using CWM and it froze the computer I was doing it from. I tried again from another computer and I decided to wait a few minutes and it started pushing it. Eventually the rom installed and all is well!
I think the problem occured when trying to install a rom before and recovery rebooted in the middle of the installation which messed up the /data directory. I lost all access to it and ended up wiping it all (prob didn't need to) and sideload fixed it.
boys, i figured it out. I have used a OTG Cable copied the rom to a usb stick and bam! i'm a satisfied customer!
Slorks said:
boys, i figured it out. I have used a OTG Cable copied the rom to a usb stick and bam! i'm a satisfied customer!
Click to expand...
Click to collapse
Good to hear
Sent from my HTC One using Tapatalk 4 Beta

[Q] HTC One: Think I've Fudged It :(

Hope this is in the right place.
I formatted my HTC1 like an idiot when I meant to wipe and am a little stuck.
ADB doesn't register on my PC so I can't sideload.
No installed ROM so I can't get into the system.
RUU flashes fail with a (remote: 24 parsing android-info fail)
Rooted, S-On and I have custom recovery images... TWRP and CWM...
I've tried everything I can think of and everything google can think of...
Any help at all would be greatly appreciated.
Thanks in advance
If you know someone with an OTG cable you can load it off a thumbdrive
Sent from my Nexus 10 using Tapatalk 4
Check this out:
http://forum.xda-developers.com/showthread.php?t=2325853&highlight=sideload
You should be able to ADB Push a Rom to your phone, then ADB Sideload it. May need to reflash recovery first, I recommend TWRP
altimax98 said:
If you know someone with an OTG cable you can load it off a thumbdrive
Sent from my Nexus 10 using Tapatalk 4
Click to expand...
Click to collapse
Figured this was my only remaining option and have ordered an OTG cable, arrives on Monday was just hoping to find another way so I didn't have to wait.
dgtiii said:
Check this out:
http://forum.xda-developers.com/showthread.php?t=2325853&highlight=sideload
You should be able to ADB Push a Rom to your phone, then ADB Sideload it. May need to reflash recovery first, I recommend TWRP
Click to expand...
Click to collapse
I've tried this and many variants of ADB just isn't recognised on my PC
Thankyou both for your replies they are greatly appreciated!
Rechi03 said:
Figured this was my only remaining option and have ordered an OTG cable, arrives on Monday was just hoping to find another way so I didn't have to wait.
I've tried this and many variants of ADB just isn't recognised on my PC
Thankyou both for your replies they are greatly appreciated!
Click to expand...
Click to collapse
The only thing I can think of then is to find an RUU for your phone hopefully. ADB Push/Sideload normally works in your situation. Try a different cable, different USB port, different computer
dgtiii said:
Check this out:
http://forum.xda-developers.com/showthread.php?t=2325853&highlight=sideload
You should be able to ADB Push a Rom to your phone, then ADB Sideload it. May need to reflash recovery first, I recommend TWRP
Click to expand...
Click to collapse
This guide saved my a$$ too, when I accidentally deleted my system folder. Try a different PC, it works all the time, it will work for you too.
And oh, OTG didn't work for me. I suggest you try a different machine.
humbug got my OTG cable this morning and it appears to work fine... installed Revolution HD 20.1.. tells me install compete and reboots and then brings me to the same blank screen I've been staring at for the last couple of days.
I'm obviously missing something but...
Rechi03 said:
humbug got my OTG cable this morning and it appears to work fine... installed Revolution HD 20.1.. tells me install compete and reboots and then brings me to the same blank screen I've been staring at for the last couple of days.
I'm obviously missing something but...
Click to expand...
Click to collapse
do you have a windows computer?
you most likely just need to install some drivers and then ADB will work.
https://dl.dropboxusercontent.com/u/74163067/HTC ONE DRIVERS.zip
those are the windows drivers. unzip the folder. open device manager. see here http://i.imgur.com/9LeGRJI.png
right click the "htc one" > "update driver software" > "browse my computer" then select the folder where you extracted the zip to. it will automatically install the correct driver. do the same for "my HTC" or any other devices that appear in those two top-level menus.
Have been through multiple drivers, some of which apparently work but still cant find the device when i try to push or sideload.
Have just done a full wipe and am going to attempt starting again from scratch with TWRP and Revolution HD.
Just to clarify I have tried multiple ports and cables, even bought a new USB 3 card, I don't have access to another PC or Laptop.
Rechi03 said:
Have been through multiple drivers, some of which apparently work but still cant find the device when i try to push or sideload.
Have just done a full wipe and am going to attempt starting again from scratch with TWRP and Revolution HD.
Just to clarify I have tried multiple ports and cables, even bought a new USB 3 card, I don't have access to another PC or Laptop.
Click to expand...
Click to collapse
Adb doesn't like usb 3, apparently.. Are you sure you're opening the cmd window from inside the adb/fastboot folder?
Sent from my HTC One using XDA Premium 4 mobile app
sideload is working as I type... it seems flashing recovery as aposed(SP?) to just booting a recovery makes a world of difference, will let you know if the install works. usb3 doesn't seem to be an issue though.
Hussah! It works! Thankyou all for you suggestions and input it has been greatly appreciated!
To flash with adb you need to boot ur phone in recovery mode, not in the bootloader... Took me a while to understand that

HELP!!! I bricked my N3!!!

Ok. So rooted my Note 3 in Oct and ROMd in Jan with XNote 7. I had it all fine and everything since. Well, I upgraded to XNote 12 and realized I couldn't receive calls and a few other weird annoying bugs. So I attempted to downgrade back to MJ5 using the Restore tutorial in the General section.
Alright, well I did the whole tutorial I Heimdalled the MI9_Fix.img.ext4 file and then started flashing the ZIPs. I did the SEC_CSC then I tried the 2400845 and it failed with a message about system/vender/lib.camerafilter.whatever.so couldn't be found and quit. I figured it was normal so and now I'm stuck at the Samsung logo with a padlock. It will go into recovery and Odin mode fine.
It also deleted my Safestrap. So I cannot get into SS recovery. I have tried the tutorial again and now Heimdall quits with error 87 and something about a I/O error.
I have also tried to Odin the MJ5 stock flash files (AP, BL, CP and PIT) but it does nothing. I cannot install a ROM and cannot use my phone.
I desperately need my phone for work, so if someone can help me out ASAP, so I don't lose my job, I would be SO grateful! THANK YOU!!!!
533y4 said:
Ok. So rooted my Note 3 in Oct and ROMd in Jan with XNote 7. I had it all fine and everything since. Well, I upgraded to XNote 12 and realized I couldn't receive calls and a few other weird annoying bugs. So I attempted to downgrade back to MJ5 using the Restore tutorial in the General section.
Alright, well I did the whole tutorial and started flashing the ZIPs. I did the SEC_CSC then I tried the 2400845 and it failed with a message about system/vender/lib.camerafilter.whatever.so couldn't be found and quit. I figured it was normal so I Heimalled the MI9_Fix.img.ext4 file and now I'm stuck at the Samsung logo with a padlock. It will go into recovery and Odin mode fine.
It also deleted my Safestrap. So I cannot get into SS recovery. I have tried the tutorial again and now Heimall quits with error 87 and something about a I/O error.
I have also tried to Odin the MJ5 stock flash files (AP, BL, CP and PIT) but it does nothing. I cannot install a ROM and cannot use my phone.
I desperately need my phone for work, so if someone can help me out ASAP, so I don't lose my job, I would be SO grateful! THANK YOU!!!!
Click to expand...
Click to collapse
do the procedure again and follow it to the letter as i can see you can still get to dl mode, btw you're supposed to flash the sec_csc and 240058 AFTER you flash the system.img with heimdall.
posersk8r said:
do the procedure again and follow it to the letter as i can see you can still get to dl mode, btw you're supposed to flash the sec_csc and 240058 AFTER you flash the system.img with heimdall.
Click to expand...
Click to collapse
I can do the ODIN part, then when I try the Heimdall part, it comes up with an error. I have tried it 5 times over. To a T... : (
And yes, I know you flash those BEFORE. That's what I meant to say, but I was in a rush...
Im in a similar pickle but my problem is that I need a way to get those files to the SD card because the thing is bricked. I can't copy the files to a bricked phone and every device in my house refuses to read the micro SD card.
533y4 said:
I was in a rush...
Click to expand...
Click to collapse
That's the problem right there. Over in my thread about the kitkat update fix people are saying it's not working for them but they are missing steps because they're not reading everything. I've used that method 3 times so far and it worked all 3 times. Start from the beginning. Delete all the files from previous attemtps, go to step 1, read everything, you will get it.
mazdamiata210 said:
That's the problem right there. Over in my thread about the kitkat update fix people are saying it's not working for them but they are missing steps because they're not reading everything. I've used that method 3 times so far and it worked all 3 times. Start from the beginning. Delete all the files from previous attemtps, go to step 1, read everything, you will get it.
Click to expand...
Click to collapse
Again, I have done this 5 times. No joke. I have redownloaded everything 3 times.
1) Download and install Heimdall from here for windows. You'll need this and this to avoid missing .dll file errors
2) Download the following files;
MI9_fix.img.ext4
https://mega.co.nz/#F!icMTnSQY!bMBNFmUnn2_K8olSTYpwIA (mirror provided by drakeymcmb)
sec_csc.zip
rldv.zip
2400258.zip
Put everything except for the system.img on your external SD card
3) Download and install the MJ5 partions. Use Odin to flash these files (match the file names with the different upload slots)
AP_N900AUCUBMJ5.zip
BL_N900AUCUBMJ5.zip
CP_N900AUCUBMJ5.zip
HLTE_USA_ATT_32G.pit
4) Now is the time to use Heimdall.
Reboot into Download Mode once Odin finishes.
Install the vcredist packages downloaded from step 1.
unzip the heimdall .zip file to c:/
go to c:/Heimdall Suite/Drivers and click on zadig.exe
click the middle menu button to select "Show All Devices"
from the dropdown, select MSM8960
click the "install driver" button.
you should see a success message
5) Navigate on your computer to c:/Heimdall Suite/ and open heimdall-frontend.exe.
IMPORTANT -- Go to the Utilities tab and click the "Detect" button
Go to the Flash tab on Heimdall, click Browse and select the HLTE_USA_ATT_32G.pit file downloaded from step 3
Click the 'add' button, then next to 'partition name' select system from the dropdown.
click the Browse button underneath the dropdown, and select the MI9_fix.img.ext4 image you downloaded from step 2.
6) Click Start. ***I usually check the 'No Reboot' box to prepare for booting into recovery
THIS IS WHERE I CAN NO LONGER GO ANY FURTHER!!! IT SPITS A I/O ERROR 87 AT THIS POINT! I CANNOT GET AROUND THIS! THIS IS WHAT I NEED HELP WITH!
7) Heimdall and your Note will report a bad flash at around 95% -- but don't worry -- your system.img got uploaded Reboot directly into recovery mode.
8) Once in recovery, select "Choose update from external" in the recovery, and select the sec_csc.zip you downloaded earlier (did you remember to put that file on your external SD card?). This will install the CSC files and run the preload checkin so you don't FC all over the place
9) IMPORTANT--After flashing the sec_csc, the Note will reboot.
Try to catch it in time to reboot BACK into recovery
Once in recovery, select "Choose update from external" in the recovery, and select the 2400258.zip you downloaded earlier.
This will give you a stock MJ5 system. You can choose to stop here if you don't want to root.
10) Extract rldv.zip to the root of your internal sdcard (NOTE **my script removes Knox apps). Reboot, then once SuperSu installs, Reboot again.
This leaves you with a rooted MJ5 device.
533y4 said:
Again, I have done this 5 times. No joke. I have redownloaded everything 3 times.
Click to expand...
Click to collapse
Did you do this??
go to c:/Heimdall Suite/Drivers and click on zadig.exe
click the middle menu button to select "Show All Devices"
from the dropdown, select MSM8960
click the "install driver" button.
you should see a success message​
mazdamiata210 said:
Did you do this??
go to c:/Heimdall Suite/Drivers and click on zadig.exe
click the middle menu button to select "Show All Devices"
from the dropdown, select MSM8960
click the "install driver" button.
you should see a success message​
Click to expand...
Click to collapse
Yes. And everytime I try this again I have to delete and revert drivers, because ODIN won't see it afterwards. X_X
The drivers named "WinUSB 6.1.7600"
533y4 said:
Yes. And everytime I try this again I have to delete and revert drivers, because ODIN won't see it afterwards. X_X
Click to expand...
Click to collapse
Switch usb ports, switch usb cables, switch computers if possible.
Are you on an administrator account for windows?
mazdamiata210 said:
Switch usb ports, switch usb cables, switch computers if possible.
Are you on an administrator account for windows?
Click to expand...
Click to collapse
I will try this. I am on a ASUS G75 with Win 7 Ultimate X64 via USB 2.0 not USB 3.0. The account I am using is the Administrator. I'm also going to try and run Heimdall as Admin. I'll report back in about 10 mins.
533y4 said:
I will try this. I am on a ASUS G75 with Win 7 Ultimate X64 via USB 2.0 not USB 3.0. The account I am using is the Administrator. I'm also going to try and run Heimdall as Admin. I'll report back in about 10 mins.
Click to expand...
Click to collapse
If that doesn't work try this...
fire up zadig, connect phone while in download mode, install the driver for msm8960, fire up heimdall frontend, go to utilities tab, hit detect button, and then go to flash screen and check no reboot, then start...
I also did mine with usb 3.0 and it worked fine so I don't think that matters. Using the stock cable also.
I was in the same boat. I had to switch computers and it worked first time. Both of them were windows 8.1 btw.
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
Did you try changing ports for heimdall? Sounds like its not recognizing your n3, had that problem before too where after odin'ing the mj5 files heimdall wouldnt see my phone. Did a reboot on my laptop and changed ports had 7 different 2.0 cables. Just keep trying did this 5 times already and always had the same result.
Sent from my SAMSUNG-SM-N900A using xda app-developers app
So is there no way to mount the card so that I can copy these files if I am bricked?
mazdamiata210 said:
If that doesn't work try this...
fire up zadig, connect phone while in download mode, install the driver for msm8960, fire up heimdall frontend, go to utilities tab, hit detect button, and then go to flash screen and check no reboot, then start...
I also did mine with usb 3.0 and it worked fine so I don't think that matters. Using the stock cable also.
Click to expand...
Click to collapse
Did this every single time. I also have tried all 4 USB ports. This program (Heimdall) worked the first time no problem. That's the weird part... The second and on time all is a no go.
I have attached pictures. 3.jpg is Heimdall with the error.
Have you tried rebooting your g75? Also make sure you're not running any anti malware antivirus firewall etc.
Sent from my SAMSUNG-SM-N900A using xda app-developers app
---------- Post added at 01:38 AM ---------- Previous post was at 01:27 AM ----------
Dumb question but did you click on replace driver on the second picture you posted? The winusb driver is the one you need for heimdall frontend to detect your phone.
Sent from my SAMSUNG-SM-N900A using xda app-developers app
posersk8r said:
Have you tried rebooting your g75? Also make sure you're not running any anti malware antivirus firewall etc.
Sent from my SAMSUNG-SM-N900A using xda app-developers app
---------- Post added at 01:38 AM ---------- Previous post was at 01:27 AM ----------
Dumb question but did you click on replace driver on the second picture you posted? The winusb driver is the one you need for heimdall frontend to detect your phone.
Sent from my SAMSUNG-SM-N900A using xda app-developers app
Click to expand...
Click to collapse
Yes. I actually powered down the machine completely, removed the charger and battery, let it sit for 5 mins and retried.
Also, yes I did. That was before I did click replace tho. Good eyes. ^__^
{[EDIT]}
Does anyone have any input on the Hard Brick recovery method? The unbrick.img method? I tried it with (what I think was MJ5, but not 100% sure) a 64GB class10 UHS-1 Lexar MicroSD Card. I booted into download mode and nothing. Not sure if I did that wrong, or if the card isn't compatible, or the IMG isn't correct (anyone have any links to the unbrick.img for MJ5?)...
533y4 said:
Yes. I actually powered down the machine completely, removed the charger and battery, let it sit for 5 mins and retried.
Also, yes I did. That was before I did click replace tho. Good eyes. ^__^
{[EDIT]}
Does anyone have any input on the Hard Brick recovery method? The unbrick.img method? I tried it with (what I think was MJ5, but not 100% sure) a 64GB class10 UHS-1 Lexar MicroSD Card. I booted into download mode and nothing. Not sure if I did that wrong, or if the card isn't compatible, or the IMG isn't correct (anyone have any links to the unbrick.img for MJ5?)...
Click to expand...
Click to collapse
Well it's not bricked because you can boot into download and recovery mode. It sounds like it's just a driver issue with heimdall.
mazdamiata210 said:
Well it's not bricked because you can boot into download and recovery mode. It sounds like it's just a driver issue with heimdall.
Click to expand...
Click to collapse
I'm going to try my girls computer tomorrow after work. See if her crappy Toshiba can do any better.
My Phone is DEAD
I was talking on my phone yesterday and it just shut off and hasn't been back on since. It is not responding to anything i try. Power + Vol down + Home. When i plug it up, there is no sounds or vibration no response. The phone is in a permanent off state. Any thought or suggestion on how to repair. I did the OTA update last week SM-N900A.

Categories

Resources