Develop Bugs

[STOCK][C650X][4.3] Update to 10.4.B.0.569 [Root & XZDualRecovery][DE-/ODEX]

{
"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"
}
Requirements:
Flashtool by @Androxyde
XZDualRecovery 2.6 RELEASE or newer.
Current FW version: 10.3.1.A.2.67, maybe others too, let me know!
Special features:
SuperSU integrated in system, FULL root, no reboots when remounting /system RW!
XZDualRecovery 2.7.43 BETA (CWM & PhilZ Touch & TWRP) pre-installed;
Tailored FTF to minimize the chance of accidental system wiping!
No need to clear caches!
For both locked and unlocked bootloaders!
The C6503 ROM is based on the FTF provided by @Androxyde in this thread. Thanks dude
In the following guide I suggest you use an external SDCard but that's just good practice, you can use your internal storage or even an USB OTG storage device in TWRP if you like to install, that's no problem!... If you are modding and the likes, best is to have an external sdcard, just for safeties sake.
How to update to 10.4.B.0.569:
Files:
For C6502: Download C6502.flashable.10.4.B.0.569.zip (Bittorrent: 807MB) and C6502_10.4.B.0.569_Stripped.ftf (18MB)
For C6503: Download C6503.flashable.10.4.B.0.569.zip (Bittorrent: 778MB), SuperSU_fix.zip (1.1Mb) and C6503_10.4.B.0.569_Stripped.ftf (18MB)
For C6506: Download C6506.flashable.10.4.B.0.569.zip (Bittorrent: 778MB) and C6506_10.4.B.0.569_Stripped.ftf (18MB)
Save them somewhere you remember;
Put 'C650X.flashable.10.4.B.0.569.zip' on (the external) SDcard1;
Put 'C650X_10.4.B.0.569_Stripped.ftf' inside the Flashtool/firmwares folder;
Create a backup of your phone in CWM or TWRP and don't forget to backup the contents of 'SDCard0';
Flash 'C650X.flashable.10.4.B.0.569.zip' in TWRP (after flashing the ROM also flash 'SuperSU_fix.zip', needed only when using the C6503 package)
do not reboot but go back to the main menu, then go to reboot->power off;
Flash everything in 'C650X_10.4.B.0.569_Stripped.ftf';
Reboot to system without clearing (dalvik-/)cache.
The first boot will be considerably slower and after a long wait at the boot animation you will see Android optimizing the apps on your phone.
As I do not have a ZL, @Bird40 tested this release prior to creating the thread, so I know it works fine
Enjoy! :laugh:
DE-ODEX your ROM! (Read the NOTE below this guide before flashing!)
AFAIK you can use this deodex package on the C6502 and C6506, as the base apps and framework are the same.
Make sure you have the flashable ROM installed before you do this.
Download C6503_deodex.10.4.B.0.569.zip (Bittorrent: 383MB), save it somewhere you remember;
Put 'C6503_deodex.10.4.B.0.569.zip' on (the external) SDcard1;
Create a backup of your phone in CWM or TWRP and don't forget to backup the contents of 'SDCard0';
Flash 'C6503_deodex.10.4.B.0.569.zip' in recovery, do not reboot but go back to the main menu;
Clear dalvik-cache ONLY;
Reboot to system.
The first boot after flashing this you will see Android optimizing the apps on your phone, this might take a while... but should be just fine
NOTE: There are some issues with the deodexed ROM, it sometimes causes a FC, specifically if you go to keyboard & language settings through the settings app. I'm not able to find why it does this but my guess is that it's a bug in the Sony ROM that surfaces with deodexing it... There is a work around for this one though: Open any keyboard driven app (text editing/entering box), tap '12!?' and then tap the tools button on the right of the space bar. This will take you to the app to modify your keyboard settings.
Known XZDualRecovery Issues:
Busybox Updater/Installer: If you have XZDualRecovery installed, un-install any Busybox updating app/tool as most if not all of them will install a version of busybox which does not support the lzma compression applets XZDualRecovery depends on. The version installed together with XZDualRecovery is very stable and I have yet to hear anyone complain about it's stability.
How to report errors:
Please, before shouting out "It doesn't work!!1!" or "I lost root!" or even "My phone reboots when remounting /system RW!!" try the following:
Restore a /system ONLY using any means you are familiar with so you can try again.
Root it using [Z][ROOT] DooMLoRD Easy Rooting Toolkit.
Install XZDualRecovery and then try to update again using TWRP. This time you can skip the FTF as it has already done it's job.
If it still fails something from there on: LOGS!!.
NOTE: The important ones can be found in /cache/recovery and in /tmp/XZDualRecovery, pack them up and send them to me.
Thank you

