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

[Q] Bloatware that is safe to remove?

Which packages did you guys remove?
I am happy that I could remove Firefly with Titanium Backup.
The app started randomly, in my pocket (I presume the camera button got pressed against My pocket), and I never really used it anyway.
I would like to know what does Whisperlink and if it is safe to remove.

arth_ur said:
Which packages did you guys remove?
I am happy that I could remove Firefly with Titanium Backup.
The app started randomly, in my pocket (I presume the camera button got pressed against My pocket), and I never really used it anyway.
I would like to know what does Whisperlink and if it is safe to remove.
Click to expand...
Click to collapse
Personally, I believe Firefly is a nifty little app that doesn't affect the phone in any way to actually consider removing it. But, well, to each his choice, right?!
Anyway, Whisperlink is an app that syncs your Kindle books info - purchases, reading progress, highlights 'n notes - across other amazon devices.

Amazon Appstore

The single issue is that it often starts up in my pocket and drains my battery.

[deleted]
NEW version here - http://forum.xda-developers.com/fire-phone/general/complete-app-list-replace-remove-t3132008

Bingo Bronson said:
FireOS 4.6.1 (KK 4.4.4)
Things I have removed so far: ........
to free up system space.
Used 'SD Maid' to scan for leftover "Libs" and other obsolete files.
Click to expand...
Click to collapse
And so after all these have been removed, how much free system space do you have, and do you think it is making an observable difference in terms of performance?

Bingo Bronson said:
FireOS 4.6.1 (KK 4.4.4)
Things I have removed so far:
REMOVED
Apps used (for now):
F-Droid Repo: AdAway, AFWall+, Amaze File Manager, ApkTrack, Autostarts, Calculator, Camera, Kernel Adiutor, Kitchen Timer, MuPDF, Sound Recorder, Swiftnotes,
VA: BusyBox, Buzz Launcher, Dolphin, KingUser, Multiling O Keyboard, MX Player, RAR, SD Maid, Titanium Backup, WhatsApp, Wifi Analyzer, WiFi File Transfer Pro
I removed all the lockscreen scenes (including \system\etc\com.amazon.lock\files\lockscenes\ls_moon.vbl) and used a black 1x1 px jpg instead, Amazon stock lockscreen.
I deleted \system\euclid , \system\media\fremedia (bootanimation.zip & boot.wav as well) and \system\tts to free up system space.
Used 'SD Maid' to scan for leftover "Libs" and other obsolete files.
Click to expand...
Click to collapse
Very radical list but thanks for trying each app. I just wonder if you remove com.amazon.device.settings then how can you change any setting in your system ever?

