CWM Installation Fails - Ouya (!) Screen - Ouya General

I am unable to post in the development forum yet, so I am posting here. For the past several weeks I have been having trouble installing CWM Recovery. I've tried using the Mod Collection tool and manual installation and still received the Ouya (!) screen. With the new Ouya update, I needed CWM to work to preserve root. If you are also having issues installing and booting to CWM, the below worked for me.
Steps I used to gain Root, setup Play Store and install CWM:
Sideload and run One Click Root
Sideload Jrummys Busybox Installer & Install Busybox
Sideload and Install Xposed Framework
Sideload ModCollection4Ouya 3.6
Open Xposed Framework and check ModCollection4Ouya 3.6 as a module
Open ModCollection4Ouya 3.6 and performed the following:
Install Play Store and Select "On" for Play Store option
Install CWM Recovery
Reboot into CWM but receive error Ouya (!)
Below corrected my CWM Install Issue and allowed me to update to the newest firmware:
Open Play Store & Install Busybox Installer (Stephen Stericson version)
Open Busybox installer - smart install automatically installed busybox
Open Mod Collection 4.0 and reinstalled CWM
Reboot to CWM
CWM Recovery worked
Open ModCollection4Ouya 3.6 and select option to Preserve SU
Reboot then install upgrade
Good Luck and hope you experience the same results! It seems the Jrummy Busybox version didn't work for me. After installing the other version, CWM installed successfully.

Thanks for posting this, I will have time to try it to tomorrow, hopefully it fixes this issue for me as well!!

boo13oo said:
I am unable to post in the development forum yet, so I am posting here. For the past several weeks I have been having trouble installing CWM Recovery. I've tried using the Mod Collection tool and manual installation and still received the Ouya (!) screen. With the new Ouya update, I needed CWM to work to preserve root. If you are also having issues installing and booting to CWM, the below worked for me.
Steps I used to gain Root, setup Play Store and install CWM:
Sideload and run One Click Root
Sideload Jrummys Busybox Installer & Install Busybox
Sideload and Install Xposed Framework
Sideload Mod Collection 4.0
Open Xposed Framework and check Mod Collection 4.0 as a module
Open Mod Collection 4.0 and performed the following:
Install Play Store and Select "On" for Play Store option
Install CWM Recovery
Reboot into CWM but receive error Ouya (!)
Below corrected my CWM Install Issue and allowed me to update to the newest firmware:
Open Play Store & Install Busybox Installer (Stephen Stericson version)
Open Busybox installer - smart install automatically installed busybox
Open Mod Collection 4.0 and reinstalled CWM
Reboot to CWM
CWM Recovery worked
Open Mod Collection 4.0 and select option to Preserve SU
Reboot then install upgrade
Good Luck and hope you experience the same results! It seems the Jrummy Busybox version didn't work for me. After installing the other version, CWM installed successfully.
Click to expand...
Click to collapse
Where can I download Mod Collection 4.0 or did you mean Mod_Collection4Ouya.3.6.apk?

Thanks I will try this.
Sent from my GT-I9100 using xda app-developers app

@Toxic_Dragon - you are correct. I meant ModCollection4Ouya version 3.6. I've updated the original post. Thanks!

boo13oo said:
I am unable to post in the development forum yet, so I am posting here. For the past several weeks I have been having trouble installing CWM Recovery. I've tried using the Mod Collection tool and manual installation and still received the Ouya (!) screen. With the new Ouya update, I needed CWM to work to preserve root. If you are also having issues installing and booting to CWM, the below worked for me.
Steps I used to gain Root, setup Play Store and install CWM:
Sideload and run One Click Root
Sideload Jrummys Busybox Installer & Install Busybox
Sideload and Install Xposed Framework
Sideload ModCollection4Ouya 3.6
Open Xposed Framework and check ModCollection4Ouya 3.6 as a module
Open ModCollection4Ouya 3.6 and performed the following:
Install Play Store and Select "On" for Play Store option
Install CWM Recovery
Reboot into CWM but receive error Ouya (!)
Below corrected my CWM Install Issue and allowed me to update to the newest firmware:
Open Play Store & Install Busybox Installer (Stephen Stericson version)
Open Busybox installer - smart install automatically installed busybox
Open Mod Collection 4.0 and reinstalled CWM
Reboot to CWM
CWM Recovery worked
Open ModCollection4Ouya 3.6 and select option to Preserve SU
Reboot then install upgrade
Good Luck and hope you experience the same results! It seems the Jrummy Busybox version didn't work for me. After installing the other version, CWM installed successfully.
Click to expand...
Click to collapse
It didn't work for me.
Sent from my GT-I9100 using xda app-developers app

