Database Users

about Ouya Toolbox 1.0 - Ouya General

creator says it doesn't work on windows 8. I can confirm the root feature and the two install features DID work for me. NO PROBLEM. Thank you! i could not post in the thread i hope maybe a mod can merge my post to that or something. (my post count wont let me post there). You just need to make sure you install the drivers with DEO (Driver Enforcement Override) after editing the Ouya lines. Then boot back to normal windows. Thanks to the creator of Ouya Tool Box im further than I was with his help than i was on my own . Creator: foil and gratitude to the other devs that also participated to make Ouya Tool Box real

m03m1x said:
creator says it doesn't work on windows 8. I can confirm the root feature and the two install features DID work for me. NO PROBLEM. Thank you! i could not post in the thread i hope maybe a mod can merge my post to that or something. (my post count wont let me post there). You just need to make sure you install the drivers with DEO (Driver Enforcement Override) after editing the Ouya lines. Then boot back to normal windows. Thanks to the creator of Ouya Tool Box im further than I was with his help than i was on my own . Creator: foil and gratitude to the other devs that also participated to make Ouya Tool Box real
Click to expand...
Click to collapse
i Can't post in that threat but when i click on Root it says that my ouya is rooted, after install supersu and busybox it seems that i don't have root privileges.

Passing this along from the General tab for those of you with Windows 8:
m03m1x said:
creator says it doesn't work on windows 8. I can confirm the root feature and the two install features DID work for me. NO PROBLEM. Thank you! i could not post in the thread i hope maybe a mod can merge my post to that or something. (my post count wont let me post there). You just need to make sure you install the drivers with DEO (Driver Enforcement Override) after editing the Ouya lines. Then boot back to normal windows. Thanks to the creator of Ouya Tool Box im further than I was with his help than i was on my own . Creator: foil and gratitude to the other devs that also participated to make Ouya Tool Box real
Click to expand...
Click to collapse
Sent from my OUYA Console using xda app-developers app

inch oilamgD
Oscar_david said:
Passing this along from the General tab for those of you with Windows 8:
Sent from my OUYA Console using xda app-developers app
Click to expand...
Click to collapse
My root didn't work with this app on windows 7

Libleir years
I have just figured out that i have screwed up my Su file, i will have to wait to another OTA update or sildeload actual firmware to install it again. Factory reset didn't help me

tonyeltriton said:
I have just figured out that i have screwed up my Su file, i will have to wait to another OTA update or sildeload actual firmware to install it again. Factory reset didn't help me
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2351782

tonyeltriton said:
i Can't post in that threat but when i click on Root it says that my ouya is rooted, after install supersu and busybox it seems that i don't have root privileges.
Click to expand...
Click to collapse
Just to confirm, do you then go into SU and BB and make sure they are activated?

dully79 said:
http://forum.xda-developers.com/showthread.php?t=2351782
Click to expand...
Click to collapse
twent4 said:
Just to confirm, do you then go into SU and BB and make sure they are activated?
Click to expand...
Click to collapse
My su file is listed, but if i open with a text editor it seems to by empty.
Su and BB are activated, when i open SuperSu and choose install i get the message"there was an error installing Superuser".

tonyeltriton said:
My su file is listed, but if i open with a text editor it seems to by empty.
Su and BB are activated, when i open SuperSu and choose install i get the message"there was an error installing Superuser".
Click to expand...
Click to collapse
Open a cms and type
adb shell
su
If it's granted then you have su.
Try manually updating just the su binary using the method provided in the dev forum, then try to install super user again.

dully79 said:
Open a cms and type
adb shell
su
If it's granted then you have su.
Try manually updating just the su binary using the method provided in the dev forum, then try to install super user again.
Click to expand...
Click to collapse
shouldn't i get a " # ", when i type su in shell? Nothing appears when i type su:
[email protected]:/ $ su
su
[email protected]:/ $
If i try to start again step by step the installation of Superuser, Su binaries and busybox this is what i get when i type these command:
[email protected]:/ $ su
su
[email protected]:/ $ mount -o rw,remount -t ext4 /dev/block/platform/sdhci-tegra.3/
by-name/APP
ev/block/platform/sdhci-tegra.3/by-name/APP <
mount: Operation not permitted
255|[email protected]:/ $

tonyeltriton said:
shouldn't i get a " # ", when i type su in shell? Nothing appears when i type su:
[email protected]:/ $ su
su
[email protected]:/ $
If i try to start again step by step the installation of Superuser, Su binaries and busybox this is what i get when i type these command:
[email protected]:/ $ su
su
[email protected]:/ $ mount -o rw,remount -t ext4 /dev/block/platform/sdhci-tegra.3/
by-name/APP
ev/block/platform/sdhci-tegra.3/by-name/APP <
mount: Operation not permitted
255|[email protected]:/ $
Click to expand...
Click to collapse
Then you have lost su, you just have a ghost file in your folder. You need to re-install the official firmware with the method i linked you.
I can guarantee it works as i purposely deleted su from bin and xbin to test the method.
Feel free to post on my thread and leave this on topic.

tonyeltriton said:
I have just figured out that i have screwed up my Su file, i will have to wait to another OTA update or sildeload actual firmware to install it again. Factory reset didn't help me
Click to expand...
Click to collapse
Try the new Ouya ToolBox version 1.1 that I've uploaded, it should push the correct SU file into your Ouya and take care of it.

foil said:
Try the new Ouya ToolBox version 1.1 that I've uploaded, it should push the correct SU file into your Ouya and take care of it.
Click to expand...
Click to collapse
Hi,
I have the same problem on 1.1. It says it has done it, but when I´ve tried to run superuser on the ouya and select "Install" (NOT install from recovery!) from the options I got an error that says "there was an error installing Superuser. Please send a log of the error to the developer". Unfortunately the log is blank.
Any advice?
Thanks very much for your work, I´m looking forward to making it work!

tonyeltriton said:
My root didn't work with this app on windows 7
Click to expand...
Click to collapse
mine either says access to adb.exe denied very frustrating tried task manager method but when i hit root it says adb is out of date and blinks cmd screens then i close and try again and again plz help
Sent from my N861 using xda app-developers app
---------- Post added at 07:01 PM ---------- Previous post was at 06:14 PM ----------
I keep getting adb.exe denied it just blinks cmd screens and i caught a glimpse of one and it said su exec failed im using toolbox 1.1
Sent from my N861 using xda app-developers app
---------- Post added at 07:08 PM ---------- Previous post was at 07:01 PM ----------
Can u give me a list of everything i need before running this toolbox? I have ADT sdk manager google driver is there more that i need because ive been at this since yesterday. im forum camping lol. havent been to sleep just slaving over this going on 15 hours
Sent from my N861 using xda app-developers app

superfly2hi2die said:
mine either says access to adb.exe denied very frustrating tried task manager method but when i hit root it says adb is out of date and blinks cmd screens then i close and try again and again plz help
Sent from my N861 using xda app-developers app
---------- Post added at 07:01 PM ---------- Previous post was at 06:14 PM ----------
I keep getting adb.exe denied it just blinks cmd screens and i caught a glimpse of one and it said su exec failed im using toolbox 1.1
Sent from my N861 using xda app-developers app
---------- Post added at 07:08 PM ---------- Previous post was at 07:01 PM ----------
Can u give me a list of everything i need before running this toolbox? I have ADT sdk manager google driver is there more that i need because ive been at this since yesterday. im forum camping lol. havent been to sleep just slaving over this going on 15 hours
Sent from my N861 using xda app-developers app
Click to expand...
Click to collapse
Try the new version 1.1.1 that I just uploaded. All problems should be fixed now.

Great, I will test the new version as soon as I go back from work. I let you know if it works.
Thanks for your awesome work!