@ O.a.T. The perfomance hasn't changed that much, feels just as fast as running it with disabled "dynamic perspective". I am just trying to get the system as lean as possible. I will encounter problems with the current configuration, no doubt, so I will update the list in the future. System partition: 733 MB used, ~ 1,38 GB free.
edit: Battery life benefits the most from these changes, of course, using apps like 'Kernel Adiutor' or 'Kernel Toolkit' have the biggest influence compared to disabling / removing apps and services. Installed 'Greenify' for a couple of minutes, tells me "no apps need to hibernate" (big surprise ^^).
@ najoor The system settings is called 'Settings' / 'Settings Storage' (AmazonSettings.apk, 99% sure it's the main settings app ^^). 'com.amazon.device.settings' is a different component, so even with this one being removed, access to the settings menu works as usual.

Anyone know to reinstall fresh firephone OS ?
I messed up something and want to reinstall it. But, the "factory reset" just reset setings and won't recover, or reinstall fresh FireOS.

stunvn said:
Anyone know to reinstall fresh firephone OS ?
I messed up something and want to reinstall it. But, the "factory reset" just reset setings and won't recover, or reinstall fresh FireOS.
Click to expand...
Click to collapse
You can find the latest FireOS ROM in one of the Topics here on XDA and then if you are rooted, I believe, you can use Flashify from the google play store to install.
Personally, I rooted, and created a nandroid and a titanium backup of my current setup and all the apps before I started tinkering with the OS.
Or maybe this ...
http://forum.xda-developers.com/fire-phone/general/how-to-update-fire-phone-to-fireos-4-6-t3085745
is even easier.

What O.a.T. said, or try this as an alternative gah, ninja'd and edit by O.a.T. nevermind
1. Download the *.bin file (FireOS 4.6.1)
UK - http://fire-phone-updates.s3.amazonaws.com/update-fire-phone-33.4.6.1_user_461013320.bin
GER - http://fire-phone-updates.s3.amazonaws.com/update-fire-phone-34.4.6.1_user_461013320.bin
US - http://fire-phone-updates.s3.amazonaws.com/update-fire-phone-35.4.6.1_user_461013820.bin
I strongly recommend using a download manager to speed up the download. Regular download with a browser is tedious.
2. Boot phone in recovery: PWR + VOL. UP (hold both buttons until recovery screen appears)
From the list, choose "Apply update from ADB"
3. adb sideload 'name_of_your_bin_file'
I recommend renaming the the downloaded file to "update.bin" so you can just type in cmd: adb sideload update.bin

Bingo Bronson said:
What O.a.T. said, or try this as an alternative gah, ninja'd and edit by O.a.T. nevermind
1. Download the *.bin file (FireOS 4.6.1)
UK - "fire-phone-updates.s3.amazonaws.com/update-fire-phone-33.4.6.1_user_461013320.bin"
GER - "fire-phone-updates.s3.amazonaws.com/update-fire-phone-34.4.6.1_user_461013320.bin"
US - "fire-phone-updates.s3.amazonaws.com/update-fire-phone-35.4.6.1_user_461013820.bin"
I can't post links yet, just copy the above mentioned file name of your choice, your browser will be able to download it.
2. Boot phone in recovery: PWR + VOL. UP
Choose "install update from ADB" (something like that...)
3. adb sideload "name_of_your_chosen bin_file"
I recommend renaming the the downloaded file to "update.bin" so can just type in cmd: adb sideload update.bin
Click to expand...
Click to collapse
I followed those steps and have trouble at step 3. Device not found. Do you know how to fix this?
I tried to run adb devices but nothing show up. It's weird. because, before that I still can see my device on the device list.

stunvn said:
Do you know how to fix this?
Click to expand...
Click to collapse
If you boot up your phone in recovery mode / ADB mode, you will need additional ADB device drivers for your Windows system.
The regular (Amazon / Kindle) USB driver that is used when you connect your phone to the PC won't work, it's simply not the same method. That's why your phone "disappears" as soon as you (re)boot into ADB.
Open your "device manager" (assuming, you're using Windows as your main OS) and check for your device with missing drivers.
{
"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"
}
Try this tool (& driver) http://forum.xda-developers.com/showthread.php?t=2588979
You can even use (old) "Google USB drivers", I successfully tested google drivers from 2010 on Win 7 x64 with this phone in ADB mode.
If everything worked as planned, it should look like this: next to your device name, it will say "sideload"

Thank you very much :fingers-crossed: :good::good::good::good::good:

TMobile GPad F 8.0 (V496) Info

For those that picked up a TMobile GPad F 8.0 recently, here's a good thread to ask questions until we either get a separate forum or get enough info to move over to the General.
Root
Kingroot works well following the instructions here: All you need for LG GPad 8.0 [LG v490] thread. Once rooted, replace it with SuperSu using this method.
It is best to use KingRoot 4.1 or earlier to root, replacing it as soon as possible. 4.5 is very difficult to uninstall, although you can purchase SuperSUMe on Google Play to attempt it.
OS
Stock OS is the only option at the moment. There is a system update available which fixes the stagefright bug. It can still be rooted.
Recovery
Thanks to @Rashed97 and @KAsp3rd a beta TWRP is available here. This is not a zip, so use Flashify, TWRP Manager or equivalent to flash zips. Hooking up a USB mouse also works well for in-recovery navigation.
Kernel
Similar to LG stock ROM on their phones, the kernel has some adjustable features accessible through Kernel Aduitor or Trickster.
Xposed
Xposed installs and runs well. G3TweakBox has the ability to adjust some extra settings.

ADB driver
I got one as part of the Father's Day promotion as I needed to upgrade my mobile internet hotspot. I would like to migrate from a Nexus 7 2013 and needed the ADB driver for restore using Helium. Has anyone come across a working ADB driver for this GPad?

I was able to root with Kingroot 4.1 and then replace Kinguser and su binaries to SuperSU using this method:
http://forum.xda-developers.com/showpost.php?p=60669196&postcount=1&nocache=1&z=4065499287098646
---------- Post added at 11:45 AM ---------- Previous post was at 11:39 AM ----------
These are the USB drivers I used . Got them from this thread: http://forum.xda-developers.com/lg-g3/general/guide-root-lg-firmwares-kitkat-lollipop-t3056951

nicknc said:
Anyone else had performance issues without rooting?
Click to expand...
Click to collapse
There are performance issues without root as well.

FYI I just unlocked this tablet. Doesn't give 4G LTE on AT&T though, only HSPDA+
To Unlock this model, access the Hidden Menu:
1) From Home screen,Touch the “ Contact”
2) Touch the “ Search Contact
3) You can see the “Keyboard” after Touch the “ Search Contact”
4) Touch the “＋ “ icon after Dialer 2945#*496#
5) Touch Network Lock, you only have 3 attempts to enter the correct Unlock Code which you can get from any online vendors.
6) Press Unlock

