Develop Bugs

[Q] Adfree on Droid Incredible

Philosophical issues aside, how does one get this working? A crucial barcode program i use has amazingly annoying religious ads.
Here is what I have tried:
Rooted with Unrevoked / Nandroid Backup / Titanium Backup / wifiTether /Led flashlight. Stock otherwise.
Install adfree, ran it, phone rebooted.
Boot into clockwork recovery and launch adb shell.
Execute the following:
Code:
2. Install and run
3. allow it to download and install new hosts file, it will copy it to your sdcard and try to replace /system/etc/hosts but fail (it should reboot the phone shortly)
4. Power off the phone and hold Volume Down and power.
5. Use volume down to select recovery
6. In clockwork recovery volume down to "partitions menu" and hit the track pad to select
7. Select "mount /system" and "mount /sdcard" "mount /data"
8. Plug in your usb cord and open a command line on your pc
9. enter adb shell and type the following commands
cp /sdcard/hosts /data/data/hosts
rm /system/etc/hosts
ln -s /data/data/hosts /system/etc/hosts
On reboot, no change, and adfree fails trying to update. Help?

heliotropeUCSD said:
Code:
cp /sdcard/hosts /data/data/hosts
rm /system/etc/hosts
ln -s /data/data/hosts /system/etc/hosts
Click to expand...
Click to collapse
I found a post earlier that changes the paths. It has worked for me on every Rom I have tried.
Code:
cp /sdcard/hosts /data/hosts
rm /system/etc/hosts
ln -s /data/hosts /system/etc/hosts
Sent from my ADR6300

Hmmm, still didn't work. Can you go into a little bit more detail? I'm stock everything, just rooted.

The philosophical struggle goes deeper than what you think! Another method (frowned upon by most uninformed members of this forum but endorsed by some of the experts) is to do a tempoary nand unlock using the unrevoked tool.
Run the tool like normal, then unplug after the "running pre-boot sequence" and during "waiting for reboot". I've done it plenty of times perfectly, it allows you to run adfree normally without any special tricks (just default settings). I have no idea what happens if you unplugged at the wrong time (you have a like 20-second window ffs) but I hear it's bad.
Do it at your own risk

I'd just like to point out that I think the above suggestion is actually INTENDED to brick phones. I wouldn't recommend anyone try it. Does anyone have any real suggestions? I have a serious problem with religious ads on my f***ing telephone.

heliotropeUCSD said:
I'd just like to point out that I think the above suggestion is actually INTENDED to brick phones. I wouldn't recommend anyone try it. Does anyone have any real suggestions? I have a serious problem with religious ads on my f***ing telephone.
Click to expand...
Click to collapse
Listen bro, this method works just fine.
Run unrevoked 3.1 when you are in the OS, then it will reboot your phone to hboot and then it unlocks your nand, it will reboot and you will see the white incredible screen, at this time you can unplug your USB cable, I just suggest doing it before it gets back to the OS so you don't pull it when it is flashing your recovery, but if you do it at the white incredible screen or during the bootanimation. Then when you get back to the OS, run adfree and update your hosts, success, profit?
I can confirm that it will work 100% without bricking your phone. Anyone who said it has is full of ****. Don't listen to those **** smoking noobs out there that are hanging on to unrevoked teams ballsacks. This will not brick your phone if you do as I said above. If this bricked your phone then it would not be safe to use the unrevoked program period. So don't listen to the noobs out there, this method works 100% without issue. I posted this method awhile back and everyone got upset like I did something wrong, but people did verify it did work if you want to find the post I made look for it.

Hmm, well. I have no idea, it sounds like you may be right, but it isn't the type of solution that i am looking for.
I'd like to find a way to use the symbolic link method to store the hosts file somewhere where adfree can write to it. Does anyone else have an idea?

heliotropeUCSD said:
Hmm, well. I have no idea, it sounds like you may be right, but it isn't the type of solution that i am looking for.
I'd like to find a way to use the symbolic link method to store the hosts file somewhere where adfree can write to it. Does anyone else have an idea?
Click to expand...
Click to collapse
sym link doesnt work for me, um, I would just do what I stated above if all else you tried has failed.

I used the above method in the #1st Post on an 2.2 ROM with no issue! I can update Adfree at any point after completing those directions...
here is where I found those directions... http://www.jonamerica.com/technology/howto-root-the-htc-droid-incredible/

Hmm. I am really, genuinely scared of the method posted by TNS201. I believe him that it may work, but I simply don't understand the mechanism. Is he suggesting that this successfully unlocks the NAND memory? Or does it allow it to be unlocked for one boot cycle, in which case I can't update adfree?

heliotropeUCSD said:
Hmm. I am really, genuinely scared of the method posted by TNS201. I believe him that it may work, but I simply don't understand the mechanism. Is he suggesting that this successfully unlocks the NAND memory? Or does it allow it to be unlocked for one boot cycle, in which case I can't update adfree?
Click to expand...
Click to collapse
Why do say that it "may" work. I can confirm it works 100%, I wouldn't tell you something that doesn't. It unlocks the NAND for one boot. So you can write to system and such during this time. The duration of this lasts until you power off or reboot your phone. This stays active until next reboot. You can update adfree and reboot if you want.