Hi F0il,
Unfortunately, version 1.1.1 doesn´t work for me at all. When I click on the application it does nothing. I don´t even see the popup saying it´s going to check for connected devices as 1.1 did, but the process is running in the background. I unpluged the ouya, I this error showed up (Don´t know if related
Code:
See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.
************** Exception Text **************
System.NullReferenceException: Object reference not set to an instance of an object.
at RegawMOD.Android.BatteryInfo.Update()
at RegawMOD.Android.Device.Update()
at RegawMOD.Android.AndroidController.GetConnectedDevice(String deviceSerial)
at OuyaToolbox.Form1.Form1_Load(Object sender, EventArgs e)
at System.EventHandler.Invoke(Object sender, EventArgs e)
at System.Windows.Forms.Form.OnLoad(EventArgs e)
at System.Windows.Forms.Form.OnCreateControl()
at System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible)
at System.Windows.Forms.Control.CreateControl()
at System.Windows.Forms.Control.WmShowWindow(Message& m)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ScrollableControl.WndProc(Message& m)
at System.Windows.Forms.Form.WmShowWindow(Message& m)
at System.Windows.Forms.Form.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
************** Loaded Assemblies **************
mscorlib
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.296 (RTMGDR.030319-2900)
CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll
----------------------------------------
OuyaToolbox
Assembly Version: 1.0.0.0
Win32 Version: 1.0.0.0
CodeBase: file:///C:/Users/casa/Desktop/OuyaToolBox_v1_1_1/OuyaToolbox.exe
----------------------------------------
Microsoft.VisualBasic
Assembly Version: 10.0.0.0
Win32 Version: 10.0.30319.1 built by: RTMRel
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/Microsoft.VisualBasic/v4.0_10.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dll
----------------------------------------
System
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.1001 built by: RTMGDR
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Core
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.233 built by: RTMGDR
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll
----------------------------------------
System.Windows.Forms
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.1002 built by: RTMGDR
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System.Drawing
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.1001 built by: RTMGDR
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
System.Runtime.Remoting
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.1 (RTMRel.030319-0100)
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Runtime.Remoting/v4.0_4.0.0.0__b77a5c561934e089/System.Runtime.Remoting.dll
----------------------------------------
AndroidLib
Assembly Version: 1.5.1.0
Win32 Version: 1.5.1.0
CodeBase: file:///C:/Users/casa/Desktop/OuyaToolBox_v1_1_1/AndroidLib.DLL
----------------------------------------
************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.
For example:
<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>
When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.
I used Win7 64bits