I had issues with ADB and fastboot until i changed the drivers for the ouya manually for every step in the device manager.

THANK YOU!!! You are the freaking man!!!! I have wasted hours trying to figure out how to fix CWM and I couldn't get anything. Finally stumbled upon this post, and I am kicking myself for not finding it sooner. Thanks a ton! :laugh:

CheeseMcGee said:
THANK YOU!!! You are the freaking man!!!! I have wasted hours trying to figure out how to fix CWM and I couldn't get anything. Finally stumbled upon this post, and I am kicking myself for not finding it sooner. Thanks a ton! :laugh:
Click to expand...
Click to collapse
What exactly did you do as I can't get this to work.
Sent from my GT-I9100 using xda app-developers app

robinscp said:
What exactly did you do as I can't get this to work.
Click to expand...
Click to collapse
I had used a different method to root and install CWM, but in order to fix the problem, I literally followed every step in order starting with sideload One Click Root. It was redundant and un-necessary, but it produced the results in the end by following step by step.

Related

[Q] Installed two busyboxes accidently

Hello,
I recently flashed my phone with Mur4ik's Gingerbread 2.3.5 RC4 and everything was fine. Two days ago when I installed the V6 SuperCharger Script I installed BusyBox installer, and like it's said in the tutorial I chose to install BusyBox 1.18.2, installed that and run the script and everything was fine.
This morning I installed DroidSheep app and it said that i need BusyBox, it took me to the market to download Busybox installer and accidently installed the newest busybox, after exiting the app, went to Root Explorer and nothing is displayed, but SuperUser says that Root acces has been granted to Root Explorer.
So what should I do now? BTW the phone is still working, rebooted and the same thing.
Martin18 said:
Hello,
I recently flashed my phone with Mur4ik's Gingerbread 2.3.5 RC4 and everything was fine. Two days ago when I installed the V6 SuperCharger Script I installed BusyBox installer, and like it's said in the tutorial I chose to install BusyBox 1.18.2, installed that and run the script and everything was fine.
This morning I installed DroidSheep app and it said that i need BusyBox, it took me to the market to download Busybox installer and accidently installed the newest busybox, after exiting the app, went to Root Explorer and nothing is displayed, but SuperUser says that Root acces has been granted to Root Explorer.
So what should I do now? BTW the phone is still working, rebooted and the same thing.
Click to expand...
Click to collapse
The new version would have just over-written the old, sadly there are several issues with the new version which can cause some apps to malfunction... just go back to the market, download the BusyBox Installer (by Jared Rummler - JRummy16) and just select to install v1.18.2 again.
olite said:
The new version would have just over-written the old, sadly there are several issues with the new version which can cause some apps to malfunction... just go back to the market, download the BusyBox Installer (by Jared Rummler - JRummy16) and just select to install v1.18.2 again.
Click to expand...
Click to collapse
Nevermind fixed with restoring from Recovery.
Martin18 said:
Nevermind fixed with restoring from Recovery.
Click to expand...
Click to collapse
lol, that's one way of doing it too...
Busybox
I think Swiftdroid already has Busybox installed
jhonnyx1000 said:
I think Swiftdroid already has Busybox installed
Click to expand...
Click to collapse
Yep, that it sure does.
Sent from my GT540f using xda premium

[Q] SuperSU hidden/half enabled