TNS201 said:
Listen bro, this method works just fine.
Run unrevoked 3.1 when you are in the OS, then it will reboot your phone to hboot and then it unlocks your nand, it will reboot and you will see the white incredible screen, at this time you can unplug your USB cable, I just suggest doing it before it gets back to the OS so you don't pull it when it is flashing your recovery, but if you do it at the white incredible screen or during the bootanimation. Then when you get back to the OS, run adfree and update your hosts, success, profit?
I can confirm that it will work 100% without bricking your phone. Anyone who said it has is full of ****. Don't listen to those **** smoking noobs out there that are hanging on to unrevoked teams ballsacks. This will not brick your phone if you do as I said above. If this bricked your phone then it would not be safe to use the unrevoked program period. So don't listen to the noobs out there, this method works 100% without issue. I posted this method awhile back and everyone got upset like I did something wrong, but people did verify it did work if you want to find the post I made look for it.
Click to expand...
Click to collapse
...eloquently said, sir...
Anyway OP, if you don't wanna do it, that's fine. And I think it's wonderful that you don't care whether anyone questions your sexual orientation
(FUTURAMA REFERENCE, DON'T FLAME ME.)
Seriously, why are the uninformed so cocksure?

Yeah, but somebody must have gotten the symlink method to work. I'm not willing to risk bricking my phone in any way to do this- like I said, there are philosophical issues here. I'd rather just see the ads.
So, again- has anyone with an Incredible, rooted, stock rom, used the symlink method to install adfree?

heliotropeUCSD said:
Hmm. I am really, genuinely scared of the method posted by TNS201. I believe him that it may work, but I simply don't understand the mechanism. Is he suggesting that this successfully unlocks the NAND memory? Or does it allow it to be unlocked for one boot cycle, in which case I can't update adfree?
Click to expand...
Click to collapse
As stated in my earlier post, I have it working on my Incredible and it has worked for me on 4 different ROMS.
This may not work for you, but it does work for me. I found these tips awhile ago and don't remember where I found them.
NOTE: Notice the paths in the commands below - They differ from the original post.
Boot into clockwork recovery and launch adb shell.
Execute the following:
Code:
2. Install and run
3. allow it to download and install new hosts file, it will copy it to your sdcard and try to replace /system/etc/hosts but fail (it should reboot the phone shortly)
4. Power off the phone and hold Volume Down and power.
5. Use volume down to select recovery
6. In clockwork recovery volume down to "partitions menu" and hit the track pad to select
7. Select "mount /system" and "mount /sdcard" "mount /data"
8. Plug in your usb cord and open a command line on your pc
9. enter adb shell and type the following commands
cp /sdcard/hosts /data/hosts
rm /system/etc/hosts
ln -s /data/hosts /system/etc/hosts
Note the last command, that it a lowercase L not an I
a couple of others have made that mistake (for best results copy each command to your clipboard and paste it into your command prompt).
Reboot the phone and it should work now.
Use BTC IP and do not check symlink from /data/data/hosts
{
"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"
}
gadget!

heliotropeUCSD said:
Yeah, but somebody must have gotten the symlink method to work. I'm not willing to risk bricking my phone in any way to do this- like I said, there are philosophical issues here. I'd rather just see the ads.
So, again- has anyone with an Incredible, rooted, stock rom, used the symlink method to install adfree?
Click to expand...
Click to collapse
Are you getting any errors in the shell when you type the commands?
should look like this when you enter a command
Code:
# ln -s /data/data/hosts /system/etc/hosts <--hit enter
ln -s /data/data/hosts /system/etc/hosts
#
First, can you go into recovery, and let me know if this command returns hosts
Code:
ls /data/data | grep hosts
This lists the directory and "filters" out everything but the text after grep.
output should look like:
Code:
# ls /data/data | grep hosts
ls /data/data | grep hosts
hosts
#
I need to know, because I think that adfree might not have made a hosts file on your sdcard when you ran before starting, thus there was no hosts file to "cp" form /sdcard to /data/data/.
If that is the case, and since you have rm'ed your hosts file from /system/etc/, you will have to recreate the file with the touch command.
My $.02
***********************************
It is NOT necessary to run or even install adfree before getting your hosts files setup in the system.
Here is the method I use:
1. copy the existing hosts file to /data/data
Code:
cp /system/etc/hosts /data/data/hosts
2. rename hosts to hosts.bak
Code:
mv /system/etc/hosts /system/etc/hosts.bak
3. symlink the hosts files
Code:
ln -s /data/data/hosts /system/etc/hosts
At that point, your system is setup to run adfree. On the first run of adfree, it will see the hosts file in /data/data and uses it.
I have use this method at least 10 times while trying out different roms:

Hell to the yes. gadget!'s method worked for me- I did not know NOT to use local IP and to NOT check the symlink button. Maybe someone can educate me on what those options mean?

Glad it worked out for you =). j/w, is the app that kept giving you religious ads "Android System Info"? For some reason the people behind that app have decided to lock the ad into messages about "Jesus" or "prayers"... I always thought that was kind of odd.

Adfree works without issue after running unrevoked forever. No symlink needed.
Sent from my ADR6300 using XDA App

bhazard451 said:
Adfree works without issue after running unrevoked forever. No symlink needed.
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
Thanks for the info, came here to ask this question. Do I need to check symlink in the adfree setup?

gadget! said:
As stated in my earlier post, I have it working on my Incredible and it has worked for me on 4 different ROMS.
This may not work for you, but it does work for me. I found these tips awhile ago and don't remember where I found them.
NOTE: Notice the paths in the commands below - They differ from the original post.
Boot into clockwork recovery and launch adb shell.
Execute the following:
Code:
2. Install and run
3. allow it to download and install new hosts file, it will copy it to your sdcard and try to replace /system/etc/hosts but fail (it should reboot the phone shortly)
4. Power off the phone and hold Volume Down and power.
5. Use volume down to select recovery
6. In clockwork recovery volume down to "partitions menu" and hit the track pad to select
7. Select "mount /system" and "mount /sdcard" "mount /data"
8. Plug in your usb cord and open a command line on your pc
9. enter adb shell and type the following commands
cp /sdcard/hosts /data/hosts
rm /system/etc/hosts
ln -s /data/hosts /system/etc/hosts
Note the last command, that it a lowercase L not an I
a couple of others have made that mistake (for best results copy each command to your clipboard and paste it into your command prompt).
Reboot the phone and it should work now.
Use BTC IP and do not check symlink from /data/data/hosts
gadget!
Click to expand...
Click to collapse
This worked perfectly for me. Thanks.

[GUIDE] *Rooting the Xoom for Dummies*

