[HOWTO]- Performing a Nandroid Restore Manually using ADB - Hero, G2 Touch Android Development

[HOW TO] Perform a Nandroid Restore via the Android Debug Bridge (ADB)
(This guide assums that you have already installed and set up adb tools on you PC)
1. Start phone in recovery mode, by turning it on while holding "Home" and "Power" buttons.
2. Plug the phone into the PC with a USB cable
3. Start Windows Command Prompt on your PC, by pressing Start on your PC and typing CMD into the run or search bar depending on your operating system. Then selecting Command Prompt.
4. Within the command prompt window, change the directory to the one your adb tools are by typing the following:
cd c:\sdk\tools
Click to expand...
Click to collapse
The path you put in may be different to this example, as it depends where on your PC your adb tools are kept.
5. Then type:
adb shell
Click to expand...
Click to collapse
6. Now type:
mount /sdcard
Click to expand...
Click to collapse
7. Now you need to change directory again to the one holding your nandroid back-up data, so first type
cd /sdcard
Click to expand...
Click to collapse
8. Then type:
cd nandroid
Click to expand...
Click to collapse
9. Now you need to find the specific name for the folder that holds your Nandroid Backup images, so type:
ls
Click to expand...
Click to collapse
and view the list that appears.
10. Now to enter the folder you want to back up to type
cd HT**********
Click to expand...
Click to collapse
obviously replacing the *s with your numbers and letters. FYI the number string is your Device Serial number.
11. Again type
ls
Click to expand...
Click to collapse
and view the list that appears.
12. Now to enter the folder you want to back up to type
cd BCD***-********-****
Click to expand...
Click to collapse
obviously replacing the *s with your numbers and letters. FYI the format of these digits is BCDXYZ-YYYYMMDD-HHMM from when the back up was created.
13. Now type:
nandroid-mobile.sh restore
Click to expand...
Click to collapse
14. Just press enter to select default.
15. Double check that the Default backup that is found is the one you want then press enter again.
Your selected backup will now be restored. When your CMD window looks like the one below you can reboot your phone and it will be as you remember it.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
A big thanks goes to Pulser, without whom I would still be stuck, and this guide wouldn't have been written.

Nice. But are steps 6-12 really necessary? When in shell it should enough enter nandroid-mobile.sh -r, press enter to get you the list of available backups, pressing enter once again restores the last backup, or if you want an older just type the full name of that backup.

Install apk
Hello Fellow Androids!
If this is off topic, please accept my apologies. I am searching through all of XDA for a simple solution to adding apk. Now before you start bashing, please keep in mind that I am well aware of the "search" options + google + XDA etc.
Long story short, I have:
1) Rooted
2) Fashed many Roms (currently on Stock 2.1)
3) Lag Fixxed (see signature)
4) Removed Bloatware
5) I am familiar with ABD and commands
Problem:
All I'm trying to do is install certain "apk"s using ADB. I am well aware of the Program that installs/ pushes apps automatically that are found in G1 + Vibrant + HTC + Droid Forums without having to do any typin......BUT.....I would like to know my way around ABD <----Main reason why i dont want the easy way out.
I have been here:
http://forum.xda-developers.com/showthread.php?t=716806
as well as here:
http://forum.xda-developers.com/showthread.php?t=743457
even been here:
http://forum.xda-developers.com/showthread.php?t=740545
I know what you are thinking, why not use them? As i said before, i would like to be efficient with ADB. So...
I have tried methods found here:
http://forum.xda-developers.com/showthread.php?t=517874
As well as:
http://forum.xda-developers.com/showthread.php?t=532719
The problem I am having is:
Whether i navigate to my folder (desktop with all my apps) and use either
"adb push app /system/sd/app
adb push app-private /system/sd/app-private"
or simply
"adb install <path to file> - Example: adb install c:/apps/apps2sd.apk"
I always get the error: "cant find <whatever apk> to install"
No matter which directory i have it, i get that message.
Note:
1) I have debugging on
2) I mounted sd <----also tried Without mounting
3) I have used the same command when I removed bloatware but i understand Adding apks are slightly different.
4) I have all the drivers installed + Microsoft's .net framework + etc
What am i doing wrong?
All Critics, input, education bashing (just not hating) lol are welcome. Thanks!

put adb in your path... cd to the apk directory and run adb push *.apk /system....

TylerDurdenK said:
[HOW TO] Perform a Nandroid Restore via the Android Debug Bridge (ADB)
(This guide assums that you have already installed and set up adb tools on you PC)
and view the list that appears.
12. Now to enter the folder you want to back up to type
obviously replacing the *s with your numbers and letters. FYI the format of these digits is BCDXYZ-YYYYMMDD-HHMM from when the back up was created.
13. Now type:
MD window looks like the one below you can reboot your phone and it will be as you remember it.
http://farm3.static.flicn.[/QUOTE]
I get the error "nandroid-mobile.sh not found" after step 13. please help.
Click to expand...
Click to collapse

Dont use this, use jordfaz's clockworkmod, if you really need to use this adb script then you need to get nandroid-mobile.sh script somewhere

Related

[Q] Adb is not recognized as an intern or extern command