Rooted with Kingroot & replaced it with SuperSu using this script. No computer required just make sure you have Terminal Emulator installed!
Download the file attached and extract it
Put the mrw folder on the root of the sd card
Open Terminal Emulator and type:
Code:
su
grant terminal emulator root access
Next type:
Code:
sh /sdcard/mrw/root.sh
The script should then run and work it's magic. After it's completed SuperSU should open up and prompt you to update the binaries. Update the "Normal" way and reboot afterwards.
And that's it! :good:

Post 1000, hooray.
VRAM seems to be on by default and is eating up about 256K according to Kernel Aduitor. Disabling that helped performance some after I did a factory reset. The LTE radio is stronger than my G3, but that might just be a longer antenna.

the 'replace kingroot...' script didn't work for me. Anybody having issues with root not working after reboot? i have to re-root with kingroot every time. going to try the adb method now

sinshiva said:
the 'replace kingroot...' script didn't work for me. Anybody having issues with root not working after reboot? i have to re-root with kingroot every time. going to try the adb method now
Click to expand...
Click to collapse
Which KingRoot version did you use?

nicknc said:
Which KingRoot version did you use?
Click to expand...
Click to collapse
KingRoot-4.1.0.524.apk
[edit/]
I think they must have updated something on their end because now the same kingroot apk is working - root correctly persisting across reboots

You Are The Man {Works Like A Charm}
xoxo_xdagirl91 said:
Rooted with Kingroot & replaced it with SuperSu using this script. No computer required just make sure you have Terminal Emulator installed!
Download the file attached and extract it
Put the mrw folder on the root of the sd card
Open Terminal Emulator and type:
Code:
su
grant terminal emulator root access
Next type:
Code:
sh /sdcard/mrw/root.sh
The script should then run and work it's magic. After it's completed SuperSU should open up and prompt you to update the binaries. Update the "Normal" way and reboot afterwards.
And that's it! :good:
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"
}
I followed your instructions to the "T"! Your method for rooting with Kingsroot 4.1 English version, and replaced it with SuperSu
works like a charm! My suggestion to everybody, do everything in the internal storage area! Don't use your external SD Card using the above instructions! I'm making phone calls on this baby to via WiFi and LTE, sweet!

now just need to get roms
kinda makes me want to try and make my own.. I've never developed before. lol!

Which custom recovery we use?

Rican2008 said:
Which custom recovery we use?
Click to expand...
Click to collapse
Nothing out there yet that I've seen. It'll come-- the v500 has had TWRP for about 9 months now. This one has only been out a couple of weeks.

Rican2008 said:
Which custom recovery we use?
Click to expand...
Click to collapse
I got a CM recovery to build using the stock kernel source from LG, but I'm super hesitant to flash it, until I can verify the LG Updater software works for me. I don't have a Windows box ATM, so it'll take a bit more effort. I'll post here with results once I'm willing to flash.

Now that we have the root, has anyone tried to adjust the color of a panel? It is way too warm compared to my other devices (viewing my DSLR pics almost makes me think thr wirte balance was off).

northantara said:
I got a CM recovery to build using the stock kernel source from LG, but I'm super hesitant to flash it, until I can verify the LG Updater software works for me. I don't have a Windows box ATM, so it'll take a bit more effort. I'll post here with results once I'm willing to flash.
Click to expand...
Click to collapse
Well, I flashed it, and things went, err, poorly. I'm done trying. Turns out, it's not actually possible to recover from download mode with LGMobile Support Tool, at least until an update is made available online.

Thanks for trying. I assume the bootloader is locked on this too, meaning we will need to bump any flashable zips anyway.

The step to replace KingRoot with Supersu failed half way for me. Apparently there's a typo in the script >.< Now KingRoot thinks that the tablet is rooted even though it isn't... stuck with broken root...

That is not good news, if this baby has a locked boot loader I am taking it back. Left AT&T for locking the boot loaders of their devices.

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.

Install Xposed Framework to LG Spirit without recovery