thanks!!! testing

It works perfect! Thanks a lot

will it work on c6502 .569 fw?

[NUT] said:
As I do not have a ZL, @Bird40 tested this release prior to creating the thread, so I know it works fine
Click to expand...
Click to collapse
All is well.
Thank you.

So we can't install busybox on this?

LiLTrippz said:
So we can't install busybox on this?
Click to expand...
Click to collapse
Whenever I try to open root explorer it doesn't work, as if I don't have root perms, it's like superuser is denying everything but in root checker it says i have root access???

LiLTrippz said:
Whenever I try to open root explorer it doesn't work, as if I don't have root perms, it's like superuser is denying everything but in root checker it says i have root access???
Click to expand...
Click to collapse
ok same problem and i cant boot into recovery as well
root checker : this device does not have proper root access

demonicjas said:
ok same problem and i cant boot into recovery as well
root checker : this device does not have proper root access
Click to expand...
Click to collapse
Well I just fixed it, my problem was fixed by going into supersu and i just made the settings to always grant.

LiLTrippz said:
Well I just fixed it, my problem was fixed by going into supersu and i just made the settings to always grant.
Click to expand...
Click to collapse
i have to do everything all over again ..
back to .244 and headed from there now
edit : done .
all good

If you run into the superuser 'grant all' issue, look up the app in the settings and clear all its cache and user settings.
That should fix that problem.

i have a problem.....
when i give root acces to a app (like root explorer or unnistaller root) before the update, i have no problems with root access after the update.... but if i do this after update, i mean, install a root app after update, i have not root access for that app, even if i have the supersu app and recovery.
any idea about how to resolve it????
MY PRINCIPAL PROBLEMS IS WITH XPOSED

There is one problem, Xposed Framework doesn work I installed the last version but still when I reboot phone, it still shows me framework is not installed yet and tells me I need to reboot again, but still it doesn work.
Anyone got this issue?

someone is having trouble with ADB after updating with this method?
Enviado de meu C6503 usando Tapatalk

felipeacydc said:
i have a problem.....
when i give root acces to a app (like root explorer or unnistaller root) before the update, i have no problems with root access after the update.... but if i do this after update, i mean, install a root app after update, i have not root access for that app, even if i have the supersu app and recovery.
any idea about how to resolve it????
MY PRINCIPAL PROBLEMS IS WITH XPOSED
Click to expand...
Click to collapse
batrian said:
There is one problem, Xposed Framework doesn work I installed the last version but still when I reboot phone, it still shows me framework is not installed yet and tells me I need to reboot again, but still it doesn work.
Anyone got this issue?
Click to expand...
Click to collapse
xposed issue is known .. Rovo89 is already working on it

any other root app have the same problem..... it doesnt apear the messege requesting root access.

[NUT] said:
If you run into the superuser 'grant all' issue, look up the app in the settings and clear all its cache and user settings.
That should fix that problem.
Click to expand...
Click to collapse
felipeacydc said:
any other root app have the same problem..... it doesnt apear the messege requesting root access.
Click to expand...
Click to collapse
.....

fixed.... my bad!
i just grant root access without request, just to all, and it works perfect.

I'm trying to find a solution to this... Luckily we have a working recovery to restore it any way we can

bug from busybox!!!
tnx for rom

Busybox fails to install

Accidentally installed the wrong busy box apk but cleared data and uninstalled then i tried installing the correct version of stericson busybox free and I'm greeted by this message
"There was a problem opening a shell with root access. this is either cause by supersu or by a device that is improperly rooted..."
It then goes on to say i should change permissions in supersu then reinstall. Of course I can't do this because our supersu does not have a settings menu.
I'm looking for help. Is there a way to resolve this over adb and change the su settings? Or can i reinstall supersu?--would that give me the popup i need to grant permissions (if that is in fact the issue...)
I'm not certain i can just run towel root again and reinstall supersu. I have the latest prerooted firmware installed.
BTW--I'm curious as to what happened. thinking the wrong busy box app is still causing issues because i did the same thing on my other fire tv and could easily install busy box again. Thanks.

You should be able to open the settingsmenu (or the apps list) of SuperSU in the FireTV system settings menu -> installed apps tab. Just start the SuperSU app for that.

