Related
{
"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"
}
Note: This application is no longer being updated and is only recommended for use on Froyo builds.
What is VISIONary?
VISIONary (so named because it was originally an application designed for the T-Mobile G2 / HTC Vision) is an application you install on your device that allows you to Temproot or optionally Permroot your device, using the 'rageagainstthecage' exploit.
How do I use it?
It's pretty simple really. The options appear as follows:
Temproot on boot - use this to automatically Temproot on each boot (I suggest Temprooting manually first to confirm all is well before enabling this)
Run visionary.sh after root - this allows you to run a script (as root) after rooting. The script file is /data/local/visionary.sh
Set system r/w after root - this allows you to leave the /system partition read/write after root
Temproot now - root temporarily (the root wil be lost after reboot)
Attempt permroot now - attempt to apply a permanent root (please read the safety information below before doing this!)
Unroot now - this will unroot your device
Safety information!
You use VISIONary at your own risk! Although we test it as much as possible, we are unable to guarantee that weird things won't happen.
As a rule, the 'Temproot' option of VISIONary should be completely safe. It installs an application (Superuser) in the conventional way and then sets up a 'ramdisk' for the other parts, which is wiped on boot. As such, no changes are made to the system partition of your device, hence it is considered a 'safe options'.
Permroot on the other hand is inherently more risky. Permroot does make changes to the /system partition of your device. Technically speaking the only change that is made is the installation of a small file to /system/xbin, but any system partition change comes with risks. If you try to permroot, be aware that you might get into a situation where your device will not boot. For this reason, we recommend you have a 'safety net'.
In general, the best 'safety net' for going ahead and doing a Permroot is ensuring that you have a copy of the stock ROM to reinstall should things go wrong. This should be an original update EXE or zip from your device manufacturer / provider which matches the software version currently installed on your device. Bear in mind that flashing older versions is often not possible, so if your device has been updated over-the-air, an update may not yet be available in this form. Hence, you may not be able to find a 'safety net' and attempting to Permroot would be inherently risky. For HTC devices at least, one option would be to Temproot, edit the MISC partition to revert the 'mainver' to an older version, thereby allowing you to flash an update older than the currently installed version should things go wrong. That option is currently outside the scope of this post, although I will provide details on how to accomplish this in another post.
Got your safety net? Aware of the risks? The download is below.
Download
r14 - (see changelog below for details) - [url="http://android.modaco.com/content/software/320350/19-nov-r14-visionary-one-click-root/]DOWNLOAD[/url]
The download is in APK format (if it is downloaded with a 'zip' extension simply rename). Copy to your device and click to install (or run 'adb install -r com.modaco.visionaryplus.r14.apk' if you have the SDK installed).
NOTE: USB DEBUGGING MUST BE ENABLED FOR VISIONARY TO WORK!
And finally
Details on how to donate should you wish to do so are in download topic at MoDaCo.
Enjoy!
P
thanks for you guys work
works perfectly! thanks
Does nothing for me, just sits there saying rooting device, flashes every few seconds
Sent from my T-Mobile G2 using XDA App
Question Answered..
Thank you P, my reboot question has been answered... just click and proceed. (To Be Tested)
It feels so good to see you on the scene.. It's been a while.. Since the N1
v8pwrdz28 said:
Does nothing for me, just sits there saying rooting device, flashes every few seconds
Sent from my T-Mobile G2 using XDA App
Click to expand...
Click to collapse
Same here
v8pwrdz28 said:
Does nothing for me, just sits there saying rooting device, flashes every few seconds
Sent from my T-Mobile G2 using XDA App
Click to expand...
Click to collapse
Reboot and try again...
P
paulobrien said:
Reboot and try again...
P
Click to expand...
Click to collapse
How long should the program run?
I have no experience whatsoever in developing or rooting on Android, so excuse me if this is a stupid question. When you say that if we want something to happen every time we finish rooting at bootup, to put it in /data/local/visionary.sh, what exactly does that mean? How does one go about doing this?
when i run this it just keeps saying rooting device with spinning wheel at top then it reboots
Not Working
Just getting the spinning wheel and flashing with no progress. Even tried to reboot and start over with no results
Thank you for making my life easier.
Does this app require you to do the "one-time" first step of the temp root process before you can use it?
Like others have said, this doesnt work for me. Just flashes rooting please wait and nothing happens.
Hey thanks it worked .. At first it kept running and nothing happened, so i rebooted the phone and it worked in the first try.
LogicHell said:
Does this app require you to do the "one-time" first step of the temp root process before you can use it?
Click to expand...
Click to collapse
No...
P
What should happen...
Boot device
Click VISIONary icon
Phase 1 runs
Logo disappears briefly as app reloads
Phase 2 runs
App disappears and root is complete
If this doesn't happen, I suggest rebooting and trying again.
P
Does it use the old 'root' script (copy everything to /system/bin and /system/app) or the new method? The old one expires eventually when linux drops the cache, the new one stays forever (until reboot). (Also, putting superuser on /data/app means it remembers it's permissions and grants across reboot, instead of losing it every time.)
The updated script is here:
Disconn3ct said:
FYI I altered the script to survive cache flushes and such. If you use this instead of the old 'root' script (and put everything in /data/local/bin instead of tmp) it will make the bare mininum number of changes to /system and those changes will last until you reboot (instead of flushing out over time).
Click to expand...
Click to collapse
Auto Root
I downloaded Startup Manager from the Market and set VISIONary to auto load on each bootup and so as of right now it auto loads with each restart. Very handy until it auto loads on itself. Just a thought.
Disconn3ct said:
Does it use the old 'root' script (copy everything to /system/bin and /system/app) or the new method? The old one expires eventually when linux drops the cache, the new one stays forever (until reboot). (Also, putting superuser on /data/app means it remembers it's permissions and grants across reboot, instead of losing it every time.)
The updated script is here:
Click to expand...
Click to collapse
Good call on putting the Superuser APK on /system/app! re: the 'old' or 'new' way, i'm doing it the old fashioned way (didn't know there was another way, heh)!
If you can point me to it, i'll change it for r2.
P
{
"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
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:
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.
Hi, so trying to get viper4andriod to work on my 5x, i've rooted (switched from MDA89E to MDB08I using factory .img), downloaded SELinux and set to permissive but i'm unable to download the drivers for viper it says it downloaded them but once it reboots the drivers are not there? tried installing viper via google play and with twrp using a zip file but no luck. also tried setting permissions via es root explorer (not sure how useful that is) but again no luck. i am new to the nexus previous phone was an S3 and also not very experienced.
i would appreciate any advice or suggestions
cheers
Have you tried downloading and installing Busybox from the Play Store? Sometimes the cause of this
Quinny899 said:
Have you tried downloading and installing Busybox from the Play Store? Sometimes the cause of this
Click to expand...
Click to collapse
@Quinny899 yeah i have busybox installed. should i uninstall it?
bump
When you installed with twrp did it install it as a priv-app or a regular apk? On the nexus 5 it needed to be int he priv-app folder to work.
@racing_md yep installed via zip in priv-app folder permissions set to 0755 and apk permissions set to 0644 (as seen on previous threads) as stated in first post i switched MDA89E to MDB08I and im not sure if that's affecting anything phone has been working smoothly only issue is a message in twrp "E: find_File: Error opening '/sys/class/backlight'. viper4android states that its installed drivers but requests driver install at every reboot and drivers don't show?
also viper4android folder containing DCC and kernel not showing when connected to my computer? not sure if that's an issue to?
Got around to rooting my 5X tonight, and got v4a working. Here's what I did:
Install v4a APK as normal from the zip
Install this version of busybox (it's the only one that I could find that installed and showed the applets installed afterwards)
Install v4a driver & reboot
Using a file manager or otherwise, delete or move "audio_effects.conf" out of /system/vendor/etc
Reboot
Disable MusicFX
Should work now
sorted got it working cheers
Quinny899 said:
Got around to rooting my 5X tonight, and got v4a working. Here's what I did:
Install v4a APK as normal from the zip
Install this version of busybox (it's the only one that I could find that installed and showed the applets installed afterwards)
Install v4a driver & reboot
Using a file manager or otherwise, delete or move "audio_effects.conf" out of /system/vendor/etc
Reboot
Disable MusicFX
Should work now
Click to expand...
Click to collapse
so there doesnt have to be an altered audio-effects.conf file put in place?
get my phone tomorrow and viper4android is one of the single reasons i root phones.
Have yal found a headphone volume boost method as well? I usually add viper and then apply a little bit of a volume boost as well.
@joho5
No custom file, just delete the other one.
I don't use a boost beyond v4a, so I can't help there
Did you have to change SE Linux to permissive for it to work? Also, could I ask if someone could please post the default Music Fx apk? It seems to have disappeared now and I originally lost eq settings in Google play music after trying to get v4a to work and I want to try getting it back to stock without wiping to test the difference.
Sent from my Nexus 5X using Tapatalk
Where do we disable the musicfx? I've been trying to find it but no luck so far.
Sent from my Nexus 6P using Tapatalk
I had to change SE Linux to permissive before running the V4A app for the first time - where it installs the driver. I never found any sign of the Music FX app so I wasn't able to disable it but V4A is working perfectly anyway.
Are you on stock or custom kernel? I'm on stock and have SELinux set to permissive but the driver wont install. I'm thinking I may need to use a custom kernel
Sent from my Nexus 6P using Tapatalk
whipstitch said:
I had to change SE Linux to permissive before running the V4A app for the first time - where it installs the driver. I never found any sign of the Music FX app so I wasn't able to disable it but V4A is working perfectly anyway.
Click to expand...
Click to collapse
I use power amp. It has the option to disable music fx
{
"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"
}
Sent from my SM-N900T using Tapatalk
Should be able to disable musicFx from the settings -> Apps -> then in the top right corner click the 3 dots and select show system - > scroll down and musicfx should be there now.
I'm running stock, unencrypted (modified boot.img)
Quinny899 said:
Got around to rooting my 5X tonight, and got v4a working.
Should work now
Click to expand...
Click to collapse
You the man Quinny!
I found the instructions and lack of links a bit confusing, so this is exactly what I did in order to get V4A working.
1. I downloaded busybox and went through the install process using this version.. https://play.google.com/store/apps/details?id=stericson.busybox&hl=en
2. Reboot
3. I flashed the LolliViper.zip from this link in TWRP. http://forum.xda-developers.com/google-nexus-5/themes-apps/discussion-viper4android-t2543796
4. I attempted to install the driver but it crashed.
5. Reboot
6. Attempted to install the driver, it hangs on the screen, but leave it and it will say that it installed.
7. Reboot.
8. Use a root file explorer, such as ES Explorer with the root explorer setting checked, to move "audio_effects.conf" out of /system/vendor/etc
9. Reboot and it will work.
Note, when using this zip, I did not have to do anything with SELinux or put it in permissive mode. Also, I did not do anything with MusicFX. I think this zip might disable it automatically.
Hope this helps!
I had similar issues, fixed by using the busybox listed in post 7 instead of the Stericson version.