I am running Nexus 7 with 4.2.1 build JOP40D.
After I got the 4.2.1 OTA update I noticed root was no longer working.
I went into Settings and Apps and disabled it and tried using SuperUser but discovered that it didn't work with 4.2.1
I used the Google Nexus_7_ToolKit_v4.0.0 and ran the root command choosing SuperSU which was the correct one for 4.2.1.
It did a cleanup of any other root stuff and successfully pushed root to the device.
It did not show up in the App Drawer, but does show up in Settings, Apps, All.
I tried again by sideloading via CWM recovery but there was no difference.
I then ran the toolkit to remove root, busybox, etc, then attempted to reinstall them both again.
I am still stuck with the same problem.
When running a root app such as Titanium Backup, it gets stuck at "asking for root rights" and not the 'you need to root your device' message.
Any help?
[edit]
When installing busybox it checks and says you should see the reply
system/xbin/busybox
but the reply I get is
system/bin/busybox
Is this a problem?
DazFromTaz said:
I am running Nexus 7 with 4.2.1 build JOP40D
After I got the 4.2.1 OTA update I noticed root was no longer working.
I went into Settings and Apps and disabled it and tried using SuperUser but discovered that it didn't work with 4.2.1
I used the Google Nexus_7_ToolKit_v4.0.0 and ran the root command choosing SuperSU which was the correct one for 4.2.1.
It did a cleanup of any other root stuff and successfully pushed root to the device.
It did not show up in the App Drawer, but does show up in Settings, Apps, All.
I tried again by sideloading via CWM recovery but there was no difference.
I then ran the toolkit to remove root, busybox, etc, then attempted to reinstall them both again.
I am still stuck with the same problem.
When running a root app such as Titanium Backup, it gets stuck at "asking for root rights" and not the 'you need to root your device' message.
Any help?
Click to expand...
Click to collapse
1. you need to flash the su binaries in your recovery, latest su binaries http://download.chainfire.eu/298/SuperSU/CWM-SuperSU-v0.99.zip
2. or you need to install busybox if you already flashed the binaries. you can find free busybox installer apps in the play store. best one is by stericson.
That's what confuses me. I have flashed the su binaries via recovery and also installed busybox.
Downloaded the busybox from Play Store now though. It can't install with root though.
Remember, SuperSU is showing up in Settings, Apps, All, it just doesn't seem to be usable or showing up in app drawer.
DazFromTaz said:
That's what confuses me. I have flashed the su binaries via recovery and also installed busybox.
Downloaded the busybox from Play Store now though. It can't install with root though.
Remember, SuperSU is showing up in Settings, Apps, All, it just doesn't seem to be usable or showing up in app drawer.
Click to expand...
Click to collapse
delete supersu from either /data/app/ or /system app/, wherever you have it installed. then reboot into recovery and wipe cache and dalvik. after, reboot and reinstall supersu app.
are you sure that you flashed the latest su binaries? if not sure, flash the one that i linked while youre in your recovery.
simms22 said:
delete supersu from either /data/app/ or /system app/, wherever you have it installed. then reboot into recovery and wipe cache and dalvik. after, reboot and reinstall supersu app.
are you sure that you flashed the latest su binaries? if not sure, flash the one that i linked while youre in your recovery.
Click to expand...
Click to collapse
Thankyou again for your response.
I deleted superuser.apk using adb, then cleared the caches. I then rebooted recovery, sideloaded the latest superuser (from the link provided) and then booted into Android.
Same as before. Superuser is not in the app drawer, but can be seen in settings.
Remember when I said I disabled it in Settings, Apps?
Well it turns out that Google remembers this, even when the app is removed and reinstalled. It will not show that it is disabled when you check it in Settings though.
To fix, I disabled again, then enabled it. Boom fixed.
Feel rather sheepish now.
Although you pushed me to learn quite a bit more about adb so thanks for that!
DazFromTaz said:
Remember when I said I disabled it in Settings, Apps?
Well it turns out that Google remembers this, even when the app is removed and reinstalled. It will not show that it is disabled when you check it in Settings though.
To fix, I disabled again, then enabled it. Boom fixed.
Feel rather sheepish now.
Although you pushed me to learn quite a bit more about adb so thanks for that!
Click to expand...
Click to collapse
no matter how it was "fixed", its still a :victory: congrats
WooooooW!!!!!! Banging my head with this one until I found this thread. Crazy but it worked, after I did all that the OP said he did.. Thanks..