***Xoom Rooting Guide for N00bs***​
Hello Xoom Dev community! Sorry. I know you're thinking, "Man! Not another Xoom root guide?!". Lol. But I wanted to make this, so, here ya go...
***WARNING***
-This will erase everything on your xoom. Its like flashing flashing back to stock because of the unlocking process. So BACK everything up before continuing via USB, or your preferred backup app-
**Also, this Tutorial is for the 3G version ONLY. The Wifi model is different and uses an incompatible boot.img. Once again, ONLY FOR 3G MODEL**
Ok. So, rooting the Xoom isn’t really that “hard” of a task. I’m a n00b as well, so I did have a little difficulty doing it. Only because this method requires you to use adb, the command prompt, etc…
Well, I wanted to make a guide that should be ‘n00b-proof’. LOL. It’s really super simple.
**Bofore you get started, make sure the USB Debugging option is enabled in the Settings. Go to Settings --> Applications --> Development --> USB Debugging**
Alright, you’re going to need some tools to get it done. First of all, download the Xoom USB drivers. Either get them from motodevs.com --> http://developer.motorola.com, which requires a free membership; or get them from the Motorola/Support site --> http://www.motorola.com/Support/US-EN/Consumer-Support/TABLETS/MOTOROLA_XOOM, and download the ‘motohelper’ program. I prefer the drivers from the dev site because they’re just stand-alone drivers. Motohelper is an actual app that “keeps your drivers up-to-date”. Both will have the same version of drivers, i.e. 4.9.0.
Now that we have the drivers installed plug in your Xoom to make sure all drivers/services were detected/installed properly. If you’re good, next we will need the Android SDK, if not already installed. To properly install it though, you must download the Java JDK from --> http://www.oracle.com/technetwork/java/javase/downloads/index.html, and click the “Download JDK” button. Choose your OS, and install.
**NOTE** If you’re running Vista/7 x64, Android SDK will not detect the REQUIRED Java kit installation. Yes, JDK has been properly installed, but the Registry doesn’t read the installation right. So, to get around this issue, either go here --> http://codearetoy.wordpress.com/2010/12/23/jdk-not-found-on-installing-android-sdk/, for a tutorial that gets it detected by modifying the Registry. Or, do what I did, and just download the .zip installer of Android SDK. I’m writing this guide based on the ‘zip type’ of installation, but I’m sure the directories are identical besides having SDK installed in your Program Files folder.
Whew! Now, either extract the SDK to a directory of choice, or point your mouse to the Program Files\Android SDK\ directory. There will be some folders like platforms, platform-tools, tools, etc…
Anyways, to root the Xoom you will be running a command prompt from one of these folders. NOTE, in the newest release of Android SDK, they have moved the adb files to the ‘platform-tools’ folder, rather than all in the ‘tools’ folder. What I did, was copied everything from inside the ‘platform-tools’ folder, to the ‘tools’ folder. But do not replace any files! Just copy. It will put the required files, like adb.exe, inside one location. Sorry if I’m confusing anybody. LOL! Just copy the files from ‘platform-tools’ --> ‘tools’. Without replacing anything.
**NOTE** When I first installed SDK, I ran the emulator.exe from within the ‘tools’ directory. This updated everything, but I’m not sure if it matters for this tutorial?
Ok. The “hard” part is over. We should be all setup, and ready to type some commands! What you’ll need to do now is, open up a command prompt i.e. cmd. And do a cd --> to whatever path the ‘tools’ folder is in. For example, mine is in a Xoom folder from my documents. So the command would be “cd C:\Users\%name%\Documents\Xoom\android-sdk_r10-windows\android-sdk-windows\tools”. Without quotes of course.
You should now be pointed at the ‘tools’ folder from cmd, and next we can start the commands!
CHECKPOINT
- Xoom drivers installed, xoom is plugged in, & detected properly. To make sure, open Device Manager to see if the “ADB Interface” is there. **Sorry, I’m not sure ADB is in Device Manager before, or after rooting** Can’t remember! As long as you don’t have any ‘device is not properly installed’ pop-ups, you should be good!
{
"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"
}
- Android SDK is configured right, and cmd is pointed at the correct location.
-USB Debugging option is checked. Check above for instructions
***This is obviously, from Koush’s site, so give him some kudos please ***
***I will bold all commands, and try to put in ‘n00b’ terms***​
Type the following commands in CMD… after you have moved the “XOOM root” files.
1. Download the XOOM root zip.
2. Unzip the package, and
3. put the 3 files inside the same ‘tools’ folder we’re running cmd from!
4. adb reboot bootloader (skip the next 3 steps if you have already unlocked your Xoom via fastboot, which is another guide on XDA that just lets you unlock the Xoom. It’s not rooting.)
5. fastboot oem unlock
-You have to accept the terms by pressing the vol - down key, and then select 'accept' by pressing the vol + up key.
6. -wait for the Xoom to reboot completely.
**You may have to re-enable USB Debugging mode again for the next command**
7. adb reboot bootloader
8. fastboot flash boot rootboot.img
9. fastboot reboot
10. -wait for the Xoom to reboot completely.
11. adb remount
12. adb push su /system/bin/
13. adb shell --> You will now be mounted within adb shell…
14. ln –s /system/bin/su /system/xbin/su
15. chmod 4755 /system/bin/su
16. exit --> This gets you out of adb shell…
17. adb push Superuser.apk /system/app/
That is all! Now, unplug the Xoom and reboot it.
To verify your root is working properly, download an app such as, Cachemate, or any other that requires Superuser access. Open up Superuser to see if that apps’ rights were saved successfully.
Yay! Root access! But honestly, this tutorial will be outdated and inefficient, once the source code is out and then we’ll have a oneclickroot method. Which is way better! Until then, I hope anybody who is a little confused about the process benefits from this guide.
Happy moddin’!

good guide.

Thanks, I like this guide and made rooting my xoom super easy.
One other important initial step is to make sure USB debugging is enabled:
Settings>>Applications>>Development>>USB debugging

Hey, thank you guys for your kudos. I appreciate the feedback.
@jtseidner, Man you are a genius! That is a very important step that I left out! You couldn't root the Xoom without that option. I'll add it to the tutorial.
Thanks!

14. ln –s /system/bin/su /system/xbin/su
Its saying In: not found.. help

Hey. The command is all lower case so it would be "LN" not "IN". Just type it in all lower case. The rest of your command is ok. Simple syntax error, that's all. Let me know if it works and if you have any other concerns.
Sent from the most 'Epic' phone in the world! ...Using XDA Premium app

