Oppo Find 5 Root with CASUAL

Search This thread

jalsamarrai

New member
May 4, 2010
3
1
And, somewhere, I read you need to install Google Framework first (of course, with the phone rooted)

Thanks for the help guys! I purchased the chinese version of this phone and, as i mentioned earlier, it is running 4.1.1. I rooted the phone using a simple root process that only required me to flash a file in recovery...Right now I am just wondering exactly how I should install gapps...I've done my research and in some places found that if one uses an incorrect version of gapps it can cause problems with the phone. I downloaded jb 20120831 (I think it's the right version for this phone?) and now just need some simple directions as to how I should install it without any problems or risk of bricking my phone...any help is much appreciated =) Thanks!
 

pvillasuso

Senior Member
Apr 16, 2007
1,940
815
Thanks for the help guys! I purchased the chinese version of this phone and, as i mentioned earlier, it is running 4.1.1. I rooted the phone using a simple root process that only required me to flash a file in recovery...Right now I am just wondering exactly how I should install gapps...I've done my research and in some places found that if one uses an incorrect version of gapps it can cause problems with the phone. I downloaded jb 20120831 (I think it's the right version for this phone?) and now just need some simple directions as to how I should install it without any problems or risk of bricking my phone...any help is much appreciated =) Thanks!

1st update to international firmware here [ gapps included inside ] : http://www.oppoforums.com/threads/find-5-beta-firmware-x909en_13_130206.563/

Then..

Follow this to root : http://xdaforums.com/showpost.php?p=37745240&postcount=35
 

EnemyOfGlaDOS

Senior Member
Nov 10, 2010
5,080
1,279
Boulder, Colorado
I've always lost the ability to receive OTA's when I root, someone was saying in another forum that I will still receive OTA updates with a rooted Find 5. Can anyone confirm this?

Sent from my X909 using Tapatalk 2
 
  • Like
Reactions: paperWastage

paperWastage

Senior Member
Mar 18, 2009
1,000
496
NJ
wasn't able to root with the Casual .jar (even with the replacement adb.exe plus PdaNet drivers)... got the error that root was unsuccessful at the end

eventually, had to manually use the adb.exe to push the insecure bootimage, then manually adb push the su and Superuser.apk to the device

root stayed on device after I wiped it

the System Updater app still works (no new updates yet, so can't test if a full OTA update will work)
 
  • Like
Reactions: EnemyOfGlaDOS

MJHawaii

Senior Member
Aug 13, 2011
892
433
Honolulu, HI
www.androidhawaii.org
Reading Drivers from Ubuntu

So I have adb installed and I am using Ubuntu but when I run casual it will not connect. I am new at using Ubuntu is there a libusb command I should be running to get the device to connect? When I run adb devices it shows up blank. Can someone help me with getting it connected in ubuntu? :confused:
 

paperWastage

Senior Member
Mar 18, 2009
1,000
496
NJ
So I have adb installed and I am using Ubuntu but when I run casual it will not connect. I am new at using Ubuntu is there a libusb command I should be running to get the device to connect? When I run adb devices it shows up blank. Can someone help me with getting it connected in ubuntu? :confused:

a) did you turn on USB debugging on the device
b) OP linked an adb.exe replacement for Windows machines ( I had to do this trick to get it working on windows)... maybe it's a similar problems for ubuntu?
 
  • Like
Reactions: EnemyOfGlaDOS

MJHawaii

Senior Member
Aug 13, 2011
892
433
Honolulu, HI
www.androidhawaii.org
a) did you turn on USB debugging on the device
b) OP linked an adb.exe replacement for Windows machines ( I had to do this trick to get it working on windows)... maybe it's a similar problems for ubuntu?

Yes I do have Debugging on I am going to try to adb into fastboot manually then try to run it see if that works
BTW I am not sure where this .exe is that you referenced this is a cross platform executable JAR package so you can use it on WIN/LIN/MAC
 
Last edited:

paperWastage

Senior Member
Mar 18, 2009
1,000
496
NJ
  • Like
Reactions: MJHawaii