[Q] Installing su and busybox in cwm

Apologies if this has been requested before, but I cannot find any updated files for this.
I want to return to stock image 4.4.2 and then install cwm, su and busybox. Recovery and SU are easy to find, but I can't find any updated files to install busybox. Or the SuperSu+busybox CWM package. I tried to install it through Play Store, but that didn't go so well.
I ran stock image with only root/su for a day or so, and it was alright. Now an app asks for busybox and I messed it up. So reinstall, and hopefully with the right files from the start.
Any help would be appreciated.
Thanks
djind said:
Apologies if this has been requested before, but I cannot find any updated files for this.
I want to return to stock image 4.4.2 and then install cwm, su and busybox. Recovery and SU are easy to find, but I can't find any updated files to install busybox. Or the SuperSu+busybox CWM package. I tried to install it through Play Store, but that didn't go so well.
I ran stock image with only root/su for a day or so, and it was alright. Now an app asks for busybox and I messed it up. So reinstall, and hopefully with the right files from the start.
Any help would be appreciated.
Thanks
Click to expand...
Click to collapse
Have a look at this. https://play.google.com/store/apps/details?id=me.timos.busyboxonrails
Thnx I will try that.. I thought there would be a cwm installer somewhere.. But if this works, then it's all good.

[Stock 5.1.1] Full Device Encryption + SuperSu + Xposed Framework + No downgrade