This is method of installing Xposed Framework which is made by @rovo89 to use some tweaks without needing to modify system files (like SystemUI).
Original post was made in General Thread by @polfrank but I need to edit it with some new things which he is missing.
Code:
I'm in no way responsible for whatever happens to your device if things go wrong.
Your device is your responsibility, proceed with caution and only if you know what you're doing.
Apps and stuff which is needed to install Xposed Framework
* Root
* BusyBox - IMPORTANT, script don't work properly without BusyBox installed
* Terminal Emulator
* adb if you don't wanna to use Terminal Emulator - use this version of adb -> http://forum.xda-developers.com/showthread.php?p=48915118#post48915118
* Installer script - Updated to work with latest version of Xposed Framework zip files. It shows some minor problems which doesn't make installer not working. Translated from Spanish to English by @midzan21 aka myself.
* Xposed Framework zip file - IMPORTANT, download SDK21-ARM variant, not ARM64 or SDK22-ARM variant, because stock ROMs are compiled with 32-bit version, not 64-bit. Also SDK21 is for Lollipop 5.0.x and SDK22 is for Lollipop 5.1.x
* Xposed Installer apk - download latest version and install it
* Brain.apk - just in case, but still important
Installation process for Terminal Emulator:
1.) Put Xposed Framework zip, Xposed Installer apk and Installer script (extracted) on Internal memory of device (Internal SD Card, not your real SD card if you have it)
2.) Install BusyBox
3.) Open Terminal Emulator and enter this commands
3.1.) Gain Root Permissions after entering su command
Code:
su
sh /storage/emulated/legacy/installer
4.) Enter once 1 to continue installation
5.) When script finishes phone would automatically reboot (hint: added reboot command in latest version of script just for safety purposes)
6.) Install Xposed Installer apk
7.) Open Xposed Installer and check in Framework section check does it writes: Xposed framework version XX is active (XX is latest version)
8.) Install module which you want and after enabling it reboot phone
9.) Enjoy
Installation process for adb:
1.) Extract adb setup of provided adb
2.) Install BusyBox
3.) Go to adb folder
4.) Press Shift and Right Mouse Click and in context menu select Open command windows here
5.) Now copy Xposed zip file and installer file in adb folder
6.) Use this commands to do check if you Enabled Debugging in Developers options
Code:
adb devices
And after that you should see LG and some numbers with enabled right after that (this LG cripple is your Android Phone name for adb and fastboot)
7.) Copy files to internal SD card with this commands
Code:
adb push xposed-v80-sdk21-arm /sdcard/
adb push installer /sdcard/
Please note: always copy with latest vXX number Xposed zip
8.) Now it is easy stuff done, now it is time to do work which is hard part - doing commands to install Xposed
Commands are:
Code:
adb shell
su
mount -o remount, rw /system/
sh /storage/emulated/legacy/installer
9.) Enter once 1 to continue installation
10.) When script finishes phone would automatically reboot (hint: added reboot command in latest version of script just for safety purposes)
11.) Install Xposed Installer apk
12.) Open Xposed Installer and check in Framework section check does it writes: Xposed framework version XX is active (XX is latest version)
13.) Install module which you want and after enabling it reboot phone
14.) Enjoy
Problems, bugs and issues:
Currently none, added to script to remove LG QuickCover which make Force Close
Old bugs, problems and issues:
Weather FC (Fixed with never versions of Xposed Framework)
Tethering and networks in Settings FC (Fixed with never versions of Xposed Framework)
After every boot you have Android is upgrading screen (fixed with never versions of Xposed Framework)
To do list:
* Nothing at this point
Credits:
@rovo89 for Xposed Framework and Installer
@polfrank for original post in General Thread
Unknown person for creating original installer script

Changelog
Update #1 - 16.10.2015 @ 19:43
* Thread created
* Added link to this thread in General Thread for LG Spirit to @polfrank update thread post #1

There's no way to fix LG QuickCircle cover? because I use it and don't want to lose it

andrekeys1 said:
There's no way to fix LG QuickCircle cover? because I use it and don't want to lose it
Click to expand...
Click to collapse
There is no way to use QuickCircle cover because it is problematic with Xposed Framework for now. I tried before updating script with QC and it just got Force Close from booting up device.
Also I'm not sure would it work, but here is link to all LG V10 apps and there is QuickCircle app. Before testing make a a backup of stock apps just to be sure that it works and there is no problems.
https://mega.nz/#F!bpQGBbLQ!Q3eTeYxe5fIBLegkQjiI6A