schif

Member
Sep 25, 2007
10
0
I have a bug on mac os x mountain lion:

http://pastebin.com/7NmL1DaP

TWRP: It will appear that you forget copy fastboot into the temp dir, i've added it manually to temp dir and work fine ;)
Root: not work:

Waiting for GUI...
installing SuperSU Authentication Controller
5222 KB/s (1468798 bytes in 0.274s)
Error: Could not access the Package Manager. Is the system running?
Error type 2
android.util.AndroidException: Can't connect to activity manager; is the system running?
at com.android.commands.am.Am.run(Am.java:100)
at com.android.commands.am.Am.main(Am.java:81)
at com.android.internal.os.RuntimeInit.nativeFinishInit(Native Method)
at com.android.internal.os.RuntimeInit.main(RuntimeInit.java:235)
at dalvik.system.NativeStart.main(Native Method)
 
Last edited:

HaTeNL

Senior Member
Aug 10, 2010
227
32
It does not work here, tried it on 2 computers. This is the log with error:
Code:
               rebooting device... please wait     
            Deploying Fastboot...     
            Fastboot deployed.     
            < waiting for device >      
            downloading 'boot.img'...      
            OKAY [  0.446s]      
            booting...      
            OKAY [  0.018s]      
            finished. total time: 0.464s      
            Booting insecure bootloader.. please wait     
            pushing files     
            3715 KB/s (380532 bytes in 0.100s)      
            rooting device     
            Setting permissions     
            Waiting for GUI...     
            installing SuperSU Authentication Controller      
            Error: Could not access the Package Manager.  Is the system running?       
            2386 KB/s (1468798 bytes in 0.601s)      
            Error type 2       
            android.util.AndroidException: Can't connect to activity manager; is the        system running?       
            	at com.android.commands.am.Am.run(Am.java:100)       
            	at com.android.commands.am.Am.main(Am.java:81)       
            	at com.android.internal.os.RuntimeInit.nativeFinishInit(Native Method)       
            	at com.android.internal.os.RuntimeInit.main(RuntimeInit.java:235)       
            	at dalvik.system.NativeStart.main(Native Method)       
            acct       
            at.rle       
            cache       
            config       
            d       
            data       
            default.prop       
            dev       
            etc       
            factorylogo.rle       
            fastboot.rle       
            firmware       
            fstab.qcom       
            init       
            init.at.rc       
            init.goldfish.rc       
            init.oppo.usb.rc       
            init.qcom.class_core.sh       
            init.qcom.class_main.sh       
            init.qcom.rc       
            init.qcom.sh       
            init.qcom.usb.sh       
            init.rc       
            init.rf.rc       
            init.target.rc       
            init.trace.rc       
            init.usb.rc       
            initlogo.rle       
            mnt       
            persist       
            proc       
            root       
            sbin       
            sdcard       
            storage       
            sys       
            system       
            tombstones       
            tpupdate.rle       
            ueventd.goldfish.rc       
            ueventd.qcom.rc       
            ueventd.rc       
            vendor       
            wlan.rle       
            Root was sucessful!  Please reboot your device to get out of insecure        mode.  You are now rooted!     
            done
 

AdamOutler