fenano said:
Hi F0il,
Unfortunately, version 1.1.1 doesn´t work for me at all. When I click on the application it does nothing. I don´t even see the popup saying it´s going to check for connected devices as 1.1 did, but the process is running in the background. I unpluged the ouya, I this error showed up (Don´t know if related
I used Win7 64bits
Click to expand...
Click to collapse
I'm wondering - do you have Microsoft .Net Framework version 4 installed?
I just ran it on 3 computers here at my shop, all on Windows 7 64bit, and I plugged in about 10 different Android devices, and each of them ran it perfectly.

foil said:
I'm wondering - do you have Microsoft .Net Framework version 4 installed?
I just ran it on 3 computers here at my shop, all on Windows 7 64bit, and I plugged in about 10 different Android devices, and each of them ran it perfectly.
Click to expand...
Click to collapse
Hi,
I had one program called .NET framework 4 client profile, don´t know if it´s the one.
Anyway, I downloaded and installed Microsoft .NET Framework 4 (Web Installer) from the Microsoft site, which I think it´s the good one, but no success (I rebooted the pc after installing it, just in case)

fenano said:
Hi,
I had one program called .NET framework 4 client profile, don´t know if it´s the one.
Anyway, I downloaded and installed Microsoft .NET Framework 4 (Web Installer) from the Microsoft site, which I think it´s the good one, but no success (I rebooted the pc after installing it, just in case)
Click to expand...
Click to collapse
Yeah, that's the one you need. Hmm...I'm really having a hard time figuring out what it could be that's throwing those exceptions that it's showing.
Try to run it in compatibility mode, like in this picture. I've got it on another computer at the shop right now, with a Motorola Droid Razr XT912 hooked up, and it's reading it perfectly fine, on Win7 64bit, again!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Edit: Also, are you able to communicate with the phone through ADB outside of my program?
ie: adb devices > XXXXXX (device id is displayed) ?

Related

Ok, so I'm going to make a little write up on how to easily install ADB and fastboot on a Mac. It's actually quite simple, and plus you don't have to worry about drivers like in Windows.
Instructions
First, make a folder named "android" (no quotes of course ) You can place it anywhere on your hard drive, it doesn't really matter. Put it somewhere you'll easily remember, because you're going to be using it a LOT. I placed mine on my desktop.
{
"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"
}
Next, you'll want to download the android SDK from Here. (you won't need to install Java first like you would on a Windows PC, though I would recommend it anyway)
(As pointed out by Wlmeng11, you could skip this step just download a zip that I will have attached at the bottom of the page containing the adb and fastboot files instead of downloading the whole SDK)
When the SDK finishes downloading, Unzip it and the contents of the "android-sdk-mac_x86" folder into your android folder.
Once you have done that, open your android folder. Go into the tools folder inside of it. Double click on the file called "android" (possibly called android sdk) This file is a UNIX executable and will open within a Terminal window.
When it finishes opening, check the folder called tools. Make sure both "Android SDK Tools" and "Android SDK Platform-tools" are selected within the tools folder. Click install and wait for them to download.
When they finish downloading, go into the platform-tools folder inside your android folder, then copy adb and fastboot and paste them into the root of your android folder.
Now that you have adb and fastboot installed, we're going to want to test them to make sure they work.
Go ahead and plug in your android device at this time. Make sure android debugging is enabled in settings. Go into Settings > Apps > Developer and check it there (for Gingerbread 2.3 and lower) or go into Settings > Developer Options and check it there for Ice Cream Sandwich or Jellybean. As of now, there are two ways to access adb and fastboot.
Open a Terminal window (look in Applications > Utilities if you can't find it). Type "cd" followed by the path you saved your android folder to (I'm going to use the Desktop for this demonstration) it should look like this
Code:
cd /Users/<yourusername>/Desktop/android
Press enter.
Now you need to actually execute an adb or fastboot command. To do this, you'll need to type "./adb (or fastboot) <command>" For this tutorial, we will use "ADB devices" since it doesn't actually do anything to the phone. (we won't use fastboot since it requires rebooting to the boot loader which is different for every device)
In the same terminal window as before type the following:
Code:
./adb devices
then hit enter. It should turn up your device's serial number. If it does, proceed to the next step, if not recheck your steps, then leave a post in this thread.
(if it says * daemon not running. starting it now on port 5037 *
* daemon started successfully * that is perfectly normal)
Now, at this moment, ADB and Fastboot are both completely useable. However, it's very annoying to have to CD into the directory and use ./ in front of every terminal command. I'll show you how to add it to your path so you don't have to do any of that.
Open a new Terminal window and type
Code:
nano ~/.bash_profile
it will open a window that looks like this:
(Yours will probably be blank, because I've added a lot of stuff to mine over the years)
Add a line to it that contains the path to your android folder. (again, I'm using Desktop) It should look like this
Code:
export PATH=${PATH}:/Users/<yourusername>/Desktop/android
Once you have added that, press CTRL+X to exit, then Y to confirm the save then press enter. It will close the nano editor. You can close the Terminal window now.
Now we need to verify that it works. Open a new Terminal window and type
Code:
adb devices
If it shows the serial number, then you have set it up successfully and are good to go!
If you have any questions or issues let me know in the thread below.
If this has helped, please press thanks!
Awesome! This made the front page of XDA Thanks guys!​

Added screenshots

you won't need to install Java first like you would on a PC
Click to expand...
Click to collapse
So... Macs are Impersonal Computers?
---------- Post added at 06:24 PM ---------- Previous post was at 06:17 PM ----------
Nice guide though btw

wlmeng11 said:
So... Macs are Impersonal Computers?
---------- Post added at 06:24 PM ---------- Previous post was at 06:17 PM ----------
Nice guide though btw
Click to expand...
Click to collapse
Lol I'll fix that. Thanks btw. I'm out today, but I'll give you one tomorrow (too lazy to use my phone)

To save time, you might want to just have a adb/fastboot combo instead of the entire sdk.
(BTW it's tomorrow )
Sent from my HTC Rezound

wlmeng11 said:
To save time, you might want to just have a adb/fastboot combo instead of the entire sdk.
(BTW it's tomorrow )
Sent from my HTC Rezound
Click to expand...
Click to collapse
Maybe, I actually use other parts of the SDK . Ill look into that though

AshtonTS said:
Maybe, I actually use other parts of the SDK . Ill look into that though
Click to expand...
Click to collapse
Well since this guide is primarily aimed towards users who only want to root their phone, rather than developers, adb/fastboot is really all you need.
So it would save time to just use an adb/fastboot combo.

I still prefer linux
I still prefer the linux enviroment, although its handy to have the adb on my macbook for when I'm not at home and have bricked my device :S
I had already got this setup, I just didn't know the ~/.bash_profile bit Now I know had to add my own programs as actual programs and not just aliases XD

First off, nice guide. I am still trying to understand why you've moved adb and fastboot from platform-tools, rather than export the path to that directory. Is there any particular reason?
EDIT: BTW, you've hit the front page on XDA.

Hi.
Would it be valid on a very old Powerbook Pismo running 10.4 Tiger??
Thanks in advance and regards.

wlmeng11 said:
Well since this guide is primarily aimed towards users who only want to root their phone, rather than developers, adb/fastboot is really all you need.
So it would save time to just use an adb/fastboot combo.
Click to expand...
Click to collapse
Indeed, though this method allows you to update your adb and fastboot via Android SDK Manager (ASM). Also, in cases where all you need is adb and fastboot, you can speed up future update checks by going to "Tools"->"Manage Add-on Sites..." in ASM and click on "Disable All" button in "Official Add-on Sites" tab. From there on Android SDK Manager will check only the default repository containing tools and APIs.

visor said:
First off, nice guide. I am still trying to understand why you've moved adb and fastboot from platform-tools, rather than export the path to that directory. Is there any particular reason?
EDIT: BTW, you've hit the front page on XDA.
Click to expand...
Click to collapse
It could be done that way, but I personally put other stuff in the android folder on my Mac, and also it's a bit quicker to just drag a file into one folder on your desktop than into a folder within a folder

straycat said:
Hi.
Would it be valid on a very old Powerbook Pismo running 10.4 Tiger??
Thanks in advance and regards.
Click to expand...
Click to collapse
You won't be able to install the SDK, but you can extract the android.zip to a folder named android on your desktop or wherever and use that in place of the SDK step

AshtonTS said:
You bet! this will work on any mac running any OS X (unless Google blocks the install of the SDK, but I have a way around that.
Click to expand...
Click to collapse
Actually, that's a PowerPC Mac, so Intel OSX software will not work.
There is no official support for PowerPC that I know of, but someone on XDA did make binaries for PowerPC.
Sent from my HTC Rezound
Edit: yup, official sdk is x86 only.
BTW, here's the link to the ported binaries.
http://forum.xda-developers.com/showthread.php?t=898744

So many graces, this thing has saved the life because I have not a PC windows, thank you still

varanhia said:
So many graces, this thing has saved the life because I have not a PC windows, thank you still
Click to expand...
Click to collapse
Glad it worked for you

Hi,
Thank you very much. Worked like a charm.
Regards,

Awesome thread. Thanks for taking out the time

DarkSorcerer said:
Hi,
Thank you very much. Worked like a charm.
Regards,
Click to expand...
Click to collapse
nigameash said:
Awesome thread. Thanks for taking out the time
Click to expand...
Click to collapse
Glad it helped you two
Sent from my HTC Sensation

Hi thanks so much for this. Ive been wanting something like this for months/ almost a year.
All the other guides didnt work for me, but this was simple and easy to follow.
Ive encountered one problem and its device specific. My nexus 7 tablet works great with adb, but my htc evo 4g lte doesnt. its rooted, and running cm 10 4.1.2. its debugged any idea how to make it see the device?
UPDATE. so i turned on my usb storage on the device and it now sees the phone. Great work!!!!
Am i going to have to connect storage to mac all the time for this to work on any device?

I'm not responsible of
bootloops
dead sdcard
overheating
success
device suicide
anything else
Click to expand...
Click to collapse
everything in here became obsolete, you still can use but now there's an better way to do it
here's the link for flashfire thanks to @Chainfire
here's the link for xposed for lollipop thanks to @rovo89
download the sdk 21 arm version
just download the xposed zip and the flashfire
and use flashfire to flash the zip
it takes around 8 minutes to flash on our device but works
the old way to do it is here:
I found some files on google from a guy called "Nodis" that promised to install xposed on lollipop
yay
they worked?
No.
:crying:
but I followed the script manually and then...
yes xposed on lollipop working
Let's start
You'll need:
Code:
d690n (but mine is using d693n rom)
Root
busybox
Some app to unninstall system apps
Working adb
SeLinuxModeChanger
usb debugging enabled
the files from here
Luck
Let's begin
uninstall lg quick view app (it'll be force closing continuously)
download the CantRecoverv4 file attached in here
extract to desktop or the place you want
open cmd (or bash for linux) in the xposed folder that you extracted
a good way for do this is open the folder, hold shift, right mouse click and click open command window here
{
"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"
}
type the following commands and then press enter to execute
Code:
adb push system /data/local/tmp/system
Code:
adb push installer /data/local/tmp
Code:
adb shell
in the adb shell type
Code:
su
in the su shell
Code:
chmod 755 /data/local/tmp/installer
and
Code:
/data/local/tmp/installer
it's really important to follow the order.
then install XposedInstaller_3.0-alpha4.apk
just open the xposedapp.bat and it will (should) install xposed app.
I've noticed that if you install SeLinuxModeChanger from @MrBIMC some blocked mods start working
So download the app here, install and set it to permissive.
reboot your device.
now xposed is probably working (worked for me)
MAYBE it'll work for other lollipop device without recovery
thanks if i helped.
If you have any questions ask in here and if I can help I'll do.
if the real author of this isn't the guy Mentioned contact me and I'll add your credits
thanks to @MrBIMC for SeLinuxModeChanger
Screenshots:
Reported working list:
D690
D693n
Xperia ZR

Can you Help me ?
gkillershots said:
Let's begin
uninstall lg quick view app (it'll be force closing continuously)
download the files attached in here
extract to desktop or the place you want
open cmd (or bash for linux) in the xposed folder that you extracted
type the following commands and then press enter to execute
Code:
push system /data/local/tmp/system
Code:
push installer /data/local/tmp
Code:
adb shell
in the adb shell type
Code:
su
in the su shell
Code:
chmod 755 /data/local/tmp/installer
and
Code:
/data/local/tmp/installer
it's really important to follow the order.
then install XposedInstaller_3.0-alpha2.apk
reboot your device.
now xposed is probably working (worked for me)
MAYBE it'll work for other lollipop device without recovery
thanks if i helped.
If you have any questions ask in here and if I can help I'll do.
if the real author of this isn't the guy Mentioned contact me and I'll add your credits
Click to expand...
Click to collapse
where I have to put the files ? here it seems "not found" im using "terminal emulator for android" and my g3 stylus is d690n with lollipop 5.0.2

V2power said:
where I have to put the files ? here it seems "not found" im using "terminal emulator for android" and my g3 stylus is d690n with lollipop 5.0.2
Click to expand...
Click to collapse
don't use terminal emulator, use adb. do you want me the tuto to setup adb?

gkillershots said:
don't use terminal emulator, use adb. do you want me the tuto to setup adb?
Click to expand...
Click to collapse
ohh thanks bro, i never used adb, but now i know how to use and i never heard of it i go try.

OW NICE !! Thanks man i finally got i,now i have xposed,thx
Sorry for my bad english

V2power said:
OW NICE !! Thanks man i finally got i,now i have xposed,thx
Sorry for my bad english
Click to expand...
Click to collapse
no problem, I'm brazilian too and please hit thanks if I helped

Hi OP,
I followed all you instructions and at the end my Xposed Installer shows.....
"Installation is only possible manually via recovery for now"
Please help.

Sunil Jagtap said:
Hi OP,
I followed all you instructions and at the end my Xposed Installer shows.....
"Installation is only possible manually via recovery for now"
Please help.
Click to expand...
Click to collapse
even if xposed is working he shows this message, just look if there are green numbers under active.
if it has, try some module because it may be working
in one of my screenshots you can see what i'm saying.

gkillershots said:
even if xposed is working he shows this message, just look if there are green numbers under active.
if it has, try some module because it may be working
in one of my screenshots you can see what i'm saying.
Click to expand...
Click to collapse
Thanks Gkillershots,
The xposed is now active, but it dont looks like other mobile. sorry OP, i dont know first.
I check modules G3 tweak but its not fully supportive do you know any modules like X Blast or Wannam for Our D690 only rooted.
Thanks in advance.

Sunil Jagtap said:
Thanks Gkillershots,
The xposed is now active, but it dont looks like other mobile. sorry OP, i dont know first.
I check modules G3 tweak but its not fully supportive do you know any modules like X Blast or Wannam for Our D690 only rooted.
Thanks in advance.
Click to expand...
Click to collapse
many modules aren't working, check if you are using the new g3 tweaksbox and use the new gravitybox lp too, because they complements each other.
and the selinux mode changer can make some things work too.

gkillershots said:
many modules aren't working, check if you are using the new g3 tweaksbox and use the new gravitybox lp too, because they complements each other.
and the selinux mode changer can make some things work too.
Click to expand...
Click to collapse
Thanks for your reply,
I have tried all kind of modules but non of theme support fully,
g3 tweaksbox only make some changes in ui but no satisfactory result
Gravitybox dont support our D690
is there any fully supportive module in your knowledge which gives me satisfactory result

Hxnter said:
Wow dude, I can't believe you made Xposed wihout recovery
I'm gonna try this out soon as I get my phone back
Click to expand...
Click to collapse
Thanks Pal!!! Work for my Xperia ZR Lollipop!!!

Sunil Jagtap said:
Thanks for your reply,
I have tried all kind of modules but non of theme support fully,
g3 tweaksbox only make some changes in ui but no satisfactory result
Gravitybox dont support our D690
is there any fully supportive module in your knowledge which gives me satisfactory result
Click to expand...
Click to collapse
i know but some tweaks works.
search for layers manager on google play store or in here. it's a new lollipop theme engine and it works on my g3
but it's not xposed

shenlong85 said:
Thanks Pal!!! Work for my Xperia ZR Lollipop!!!
Click to expand...
Click to collapse
thanks for the report

Al ejecutar el primer codigo me aparece
Error: device not found no me explico por que soy root. La depuracion usb esta activa que falla?

How do I uninstall it if I installed framework with this method?

Dereklop said:
Al ejecutar el primer codigo me aparece
Error: device not found no me explico por que soy root. La depuracion usb esta activa que falla?
Click to expand...
Click to collapse
Try Installing the drivers

irsal226dunkz said:
How do I uninstall it if I installed framework with this method?
Click to expand...
Click to collapse
I recommend you re-flashing the stock rom because it's a lot easier

Do I have to uninstall the quick view app with the new method? If so, can I install it again later? Or should I totally ignore the old method?

the-careta said:
Do I have to uninstall the quick view app with the new method? If so, can I install it again later? Or should I totally ignore the old method?
Click to expand...
Click to collapse
totally ignore the old method, just download the newest xposed zip for our phone (sdk21 armv7) then flash it via flashfire
no need to uninstall quickview

I wanted to help develop root for my and anybody else's LG Stylo 2. I'm ready to help in almost any way possible. Attached is my info. Let me know if anything can be done or if development has started.
{
"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"
}

Cant wait for permanent root. things i have learned about this phone is it can be temporary rooted with kingroot 4.9.6 things i have been able to do with temp root are remove bloat, install busybox and I use Lspeed tweeks. You can softboot without losing root also if you power down you phone then hold power + volume down it will boot into recovery mode there is a option to apply a update through adb or any basic adb commands and if you go to the option in recovery to to boot to bootloader that will put your phone in fastboot mode. Also if you power your phone down and hold volume up while plugging in your phone to the power cord via wall plug or computer it will boot into download mode i believe that is for flashing our .kdz firmware files thru lg flasher program for pc but have yet to find a firmware file for the LGLS775. those are the only things i have found and contribute thus far. good luck and god speed. Oh also i believe if you can find a way to switch kingroot with supersu without having to reboot and lose root then we should be able to use (Root) Flash Fire to possibly flash a updated supersu binary and hopefully keep root I know that flash fire needs supersu binaries or it wont work it wont even recognize root with kingroot.

DirtyPISTOLA said:
Cant wait for permanent root. things i have learned about this phone is it can be temporary rooted with kingroot 4.9.6 things i have been able to do with temp root are remove bloat, install busybox and I use Lspeed tweeks. You can softboot without losing root also if you power down you phone then hold power + volume down it will boot into recovery mode there is a option to apply a update through adb or any basic adb commands and if you go to the option in recovery to to boot to bootloader that will put your phone in fastboot mode. Also if you power your phone down and hold volume up while plugging in your phone to the power cord via wall plug or computer it will boot into download mode i believe that is for flashing our .kdz firmware files thru lg flasher program for pc but have yet to find a firmware file for the LGLS775. those are the only things i have found and contribute thus far. good luck and god speed. Oh also i believe if you can find a way to switch kingroot with supersu without having to reboot and lose root then we should be able to use (Root) Flash Fire to possibly flash a updated supersu binary and hopefully keep root I know that flash fire needs supersu binaries or it wont work it wont even recognize root with kingroot.
Click to expand...
Click to collapse
I tried another method for fastboot. But nothing.....is there anything that you can recommend?

JOKERx2 said:
I tried another method for fastboot. But nothing.....is there anything that you can recommend?
Click to expand...
Click to collapse
unfortunately not as of now I actually gave this phone to my sister in law and went to the ZTE Warp Elite 4G and the screen on that phone cracked in my pocket like the 2nd day I bought it and now on the Samsung Galaxy J7 but my wife is still using the ver4 of the stylo 2 Ill mess around with it here or there and if i find something ill let you guys know for sure.

please need stock filmware ls775zv5

ltindi32 said:
please need stock filmware ls775zv5
Click to expand...
Click to collapse
me too idk whats up with my phone im getting no notifications and my home and recent apps not working

temp 2 perm
JOKERx2 said:
I tried another method for fastboot. But nothing.....is there anything that you can recommend?
Click to expand...
Click to collapse
I believe there are couple threads on XDA, one was even by a "Joker" username on switching cfChainfiresSuperSU out for Kingoroots temp root............
Once even temp root is obtained, Chainfires su can be pushed.........
Just thought 2 comment, looking at switching from my Samsung Galaxy J3 (2016) back to an LG. Had this one before but it had lollipop 5.1.1 and only 1gb of ram..........
zach

got something maybe
JOKERx2 said:
I wanted to help develop root for my and anybody else's LG Stylo 2. I'm ready to help in almost any way possible. Attached is my info. Let me know if anything can be done or if development has started.
Click to expand...
Click to collapse
I just bought this same exact phone yesterday at BestBuy because it was such a good price ($119), plus I thought a thread I was looking at on XDA was for it with twrp & root..........
Reason I'm writing you right now, is out of the box this phone has an update waiting to install that is 454.4mb, I'm pretty sure its the complete KDZ file.
Any idea how to get it off this phone??? Since this could be the break were looking for recovering from trying stuff out!!!!!!
I'll leave the phone like it is, for awhile...........
Hoping to get a response back soon
zach

You might need to PM the OP for options. But I do believe there is a way to get the file now
sent from Joker Stylos2

smile
DirtyPISTOLA said:
Cant wait for permanent root. things i have learned about this phone is it can be temporary rooted with kingroot 4.9.6 things i have been able to do with temp root are remove bloat, install busybox and I use Lspeed tweeks. You can softboot without losing root also if you power down you phone then hold power + volume down it will boot into recovery mode there is a option to apply a update through adb or any basic adb commands and if you go to the option in recovery to to boot to bootloader that will put your phone in fastboot mode. Also if you power your phone down and hold volume up while plugging in your phone to the power cord via wall plug or computer it will boot into download mode i believe that is for flashing our .kdz firmware files thru lg flasher program for pc but have yet to find a firmware file for the LGLS775. those are the only things i have found and contribute thus far. good luck and god speed. Oh also i believe if you can find a way to switch kingroot with supersu without having to reboot and lose root then we should be able to use (Root) Flash Fire to possibly flash a updated supersu binary and hopefully keep root I know that flash fire needs supersu binaries or it wont work it wont even recognize root with kingroot.
Click to expand...
Click to collapse
Would a kdz file help?
https://mega.nz/#!6BMlmIZB!CBKqxLvGl3c2EfYXj6_hIbdUKxPtbfWzgoglQb0d5aA
When I purchased my BOOST Stylo 2 two days ago, it had an update popped up not long after powering on.......
logcatted it, went through a bunch of URL's until one gave me a username/password popup, admin by itself with no password got the 454.4mb .zip downloaded!
http://imgur.com/q2dvC13
what it looks like unzipped.........
Hope this helps!!!!!!!
zach
---------- Post added at 07:10 PM ---------- Previous post was at 07:06 PM ----------
ltindi32 said:
please need stock filmware ls775zv5
Click to expand...
Click to collapse
I just purchased my LGLS775, 6.0.1, update out of box popped up and I captured it. Phone says software version is ZV4 but with the update????
I'm no expert on this, why I'm in this forum with the kdz...............
heres the link in case it will help:
https://mega.nz/#!6BMlmIZB!CBKqxLvGl3c2EfYXj6_hIbdUKxPtbfWzgoglQb0d5aA
let me know........
zach

O'tay, if anyones interested. BOOST Stylo 2, same specs that Joker put up. I have 1.02gb kdz, LGUP recognizes it in download mode, still says it can't open it...........
Got Terminal script to replace Kingroot's temp root with SuperSU but I issz not gonna go a step further until I know I can flash this bad boy when the going gets rough................
Any ideas, hello????
Did everyone toss their Stylo 2's on the heap?
jeez
zach

Ok, so the update was ZV5, but in theory now that I have the LG OTA cert, I might be able to possibly package SuperSU in it. It depends on LG's update checking, some manufacturers just check the cert, others check the sum of the package, so I'll see what the case is with LG.
---------- Post added at 06:52 AM ---------- Previous post was at 06:44 AM ----------
Ok, so apparently, they are checking some footer that doesn't match, so a no go there.
---------- Post added at 06:53 AM ---------- Previous post was at 06:52 AM ----------
I wonder if I replace their aboot with a modified kernel and update the signatures if it would install.

https://mega.nz/#!LFlBRAhS!rDl7PJMkFq7HqUDDgbKV6ddv-C3qkQIJl_CJkhkx2sc
Dirtycow exploit, ADB folder with the adb/fastboot, .bat & .dll's, either replace whats in your folder with the included or for those without refer how to setup and just place this under your OS C: directory and cd c:\adb in command screen to get there! control+shift keys before, as you click on cmd screen will open as admin. Includes Drammer.apk, if your ZV4 or ZV5.... Rock & Roll!!!... I'm ZV6 but I believe running this along with Drammer taxing the processor allowed my Kingroot (included in dwnld, BETA ver.) to achieve root, even if only temporarily, it lost it by the time I picked phone up @ 1:33am this morning but still allowing me to attempt to fix "root auth" over & over.........
Happy Holidays
Not responsible for bricks or burnt turkeys!
zach
thanks to slickrick for putting the binaries and commands together off github, and to messi2050 who has TWRP built and waiting for the LG Stylo 2 (not the plus the LGLS775ABB)

coolbeans2016 said:
https://mega.nz/#!LFlBRAhS!rDl7PJMkFq7HqUDDgbKV6ddv-C3qkQIJl_CJkhkx2sc
Dirtycow exploit, ADB folder with the adb/fastboot, .bat & .dll's, either replace whats in your folder with the included or for those without refer how to setup and just place this under your OS C: directory and cd c:\adb in command screen to get there! control+shift keys before, as you click on cmd screen will open as admin. Includes Drammer.apk, if your ZV4 or ZV5.... Rock & Roll!!!... I'm ZV6 but I believe running this along with Drammer taxing the processor allowed my Kingroot (included in dwnld, BETA ver.) to achieve root, even if only temporarily, it lost it by the time I picked phone up @ 1:33am this morning but still allowing me to attempt to fix "root auth" over & over.........
Happy Holidays
Not responsible for bricks or burnt turkeys!
zach
thanks to slickrick for putting the binaries and commands together off github, and to messi2050 who has TWRP built and waiting for the LG Stylo 2 (not the plus the LGLS775ABB)
Click to expand...
Click to collapse
[email protected]:/ $ run-as -exec id
run-as -exec id
Current uid: 2000
Setting capabilities
Attempting to escalate to root
Current uid: 0
Executing: 'id' with 0 arguments
uid=0(root) gid=0(root) groups=0(root),1004(input),1007(log),1011(adb),1015(sdcard_rw),1028(sdcard_r),3001(net_bt_admin),3002(net_bt),3003(inet),3006(net_bw_stats) context=u:r:runas:s0
[email protected]:/ $ run-as -exec sh
run-as -exec sh
Current uid: 2000
Setting capabilities
Attempting to escalate to root
Current uid: 0
Executing: 'sh' with 0 arguments
Failed to execute 'sh'!
1|[email protected]:/ $ chmod 0777 /system/bin/sh
chmod 0777 /system/bin/sh
chmod: chmod '/system/bin/sh' to 100777: Read-only file system
1|[email protected]:/ $
im LS775ZV5 trying to get root so I can hopefully use shortcut master lite to access hidden menu to bring up unlock menu to enter the unlock code I brought...

patched
mrw187 said:
[email protected]:/ $ run-as -exec id
run-as -exec id
Current uid: 2000
Setting capabilities
Attempting to escalate to root
Current uid: 0
Executing: 'id' with 0 arguments
uid=0(root) gid=0(root) groups=0(root),1004(input),1007(log),1011(adb),1015(sdcard_rw),1028(sdcard_r),3001(net_bt_admin),3002(net_bt),3003(inet),3006(net_bw_stats) context=u:r:runas:s0
[email protected]:/ $ run-as -exec sh
run-as -exec sh
Current uid: 2000
Setting capabilities
Attempting to escalate to root
Current uid: 0
Executing: 'sh' with 0 arguments
Failed to execute 'sh'!
1|[email protected]:/ $ chmod 0777 /system/bin/sh
chmod 0777 /system/bin/sh
chmod: chmod '/system/bin/sh' to 100777: Read-only file system
1|[email protected]:/ $
im LS775ZV5 trying to get root so I can hopefully use shortcut master lite to access hidden menu to bring up unlock menu to enter the unlock code I brought...
Click to expand...
Click to collapse
not sure what versions after ZV3 are for which xploit patches...... but if you are ZV5 & getting this return (read-only) when executing the dirtycow xploit, it means ZV5 has that xploit patched....
& at this time, it was the last available xploit to get root.........
so........
waiting game

A little late to the party, but I just got this phone as a replacement and so far am loving it. I always had root, so I hope we can find a way soon. I'm on v4, are you guys saying temp root is possible via king root v4.96?
Ouch, never mind I'm on v5 no exploits?
Sent from my LGLS775 using Tapatalk

coolbeans2016 said:
not sure what versions after ZV3 are for which xploit patches...... but if you are ZV5 & getting this return (read-only) when executing the dirtycow xploit, it means ZV5 has that xploit patched....
& at this time, it was the last available xploit to get root.........
so........
waiting game
Click to expand...
Click to collapse
Hey guys, happy new to all. I just got this phone but bought a BOOST version instead of a VIrgin mobile version by mistake. I have had it SIM GSM unlocked yet cannot enable APN settings. I am on V3 of software. Any one have full V4 KDZ or at least how to enable APN configuration? Thanks!

keep ZV3!!!!!
luisitox22 said:
Hey guys, happy new to all. I just got this phone but bought a BOOST version instead of a VIrgin mobile version by mistake. I have had it SIM GSM unlocked yet cannot enable APN settings. I am on V3 of software. Any one have full V4 KDZ or at least how to enable APN configuration? Thanks!
Click to expand...
Click to collapse
If you want root & TWRP DON'T TAKE THE UPDATES
ALSO DO NOT USE KINGROOT VER. 4.6, USE 5.0 BETA (or 4.9)
zach

coolbeans2016 said:
If you want root & TWRP DON'T TAKE THE UPDATES
ALSO DO NOT USE KINGROOT VER. 4.6, USE 5.0 BETA (or 4.9)
zach
Click to expand...
Click to collapse
Thanks for the reply bro. Unfortunately, I miss read instructions in another thread and took a small update that took me to v6. Is it possible to downgrade?
Thanks?

nope
luisitox22 said:
Thanks for the reply bro. Unfortunately, I miss read instructions in another thread and took a small update that took me to v6. Is it possible to downgrade?
Thanks?
Click to expand...
Click to collapse
Your now the proud owner of the MOST undevelopable device known to man....

Hey guys, recently a member from Discord channel (ikkun) showed me steps on how to root Phoenix OS by just placing the su binary in the system folder. This method is so much easier and convenient than replacing the system.img, that it should be the main way to root your Phoenix OS installation.
Advantages:
No need to wait to download and extract a 500MB system.img. Instead, download a 5MB .zip file
No need to do a fresh install. You can root an existing installation without removing all your data.
Play store and Google Calendar sync work
Tested and works with:
v2.2.0 64-bit
v2.2.1 64-bit
v2.5.0 64-bit
v2.5.3.64 64-bit
v2.5.7.348 64-bit (Tested myself)
(Probably works on your system too. Why not test it and post your results below?)
Instructions:
Download and extract the .zip file. For the purposes of the tutorial, I'm going to assume that you extract it in the Download folder and rename the SuperSU folder to su. Inside su, you should see META-INF, x64, x86, etc folders.
{
"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"
}
Open the terminal by pressing Alt+F1
If you have Phoenix OS 32-bit, type in these commands:
Code:
cd /system/xbin
mv su su.orig
cp /sdcard/Download/su/x86/[B]su.pie[/B] su
chmod 4751 su
su --install
su --daemon
If you have Phoenix OS 64-bit, type in these commands:
Code:
cd /system/xbin
mv su su.orig
cp /sdcard/Download/su/x64/[B]su[/B] [B].[/B]
chmod 4751 su
su --install
su --daemon
This screenshot is for 64-bit:
Note 1:
If after typing in the mv su su.orig command, you get an error saying:
mv: rename su to su.orig: No such file or directory
Click to expand...
Click to collapse
That means your Phoenix OS installation does not come with the su binary. Skip the mv command and proceed to the next step since there is nothing to make a backup of.
I usually install my Phoenix OS using the .exe installer and always see the su file in that folder during the rooting process so I never see this error. It was never clear to me why people are missing the su binary, but my observations tell me it could be because people are installing it using the ISO file or using 32-bit. I never had the opportunity to test this out, but if you have this error, please post your Phoenix OS version, architecture, and installation method.
Click to expand...
Click to collapse
Note 2:
Make sure you type in the commands exactly as provided. I saw other people were having trouble because they typed in the command incorrectly; they were missing a period after a space. It should be with a period and a space after the command (if you're rooting x64):
Code:
cp /sdcard/Download/su/x64/su [B].[/B]
and not:
Code:
cp /sdcard/Download/su/x64/su
The dot simply tells the cp command to place the file in the working directory (which was set earlier by the cd /system/xbin command). Alternatively, you can replace the dot with the current directory, the new command being:
Code:
cp /sdcard/Download/su/x64/su /system/xbin
It's just easier to type a dot then type out the whole directory, especially considering the fact that you can't copy-paste in the terminal (as far as I know, could be wrong)
Click to expand...
Click to collapse
Close the console by pressing Alt+F7. (If you have trouble exiting the console, post below with your Phoenix OS version and architecture. Then, try pressing Ctrl+Alt+F7)
Phoenix OS might crash and restart. Using the File Manager, go to the Download folder. Navigate to su>common> and install Superuser.apk
Launch SuperSU app from the app drawer. Press Continue, then select Normal to update the binary normally. Exit out of the app after the update is successful.
Launch Security app from the app drawer. Click AutoRun.
Toggle SuperSU to enable it so that it can automatically run when other apps request Superuser access. Exit out of the app.
History:
Added notes for common errors people were having
Added another keystroke to exit console (Ctrl+Alt+F7)
Added screenshots. Removed unnecessary steps. Fixed grammar mistakes.
These instructions were posted in the Phoenix OS Discord Server by ikkun. Thanks to Chainfire for SuperSU.
Instructions ported from tutorial Installing SuperSU on Remix OS 2.0
Attached zip file in case their website is down.

Thanks, it works

jamarita said:
Thanks, it works
Click to expand...
Click to collapse
Thank you for the confirmation! What device do you have and what GPU does it come with?

Does not work on hp 655 32 bit

lomax84 said:
Does not work on hp 655 32 bit
Click to expand...
Click to collapse
First of all, what kind of a computer is an "hp 655"? Second, can you provide more details to what exactly doesn't work? What step are you failing at?

Working fine for me on PhoenixOS 2.2.1. My computer is a HP Spectre x360.

ariadnejro said:
Working fine for me on PhoenixOS 2.2.1. My computer is a HP Spectre x360.
Click to expand...
Click to collapse
Awesome, thanks for letting us know!

The method here is which I use to make a partition of demarage for another os, the method is simple and it erases nothing in the PC videos Show a complete installation has 2m30 you can see the procedure. On the second video we little to see how installing Android 7.1 Phoenixos 2.2 new version the whole in two-tier and triple boot.
Phoenixos 1.1
Partition at 2mn30
https://youtu.be/NUCsSkbooqw
https://youtu.be/LWYU3eIp-Zk
Phoenixos 2.2
https://youtu.be/fYpLOBjnYxM
https://youtu.be/W0kz9LUXdiA
Here is I hope to have taken forward l.

This method still causing the Play Services sync problems with Gmail, etc. Any fix?

mic1000s said:
The method here is which I use to make a partition of demarage for another os, the method is simple and it erases nothing in the PC videos Show a complete installation has 2m30 you can see the procedure. On the second video we little to see how installing Android 7.1 Phoenixos 2.2 new version the whole in two-tier and triple boot.
Phoenixos 1.1
Partition at 2mn30
https://youtu.be/NUCsSkbooqw
https://youtu.be/LWYU3eIp-Zk
Phoenixos 2.2
https://youtu.be/fYpLOBjnYxM
https://youtu.be/W0kz9LUXdiA
Here is I hope to have taken forward l.
Click to expand...
Click to collapse
I'm sorry, it's kind of hard to understand what you're trying to say, but I'm assuming this is a guide on how to set up a triple-boot system.
jbardi said:
This method still causing the Play Services sync problems with Gmail, etc. Any fix?
Click to expand...
Click to collapse
This method only roots the system, it's not supposed to fix the sync problems with Gmail. The problem exists even before you root, so we need to search around for a solution. I would recommend asking in the Discord channel and someone might shed you some light on this issue.

It is exactly it, forgiveness if my English is not very clear. It is a method to install a dual boot or a triple boot in this particular case on a tablet Teclast x98 or on a mini PC Pipo X7 that have the same characteristics it does not solve at all the problems of synchronization of Google moreover I have no problem of synchronization on Phoenix os 2.2

mic1000s said:
It is exactly it, forgiveness if my English is not very clear. It is a method to install a dual boot or a triple boot in this particular case on a tablet Teclast x98 or on a mini PC Pipo X7 that have the same characteristics it does not solve at all the problems of synchronization of Google moreover I have no problem of synchronization on Phoenix os 2.2
Click to expand...
Click to collapse
Oh okay, thank you for the guide, I hope others find it useful. The other reply was to another user, not to you. Phoenix OS has a Gmail sync issue. So if you try to install and sign into the Gmail app, you will not be able to synchronize your mail. You actually do have a synchronization issue, it's just that you haven't experienced it yet because you haven't tried using the Gmail app.

meanhacker said:
I'm sorry, it's kind of hard to understand what you're trying to say, but I'm assuming this is a guide on how to set up a triple-boot system.
This method only roots the system, it's not supposed to fix the sync problems with Gmail. The problem exists even before you root, so we need to search around for a solution. I would recommend asking in the Discord channel and someone might shed you some light on this issue.
Click to expand...
Click to collapse
when I type the 2nd command, mv su su.orig it says no such file, what am i doing wrong ?
Im single OS booting and the files are as you laid out, but in the Download folder from within Phoenix OS

Seanie280672 said:
when I type the 2nd command, mv su su.orig it says no such file, what am i doing wrong ?
Im single OS booting and the files are as you laid out, but in the Download folder from within Phoenix OS
Click to expand...
Click to collapse
It sounds like you're not in the right folder. What Phoenix OS version do you have and what processor architecture? (32/64-bit) are you sure you're running the first command correctly (cd /system/xbin)? In the terminal, type in pwd and press enter. Post the output here. It should say /system/xbin. If not, use the command cd /system/xbin. If that doesn't work, type in ls -a and post the output here. Can you find su in that list of files? If so, all we're trying to do is make a backup of it before replacing it with the one we downloaded from Chainfire

meanhacker said:
It sounds like you're not in the right folder. What Phoenix OS version do you have and what processor architecture? (32/64-bit) are you sure you're running the first command correctly (cd /system/xbin)? In the terminal, type in pwd and press enter. Post the output here. It should say /system/xbin. If not, use the command cd /system/xbin. If that doesn't work, type in ls -a and post the output here. Can you find su in that list of files? If so, all we're trying to do is make a backup of it before replacing it with the one we downloaded from Chainfire
Click to expand...
Click to collapse
Im running the latest version x86-64bit ver: 2.21.247
Ive manually had a look in the system xbin folder and can see all of the above mentioned files and commands etc, mv, su.orig etc etc thats why I dont understand why its not working, so ill try your other commands now and let you know.
EDIT: running it on a packard bell easynote TE, Intel celeron N2820 CPU, 4gb DDR3l with a samsung evo 120gb ssd
EDIT 2: when im in system/bin and type pwd it gives the result /system/xbin, posted a couple of pictures below.

Seanie280672 said:
Im running the latest version x86-64bit ver: 2.21.247
Ive manually had a look in the system xbin folder and can see all of the above mentioned files and commands etc, mv, su.orig etc etc thats why I dont understand why its not working, so ill try your other commands now and let you know.
EDIT: running it on a packard bell easynote TE, Intel celeron N2820 CPU, 4gb DDR3l with a samsung evo 120gb ssd
EDIT 2: when im in system/bin and type pwd it gives the result /system/xbin, posted a couple of pictures below.
Click to expand...
Click to collapse
Great, thanks for the pictures. So it looks like you already made a backup of the su, which is now named su.orig. Proceed with the rest of the steps

meanhacker said:
Great, thanks for the pictures. So it looks like you already made a backup of the su, which is now named su.orig. Proceed with the rest of the steps
Click to expand...
Click to collapse
Thanks for all of your help, all the commands went in ok this time, however a little problem, ALT+F7 isnt working to close down terminal, so I have to force restart, then once its back up and running, continuing with the instructions to install super SU says not root found.

Seanie280672 said:
Thanks for all of your help, all the commands went in ok this time, however a little problem, ALT+F7 isnt working to close down terminal, so I have to force restart, then once its back up and running, continuing with the instructions to install super SU says not root found.
Click to expand...
Click to collapse
I don't remember off the top of my head, but try Ctrl+Alt+F7. Also, try other numbers for the F (Function) keys. If superuser doesn't work for you, go into the Security app and enable SuperUser for AutoRun.

meanhacker said:
I don't remember off the top of my head, but try Ctrl+Alt+F7. Also, try other numbers for the F (Function) keys. If superuser doesn't work for you, go into the Security app and enable SuperUser for AutoRun.
Click to expand...
Click to collapse
Thank youu very much, strangest thing happened, just reinstalled the whole OS and all the commands went in this time perfectly fine, the keys to get out of Terminal are indeed Ctrl+Alt+F7.
Managed to have a bit of a play and sort of get the latest version of showbox running, also installed it through Kodi where it appears to be working perfectly fine, going to stick with this OS for a while now, does everything that I need it for, without the crap sluggishness of Windows, looking out for any future updates.

Seanie280672 said:
Thank youu very much, strangest thing happened, just reinstalled the whole OS and all the commands went in this time perfectly fine, the keys to get out of Terminal are indeed Ctrl+Alt+F7.
Managed to have a bit of a play and sort of get the latest version of showbox running, also installed it through Kodi where it appears to be working perfectly fine, going to stick with this OS for a while now, does everything that I need it for, without the crap sluggishness of Windows, looking out for any future updates.
Click to expand...
Click to collapse
I'm glad you got it to work! I will update the OP with the new information. What made it work? Was it the fact that you could now escape the terminal or letting Superuser in AutoRun?

This tool is a part of ADK software, thread can be found here (For summary read Introduction part below). Links to download this program will be found at the end of this post. Usage info can be found in second thread.
Click to expand...
Click to collapse
{
"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"
}
Introduction
Deodexing ROM is not so simple task since the recent changes in Android 9 introducing .vdex files. Thanks to anestisb for his vdexExtractor, now deodexing android 9.0 is not quite a difficult task. But hey, let me tell you not all APK, JAR can be deodexed as OEMs god knows adds what's so ever classpath in their vdex, odex, etc. to prevent it from converting to classes.dex
The tool requires build.prop file & app, priv-app, framework folder of either system or vendor partition. Browse it, check if it's supported by the tool. Hit Play button that's it. It may not take much time deodexing your ROM. The tool just process files and deodex them for you, it can be easier if you use an kitchen with it i.e first unpack ROM or decode system.img then run this tool on it. Well I'll recommend you to use ADK kitchen as it's currently made for that
What is ADK?
Well if I've to say, ADK (Android Development Kit) is a complete Windows based GUI application which allows you to edit Android apk files, ROM zips, boot or recovery images, Android Firmware and also to create TWRP/CWM flashable recovery zips easily. It's like a complete Android Kitchen with lots of mods, patches, scripts, templates, rich text editor, etc. like an IDE. For more info visit official thread here.
Click to expand...
Click to collapse
[/QUOTE]
Features
Well here you go,,,
Supports Android 9 ROM.
Powerfull analyzing or ROM structure.
Logs all the process in tools\deodex.log and shows summary within tool.
Manually set tool dir through settings.
Click to expand...
Click to collapse
Changelog and Known Issues
Changelog as per release 1.0.0.0 (19th January 2019)
*Initial Release
Click to expand...
Click to collapse
Downloads & Instructions
To use these tool you must have ADK to be installed. So read steps below (noob friendly) in order to get it. If you want to know what is ADK read Introduction Part above. Also this tool supports deodexing from Android 5.0 to 9.0.
Step 1: Install ADK
Grab a latest release of the software from above link (should be greater than 1.0.4.6).
Step 2: Extract the ZIP and install setup.exe as we normally do.
Do not install the software in C:\Program Files or Program Files (x86) folder.
Step 3: Launch ADK from desktop shortcut, check & download updates if available for ADK.
Step 4: Now open the Deodex Tool.
The tool can be opened from Tools > Deodex Tool or create a ROM Project in ADK then select Project > Deodex Project.
Step 5: Read Usage Instructions below.
Click to expand...
Click to collapse

Using the Program
Standard way
Once you've successfully installed and updated ADK to the latest version. Click on Tools > Deodex Tool option. A window will pop up as shown in first post.
Now click on browse button. The three dot button and select a folder containing apps, priv-apps, frameworks folder & build.prop file. The tool will load all the details.
Now click on the Play button to start the deodexing, it will not take much time (as shown below).
In above image Green text showing number 18 is the success rate, Orange showing 0 is warning messages & Red showing number 21 is Error i.e the number of failed to deodex files.
Logs along with the exception will be generated in tools\debug.log file. A summary will be shown within the output in the tool.
It will notify you once the task is Finished.
Click to expand...
Click to collapse
Using ADK
First we are going to create a ROM project. Not only this will allow us to deodex ROM but also to add more mods and tweaks to ROM.
So let's start ADK, then click File > New > New project a window will pop-up from there select ROM/Update.zip. Give your project a name and browse for the ROM zip file from below three dot button (as shown below).
In above image, 360OS_LP is my project name and C:\Users\Dell\Documents\Roms\360_OS_VF1.zip is the location of ROM zip.
Now click create button to start the project creation. The process will take time according to your ROM structure. Once done you will see something like below.
Now directly click on Project > Deodex Project then simply hit Play button as we do. Done...!
Also you to load updater-script from your ROM, you can click Project > Load updater-script. See Project tab or read the current Getting started Page to know what cool things you can do to your ROM project.
Click to expand...
Click to collapse

[email protected] said:
Using the Program
Click to expand...
Click to collapse
Hi, thanks for the tool.
one question , can it be used to deodex an apk with (odex,vdex) files and then recompile it as single apk file ?
in fact i want to port an apk from an odex stock Rom to custom rom
EDIT:
mh this tool seems to powerful to convert a single App lool

rodolphe06 said:
Hi, thanks for the tool.
one question , can it be used to deodex an apk with (odex,vdex) files and then recompile it as single apk file ?
in fact i want to port an apk from an odex stock Rom to custom rom
EDIT:
mh this tool seems to powerful to convert a single App lool
Click to expand...
Click to collapse
Single APK option is not added yet, I will add an update to it as quick as I can!

nice job... how to know deodex rom or not ?

zynonimoux said:
nice job... how to know deodex rom or not ?
Click to expand...
Click to collapse
That's a good question! This feature is not implemented yet. I will implement it soon.
If you manually want to check if ROM is deodexed or not! Go to folders like app, priv-app. Check if there exist files like .odex or .vdex. If they exist then it means ROM is not deodexed.

@[email protected]
Can't deodex this ROM:
http://download.h2os.com/OnePlus 3T...8_OTA_060_all_1903310222_b76c39af1e5d4362.zip
for build.prop see attached file.
For more information about calling real-time (JIT) debugging instead of this dialog box,
See end of this message.
Exception text **************
System.IndexOutOfRangeException: The index exceeds the array boundary. In ADK_context.
Classes.Tasks.GetPropValue (String ID, String filename)
In DeodexTool.Form1.loadinfo (Boolean first)
In DeodexTool.Form1.button1_Click (Object sender, EventArgs e)
In System.Windows.Forms.Control.OnClick (EventArgs e)
In System.Windows.Forms.Button.OnClick (EventArgs e)
In System.Windows.Forms.Button.OnMouseUp (MouseEventArgs mevent)
In System.Windows.Forms.Control.WmMouseUp (Message& m, MouseButtons button, Int32 clicks)
In System.Windows.Forms.Control.WndProc (Message& m)
In System.Windows.Forms.ButtonBase.WndProc (Message& m)
In System.Windows.Forms.Button.WndProc (Message& m)
In System.Windows.Forms.Control.ControlNativeWindow.OnMessage (Message& m)
In System.Windows.Forms.Control.ControlNativeWindow.WndProc (Message& m)
In System.Windows.Forms.NativeWindow.Callback (IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
Loaded Assemblies **************
Mscorlib
Assembly version: 4.0.0.0
Win32 version: 4.7.3362.0 built By:net472rel1last_c
Basic code: file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll
----------------------------------------
Deodex
Assembly version: 0.5.0.0
Win32 version: 0.5.0.0
Basic code: file:///D:/ADK/deodex.exe
----------------------------------------
System.Windows.Forms
Assembly version: 4.0.0.0
Win32 version: 4.7.3324.0 built By:net472rel1last_c
Basic code: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System
Assembly version: 4.0.0.0
Win32 version: 4.7.3362.0 built By:net472rel1last_c
Basic code: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Drawing
Assembly version: 4.0.0.0
Win32 version: 4.7.3190.0 built By:net472rel1last_c
Basic code: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
---------------------------------------- ADK.
FastColoredTextBox
Assembly version: 2.16.23.0
Win32 version: 2.16.23.0
Basic code: file:///D:/ADK/ADK.FastColoredTextBox.DLL
----------------------------------------
System.Configuration
Assembly version: 4.0.0.0
Win32 version: 4.7.3324.0 built By:net472rel1last_c
Basic code: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------
System.Core
Assembly version: 4.0.0.0
Win32 version: 4.7.3362.0 built By:net472rel1last_c
Basic code: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll
----------------------------------------
System.Xml
Assembly version: 4.0.0.0
Win32 version: 4.7.3190.0 built By:net472rel1last_c
Basic code: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
---------------------------------------- ADK.
Progress
Assembly version: 1.0.0.0
Win32 version: 1.0.0.0
Basic code: file:///D:/ADK/ADK.Progress.DLL
----------------------------------------
Mscorlib.resources
Assembly version: 4.0.0.0
Win32 version: 4.7.3190.0 built By:net472rel1last_c
Basic code: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/mscorlib.resources/v4.0_4.0.0.0_zh-Hans_b77a5c561934e089/mscorlib.resources.dll
----------------------------------------
System.Windows.Forms.resources
Assembly version: 4.0.0.0
Win32 version: 4.7.3190.0 built By:net472rel1last_c
Basic code: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms.resources/v4.0_4.0.0.0_zh-Hans_b77a5c561934e089/System.Windows.Forms.resources.dll
----------------------------------------
JIT Debugging **************
To enable real-time (JIT) debugging,
Must be set in the system.windows.forms section of the application or computer's. config file (machine.config)
JitDebugging value.
You must also enable the application when compiling the
Debugging.
For example:
<configuration>
<system.windows.forms jitdebugging=""true""></system.windows.forms>
</configuration>
When JIT debugging is enabled, any unhandled exceptions
Will be sent to the JIT debugger registered on this computer, Instead of processing from this dialog box.

qqzwc said:
@[email protected]
Can't deodex this ROM:
http://download.h2os.com/OnePlus 3T...8_OTA_060_all_1903310222_b76c39af1e5d4362.zip
for build.prop see attached file.
For more information about calling real-time (JIT) debugging instead of this dialog box,
See end of this message.
Exception text **************
System.IndexOutOfRangeException: The index exceeds the array boundary. In ADK_context.
Classes.Tasks.GetPropValue (String ID, String filename)
In DeodexTool.Form1.loadinfo (Boolean first)
In DeodexTool.Form1.button1_Click (Object sender, EventArgs e)
In System.Windows.Forms.Control.OnClick (EventArgs e)
In System.Windows.Forms.Button.OnClick (EventArgs e)
In System.Windows.Forms.Button.OnMouseUp (MouseEventArgs mevent)
In System.Windows.Forms.Control.WmMouseUp (Message& m, MouseButtons button, Int32 clicks)
In System.Windows.Forms.Control.WndProc (Message& m)
In System.Windows.Forms.ButtonBase.WndProc (Message& m)
In System.Windows.Forms.Button.WndProc (Message& m)
In System.Windows.Forms.Control.ControlNativeWindow.OnMessage (Message& m)
In System.Windows.Forms.Control.ControlNativeWindow.WndProc (Message& m)
In System.Windows.Forms.NativeWindow.Callback (IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
Loaded Assemblies **************
Mscorlib
Assembly version: 4.0.0.0
Win32 version: 4.7.3362.0 built By:net472rel1last_c
Basic code: file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll
----------------------------------------
Deodex
Assembly version: 0.5.0.0
Win32 version: 0.5.0.0
Basic code: file:///D:/ADK/deodex.exe
----------------------------------------
System.Windows.Forms
Assembly version: 4.0.0.0
Win32 version: 4.7.3324.0 built By:net472rel1last_c
Basic code: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System
Assembly version: 4.0.0.0
Win32 version: 4.7.3362.0 built By:net472rel1last_c
Basic code: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Drawing
Assembly version: 4.0.0.0
Win32 version: 4.7.3190.0 built By:net472rel1last_c
Basic code: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
---------------------------------------- ADK.
FastColoredTextBox
Assembly version: 2.16.23.0
Win32 version: 2.16.23.0
Basic code: file:///D:/ADK/ADK.FastColoredTextBox.DLL
----------------------------------------
System.Configuration
Assembly version: 4.0.0.0
Win32 version: 4.7.3324.0 built By:net472rel1last_c
Basic code: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------
System.Core
Assembly version: 4.0.0.0
Win32 version: 4.7.3362.0 built By:net472rel1last_c
Basic code: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll
----------------------------------------
System.Xml
Assembly version: 4.0.0.0
Win32 version: 4.7.3190.0 built By:net472rel1last_c
Basic code: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
---------------------------------------- ADK.
Progress
Assembly version: 1.0.0.0
Win32 version: 1.0.0.0
Basic code: file:///D:/ADK/ADK.Progress.DLL
----------------------------------------
Mscorlib.resources
Assembly version: 4.0.0.0
Win32 version: 4.7.3190.0 built By:net472rel1last_c
Basic code: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/mscorlib.resources/v4.0_4.0.0.0_zh-Hans_b77a5c561934e089/mscorlib.resources.dll
----------------------------------------
System.Windows.Forms.resources
Assembly version: 4.0.0.0
Win32 version: 4.7.3190.0 built By:net472rel1last_c
Basic code: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms.resources/v4.0_4.0.0.0_zh-Hans_b77a5c561934e089/System.Windows.Forms.resources.dll
----------------------------------------
JIT Debugging **************
To enable real-time (JIT) debugging,
Must be set in the system.windows.forms section of the application or computer's. config file (machine.config)
JitDebugging value.
You must also enable the application when compiling the
Debugging.
For example:
<configuration>
<system.windows.forms jitdebugging=""true""></system.windows.forms>
</configuration>
When JIT debugging is enabled, any unhandled exceptions
Will be sent to the JIT debugger registered on this computer, Instead of processing from this dialog box.
Click to expand...
Click to collapse
I got how to solve this problem.
1. your tool expect [ro.build.version.release=9.0.0] but actually it is [ro.build.version.release=9 and ro.rom.version=9.0]
2. your tool expect [ro.product.name=OnePlus3T] but actually it is [ro.product.device=OnePlus3T]
So this tool crashes.
But it still cann not deodex the provided rom for me, you can have a try:
http://download.h2os.com/OnePlus 3T...8_OTA_060_all_1903310222_b76c39af1e5d4362.zip

This tool does not deodex boot.oat?

lieuliau said:
This tool does not deodex boot.oat?
Click to expand...
Click to collapse
I tried deodexing it for some ROMs for 2 of my devices using latest oat2dex, but it does not work and sometimes failed to boot (Roms were above 8.1), so I thought of removing deodexing of boot.oat from release! But in future I will add an option for user to choose if they want to deodex them at their own risk.

Does not support deodexing up to 9.0

Hello
[email protected] said:
Introduction
Click to expand...
Click to collapse
Features
Changelog and Known Issues
Downloads & Instructions[/QUOTE]
Great tool !!! very beautiful! on the roms android 8 everything ok, perfect !!! while on the rom android 9 I have an error in unzipping the file "system.new.dat.br ... so with another program I converted it to:
"system.new.dat". Now your tool executes the Unzip of "filesystem.new.dat", but when I run the deodex tool it gives me an error in all the apks. (Error: or: "Could not deodex!")

ankh3 said:
Great tool !!! very beautiful! on the roms android 8 everything ok, perfect !!! while on the rom android 9 I have an error in unzipping the file "system.new.dat.br ... so with another program I converted it to:
"system.new.dat". Now your tool executes the Unzip of "filesystem.new.dat", but when I run the deodex tool it gives me an error in all the apks. (Error: or: "Could not deodex!")
Click to expand...
Click to collapse
Do this:
1. Yesterday i release a new version of ADK so update it from website https://androdevkit.github.io by downloading latest release and perform an overwrite install.
2. Now create a ROM project in ADK (i fixed the issue you are facing).
3. Once you have your system folder in Solution, select Tools > Deodex Tool.
4. Now try deodexing it. (Note: when you are trying to Deodex framework folder some of the apk and binaries will remain odexed due to incompatibility)

[email protected] said:
Do this:
1. Yesterday i release a new version of ADK so update it from website by downloading latest release and perform an overwrite install.
2. Now create a ROM project in ADK (i fixed the issue you are facing).
3. Once you have your system folder in Solution, select Tools > Deodex Tool.
4. Now try deodexing it. (Note: when you are trying to Deodex framework folder some of the apk and binaries will remain odexed due to incompatibility)
Click to expand...
Click to collapse
Thanks! I tried your procedure but during the deodex I have the same error ...

ankh3 said:
Thanks! I tried your procedure but during the deodex I have the same error ...
Click to expand...
Click to collapse
Send your ROM zip so that i can check it!

[email protected] said:
Send your ROM zip so that i can check it!
Click to expand...
Click to collapse
OK thank you very much!
I tried with 3 Rom with android 9, same error. try this:https://drive.google.com/open?id=1DqY6zTScWU4F1TpDd4FcoaiEDs1dkSFI

ankh3 said:
OK thank you very much!
I tried with 3 Rom with android 9, same error. try this:https://drive.google.com/open?id=1DqY6zTScWU4F1TpDd4FcoaiEDs1dkSFI
Click to expand...
Click to collapse
Hello this could take a while! Due to busy work schedule.

[email protected] said:
Hello this could take a while! Due to busy work schedule.
Click to expand...
Click to collapse
Do you get the same error?
Did I do something wrong in the process?

ankh3 said:
Do you get the same error?
Did I do something wrong in the process?
Click to expand...
Click to collapse
Check PM

Hi! and thank you for this app.
I've same error with LineageOS for Sony xz1 compact (this Rom: lineage-16.0-20191118-UNOFFICIAL-RC6-lilac, By Modpunk on XDA. Sorry, I can't to post external links because I'm new user).
"Error: Could not deodex!" in all the apks.
Have you got a solution?
Thanks!