After a couple of days bricking around, finally found a way to have all the goodies and still have full device encryption. Something that isn't working with custom recovery installed.
Short guide:
1. Stock ROM 5.1.1
2. Encrypt device first (!)
3. Root using Kingroot (NewKingrootV4.82_C138_B250_xda_release_2016_03_09_105243.apk) (http://forum.xda-developers.com/android/apps-games/one-click-root-tool-android-2-x-5-0-t3107461)
4. Reboot
4. Remove Kingroot and install SuperSu using this guide (http://www.w0lfdroid.com/2015/05/How-to-Remove-Replace-KingUser-KingRoot-with-SuperSU.html)
5. Reboot
6. Download Xposed Framework sdk22, arm (not arm64) from http://forum.xda-developers.com/showthread.php?t=3034811
6. Install Xposed Framework zip trough flashfire-0.24.apk using this guide (http://forum.xda-developers.com/g4/themes-apps/guide-installing-xposed-locked-t3181593)
7. Reboot
7. Install the xposed installer
8. Good to go!
Finally have all the tweaks and no worries in case of lost/stolen device.
It's working!
Only followed steps 3 to 5 though.
Rest are not required.
Do I need to have a unlcoked bootloader?
Dinkec27 said:
Do I need to have a unlcoked bootloader?
Click to expand...
Click to collapse
no, you keep all the goodies
Please, note that according to this thread :
http://forum.xda-developers.com/z3-compact/general/kingroot-4-0-t3105593
There may be issues with privacy and your IMEI may be sent to China when you're rooting with Kingroot... Which may be bad. Pretty bad. (It allows for instance the creation of fake phones with real IMEI.)
Has anyone tried flashing Xposed through Flashfire on Android 6.0.1 Beta?
I get root with this easy method, thank you man!
I try to install V4A (through Apk) but when i install the drivers, a message says: "Driver install failed: the busybox installation on you device does not work... etc."
I have just installed the last version of busybox in /system/xbin.
How can i resolve it?
FunkyCrime said:
I get root with this easy method, thank you man!
I try to install V4A (through Apk) but when i install the drivers, a message says: "Driver install failed: the busybox installation on you device does not work... etc."
I have just installed the last version of busybox in /system/xbin.
How can i resolve it?
Click to expand...
Click to collapse
I think you need to install XZDualRecovery because that has the RIC fix(basically read and write permissions for system without unlocked bootloader),I had this issue as well and this solved it for me

Help with installing Magisk on Verizon Samsung Galaxy Note 3 SM-N900V

I have read many threads and lots of videos and cannot seem to get the Magisk installed.
I have flashed back to stock many times with (N900VVRUEOF1_N900VVZWEOF1_N900VVRUEOF1_HOME.tar.md5) in order to try multiple methods.
Rooted with Arabictoolapp - used rootchecker to verify/application also says true for root
followed: https://forum.xda-developers.com/ve...guide-ob6-of1-root-bootloader-unlock-t3439010
installed SU from playstore to unlock bootloader using the adp method - shows developer mode to verify - using eMMc to verify CID starts with 15
followed: https://forum.xda-developers.com/ve...l/official-note-3-verizon-bootloader-t3359370
installed twrp using official twrp app & also tried ODIN in another trial (picked verizon americas and got twrp-3.2.3-0-hlte.img.tar and twrp-3.2.3-0-hlte.img )
turned phone off and boot into recovery to verify; at this time i created a recovery
using MagiskManager i downloaded the zip (Magisk-v18.1.ip) and flashed using twrp - no errors but when i restart the phone it says Magisk not installed
next attempt was to extract the boot.img from the stock OF1 and then flash the Magisk - no errors but when i restarted the phone it says the same thing - Magisk not installed
another attempt was to patch the boot.img and got a patch_boot.img then using TWRP i flashed the patch_boot.img - restarted and magisk not installed
after further digging, i tried another method which was to unroot using SU, reboot, go into recovery to then install Magisk - magisk not installed
*note each attempt to install Magisk unrooted my phone
*was able to use Magisk-uninstaller-20190204.zip to uninstall Magisk manager from recovery - icon went away
anyways i am completely stuck now. any suggestions or comments on my approach?
jordanfan23 said:
installed SU from playstore to unlock bootloader using the adp method - shows developer mode to verify - using eMMc to verify CID starts with 15
followed:
Click to expand...
Click to collapse
Did you uninstall SU before trying to install magisk. The two together may cause conflict.
cssr said:
Did you uninstall SU before trying to install magisk. The two together may cause conflict.
Click to expand...
Click to collapse
Yes my last attempt i tried.
please help! there has got to be something i am doing wrong or missing. i can flash the uninstall zip and it does uninstall the magisk manager
@cssr any other input or suggestions?
jordanfan23 said:
@cssr any other input or suggestions?
Click to expand...
Click to collapse
Try twrp 2.8.7 hltevzw. You are using the stock ROM which is android 5. Twrp 3.1 and higher is for android 7 and up. I missed that the first time I read your post.
cssr said:
Try twrp 2.8.7 hltevzw. You are using the stock ROM which is android 5. Twrp 3.1 and higher is for android 7 and up. I missed that the first time I read your post.
Click to expand...
Click to collapse
no go =(
@cssr should i try another version of magisk?
jordanfan23 said:
@cssr should i try another version of magisk?
Click to expand...
Click to collapse
Yes. Are you installing Magisk .zip in twrp and installing Magisk Manager APK after normal reboot?
cssr said:
Yes. Are you installing Magisk .zip in twrp and installing Magisk Manager APK after normal reboot?
Click to expand...
Click to collapse
what do you mean after normal reboot? so flash magisk in twrp. reboot. reboot again then install magisk manager? do you know what version of magisk i should run and where i can find the dl link?
What he means is you install the Magisk ZIP via TWRP in Recovery mode, reboot the phone, then you install Magisk Manager via the APK.
Go to magiskmanager dot com website which has the ZIP installer plus the APK for the Manager.
I only just recently tried to tackle this challenge. I also installed 0F1 with Odin, then rooted with Arabic. I was messing with Pokemon go and it wasn't happy I was rooted. I downloaded magisk manager, installed it that way. At reboot, angry message from Verizon that I have custom software and phone won't boot. I assume this is because I didn't install custom recovery.
If you figure a way to get this done, I will be grateful. One thing I don't quite follow. Magisk is a root method...so should we really be rooting the phone prior? Seems redundant and going against the whole point of magisk. Right?
I wanted to play around with spoofing GPS with PGO which requires making a GPS spoofer a system app (need root for that). Is that still possible using magisk?
I'll post any updates I have as well.

Categories

Resources