Hi, so i'm very new to Android and while attempting to do the gfree permaroot for my desire Z, i came across a problem. When I type the commands, it says that adb is not and intern or extern command. I have adb file in platform-tools (400ko). When i open it, it make a cmd screen for about 2 seconds then shuts down. Can someone help me with this problem
I just installed HTC sync and my computer cannot find any device attached. It says: the htc vision htc port does not repons.
Thanks
Vince
are you doing CD C:/location of adb/adb?
You must direct your command line to the directory of adb.
also run cmd as administrator if you're on vista or win7.
If you're not a command line pro I suggest you just rename your folder to whatever you want in C:/folderhere
For example heres the folder renamed to "android"
then just do CD C:/android
Then type "adb" and hit enter
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
and boom! you're in adb!
Hope this helps
I'm no adb pro but I'm ok at cmd. Maybe I should make a video or something on the basics to getting adb running if there isn't one already?
Thanks for the quick reply! It helped me figure out that you need to open adb before using the adb command but the same error occurs (is not an intern/extern command) when i try it
Vincethedevil said:
Thanks for the quick reply! It helped me figure out that you need to open adb before using the adb command but the same error occurs (is not an intern/extern command) when i try it
Click to expand...
Click to collapse
Nah, you still aren't getting it
How did you install ADB? If you search in Windows for the file "adb.exe" what does it tell you?
it's in the platform tools folder in the sdk
Vincethedevil said:
Thanks for the quick reply! It helped me figure out that you need to open adb before using the adb command but the same error occurs (is not an intern/extern command) when i try it
Click to expand...
Click to collapse
I'm not quite sure what you mean by this, I wonder if you're doing something wrong. Have you followed this guide ? http://forum.xda-developers.com/showthread.php?t=865685
If you have added the correct folders to your path, as explained in the guide, it should find adb ok.
If it's finding adb ok, then if you run "adb devices", is that not showing your phone ? Are you using the original HTC cable to connect to your phone ? Third-party ones sometimes will not work.
Yeah i'm using the original Htc cable. I have downloaded Htc Sync and it appears as "my htc" in device manager. Although, Htc sync doesn't recognize any plugged in phone.
For adb, i go in cmd, change the path with cd to the path where is the adb.exe, then type adb. A series of text follow. Then, i switch to the folder where is gfree (with cd) and type the first line for temp root. That when it says that adb is not recognized as an intern or extern command
Since adb.exe is not located in your gfree directory, it's not a recognized command. You either need to run the commands directly from your platform tools directory (and use the full directory paths for the gfree commands) or place the path for adb in your environment variables so that adb can be called from any directory (step four in the ADB for noobies linked earlier). This is the easier method.
I tried it but it's not working. I'll take pictures tomorrow so my obvious noob error can be spotted
Adding adb to your path
Hey there,
Here's a quick guide to fix your problem (basically, you don't have adb added to your path). Btw, this guide was made on Windows 7, but the principle should be the same for Vista and XP (though the steps are different).
Step 1: Right click "Computer" or "My Computer"
Step 2: On the left side find "Advanced system settings" and click it.
Step 3: On the Advanced tab, click "Environment variables"
Step 4: In the bottom part of the window, scroll until you find the row that starts with "Path" and click "Edit"
Step 5: At the end of the existing line, add a semicolon ( ; ) and the path to your android toolkit. If the path contains spaces, don't forget to enclose it in quote marks ( "C:\path to adb\tools\" )
Vincethedevil said:
For adb, i go in cmd, change the path with cd to the path where is the adb.exe, then type adb. A series of text follow. Then, i switch to the folder where is gfree (with cd) and type the first line for temp root. That when it says that adb is not recognized as an intern or extern command
Click to expand...
Click to collapse
You haven't set the Path up so that it can find adb, as has been said, and that's all covered in the guide that I previously linked to. But the previous poster has provided you with an excellent step-by-step solution.
Thanks alot, my adb problem is now solved! I just have one more question, when i plug my phone, htc sync cannot recognize it. Although, when i write adb devices in cmd, my phone appear. Am I still gonna be able to permaroot or should i mess with the drivers.
Thx
Vince
It's not a driver problem, it's an HTC Sync problem. Your phone has to be in Sync mode and you have to wait a few minutes (mine takes up to 20 mins) for HTC Sync to recognize it.
sounds like you'll be able to root just fine if it recognizes and responds to adb.
Not sure about htc sync, I don't even know what that is...lol
not able to root
i am using this procedure
http://forum.xda-developers.com/showthread.php?t=1601038
as i am running runme.bat i am getting this screen please help
Need to set up adb, there are tons of guides on xda and the web to do this properly, follow one of them and then try your whatever you're doing again
Sent from my Nexus 7 using xda premium
demkantor said:
Need to set up adb, there are tons of guides on xda and the web to do this properly, follow one of them and then try your whatever you're doing again
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
thanx for reply/..
not able to to set up adb.. please help if you can
should i uninstall existing drivers and again install it
You may need to reinstall drivers but first make sure you have the right ones as well as adb.exe download from the sdk or whereever you get it
See the third post. In this thread
http://forum.xda-developers.com/showthread.php?p=31899577
If you're still having issues let me know and ill help ya
Sent from my MyTouch 4G Slide using xda premium

Backup and Restore Galaxy Nexus without root (Mac)