Retired Senior Recognized Developer
Feb 18, 2011
5,224
9,827
Miami, Fl̨̞̲̟̦̀̈̃͛҃҅͟orida
It does not work here, tried it on 2 computers. This is the log with error:
Code:
               rebooting device... please wait     
            Deploying Fastboot...     
            Fastboot deployed.     
            < waiting for device >      
            downloading 'boot.img'...      
            OKAY [  0.446s]      
            booting...      
            OKAY [  0.018s]      
            finished. total time: 0.464s      
            Booting insecure bootloader.. please wait     
            pushing files     
            3715 KB/s (380532 bytes in 0.100s)      
            rooting device     
            Setting permissions     
            Waiting for GUI...     
            installing SuperSU Authentication Controller      
            Error: Could not access the Package Manager.  Is the system running?       
            2386 KB/s (1468798 bytes in 0.601s)      
            Error type 2       
            android.util.AndroidException: Can't connect to activity manager; is the        system running?       
            	at com.android.commands.am.Am.run(Am.java:100)       
            	at com.android.commands.am.Am.main(Am.java:81)       
            	at com.android.internal.os.RuntimeInit.nativeFinishInit(Native Method)       
            	at com.android.internal.os.RuntimeInit.main(RuntimeInit.java:235)       
            	at dalvik.system.NativeStart.main(Native Method)       
            acct       
            at.rle       
            cache       
            config       
            d       
            data       
            default.prop       
            dev       
            etc       
            factorylogo.rle       
            fastboot.rle       
            firmware       
            fstab.qcom       
            init       
            init.at.rc       
            init.goldfish.rc       
            init.oppo.usb.rc       
            init.qcom.class_core.sh       
            init.qcom.class_main.sh       
            init.qcom.rc       
            init.qcom.sh       
            init.qcom.usb.sh       
            init.rc       
            init.rf.rc       
            init.target.rc       
            init.trace.rc       
            init.usb.rc       
            initlogo.rle       
            mnt       
            persist       
            proc       
            root       
            sbin       
            sdcard       
            storage       
            sys       
            system       
            tombstones       
            tpupdate.rle       
            ueventd.goldfish.rc       
            ueventd.qcom.rc       
            ueventd.rc       
            vendor       
            wlan.rle       
            Root was sucessful!  Please reboot your device to get out of insecure        mode.  You are now rooted!     
            done

That's not the log. use Ctrl+L, then hit the pastebin button.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 33
    Introduction
    Here's a one-click root method for the Oppo Find 5. You can find source here: https://code.google.com/p/android-casual/source/browse/#svn/trunk/GUI/src/SCRIPTS

    The way this works is it will reboot your device into fastboot, boot a kernel, inject root and SuperSU(available on Android Market), set permissions, test itself and let you know if it passed or failed.

    CASUAL also provides an unroot option to remove root permissions. This can also be done from within SuperSu.


    Instructions
    • Open CASUAL with JAVA. Do you have Java?
    • Select which script you want (root or recovery_
    • Click the do-it button


    All scripts in CASUAL are automated. Simply click the button and it will "do it". If you are a windows user, please ensure you are using proper drivers.



    10z0d1d.png



    Download
    For nightly builds, click here: http://goo.im/devs/AdamOutler/OppoFind5

    Credits
    Thanks to Justin Case for whippin' up a unsecure kernel before I could do it.
    TWRP comes from kamma's thread here http://xdaforums.com/showthread.php?t=2147999


    About CASUAL
    CASUAL stands for Cross-platform ADB Scripting, Univeral Android Loader. CASUAL jar files are a wrapper for the CASUAL scripting language. CASUAL allows rapid and accurate deployment of hacks and exploits. CASUAL allows for automatic updating of its scripts via pushes to the SVN server at android-casual.googlecode.com. While I expect no problems at all, if at any time a serious problem is detected with the script, i can flip a kill switch to shut CASUAL downand you will be brought to a support page.... most likely here. This is intended to add a level of security so that you know this will be safe.
    3
    Just updated the first post. This now includes a recovery and I bumped the CASUAL up from R280 something to R416 There are alot of improvements.
    2
    If anyone on Windows is having problems... i have a potential solution. please try this.


    Download this file: http://d-h.st/em7
    rename "adbx-1031-stripped-windows.exe" to "adb.exe"
    open the CASUAL jar file with WinZip or equivalent.
    navigate to CASUAL/resources/ADB in the jar.
    Replace adb.exe with the downloaded "adb.exe"
    run CASUAL again.

    let me know if this works or not.
    2
    International firmware released:
    http://www.oppoforums.com/threads/find-5-beta-firmware-x909en_13_130206.563/#post-10744

    I suppose, CASUAL also works with it, right?
    2
    EDIT :actually, info better posted on a separate thread (as this thread is for rooting the phone)

    http://xdaforums.com/showpost.php?p=37684053&postcount=32