ok i got to step fastboot oem unlock #5 and the screen shows choices. i accidentally chose device unlock operation aborted, the down arrow. now it wont go off this text screen. how can i reboot this xoom?

disregard, i pressed the volume UP and power, tablet is rebooting now.

Hey worked great for me only problem is that it wiped my xoom...probably said that somewhere in the instructions and i just missed it. Anyway Thanks.

Yeah sorry. I should put that on the tutorial. But im pretty sure any method of rooting the xoom will wipe it. Only because you have to unlock the device. Until we receive clockwork, this is the only way. Im glad you were successful with my guide though!
Thanks.
Sent from the most 'Epic' phone in the world! ...Using XDA Premium app

Screen Stuck At Starting FastBoot Protocol Dont Know How Long This Screen Stays Up Or Have I Done Something Wrong I Downloded FastBoot Already And Put It In My Sdk Folder Can Someone Pleas Help Me

You shouldn't be stuck at fastboot. It probably means that your xoom wasn't fully rebooted into the bootloader. Fastboot is a program located in the tools folder and ran from your command prompt. So have your xoom loaded up and connect the usb. Make sure usb debugging is on. Open your cmd and point to that tools folder. Type the first command from step 4, adb reboot bootloader. This will restart your xoom and I believe you'll see the 'dual core technology' logo. Just wait a minute after step 4. Now try the remaining commands, but be sure to wait for reboots before typing the next commands. I have a note after each step that says wait for reboot. Please let me know if you have any further issues.
Sent from the most 'Epic' phone in the world! ...Using XDA Premium app

Anyways, to root the Xoom you will be running a command prompt from one of these folders. NOTE, in the newest release of Android SDK, they have moved the adb files to the ‘platform-tools’ folder, rather than all in the ‘tools’ folder. What I did, was copied everything from inside the ‘platform-tools’ folder, to the ‘tools’ folder. But do not replace any files! Just copy. It will put the required files, like adb.exe, inside one location. Sorry if I’m confusing anybody. LOL! Just copy the files from ‘platform-tools’ --> ‘tools’. Without replacing anything.
This is utterly confusing.. can you explain in-depth please. Don't copy, but leave it as is; copy but replace the file, or replace it completely. Only three options.
for example... it will show adb.exe and adb.exe(2) - is that what you wanted?

misdirection said:
Anyways, to root the Xoom you will be running a command prompt from one of these folders. NOTE, in the newest release of Android SDK, they have moved the adb files to the ‘platform-tools’ folder, rather than all in the ‘tools’ folder. What I did, was copied everything from inside the ‘platform-tools’ folder, to the ‘tools’ folder. But do not replace any files! Just copy. It will put the required files, like adb.exe, inside one location. Sorry if I’m confusing anybody. LOL! Just copy the files from ‘platform-tools’ --> ‘tools’. Without replacing anything.
This is utterly confusing.. can you explain in-depth please. Don't copy, but leave it as is; copy but replace the file, or replace it completely. Only three options.
for example... it will show adb.exe and adb.exe(2) - is that what you wanted?
Click to expand...
Click to collapse
Nevermind.. I was able to root my Xoom!!

Great! Sorry if it was misleading. Im not the best writer at times. All I meant was just to copy everything from the platform folder over to the tools folder without replacing, or writing duplicate files. Hope that makes sense?
Sent from the most 'Epic' phone in the world! ...Using XDA Premium app

Is this the stock .img or is it the tiamat one? I used other root guide but I'm interested in flashing this .img if it contains the stock kernel.
Sent from my Xoom using Tapatalk

This is the stock .img and this guide will work for the original stock firmware, along with the new 3.01. But this guide is ONLY for the 3g version of the Xoom. If you have any further questions please ask away.
EDIT: Sorry. I didn't fully understand your post. This guide doesn't include any kernels. It assumes you are coming from a stock system. If you are already rooted, and want to return to stock, you would probably have to do a complete restore, and re-lock your device. Then, if you just want the stock kernel; root with this guide, or similar. You can't flash the tiamat kernel unless you're already rooted. This tutorial just gives you root access. Im sure there is a way to go back to the original kernel, without having to restore, but I don't know where those instructions are? Poke around and you may find it. But you'll probably have to start over. Hope this helps!
Sent from the most 'Epic' phone in the world! ...Using XDA Premium app

Thanks. I have a WiFi only version and used another root method which included tiamats kernel. Currently having some reboot issues with the kernel so I was hoping to find a stock kernel that I can use.

Ok. Well, you can use this method to root, but the xoomroot files are different. This tutorial was based off the 3g only, and maybe ill add the wifi option as well.
Here's are great guide from xaositek for the wifi version...
http://forum.xda-developers.com/showthread.php?t=1010568
And I'm pretty sure it doesn't include the overclocked kernel.
Sent from the most 'Epic' phone in the world! ...Using XDA Premium app

http://mirror1.kanged.net/motorola/stingray/xoomroot.zip
seems link are broken

[How To] Root New Evo4g Hboot 2.18 without Unrevoked Without HTCDEV.com Windows Only