UPDATED 2/3/12
Thanks to @copkay for writing this! http://forum.xda-developers.com/showthread.php?t=1420351 (windows version)
copkay said:
Like a lot of you, I have been putting off unlocking the bootloader on my Nexus because I didn't want to have to go through the hassle of backing up everything manually and restoring individual application data; logging back into apps; saving settings; etc. I found an undocumented (at least as far as my googling was able to find) feature in the latest version of the ADB platform tools (for Android 4.0+) that allows you to create a full system backup, including app apks, their respective data, as well as the internal storage.
This guide assumes you have already installed the Android SDK, and updated the Android SDK Platform Tools to the latest version (currently Rev 10) using the SDK Manager.
Click to expand...
Click to collapse
1. Connect your device via USB, and open Terminal.
2. In Terminal, type "cd " with the space and then drag your "platform-tools" folder in the android sdk where the space is, it should look like this "cd /where ever you put the folder/name of you computer/android-sdk-mac-osx/platform-tools". Drag and drop will do this for you, then hit enter.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
3. In the same terminal window, type "./adb" and hit enter. A lot of stuff with come up that you really dont need to worry about.
4. Optionally, type the command "./adb devices" to ensure that your device is properly recognized. If you're comfortable with ADB already, just skip this.
The command parameters format is:
./adb backup [-f <file>] [-apk|-noapk] [-shared|-noshared] [-all] [-system|nosystem] [<packages...>]
Click to expand...
Click to collapse
The most basic command you can use is simply:
./adb backup -all
Click to expand...
Click to collapse
This will use the defaults to backup only app and device data (not the APKs themselves) to the current directory as 'backup.ab'
To explain the parameters:
./adb backup -f <file>
Click to expand...
Click to collapse
Use this to choose where the backup file will be stored, e.g. '-f /backup/mybackup.ab', which will save it at the root of your drive (C:\ for Windows, etc.) in a folder called backup, as a file named 'mybackup.ab'. I recommend using this flag to set a location manually, as with my first backup test, it said that it completed successfully, but I was unable to locate the backup file. I have no idea where it was saved, but it wasn't where it should have been located.
./adb backup -apk|-noapk
Click to expand...
Click to collapse
This flags whether or not the APKs should be included in the backup or just the apps' respective data. I personally use -apk just in case the app isn't available in the Market, so that I don't have to go hunt it down again. The default is -noapk.
./adb backup -shared|-noshared
Click to expand...
Click to collapse
This flag is used to "enable/disable backup of the device's shared storage / SD card contents; the default is noshared.", which for the Nexus I would certainly flag to -shared, but from my test, it did not restore all of the contents of my internal storage, so I recommend backing up music, pictures, video, and other internal storage items manually, just to be on the safe side. The default is -noshared.
./adb backup -all
Click to expand...
Click to collapse
This flag is just an easy way to say to backup ALL apps. The packages flag (further on) can be used to choose individual packages, but unless you're just wanting to backup a specific application, use -all for a full system backup.
./adb backup -system|-nosystem
Click to expand...
Click to collapse
This flag sets whether or not the -all flag also includes system applications or not. I used -system, but this is probably unnecessary, and I would almost guess that it is safer to use -nosystem, but use your own judgment on this. The default is -system.
./adb backup <packages...>
Click to expand...
Click to collapse
Here you can list the package names (e.g. com.google.android.apps.plus) specifically that you would like to backup. Use this only if you're looking to backup a specific application.
3. Once you've made your decision on how to perform the backup, simply type the command as you would like it; in my case, this is the command that I used:
./adb backup -apk -shared -all -f /c/backup20111230.ab
or
./adb backup -apk -shared -all -----------and then just search for it in finder.
Click to expand...
Click to collapse
4. You will see a screen like the following:
5. Enter a password (if desired) for encryption of the backup file. RETAIN THIS PASSWORD FOR RESTORING LATER.
6. This process will take several minutes to complete, depending on the settings you've chosen, but when completed, you should get a toast on-screen saying 'Backup Complete', or if you miss that, you'll know once your command line has returned.
7. Now go unlock your bootloader (not going to go into the process for this guide, but you probably know how already, and if not, there are several guides a search away).
8. Once you're booted back into Android, you can choose to add your account now, or skip that for later. I skipped it for later, but I think it might make the process more smooth to sign in before the restore. YMMV.
9. To restore, with your device connected open your command prompt again, and type:
./adb restore /backup/mybackup.ab
Click to expand...
Click to collapse
replacing '/backup/mybackup.ab' with the location of your backup file.
10. You will see a screen like the one below:
11. Simply type in your current encryption password (if you've set one), and the password with which the backup was encrypted (if you chose to set a password), and the restore will begin. It again will take several minutes depending on the size of the backup and the options chosen.
12. You're back to normal, short of possibly some widgets on the home screen. My wallpaper was even restored, my app folders remained just as I had them before, my alarms remained, and for most applications, I didn't even have to log back in; it kept everything.
________________________
NOTE: I did have an issue with not all files being restored to the Internal Storage; in particular, the Gallery still displayed all the folders and files that it had cached (which it expected to be there) as only gray boxes, and would not display the images, nor would it rescan the media. I simply copied the files back to the Internal Storage directory manually, and all was well again. Again, YMMV.
NOTE : Also to note, this will not back up SMS messages, so if you're concerned about those, you may want to look into an alternative application to back up SMS.
Hope this is able to help! If so, give me a thanks )) and let me know how your experience goes.
- Sean
Worked
I couldn't get it to work no matter how much I tried. I could connect and see the device but when I ran the command, all I would get was a list of commands. I finally found a way upgrade the sdk by:
./android update sdk --no-ui
Then it worked perfectly!!
bosshoss16 said:
I couldn't get it to work no matter how much I tried. I could connect and see the device but when I ran the command, all I would get was a list of commands. I finally found a way upgrade the sdk by:
./android update sdk --no-ui
Then it worked perfectly!!
Click to expand...
Click to collapse
Ya in the beging when I said you need the sdk package, I forgot to say for all to be updated, whoops. Was that your problem?
Hipe0ples555 said:
Ya in the beging when I said you need the sdk package, I forgot to say for all to be updated, whoops. Was that your problem?
Click to expand...
Click to collapse
Yeah, after I updated the sdk, it worked perfectly! Thanks!!
I'm completely new to this. I downloaded the SDK manager and the Platform tools.
Terminal opened automatically with the manager. Then I did number 2 which worked fine.
After that when I type the commands from number 3 and 4 nothing happens when I hit enter. Any help would be appreciated.
Is it possible my Mac doesn't see the Nexus. Is the Nexus supposed On or Off by the way, I had it On.
ivoniko said:
I'm completely new to this. I downloaded the SDK manager and the Platform tools.
Terminal opened automatically with the manager. Then I did number 2 which worked fine.
After that when I type the commands from number 3 and 4 nothing happens when I hit enter. Any help would be appreciated.
Is it possible my Mac doesn't see the Nexus. Is the Nexus supposed On or Off by the way, I had it On.
Click to expand...
Click to collapse
Code:
./adb devices [enter]
Will tell you if its connected (per #3).
If #2 works properly and it navigates to your platform-tools folder, then you should be able to type ./adb [enter] and have all of th ADB commands come up. If not, you haven't properly updated/installed the SDK, or you haven't navigated to the folder properly.
martonikaj said:
Code:
./adb devices [enter]
Will tell you if its connected (per #3).
If #2 works properly and it navigates to your platform-tools folder, then you should be able to type ./adb [enter] and have all of th ADB commands come up. If not, you haven't properly updated/installed the SDK, or you haven't navigated to the folder properly.
Click to expand...
Click to collapse
Thanks for the fast reply. I've no idea what to do. I did install it, I'm not sure what - navigate properly means. I just did what it says.
Neither ./adb [enter] nor ./adb devices [enter] work, just nothing happens. Here is copy for the Terminal:
cd /Users/name/Desktop/android-sdk-macosx/platform-tools
./adb
./adb devices
If you have any ideas please let me know.
ivoniko said:
Thanks for the fast reply. I've no idea what to do. I did install it, I'm not sure what - navigate properly means. I just did what it says.
Neither ./adb [enter] nor ./adb devices [enter] work, just nothing happens. Here is copy for the Terminal:
cd /Users/name/Desktop/android-sdk-macosx/platform-tools
./adb
./adb devices
If you have any ideas please let me know.
Click to expand...
Click to collapse
when you type ./adb , does it run a long command line?
Hipe0ples555 said:
when you type ./adb , does it run a long command line?
Click to expand...
Click to collapse
No matter what I type nothing runs. Even when I try the update command from the SDK Readme.txt that came in the ZIP - "tools/android update sdk --no-ui" nothing happens.
Could there be something wrong with my Terminal.
ivoniko said:
No matter what I type nothing runs. Even when I try the update command from the SDK Readme.txt that came in the ZIP - "tools/android update sdk --no-ui" nothing happens.
Could there be something wrong with my Terminal.
Click to expand...
Click to collapse
Probably not, I would just try to delete the whole android_sdk folder and re-download it, even though it may take some time, it will be worth it if it works!
ivoniko said:
No matter what I type nothing runs. Even when I try the update command from the SDK Readme.txt that came in the ZIP - "tools/android update sdk --no-ui" nothing happens.
Could there be something wrong with my Terminal.
Click to expand...
Click to collapse
Probably not, just delete the whole Android_SDK folder and re-install everything! You know to go into the folder, go to tools and click android to updated all 6 things right?
Probably not, just delete the whole Android_SDK folder and re-install everything! You know to go into the folder, go to tools and click android to updated all 6 things right?
ivoniko said:
No matter what I type nothing runs. Even when I try the update command from the SDK Readme.txt that came in the ZIP - "tools/android update sdk --no-ui" nothing happens.
Could there be something wrong with my Terminal.
Click to expand...
Click to collapse
Did you see my other post, it is not showing up for some reason, is it working yet?
ivoniko said:
Thanks for the fast reply. I've no idea what to do. I did install it, I'm not sure what - navigate properly means. I just did what it says.
Neither ./adb [enter] nor ./adb devices [enter] work, just nothing happens. Here is copy for the Terminal:
cd /Users/name/Desktop/android-sdk-macosx/platform-tools
./adb
./adb devices
If you have any ideas please let me know.
Click to expand...
Click to collapse
One thing that I noticed, I had my Nexus plugged in through a USB hub, and I was seeing the same behavior you described. I then plugged it in directly into my laptop and I was able to see it. May or may not apply to your situation.
Alright so an update to my previous comment.
I was able to follow this guide and create a backup, unlock the boot loader and root the phone successfully. I am now in the process of restoring my backup, however when I type in:
./adb devices
in the terminal, nothing is listed. Therefore, I am unable to restore my back up. Any ideas on what may be going on?
EDIT: Figured it out, I forgot to re-enable USB debugging after my phone was wiped
Hipe0ples555 said:
Probably not, just delete the whole Android_SDK folder and re-install everything! You know to go into the folder, go to tools and click android to updated all 6 things right?
Click to expand...
Click to collapse
Yes, I went to tools, clicked on android, updated 6 things and after that when I entered the commands nothing happened.
In any case I will listen to your advice and download everything again.
Entering commands in terminal doesn't work. Even before having to conect the phone just entering the update commands in terminal doesn't do anything. I have no clue.
Here it is how it looks -
Last login: Tue Jan 31 00:53:34 on ttys000
/Users/name/Desktop/android-sdk-macosx/tools/android ; exit;
Name-MacBook-Pro:~ name$ /Users/name/Desktop/android-sdk-macosx/tools/android ; exit;
tools/android update sdk --no-ui
./android update sdk --no-ui
ivoniko said:
Thanks for the fast reply. I've no idea what to do. I did install it, I'm not sure what - navigate properly means. I just did what it says.
Neither ./adb [enter] nor ./adb devices [enter] work, just nothing happens. Here is copy for the Terminal:
cd /Users/name/Desktop/android-sdk-macosx/platform-tools
./adb
./adb devices
If you have any ideas please let me know.
Click to expand...
Click to collapse
Ok, so it is not literally; cd /Users/name/Desktop/android-sdk-macosx/platform-tools if thats not where it is; in terminal just type "cd " then just drag the platform-tool folder into the terminal and you should get something that LOOKS like cd /Users/name/Desktop/android-sdk-macosx/platform-tools but if thats not where it is, it will have a different path. Does that help?
ivoniko said:
Entering commands in terminal doesn't work. Even before having to conect the phone just entering the update commands in terminal doesn't do anything. I have no clue.
Here it is how it looks -
Last login: Tue Jan 31 00:53:34 on ttys000
/Users/name/Desktop/android-sdk-macosx/tools/android ; exit;
Name-MacBook-Pro:~ name$ /Users/name/Desktop/android-sdk-macosx/tools/android ; exit;
tools/android update sdk --no-ui
./android update sdk --no-ui
Click to expand...
Click to collapse
You forgot to type cd*space*, "cd " before draging the folder into the terminal.
Just updated everything! Does the change help?

[Tut] Preparing Your One X for Custom Roms (For Dummies) [Mac OS X]

Big thanks to bagofcrap24 for his great original guide here.
This one is for OS X users with an administrator account, I did it in OS X (Lion) because I haven't got the Android SDK installed on Windows at the moment and didn't want the hassle of downloading it just for the USB drivers.
If you get the [Waiting For Device] message in Windows Command Prompt and have access to a Mac instead, you might also want to try this guide.
If you get 'Permission Denied' in Terminal try this.
If I made any errors let me know and I'll correct it.
UPDATE: If you see any errors on HTC-dev such as "We are sorry, but this section of site is temporarily closed." just be patient, wait a little while and try again.
Unlocking Your Bootloader
Before we can even think about doing anything the first port of call is unlocking your bootloader.
As of the time of writing this there is currently no S-OFF method available so this is the only method of flashing a new recovery or boot image.
I'm going to keep this as simple as possible.
1. Go Here "http://www.htcdev.com/" and create yourself an account on HTCDEV.
2. Download this fastboot file for Mac.
3. Make a new folder on your desktop called 'fastboot'.
4. Extract the file 'fastboot-mac' from the .zip downloaded in step 2 to this folder.
5. Go here http://www.htcdev.com/bootloader/ and select "All Other Supported Models" and "then begin unlock bootloader".
6. Yes, tick both boxes, proceed.
7. Skip up to step 8 as we have all we need for the first 7 steps.
8. Power off your phone by holding the power button down for 10 seconds.
9. Power your phone on by holding power and volume down.
10. Highlight Fastboot with volume +/- then press power.
11. Plug your phone into your Mac and open a Terminal window.
12. Type this into your Terminal window:
sudo -s (then type your password and press enter)
cd /volumes/"your OSX drive name"/Users/your-username/Desktop/fastboot
./fastboot-mac oem get_identifier_token
Click to expand...
Click to collapse
13. Select & copy the text as per step 9 on the HTCDev website.
Terminal will add some characters to the left of the token, compare yours with the HTC example token, copy your token into the Textedit application and remove the text along the left to make them match, then copy the token again.
14. Paste your identifier token into the box at the bottom and submit.
You will receive an e-mail shortly from HTCDev with a link to the second part of the instructions and your "Unlock_code.bin" attached.
15. Download the "Unlock_code.bin" from the e-mail and save it to the same folder that we extracted fastboot files to in step 2.
16. Type this into your Terminal window:
./fastboot-mac flash unlocktoken Unlock_code.bin
Click to expand...
Click to collapse
17. The Display Will change on your phone, press Vol + to accept and power to confirm.
Congratulations, you have successfully unlocked your bootloader.
Now to the good stuff..
Installing A Recovery
This one is very simple to do once you have your bootloader unlocked.
A thing to note; at present there is no USB-Mass Storage in recovery so if you are planning to install a custom rom i would get it put on the internal memory of your phone now rather than messing things up later and been unable to install it.
(if you have follwed my unlocking guide skip to step 4)
1. Download this fastboot file for Mac.
2. Make a new folder on your desktop called 'fastboot'.
3. Extract the file 'fastboot-mac' from the .zip downloaded in step 2 to this folder.
4. At Present The Latest Recovery is an Interim made by Paul O'Brien from Modaco, you can grab it HERE
P.S. its the top one out of the two, the bottom is stock recovery.
Update: Latest official touch and non-touch recovery versions by Koush are available here.
5. Download the custom recovery and save it in the same folder as you did the fastboot files.
6. Power the phone off by holding the power button for 10 secs.
7. Select Fastboot with volume + or - then press power.
8. Plug your phone into your Mac and open a Terminal window.
10. If you still have the Terminal window open from installing your bootloader then skip to the next step, if not then type this into your Terminal window:
sudo -s (then type your password and press enter)
cd /volumes/"your OSX drive name"/Users/your-username/Desktop/fastboot
Click to expand...
Click to collapse
11. Type this into your Terminal window:
./fastboot-mac flash recovery name_of_recovery_image.img
in my case it was ./fastboot-mac flash recovery r1-modaco-recovery-clockwork-touch-endeavoru.img
Click to expand...
Click to collapse
Congratulations, you now have a custom recovery.
Flashing A ROM
1. Select reboot bootloader with volume +/- then power to select
2. Select HBOOT with volume +/- then power to select
3. Select recovery with volume +/- then power to select
You are now on your custom recovery.
4. First things first - do a Nandroid Backup of your current ROM in case anything bad happens.
5. Make sure you already have your shiny new ROM .zip on your internal memory as you cannot enable mass storage in the current recovery builds.
6. Wipe then flash your new custom ROM.
(You can flash the Super Wipe .zip from here to easily wipe your system partition and prepare it for the fresh ROM, thanks mike1986.)
OR you can download the latest SuperSU binaries from HERE and install them Via Recovery to just root the stock ROM.
Hope this helps some of you.
You can use Homebrew to install the Android tools if you want. It will also update them for you if you ask it to, via a simple command. Pretty convenient.
http://mxcl.github.com/homebrew/
thanks looking to try it but the dev web in htc it's down
Thanks for the guide....was helpful
./fastboot-mac oem get_identifier_token
'sudo ./fastboot-mac flash recovery name_of_recovery_image.img'
i use this two commands and say sudo: ./fastboot-mac: command not found
Terminal needs to be navigated to the same folder as the fastboot-mac file you extracted earlier, you can do this automatically in Lion (not sure about older versions) by right-clicking the folder and going to 'Services' then selecting 'New Terminal at Folder'.
You can navigate manually either by using the 'cd' command, for example:
cd /volumes/"OS X"/fastboot
Note the importance of quotes for a drive name with spaces.
You can also activate root before you do anything by typing sudo -s
i don't find that option new terminal at folder not showing it mmm
Sent from my HTC One X using xda premium
x.Orville.x said:
i don't find that option new terminal at folder not showing it mmm
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Just use the cd command then instead:
cd /volumes/"your OSX drive name"/fastboot
Sent from my HTC One X using xda premium
i have lion and i click it the folder and i don't see this
Services > New Terminal at Folder)
---------- Post added at 06:52 PM ---------- Previous post was at 06:29 PM ----------
i have the folder on the desktop and no here the error
No such file or directory
---------- Post added at 06:57 PM ---------- Previous post was at 06:52 PM ----------
that's my name of the hd
cd/volumes/"Orville HD"/fastboot
---------- Post added at 07:02 PM ---------- Previous post was at 06:57 PM ----------
any one can help me i put the folder on desktop or in the hd and the commands not work
Hmm it might not be there by default.
If the fastboot folder is on your desktop use this:
cd /volumes/"Orville HD"/users/your-user-name/Desktop/fastboot
i got the key but when i paste the other key on terminal have a error
When you get your key from Terminal you need to compare it with the example key HTC have on their site, theres some stuff you need to remove on the left to make them look the same.
Copy it into the Textedit app to remove them then select the whole key and paste it into the HTC site.
got it have unlocked and clockword thanks
No problem, have fun
Thank you so much for a clear guide.
Might be worth mentioning that the official CW recovery is available in basic and touch formats from here: http://forum.xda-developers.com/showpost.php?p=24738635&postcount=1
Great and concise guide, by the way. Hope this helps someone.
hmm i get permission denied even after sudo.. any ideas?
visor said:
Might be worth mentioning that the official CW recovery is available in basic and touch formats from here: http://forum.xda-developers.com/showpost.php?p=24738635&postcount=1
Great and concise guide, by the way. Hope this helps someone.
Click to expand...
Click to collapse
please note that there is an error in the coding of device.id on the official CW recovery and any rom that uses the aroma installer will not work at present, that is the reason i have left my guide with the links to the interim
x.Orville.x said:
i have lion and i click it the folder and i don't see this
Services > New Terminal at Folder
Click to expand...
Click to collapse
Just for the records...to get the "services" option after you right click, go to system preferences and then select keyboard and then choose "services" on left there is a option on the right panel where you can check for the "new terminal at folder" (do not remember exactly where)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
EDIT: Screenshot added
MrGarak said:
Terminal needs to be navigated to the same folder as the fastboot-mac file you extracted earlier, you can do this automatically in Lion (not sure about older versions) by right-clicking the folder and going to 'Services' then selecting 'New Terminal at Folder'.
You can navigate manually either by using the 'cd' command, for example:
cd /volumes/"OS X"/fastboot
Note the importance of quotes for a drive name with spaces.
You can also activate root before you do anything by typing sudo -s
Click to expand...
Click to collapse
I keep getting denied permission, even with the password, and "operation not supported." Is this guide for use in Snow Leopard or Lion?

Simple guide to ADB/Fastboot

I've noticed an increase of users "bricking" their handsets. I use the term "bricking" in the slightest sense, as to them, it is bricked.
The main cause is simply a lack of background knowledge & experience with ADB & Fastboot, I've also noticed that the very helpful guides to recover handsets from this "bricked" state, have an assumption that the users know basic things such as using ADB/Fastboot & cmd. The very things that caused the "brick" in the first place.
Here I'm going to throw together a crash course in the very basics of ADB/Fastboot and how to implement them into your system so that they work all the time and from anywhere on your system. Then an example on how to flash a ROM.
Ensure that USB debugging is enabled on your handset. On HTC Sense it can be found under Settings > Developer Options > Check USB Debugging.
Step One - Download ADB & Fastboot - HERE
Step Two - Extract this to a folder on your C:\ - e.g. "C:\ADB"
Step Three - Add this location to your System PATH - This is important as it makes things a lot easier later
Control Panel > System > Advanced System Settings > Environment Variables...
At the bottom "System Variables" scroll down and find "Path", Click it then "Edit..."
Add to the end of the line named "Variable Value:" ";C:\ADB\" - Try not to delete anything previously in there, the ; is needed, just omit the quotes "".
Hit Ok on the menus and go back to your desktop.
Step Four - Reboot your system or just log out and back in.
Here is a image guide to follow.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
-
-
Adding ADB & Fastboot to your System PATH allows you to run the commands adb & fastboot from anywhere in your system. Normally the guide you'd follow would say,
cd into fastboot folder
Click to expand...
Click to collapse
Now you don't need to.
Example usage.
You download a new ROM (CM10) plus GApps & the boot.img from the relevant thread. You copy the ROM & GApps from your computers download folder to your handset. Unmount USB storage and you do the following, making sure that your handset is still plugged in.
Open your computers default download folder.
Shift + Right Click > Open command window here
Type the following
adb devices > Serial Number should be printed
adb reboot bootloader > Device reboots into HBOOT, Fastboot is automatically selected.
fastboot devices > Serial Number should be printed again
fastboot flash boot boot.img > boot.img is sent and flashed, easy. Sometimes the boot.img maybe named different, just start typing and hit TAB, should autocomplete.
fastboot erase cache > not always needed, better being safe
Press the power button on your handset to enter HBOOT, then navigate to RECOVERY and press power.
In Recovery, make your backups as per, and wipe & flash the ROM + GApps, then reboot normally.
Profit
If you still do not understand what you are doing, don't do it. You would not attempt to change a head gasket in your cars engine, unless you knew and understood what you were doing. If you are unsure, search, read & ask until you know what your doing. Sometimes what I write looks too clinical so here's a :cyclops: smiley to lighten the post.
Andy said:
I've noticed an increase of users "bricking" their handsets. I use the term "bricking" in the slightest sense, as to them, it is bricked.
The main cause is simply a lack of background knowledge & experience with ADB & Fastboot, I've also noticed that the very helpful guides to recover handsets from this "bricked" state, have an assumption that the users know basic things such as using ADB/Fastboot & cmd. The very things that caused the "brick" in the first place.
Here I'm going to throw together a crash course in the very basics of ADB/Fastboot and how to implement them into your system so that they work all the time and from anywhere on your system. Then an example on how to flash a ROM.
Ensure that USB debugging is enabled on your handset. On HTC Sense it can be found under Settings > Developer Options > Check USB Debugging.
Step One - Download ADB & Fastboot - HERE
Step Two - Extract this to a folder on your C:\ - e.g. "C:\ADB"
Step Three - Add this location to your System PATH - This is important as it makes things a lot easier later
Control Panel > System > Advanced System Settings > Environment Variables...
At the bottom "System Variables" scroll down and find "Path", Click it then "Edit..."
Add to the end of the line named "Variable Value:" ";C:\ADB\" - Try not to delete anything previously in there, the ; is needed, just omit the quotes "".
Hit Ok on the menus and go back to your desktop.
Step Four - Reboot your system or just log out and back in.
Here is a image guide to follow.
-
-
Adding ADB & Fastboot to your System PATH allows you to run the commands adb & fastboot from anywhere in your system. Normally the guide you'd follow would say,
Now you don't need to.
Example usage.
You download a new ROM (CM10) plus GApps & the boot.img from the relevant thread. You copy the ROM & GApps from your computers download folder to your handset. Unmount USB storage and you do the following, making sure that your handset is still plugged in.
Open your computers default download folder.
Shift + Right Click > Open command window here
Type the following
adb devices > Serial Number should be printed
adb reboot bootloader > Device reboots into HBOOT, Fastboot is automatically selected.
fastboot devices > Serial Number should be printed again
fastboot flash boot boot.img > boot.img is sent and flashed, easy. Sometimes the boot.img maybe named different, just start typing and hit TAB, should autocomplete.
fastboot erase cache > not always needed, better being safe
Press the power button on your handset to enter HBOOT, then navigate to RECOVERY and press power.
In Recovery, make your backups as per, and wipe & flash the ROM + GApps, then reboot normally.
Profit
Click to expand...
Click to collapse
This is what i was looking for. I am just about to flash a ROM in a HTC vivid S-ON and i need it to flash the kernel manually.
Thank you. :cyclops:
Can you boot into recovery with a fast boot command?
Sent from my HTC One X using xda app-developers app
Tw1tchy said:
Can you boot into recovery with a fast boot command?
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Fastboot works in the bootloader
ADB works in the running OS and the recovery
So fastboot reboot recovery will work in the bootloader, adb reboot recovery works in the running OS and inside the recovery (if you want to reboot it for some reason when you are already in)
Unfortunately there is no fastboot command (AFAIK) to reboot into recovery from fastboot directly. Your only fastboot reboot options are
fastboot <command>
Code:
reboot
reboot-bootloader
Andy said:
Unfortunately there is no fastboot command (AFAIK) to reboot into recovery from fastboot directly. Your only fastboot reboot options are
fastboot <command>
Code:
reboot
reboot-bootloader
Click to expand...
Click to collapse
Ah my mistake , sorry mate. So it only apply to adb .
Thanks
Mr Hofs said:
Ah my mistake , sorry mate. So it only apply to adb .
Thanks
Click to expand...
Click to collapse
if you are in ADB
"
adb reboot bootleader
adb reboot recovery.
"
but if you are in fastboot you need to navigate to recovery option using the vol up and vol down keys and power on recovery.
:facepalm:
and i was wondering why fastboot write: waiting for device, of course if i use fastboot instead adb to try to reboot my phone in OS
i had forgotten...
Hi Im desperatte trying to root my ATT HTC ONE X with 1.5 using this method http://forum.xda-developers.com/showthread.php?t=1709296
I found this tutorial and I dont know if could work.
I have one big question: After i extracted the file in step one I get a folder named fastboot, instead en adb folder U mentioned in step 2
Im feeling stupid asking so basic things but I prefer to ask and not cry later
Thanks
ErnestoD said:
Hi Im desperatte trying to root my ATT HTC ONE X with 1.5 using this method http://forum.xda-developers.com/showthread.php?t=1709296
I found this tutorial and I dont know if could work.
I have one big question: After i extracted the file in step one I get a folder named fastboot, instead en adb folder U mentioned in step 2
Im feeling stupid asking so basic things but I prefer to ask and not cry later
Thanks
Click to expand...
Click to collapse
No worries, mate. Fastboot folder contains both fastboot and adb commands, so all you have to do is open command prompt in it (something like C:/fastboot/) and then type commands.
Beforehand, you must have htc drivers installed, and the phone connected, of course.
Also, beware that this forum is for International One X with Tegra 3, so be careful with instructions found here.
Thanks man.
I undestood what u said.
My problem is with the fisrt command I should write in the root proccess: adb shell rm /data/data/com.redbend.vdmc/lib/libvd*
I copied SU as stated, then typed adb shell and then rm /data/data/com.redbend.vdmc/lib/libvd* . here I get notification about missin file or folder.
The thread Im in is: http://forum.xda-developers.com/showthread.php?t=1709296
Do U understant what should I do or. If Im missing something
Thanks
[email protected]|-|oR said:
No worries, mate. Fastboot folder contains both fastboot and adb commands, so all you have to do is open command prompt in it (something like C:/fastboot/) and then type commands.
Beforehand, you must have htc drivers installed, and the phone connected, of course.
Also, beware that this forum is for International One X with Tegra 3, so be careful with instructions found here.
Click to expand...
Click to collapse
Where did you extract your fasboot/adb commands? Is SU in the same folder? Where do you open your command prompt?
Again, I'm no expert in AT&T One X, but fastboot/adb should be the same.
I suggest you open Windows Explorer, go to your fastboot/adb folder, press SHIFT, and right click your mouse.
Select "Open command window here".
Then type "adb devices" (make sure your phone is connected with USB cable, and USB debugging is turned on).
If adb sees your phone that's good.
Type dir and see if SU inside the folder.
Then follow the steps you should.
I hope this helps.
yes It has worked . Thanks man.
So now I know Im at least oriented. Lets see If I receive more help in the root thread Im talking about.
Thanks one more time
[email protected]|-|oR;40510609]Where did you extract your fasboot/adb commands? Is SU in the same folder? Where do you open your command prompt?
Again, I'm no expert in AT&T One X, but fastboot/adb should be the same.
I suggest you open Windows Explorer, go to your fastboot/adb folder, press SHIFT, and right click your mouse.
Select "Open command window here".
Then type "adb devices" (make sure your phone is connected with USB cable, and USB debugging is turned on).
If adb sees your phone that's good.
Type dir and see if SU inside the folder.
Then follow the steps you should.
I hope this helps.[/QUOTE]
It's alright, mate. That's the whole spirit of XDA.
Take care of you and of your One X, mate! :good:
Thanks
Woot Saved me
Thanks