Calibaan said:
You should be able to open the settingsmenu (or the apps list) of SuperSU in the FireTV system settings menu -> installed apps tab. Just start the SuperSU app for that.
Click to expand...
Click to collapse
Unless I'm misunderstanding, you can't do that with our supersu (think its just the way rbox designed it that supersu can't be opened). Go to applications and try it. I assume your setup is the same as mine--cwm & and prerooted firmware.
I'm thinking I'll just uninstall/reinstall supersu, but not even sure that will resolve the busybox issue.

No, I have not a rooted aTV (those for the german market were never deliverered with a rootable firmware, hope this changes with stagefright vulnaribilty). I assumed you´re running the regular SuperSU from Chainfire which does acts as a Superuser access management tool:
{
"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"
}
It should be possible to call this superuser app from the apps tab within the system menu like every other sideloaded app. Of course when you´re running another supersu app this probably won´t work.

Calibaan said:
No, I have not a rooted aTV (those for the german market were never deliverered with a rootable firmware, hope this changes with stagefright vulnaribilty). I assumed you´re running the regular SuperSU from Chainfire which does acts as a Superuser access management tool:
It should be possible to call this superuser app from the apps tab within the system menu like every other sideloaded app. Of course when you´re running another supersu app this probably won´t work.
Click to expand...
Click to collapse
Thanks. I have read in other thread people talking about using superuser app to access those settings we can't get with supersu on AFTV. That was a long time ago and don't think there was much feedback on how it worked.
I messed things up more than I thought. None of my root apps are working (ROM manager, titanium backup, samba file sharing, etc.
Wondering if just reinstalling the ROM.zip will fix everything? Only thing about that is it doesn't ask to regrant su for my installed apps normally. Not sure if it'll be different because root isn't functioning properly...

So maybe someone can confirm this? If I wipe factory reset in cwm will supersu reinstall and reset su settings? (Actually pretty sure it will) But really rather not do that because I'm forward thinking enough to install titanium backup but not smart enough to backup apps and data (always put it off then forgot) Now of course I can't use titanium.
So if that's my only option I'll do it but hoping there's a simpler way like flashing supersu zip in recovery. AND if that's an option should I first remove supersu apk in system/app?

I've had issues with the Busybox installer, too. It claims you can begin installing right away, but it's a good idea to wait until it finishes its scan to do the install.

Sizzlechest said:
I've had issues with the Busybox installer, too. It claims you can begin installing right away, but it's a good idea to wait until it finishes its scan to do the install.
Click to expand...
Click to collapse
Well I didn't actually want busybox installer. I wanted busybox free by stericson. I'm not even sure if the installer is by stericson. So did you try to run that installer program again and let it complete? Or were you actually talking about busybox free which is what I've always used on AFTV (its the recomended version we all are probably using). But not paying attention I installed the wrong apk. Now none of my root apps work which I don't understand. Busybox having trouble makes sense but pretty sure I've run other root apps without busybox in the past.
Its looking like I need to wipe it but not in a huge hurry. The AFTV functions OK without root so I'll hang around for a better solution.

KLit75 said:
Well I didn't actually want busybox installer. I wanted busybox free by stericson. I'm not even sure if the installer is by stericson. So did you try to run that installer program again and let it complete? Or were you actually talking about busybox free which is what I've always used on AFTV (its the recomended version we all are probably using). But not paying attention I installed the wrong apk. Now none of my root apps work which I don't understand. Busybox having trouble makes sense but pretty sure I've run other root apps without busybox in the past.
Its looking like I need to wipe it but not in a huge hurry. The AFTV functions OK without root so I'll hang around for a better solution.
Click to expand...
Click to collapse
This is what I was referring to: https://play.google.com/store/apps/details?id=stericson.busybox&hl=en
Can you connect to your Fire TV using adb and do a "su" command to see if you get root? Did you fully unlock your bootloader?

Sizzlechest said:
This is what I was referring to: https://play.google.com/store/apps/details?id=stericson.busybox&hl=en
Can you connect to your Fire TV using adb and do a "su" command to see if you get root? Did you fully unlock your bootloader?
Click to expand...
Click to collapse
That's the one that won't install. Yes. I can connect adb, reboot recovery and bootloader fully unlocked. I can't access everything in es file explorer because the root explorer option won't work without su permissions. But adb shell will get the # sign.

[TOOL] Install Xposed on 5.0.X

What is it?
A simple tool for installing Xposed on rooted N1s running 5.0.1 or 5.0.2 - any build ID will work. Tested on Win 7 and 8.1.
This package will install Xposed 3.0-alpha2. You can replace the apk inside the folder with your own version, but alpha2 works great for me.
This is not my work, the source is in Russian here: h__ps://vk.com/page-80817152_50267799
Sorry about the links, not allowed to post them or attach files yet.
Download
h__ps://vk.com/away.php?to=https%3A%2F%2Fapp.box.com%2Fs%2Frivif2p7qqa6ak9gv07sq600b917depn
Instructions
1 - Download and unzip the folder somewhere
2 - Plug in N1 and check you have the correct drivers (get Intel's drivers here: h__ps://software.intel.com/en-us/android/articles/intel-usb-driver-for-android-devices). If youre unable to connect to the device, disable MTP in the storage section of the settings.
3 - In the root of the unzipped folder run InstallXposedInstaller.bat - grant the shell root and press any key to close once its done
3 - In the same forlder, run InstallXposedFramework.bat and wait for it to reboot
Thats it, you now have working Xposed on your tablet. Most AOSP-compatible modules will work. Tested GravityBox and Amplify only as theyre all i need.

I have no idea how to root it, please guild me

How to install Xposed Framework on the Huawei GX8/G8.

I was curious to know to how xposed framework can be installed on the Huawei GX8 so I went through different sites to find at least an easy way to do that but honestly i didn't find any easy steps. They are more or less complicated depending on the individual attempting the procedure. ok
It is advised to take complete backup before deodexing so that you can replace the deodexed apps with the odexed backups in case you face some Apps crashing. Deodexing is important in order to make xposed framework install successfully and use some modules as well.
Warning: You attempt this procedure at your own risk, bare in mind that I will not be held responsible if you brick your device for attempting this procedure.
Prerequisites:
Rooted device.
Fully functional TWRP recovery or any other recovery with File manager support.
Backup all your data & apps.
Download this APP for deodexing:https://docs.google.com/uc?id=0BwSanb5zBfFiaHN5MGV2ZnFqcVU&export=download
Deodexing the ROM:
Step 1: Extract the BatchAPKTool to your preferred location.
Step 2: Open BatchAPKTool.exe. Set Language to English when prompted.
Step 3: The tool will now ask you to chose task.
Step 4: Type 83 and set smali version to smali-2.1.2.jar by entering 2. Now type 84 and set Android API level to 21 (Android 5.0), 22 (Android 5.1.1) or 23 (Android 6.0). This value must match with the firmware you have currently installed on your device.
Step 5: Now connect your device to PC. Make sure USB Debugging Mode is enabled and necessary Huawei Drivers are installed.
Step 6: In BatchAPKTool window, type 13 and then enter 4. This will pull all files from /system/app , /system/framework , /system/priv-app from your device. This may take some time so wait patiently. (You might also do it manually using Root Explorer)
Step 7: Once it’s done press Enter to return to main BatchAPKTool Menu.
Step 8: We’ll now deodex the apps. Enter 01 in the tool. It will now ask you for your ARM version. Enter “arm” and press Enter. Wait for the process to be completed.
Step 9: In the directory where you have extracted BatchAPKTool, you’ll find three folders named _priv-app, _app and _framework. Remove the underscore from the folder names so that they are now priv-app, app and framework respectively.
Step 10: Create a new SYSTEM FOLDER and name it DEODEXED SYSTEM and copy those three folders inside it. Now copy the System folder to your SD card or Internal Memory.
Replacing Odexed Apps with Deodexed Apps:
1: Boot your device into recovery and backup System partition
2: Using the built in file manager in recovery, delete the app, framework and priv-app folders from your system partition.
VERY IMPORTANT: Make sure that in twrp in the "Mount" section the "Only mount system read-only" is unchecked in order to copy the files to system.
3: Now copy the app, framework and priv-app folders from system folder (which we copied to SD card or Internal) and paste them to the SYSTEM partition i.e. /system/
4: When done, reboot your device. First boot will be extremely long. Might take 20-30 minutes so be patient.
ALTERNATE METHOD:
NOTE: It may not be possible to copy files from one folder to another in recovery mode, so this is what i did...
1. Create a NEW FOLDER in your internal memory and name it ORIGINAL SYSTEM.
2. Copy PRIV-APP, APP and FRAMEWORK from the ORIGINAL SYSTEM FOLDER and paste it in the ORIGINAL SYSTEM FOLDER in the memory of your device.
3. Now copy the THREE files in the DEODEXED SYSTEM FOLDER to the ORIGINAL SYSTEM FOLDER in the root of your device.
4. Your device will reboot immediately the files are copied. The boot may take 20-30 minutes so be PATIENT..
Installing Xposed Framework.
1. Go to the official thread and download the latest version(xposed-v86-sdk23-arm64) for Marshmallow
2. Download the apk and the uninstaller arm zip just in case anything goes sideways you can flash the uninstaller to unistall xposed framework.
3. Install the apk file and flash the v80-sdk23-arm zip in recovery. Again device might take 20-30 minutes to boot.
4. For Android 6.0:
Open build.prop
add these lines ro.config.hwtheme=0
ro.config.hw_theme=0
For Android 5.0-5.1.1:
Open local.prop (in system/emui/base/prop/local.prop)
add these lines ro.config.hwtheme=0
ro.config.hw_theme=0
The commands is to ACTIVATE the framework.
Thanks to mfbcool for the guide and Rockchip for Batch tool.

OK I have successfully installed xposed installer and some xposed modules, however some of the modules seem not to be working.

Partially working modules....
N-ify
Not working.......
Gravitybox
Lockscreen Mods
Qs tiles per row
xnotifications
Working.......
YouTube Adaway
Greenify
Maxlock
Flat Style Bar Indicators
Jit Screen On

Has anyone tried this method and had some success .....?

Ok. I'm now on cyanogenmod so I will be releasing xposed modules that are working perfectly on the rom. Stay tuned.
Its been a while. Yeah, have been busy with school and work.
Ok, here's a list of xposed modules working flawlessly with cyanogenmod.....
Gravitybox MM
Flat Style Bar Indicators
Android N-ify
Blurred System Ui MM
ifont
Youtube adaway
Maxlock
USB for Marshmallow
Adblock
Greenify
The list will be updated with time. If I helped you in any way, don't forget to hit the like button... Thanks
Sent from my HUAWEI GX8 using XDA Labs

Good joob BRO

bro i have LAG after install xposed its work 100% but there is some lag in apps

Ahmed-Iraq said:
bro i have LAG after install xposed its work 100% but there is some lag in apps
Click to expand...
Click to collapse
Sorry for the late reply....which apps are you experiencing lags with???
Sent from my Nexus 6 using Tapatalk

Can't get Viper4Android working on my M8 running GPE 6.0 ROM

I'm struggling with installing Viper4Android on my device.
I tried installing using either the apk from the original thread (http://forum.xda-developers.com/showthread.php?t=2191223). It install successfully but I keep getting a driver install prompt, after installing the driver and rebooting.
Things I already tried without success:
- Installed BusyBox with BusyBox app (https://play.google.com/store/apps/details?id=ru.meefik.busybox)
- Setting the SELinux mode to permissive using SELinuxModeChanger app (http://forum.xda-developers.com/showthread.php?t=2524485)
- Setting the SELinux mode to permissive using flashable permissive.zip
- Installing the apk from the Material design Viper4Android thread (http://forum.xda-developers.com/android/software/app-material-viper4android-2-3-4-0u-t3190352)
- Flashing the .zip from the same thread.
I'm currently running Android 6.0 GPE, flashable version (http://forum.xda-developers.com/showthread.php?t=2708589)
Root access is granted through SuperSU, so no problem on that matter I suppose.

2. With a File Manager(Solid Explorer Recommended) locate " /system/etc/htc_audio_effects.conf" and rename "htc_audio_effects.conf" to "htc_audio_effects.bak" (Renaming this file will make it inactive but while keeping it backed up just in case this doesn't work for you, however it appears this file is not needed as no negative effects occur, and this should fix V4A.)
3. Reboot Device.
And if this doesn't work I thin you should grant storage permission for V4A under settings. I hope I can help you!

Duccibreeezy said:
2. With a File Manager(Solid Explorer Recommended) locate " /system/etc/htc_audio_effects.conf" and rename "htc_audio_effects.conf" to "htc_audio_effects.bak" (Renaming this file will make it inactive but while keeping it backed up just in case this doesn't work for you, however it appears this file is not needed as no negative effects occur, and this should fix V4A.)
3. Reboot Device.
And if this doesn't work I thin you should grant storage permission for V4A under settings. I hope I can help you!
Click to expand...
Click to collapse
Thanks mate!! This worked for me.
Thanks for ur help