Changelog
Update #2 - 7. 11. 2015 (0:12 @ CET)
* Updated installer script so it automatically remove /cache and /data/dalvik-cache (created back in end of October, tested and it works)
* Updated tutorial (shortened for few lines, but still it is way easier right now)
To-do list:
* Automatic installer without first confirmation and with automated reboot ( ETA: few days after this posting, need neighbours phone without Xposed to check it and test )
* Porting script to Android app ( early ETA: mid to end of December this year )

Is it possible to uninstall xposed?

Hallo. Whats the problem I have? i added files to internal /emulated/ directory. ES file manager said its internal SD Card. Maybe trouble is somewhere else?
{
"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"
}

xyster13 said:
Hallo. Whats the problem I have? i added files to internal /emulated/ directory. ES file manager said its internal SD Card. Maybe trouble is somewhere else?
View attachment 3539627
Click to expand...
Click to collapse
Missing BusyBox, need to install that first before doing anything.

midzan21 said:
Missing BusyBox, need to install that first before doing anything.
Click to expand...
Click to collapse
But its installed. I checked with BusyBox Checker ant it shows that its installed. Any thoughts?

xyster13 said:
But its installed. I checked with BusyBox Checker ant it shows that its installed. Any thoughts?
Click to expand...
Click to collapse
Are files in
/storage/emulated/0
because that folder is linked to
/sdcard
I have no clue why some File Managers says different for internal SD, that is info which I get while using original Root Explorer (purchased while back when it was on some discount with few other apps like Titanium Backup Pro and Nova Launcher Prime as I remember good enough)

midzan21 said:
Are files in
/storage/emulated/0
because that folder is linked to
/sdcard
I have no clue why some File Managers says different for internal SD, that is info which I get while using original Root Explorer (purchased while back when it was on some discount with few other apps like Titanium Backup Pro and Nova Launcher Prime as I remember good enough)
Click to expand...
Click to collapse
Ok I did it. ES File Explorer(free version doesnt show emuated/0 directory thats why files where in /sdcard. Also just to warn - Root Explorer doesnt work Copy/Move/Paste commands doesnt work on this device or at least on mine. Explorer from google play works fine and I moved those files with this program.
Thank You!

xyster13 said:
Ok I did it. ES File Explorer(free version doesnt show emuated/0 directory thats why files where in /sdcard. Also just to warn - Root Explorer doesnt work Copy/Move/Paste commands doesnt work on this device or at least on mine. Explorer from google play works fine and I moved those files with this program.
Thank You!
Click to expand...
Click to collapse
ES Fle Explorer was always free, you maybe mistaken ES for some other File Explorer which have free & paid options.
On mine device Root Explorer works fine. That Explorer app is just free version of this paid app Root Explorer (same dev is for both apps)

midzan21 said:
ES Fle Explorer was always free, you maybe mistaken ES for some other File Explorer which have free & paid options.
On mine device Root Explorer works fine. That Explorer app is just free version of this paid app Root Explorer (same dev is for both apps)
Click to expand...
Click to collapse
Oops yeah my mistake. I was confused a little by the program list and names on google play. You are right about ES File Explorer

@midzan21
I'm wondering why do you need to further improve your method? It works perfectly fine for me, without any issues. I'm just curious.

there is any way to get quickcirle install zip or smth?
I uninstalled xposed framework cuz i am not using it anymore and i want to get my qucikcirle back.

fliperpl said:
there is any way to get quickcirle install zip or smth?
I uninstalled xposed framework cuz i am not using it anymore and i want to get my qucikcirle back.
Click to expand...
Click to collapse
How did you uninstall it ?

BrosseLi said:
How did you uninstall it ?
Click to expand...
Click to collapse
i broke it by change default SDCARD write partition (with some xposed module :E) and its not working. I uninstalled it with xposed uninstaller flashed by flashfire

fliperpl said:
i broke it by change default SDCARD write partition (with some xposed module :E) and its not working. I uninstalled it with xposed uninstaller flashed by flashfire
Click to expand...
Click to collapse
Okey, and FlashFire proposed you to mount the partitions ( Read&Write ), did you tick it or no ? I
I didn't and the log says that he couldn't mount my SD

BrosseLi said:
Okey, and FlashFire proposed you to mount the partitions ( Read&Write ), did you tick it or no ? I
I didn't and the log says that he couldn't mount my SD
Click to expand...
Click to collapse
i did.

fliperpl said:
i did.
Click to expand...
Click to collapse
Thanks a last question: which uninstaller did you download ?
The arm ,arm64 or armx86 ?
EDIT: flashed the arm version, it worked well