[Q] Can't figure out how to flash CWM via Mac OS X

Hello everyone, I have an OUYA and I really want to get CyanogenMod on it. The first step is obviously CWM. I have tried flashing via this method http://forum.xda-developers.com/showthread.php?t=2295645 on my Windows 7 PC, I get the error message "no device found" every time, tried numerous drivers, nothing worked. So I decided to try it out on my Mac. Well its still not working. I run the .sh file and nothing happens.
My question is, how do I do this?
Im kinda new to terminal on Mac OS X, and I've barely used it in Linux, so I think I need some help here :/ I hope someone has advice.
Thanks
Orange_furball said:
Hello everyone, I have an OUYA and I really want to get CyanogenMod on it. The first step is obviously CWM. I have tried flashing via this method http://forum.xda-developers.com/showthread.php?t=2295645 on my Windows 7 PC, I get the error message "no device found" every time, tried numerous drivers, nothing worked. So I decided to try it out on my Mac. Well its still not working. I run the .sh file and nothing happens.
My question is, how do I do this?
Im kinda new to terminal on Mac OS X, and I've barely used it in Linux, so I think I need some help here :/ I hope someone has advice.
Thanks
Click to expand...
Click to collapse
hmm,
On my MBP the script worked,
Did you navigated to the folder with the terminal ? (i'm also not a terminal hero ) and run the script ?. with Osx the "dir" fuction is "ls" so you can see the folders. Navigate to the specific MacOSX folder and with the Ouya and your MAc connected, type ./adb devices (with the ./). It should give you a line with "List of devices attached " and the line below that a long number that stands for your ouya.
Sometimes i had to do this twice or three times for the ouya to show up. If the ouya showes up. Then run type ./InstallOuyaCWMRecovery.sh (with the ./). It should work that way.
Greetz,
Michel
Re-Mi said:
hmm,
On my MBP the script worked,
Did you navigated to the folder with the terminal ? (i'm also not a terminal hero ) and run the script ?. with Osx the "dir" fuction is "ls" so you can see the folders. Navigate to the specific MacOSX folder and with the Ouya and your MAc connected, type ./adb devices (with the ./). It should give you a line with "List of devices attached " and the line below that a long number that stands for your ouya.
Sometimes i had to do this twice or three times for the ouya to show up. If the ouya showes up. Then run type ./InstallOuyaCWMRecovery.sh (with the ./). It should work that way.
Greetz,
Michel
Click to expand...
Click to collapse
I think I'm royally failing. I can't even access my downloads directory and ./adb devices renders no results
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Ps: I'm not Paul.. The guy I bought this Mac off of left his info and I never took the time to take t off..
Orange_furball said:
I think I'm royally failing. I can't even access my downloads directory and ./adb devices renders no results
Click to expand...
Click to collapse
ok when first entering the terminal type
Code:
cd \
(then enter, you will see a > enter again)
then type
Code:
ls
( its an L )
you can scroll up but i'm pretty sure there is a folder "Downloads" to get into this folder you have to type (just like windows)
Code:
cd Downloads
As i'm not a terminal hero also i type everything Cap sensitive (this way i know it works)
do the "ls" and "cd" commands until you reach the downloaded folder and you are into the MacOSX folder, then do the
Code:
./adb devices
and if you mac sees the ouya then run the bash file
Re-Mi said:
ok when first entering the terminal type
Code:
cd \
(then enter, you will see a > enter again)
then type
Code:
ls
( its an L )
you can scroll up but i'm pretty sure there is a folder "Downloads" to get into this folder you have to type (just like windows)
Code:
cd Downloads
As i'm not a terminal hero also i type everything Cap sensitive (this way i know it works)
do the "ls" and "cd" commands until you reach the downloaded folder and you are into the MacOSX folder, then do the
Code:
./adb devices
and if you mac sees the ouya then run the bash file
Click to expand...
Click to collapse
I feel like I'm so close! Thank you! But my Mac doesn't see the OUYA in devices attached :/
Orange_furball said:
I feel like I'm so close! Thank you! But my Mac doesn't see the OUYA in devices attached :/
Click to expand...
Click to collapse
I pm-ed you.
Re-Mi has helped me solved my issue! Thank you so much!
Here is more detail on what I did, First of all I followed Re-Mi's instructions. Here they are:
So first things first Root
http://forum.xda-developers.com/show....php?t=2387507
Sideload the app and run the apk
second install the xposed installer (latest apk file at the end of the first post) make sure it's installed (Launch the Xposed Installer and click on "Install/Update" ,Reboot ,Done!)
http://forum.xda-developers.com/show....php?t=1574401
Then install mod collection for Ouya and install CWM from there
http://forum.xda-developers.com/show....php?t=2359390
It's a long detour but i think it will work. After that just install stockplus rom and you got everything you wanted (otherwise you would not even bother to install cwm )
Click to expand...
Click to collapse
Now let me go into more detail. What you do is type the first link into your OUYA's web browser (It is under Make>Software>Web Browser I believe) Then download the file. Now go to Manage>Settings>Advanced>Storage>Downloads and hit the file you just downloaded. Install that APK, hit open, then hit root. Now accept the SU request. After this is done repeat the steps until you have the other file downloaded. Now install that APK for the Xposed Installer and hit "Install/Update" then reboot. Now download the mod collection from the third link.
Install it and install CWM from there. It will take you to a download link, wait a few seconds, then hit install CWM again. Now it'll be installed.
Plug your Ouya into your computer, If its a Mac you will need the program from www.android.com/filetransfer . If its Windows you wont need that. Go in XDA and download whatever ROM tickles your fancy. Drag and drop that into your Ouya's storage. Now on the Ouya reboot to recovery (Via the Mods app)
Now im CWM hit the install zip from SD card, select the .zip of the ROM you chose, and install. Now wait until its all done, reboot, and enjoy!
*IF YOUR OUYA GETS BRICKED, NEITHER I NOR RE-MI NOR ANYONE EXCEPT YOURSELF ARE RESPONSIBLE!*
Good luck! If this helps be sure to thank Re-Mi!!!

Categories

Resources