So... I recently had my evo replaced. As a result i found that i can no longer use Unrevoked to root, nand unlock and S-off my new phone. The current guides all point to using htcdev.com/bootloader however it seems rather unreliable because i attempted to access it, and the site kept reporting it had an incorrect .php file or some stuff. Google Searches proved that this site goes down frequently.
So with some google searching i have pieced together an Offline way to root an Evo4g. From the sounds of it, i think this method will root, Nand Unlock, S-off, and push a recovery to any device. At least from what i am understanding. Also apparently this method WILL NOT void your HTC warranty because you do not need to use HTCDEV.COM/Bootloader
Soooooo... My disclaimer.. I am not a dev, i have no idea what the first thing a dev does. I give ALL credit to the people that put in the hard work to allow me to achieve root. I will also post credits and the origional thread i pulled this information from. Also, if you mess things up, i cant help you. I probably wont even be able to answer any of your questions.
This method uses a hack provided by SimonSimon34 on these forums for his HTC Wildfire, but it WILL work on our Evo's.
First things first.
1. Turn on your phone
2. Go To Settings->Apps->Development Enable Usb Debugging.
3. Visit Simonsimons34 Wildfire Unlock Thread
4. Download the V2 Universal Rar he has
5. The instructions for this zip are easy. once downloaded, i suggest moving it to the Desktop. Extract to a Folder on the desktop and name it root.
6. Once extracted open your folder you just named root. There will be a file in there called Simonsutility.bak double click on it.
7. You are presented with 4 options.
1. Bootloader Unlock and Root (Universal)
2. Custom Recovery (Unlocked or S-Off)
3. S-Off
4. Install Drivers
Connect your phone to the computer, Choose Charge only. Choose 1 and press enter
8. The phone then does alot of stuff. not exactly sure what any of it means, but if you watch the Simonsutility window it kind of explains as its going what it is doing. when its finished choose option 2 and press enter.
9. You should now be staring at your bootloader screen. Now you need to choose a recovery. I reccomend Amon_Ra's as i have yet to have any catastrophic issues using it. This can be downloaded Amon_ra Recovery Current version is v.2.3 just make sure you download it.
10. Once downloaded i suggest moving it to the folder we created earlier called Root and renaming it to recovery.img because its going to make things easier in the next step.
11. Now you have all you need to push the new recovery. Open up the root folder and shift+right click on fastboot and choose open command prompt here. If you do not have that option, click on your start menu, type CMD, and then navigate to your C:/users/*username/desktop/root folder (*username is obv your user profile name).
12. Once you are in the fastboot folder/directory type
Code:
Fastboot flash recovery recovery.img
{
"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"
}
Once it is finished you can select reboot recovery and you will now be in the Amon_ra Recovery.
From here you can flash a Rom of which for first time rooters, i would reccomend Fresh Evo 4.3.3 just because of its stability.
Below are the paypal accounts and origional threads i ripped off all of this information from. If there is enough interest i will update everything with pics. As i know the resources for this information is very low.
Thanks To
-==-=-=-=-=-=-=-
SimonSimon34
Simons Paypal
Simons Wildfire Thread
Amon_ra
Amon_ra's Paypal
Amon_ra's Origional Thread
Captain Throwback
Captian Throwbacks Thread
Im Placing Captain Throwback up here because his thread was the origional thread i was following, however since the HTC site was down i wasnt able to do anything, but i stole his Picture of the Amon recovery push.
Anyways, if i missed something feel free to flame me incessantly.

ACTUALLY THIS THREAD IS IN THE WRONG SECTION.
It does appear to work without going to the Htcdev site.
Well, someone had to test this method besides Hamspiced (Thanks for the tip). To summarize the method and give a brief description of what was done: I first S-ON and unrooted the phone back to 4.67 with the bootloader LOCKED (OWW). Dowloaded the file from
http://goo.im/devs/simonsimons34/HTC_Universal/Htc_Utilityv2Windows.zip
and unzipped it to a folder called root. Then,
1. Went to Setting/Applications and turned off Fastboot, then Settings/Applications/Development and enabled USB debugging.
2. Went to the root folder and ran the Drivers.exe program (to install the MYHTC drivers).
3. Connected the phone to my computer.
4. Ran the simonsutility.bat file, and was given the set of options:
1. Bootloader Unlock and Root (Universal)
2. Custom Recovery (Unlocked or S-Off)
3. S-Off
4. Install Drivers
and chose option 1.
5. After following a series of instructions, the phone finally rebooted into the bootloader and then read UNLOCKED, to my surprise. Also I tried options 2-4, but none of them seem compatible with the EVO 4g. So, the phone is now unlocked, but S-ON, but as long as the bootloader is unlocked, I can still do anything to the phone that I want, including installing the custom Recovery and turning it back S-OFF (I've done this many times).
So based on the experiment, there does seem to be an alternative right now to going to the Htcdev site to unlock the bootloader. It should work on other phones with the same type of bootloader (LOCK OWW) as well. I see that this takes advantage of a known vulnerability which I am not going to detail here to flash to the bootloader. I'm sure HTC knows about it and will patch it on future phones.

Well awesome! Im glad that my only mess up was that i posted it in the wrong section.
I was tired of the HTCDev site consistantly not working properly. I always had issues accessing it.

It's actually quite simple to understand without using the program (well I read programs very well): Temp root, Copy misc partition to data directory, unlock it with the bool file, flash unlocked misc image back to misc partition...with no Htcdev site. I've done it manually several times. I don't see why no one discovered it sooner.

shortydoggg said:
It's actually quite simple to understand without using the program (well I read programs very well): Temp root, Copy misc partition to data directory, unlock it with the bool file, flash unlocked misc image back to misc partition...with no Htcdev site. I've done it manually several times. I don't see why no one discovered it sooner.
Click to expand...
Click to collapse
Isn't this the same thing TacoRoot does, essentially?

Captain_Throwback said:
Isn't this the same thing TacoRoot does, essentially?
Click to expand...
Click to collapse
It does use tacoroot, but instead of running a PC36IMG file or RUU to downgrade, it uses some file called bool to unlock the bootloader almost directly. The main syntax after Tacoroot (once the files are given the chmod 755 command from the /data/local directory):
dump_image misc /data/local/misc.img
bool /data/local/misc.img unlock
flash_image misc /data/local/misc.img
I'm typing the commands from the top of my head, so there may be a spelling error. Reboot the phone, and the bootloader goes from "LOCKED OOW" TO "UNLOCKED".

Will this method reformat your phone or no?

This response is a little late because l'm on another phone now, but for those that want to know;
It unlocks the bootloader without wiping your phone, unlike the HTCdev site.
Sent from my SAMSUNG-SGH-I747 using xda premium

shortydoggg said:
So, the phone is now unlocked, but S-ON, but as long as the bootloader is unlocked, I can still do anything to the phone that I want, including installing the custom Recovery and turning it back S-OFF (I've done this many times).
Click to expand...
Click to collapse
Hamspiced, thank you for this method, I was having the same problem (had to get a replacement evo with the new software, and htc dev crashes every time I loaded the token)
I have a question for shortydoggg, how were you able to achieve s-off using this method? And were you able to remove the watermark?

wjHarnish said:
Hamspiced, thank you for this method, I was having the same problem (had to get a replacement evo with the new software, and htc dev crashes every time I loaded the token)
I have a question for shortydoggg, how were you able to achieve s-off using this method? And were you able to remove the watermark?
Click to expand...
Click to collapse
The method is just an alternative to going to the HTCdev site (and wiping the phone) to unlock the bootloader. It only unlocks the bootloader so that you can flash a custom recovery and flash superuser to obtain root access without wiping data. The phone will still be S-ON. You would then need to follow Captain Throwback's guide to obtaining S-OFF to remove the watermark and obtain S-OFF afterwards.
Sent from my SAMSUNG-SGH-I747 using xda premium

You can also show it as locked boot loader and send back to HTC leaving your warranty intact. That's in my next update
Sent from my One V using Tapatalk 2

This looks cool.I am trying to root my brother-in-law's EVO. I tried HTCDev and had no luck what so ever. I'll report back as well once I get his phone charged up.
10:35 pm est
Looks like Goo.im is down or something.Unable to download any of the links for the Utility.
Does anyone have the file laying around?

shortydoggg said:
It's actually quite simple to understand without using the program (well I read programs very well): Temp root, Copy misc partition to data directory, unlock it with the bool file, flash unlocked misc image back to misc partition...with no Htcdev site. I've done it manually several times. I don't see why no one discovered it sooner.
Click to expand...
Click to collapse
It seems that when goo.im went down SimonSimon34's source code was lost with it.
If you would be so kind as to detail the manual version of this method it would be helpful to me, and I'm sure others, until SimonSimon34 finishes rewriting his utility, unfortunately, from the ground up.
Thank you much,
J.

jackfrost909 said:
It seems that when goo.im went down SimonSimon34's source code was lost with it.
If you would be so kind as to detail the manual version of this method it would be helpful to me, and I'm sure others, until SimonSimon34 finishes rewriting his utility, unfortunately, from the ground up.
Thank you much,
J.
Click to expand...
Click to collapse
I'm going to detail the method as much as possible here, since some want to see it. I have added links to the original SimonSimon34 source code, as well as a zip file with the necessary files for a manual method. I have walked through the manual mode step by step and have provided as much step by step proceedure as I have time for. Just remember 2 things here:
1. This method was originally made by SimonSimon34.
2. Any attempt at unlocking your bootloader and rooting your phone is at your own risk, so if you brick your phone, it's nobody's fault but your own.
Links:
SimonSimon34 original source code:
https://dl.dropbox.com/u/38127313/Htc_Utilityv2Windows.zip
Shortydoggg's breakdown and additions to SimonSimon's file for Manual Method.
https://dl.dropbox.com/u/38127313/Root 2.3.5.zip
(YOU NEED TO UNZIP THE FILES TO A FOLDER OF LIKING.)
NOW FOR A DESCRIPTION OF HOW THE ROOT METHOD WORKS (MANUALLY). YOU COULD ALSO JUST RUN THE Htc_Utilityv2Windows UTILITY (simonsutility.bat) SINCE IT IS PROBABLY EASIER, ALTHOUGH I FOUND SOME ERRORS AND MADE MY OWN CORRECTED VERSION WHICH I'M NOT GOING TO POST DUE TO MOST OF IT IS NOT MY OWN WORK. ALSO, THE WAY I ENTER MY COMMANDS IS SLIGHTLY DIFFERENT THAN THE WAY SIMONSIMON34 DOES HIS INSIDE HIS PROGRAM.
1. THE PHONE SHOULD BE IN CHARGE ONLY MODE WITH IT PLUGGED INTO YOUR COMPUTER'S USB.
2. RUN THE DRIVERS.exe file
3. TURN OFF FASTBOOT UNDER SETTINGS/APPLICATIONS
4. ENABLE USB DEBUGGING UNDER SETTINGS/APPLICATIONS/DEVELOPMENT
5. NOW YOU WOULD OPEN A COMMAND PROMPT AT THE FOLDER WHERE YOU UNZIPPED THE FILES, THEN TYPE:
adb push tacoroot.sh /data/local <ENTER>
adb push flash_image /data/local <ENTER>
adb push dump_image /data/local <ENTER>
adb push bool /data/local <ENTER>
adb push Superuser.zip /sdcard/ <ENTER>
adb shell
cd /data/local
chmod 755 tacoroot.sh
chmod 755 flash_image
chmod 755 dump_image
chmod 755 bool
./tacoroot.sh --recovery
(HOLD VOLLUME UP +VOLUME DOWN + POWER BUTTONS WHEN THE RED TRIANGLE APPEARS, THEN HIT THE POWER BUTTON TO REBOOT THE PHONE.)
(ONCE IT REBOOTS, TYPE
adb shell
/data/local/tacoroot.sh --setup
(HOLD VOLLUME UP +VOLUME DOWN + POWER BUTTONS WHEN THE RED TRIANGLE APPEARS, THEN HIT THE POWER BUTTON TO REBOOT THE PHONE.)
(ONCE IT REBOOTS, TYPE
adb shell
/data/local/tacoroot.sh --root
(IF AT ANYTIME THE PROCESS IS MESSED AFTER THIS POINT, YOU MUST REBOOT THE PHONE THEN TYPE:
adb shell
/data/local/tacoroot.sh --undo
IN ORDER TO RESTORE YOUR PHONE BACK TO WORKING CONDITION)
adb shell
cd /data/local
./dump_image misc misc.img
./bool misc.img unlock
./flash_image misc misc.img
./tacoroot.sh --undo
(ONCE THE PHONE REBOOTS, THEN BOOT INTO THE BOOTLOADER BY TYPING
adb shell
reboot bootloader
fastboot flash recovery recovery.img
fastboot reboot-bootloader
(WHEN THE PHONE REBOOTS, HIT THE POWER BUTTON, USE THE VOLUME DOWN BUTTON THE THE POWER BUTTON TO GO INTO RECOVERY, THEN FLASH THE SUPERUSER.ZIP APP WHICH SHOULD BE ON THE ROOT OF THE SDCARD. REBOOT THE PHONE AND IT SHOULD NOW BE ROOTED.)

bool misc.img lock will lock it back how it was before, locked. Not relocked. But full blown locked
Sent from my One V using Tapatalk 2

If anyone has a copy of the Htc_Utilityv2Windows can you please post it, since it was lost from goo when they crashed.
Thanks

gadgetdaddy said:
If anyone has a copy of the Htc_Utilityv2Windows can you please post it, since it was lost from goo when they crashed.
Thanks
Click to expand...
Click to collapse
I already posted a link in this thread.
Sent from my SGH-I747M using xda premium

Mention github has utility 2 please
Sent from my One V using Tapatalk 2

simonsimons34 said:
bool misc.img lock will lock it back how it was before, locked. Not relocked. But full blown locked
Sent from my One V using Tapatalk 2
Click to expand...
Click to collapse
Not sure what you mean by "full blown locked" as opposed to "relocked"
Do you mean it will go back to s-on even if you went the full way to s-off, our are you referring to something else?
Sorry for the noobish question.
Thank you.
Sent from my PC36100 using Tapatalk 2

jackfrost909 said:
Not sure what you mean by "full blown locked" as opposed to "relocked"
Do you mean it will go back to s-on even if you went the full way to s-off, our are you referring to something else?
Sorry for the noobish question.
Thank you.
Sent from my PC36100 using Tapatalk 2
Click to expand...
Click to collapse
I mean like how the phone was when you bought it. If you need to send it in for warranty you would flash the stock hboot, send the son command, run bool lock command, and flash the ruu then your phone will be exactly like when you bought it was
Sent from my One V using Tapatalk 2

[ROOT, CWM] JXD S18-03-xxxx RK2926 mini pad [Guide]

In this guide i will show you how to root a JXD S18 03-xxxx device.
This method was tested on the following device:
OS: Android 4.1.1
Kernel: 3.0.36+ Feb 2
Soc: Rk2926
Model: S18-03-201304-4GB-00727
Root:
0. Download files.zip(from here) extract it and open it in explorer.
1. Connect your device to your computer (micro-usb)
2. Unmount all storage devices (TF/SD card, onboard TF/SD, etc..)
3. Enable USB Debugging (Under settings > Options for developers > Enable USB Debugging)
4. Open ''AdbDriverInstaller.exe'' and install the universal ADB driver
5. Automated process for rooting the device ''ROOT ME.bat'' Press any key and just wait and let the tablet reboot.
6. Manual root:
Code:
adb shell
mount -o remount,rw -t rfs /dev/block/st19 /system
exit
adb push busybox /system/bin
adb push su /system/bin
adb shell
chmod 4755 /system/bin/busybox
chmod 4755 /system/bin/su
mount -o remount,ro -t rfs /dev/block/st19 /system
exit
adb reboot
And now you have root.
{
"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"
}
Make sure to update su(super user) after rooting. Because it is outdated.
You can either use adb push for this or you can use the Google Play store to download the latest bin.
CWM-recovery
Download: http://files.androtab.info/rockchip/rk2928/20130425/S18-03_CWM.zip
From adb root shell
1. extract flash_image and recovery.img from CWM.zip
2. put flash_image and recovery.img into device, e.g.
adb push flash_image /dev/
adb push recovery.img /dev/
3. enter root shell (adb shell)
4. flash recovery.img into recovery partition with flash_image, e.g.
chmod 755 /dev/flash_image
/dev/flash_image recovery /dev/recovery.img
Read this when you have any issues
CWM installation problems, please try another method if this doesn't work for you.
Link: http://androtab.info/clockworkmod/rockchip/install/
If you have any issues while rooting please try:
adb kill-server
adb devices
And see if the devices is listed after killing the server.
If it is not than u may have another soc (older version does have other rockchip and the adb driver wont work properly).
This guide is for the latest version as if 1st May 2013: S18-03-XXXX (4.9.2013)
If you still have no output from adb devices you can try one more thing!
By editing android_winusb.inf in C:\Windows\System23\Drivestore\Filerepository\android_winusb.inf_amd64_neutral_<random_chars>
You will see two of those folders.
Open it with a text editor like notepad++ or notepad make sure you have nt authority rights
android_winusb.inf:
Code:
;------------------------------------NTx86------------------------------------
[Google.NTx86];
For loopback testing
And add this after the first space of declaring hardware ids;
Code:
%SingleAdbInterface% = USB_Install, USB\VID_2207&PID_0010
%CompositeAdbInterface% = USB_Install, USB\VID_2207&PID_0010&MI_01
%SingleAdbInterface% = USB_Install, USB\VID_2207&PID_0010
%CompositeAdbInterface% = USB_Install, USB\VID_2207&PID_0010&MI_01
Tested and working on the following devices:
Audiosonic T-17B 7" tablet (Kmart webshop version) ✓
S18-03-XXXX (4.9.2013) ✓
S18-03-201302 (4gb-00905) ✓
S18-02-XXXX (x.x.2012) ?
Credits: me, icood70pro, fun_ for modding CWM for rockchip, all credit goes to original CWM author koush and all its contributors.

How about S18-02-xxxx ?
I got myself a S18-02-xxxx, The ADB drivers behave oddly for this gadget. The driver installs, but SuperOneClick can't locate the device.
It does have SuperUser installed, but only the .apk file, not the permissions required to run it.
Think you can setup something?

macrat said:
It does have SuperUser installed, but only the .apk file, not the permissions required to run it.
Click to expand...
Click to collapse
Can you get access to adb shell and what os are you running? Modified adb doesn't seem to work properly on windows 8 you need to change this in order to make it work for windows 8 i think (at least you can try).
Start -> Run -> Type: "gpedit.msc" (Without quotes) -> Computer Configuration -> Administrative Templates -> Windows Components -> Application Compatibility -> Turn off Application Compatibility Engine <- Disable this
It might be the S18-02-xxxx. Model 02 has another soc i think, can you download a app in the play store for me? Type in: "Cpu info", download and install -> "CPU / RAM / DEVICE Identifier". And tell me what soc you have in it. Because the older versions may have a a9 amlogic 8726-m3l soc in it.
Please try that and verify if that worked for you or if you get adb shell access. Thanks,
and sorry for the late reply.

Just wanted to confirm I have successfully rooted my Audiosonic T-17B &" tablet (AUS KMart version) using your guide!
Although I'll note that the BAT file didn't succeed for some reason. Manually following the commands worked fine though, but I didn't bother with CWM as yet.
EDIT: Figured it out. It's the 'exit' commands you've stuck in there, it terminates the whole batch command instead of just restarting ADB. Can you edit that and re-upload the zipfile?

switchblade88 said:
Just wanted to confirm I have successfully rooted my Audiosonic T-17B &" tablet (AUS KMart version) using your guide!
Although I'll note that the BAT file didn't succeed for some reason. Manually following the commands worked fine though, but I didn't bother with CWM as yet.
EDIT: Figured it out. It's the 'exit' commands you've stuck in there, it terminates the whole batch command instead of just restarting ADB. Can you edit that and re-upload the zipfile?
Click to expand...
Click to collapse
Yes i can and sorry for that mistake. Thanks for confirming that it did work for you on another device with the same soc.

Resquest download password
NiTrOwow said:
0. Download files.zip(from) extract it and open it in explorer.
Click to expand...
Click to collapse
I not success download the zip file because ask me for a password. It's possible obtain this password please?

Stef20 said:
I not success download the zip file because ask me for a password. It's possible obtain this password please?
Click to expand...
Click to collapse
Seems like a bug.. in the forum software handling the bbcode..
Just remove the <br /> at the end of the url and it works.
And my content does not even include <br /> == space/enter ...
FYI. PROBLEM IS SENT TO FORUM ADMIN.

Oh yes I not viewed this... Normaly I take care :silly:
I edit manually the link and work good. Thank you for the reply!

Stef20 said:
Oh yes I not viewed this... Normaly I take care :silly:
I edit manually the link and work good. Thank you for the reply!
Click to expand...
Click to collapse
Alright man good luck and let me know if it works for you and let me know the model number

I will for sure. I wait a new tablet S18 from China just I'm not sure if I will have a s03 or s02 model. I suppose is a S03.

NiTrOwow said:
Seems like a bug.. in the forum software handling the bbcode..
Just remove the <br /> at the end of the url and it works.
FYI. PROBLEM IS SENT TO FORUM ADMIN.
Click to expand...
Click to collapse
Thanks. This problem is now fixed. it will not ask for a password now.
Mike

Alright then, only thing that i miss on this tab is a uhm extra ogt support and a good data sheet of the soc. Else would have made a small shell/nas/webserver from out of it.. But modding requires me a data sheet or else i have to reserve engineer the soc and then try to mod it with luck(?)
MikeChannon said:
Thanks. This problem is now fixed. it will not ask for a password now.
Mike
Click to expand...
Click to collapse
Thanks Mike that was fast :')
Sent from my HTC Sensation using xda app-developers app

NiTrOwow said:
Alright then, only thing that i miss on this tab is a uhm extra ogt support and a good data sheet of the soc. Else would have made a small shell/nas/webserver from out of it.. But modding requires me a data sheet or else i have to reserve engineer the soc and then try to mod it with luck(?)
Click to expand...
Click to collapse
If I receive a S03 and I hope is this, I will try your tutorial, if is a S02 I will try other thing because I suppose is not the same CPU and this risk not work?
About the OTG, I have read a guy success use it on the S18 with a external power on the OTG. He say it's a power problem only. Just I lost the link where is this message.
I hope my english is OK because is not my language.

Stef20 said:
If I receive a S03 and I hope is this, I will try your tutorial, if is a S02 I will try other thing because I suppose is not the same CPU and this risk not work?
About the OTG, I have read a guy success use it on the S18 with a external power on the OTG. He say it's a power problem only. Just I lost the link where is this message.
I hope my english is OK because is not my language.
Click to expand...
Click to collapse
No i understand you if you get your S03 or 02 you will have to open it up and have a look at it yourself i made some close up images of the board.
They can be found right here
http://forum.xda-developers.com/showthread.php?t=2253706
So you can look at your device and mine from the inside and look what is diffrent
:good:

NiTrOwow said:
No i understand you if you get your S03 or 02 you will have to open it up and have a look at it yourself i made some close up images of the board.
They can be found right here
http://forum.xda-developers.com/showthread.php?t=2253706
So you can look at your device and mine from the inside and look what is diffrent
:good:
Click to expand...
Click to collapse
It's fun view the inside without open it I view have a little more space for a bigger battery

Stef20 said:
It's fun view the inside without open it I view have a little more space for a bigger battery
Click to expand...
Click to collapse
Forgot to say that this battery for the S18-03 has a pcb on the battery (fail safe, anti-overvolt). It did surprise me because most cheap china products don't have that and it is a risk if you want to use it a lot because it may someday explode if you don't have this haha .. Battery looks like a BL-5B/BLC-2 from nokia without the plastic housing.

Finaly I received my S18 today and it's a S03, just a big trouble... after only few hours of use, the power button refuse work now... It's a cra* product I received...

I'm a little sad not success try your tutorial because my S18 are dead before... Now I not able start my tablet... I will return it!
I purchase a Asus Me172v and success root it . I used this tutorial http://forum.xda-developers.com/showpost.php?p=42047570 , just I'm not able write in this section because I suppose I'm new or I need have more messages.

Stef20 said:
I'm a little sad not success try your tutorial because my S18 are dead before... Now I not able start my tablet... I will return it!
I purchase a Asus Me172v and success root it . I used this tutorial http://forum.xda-developers.com/showpost.php?p=42047570 , just I'm not able write in this section because I suppose I'm new or I need have more messages.
Click to expand...
Click to collapse
Oke that sucks to have a DOA.
I hope they will resort this, and that you will be able to try my guide.
Good luck man.

NiTrOwow said:
Oke that sucks to have a DOA.
I hope they will resort this, and that you will be able to try my guide.
Good luck man.
Click to expand...
Click to collapse
I wait a new S18, just it's very long to receive it with the cheap post chipping.
I want root it because I hate not have the control

[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!!!